Those who've moved to broadband connections and wireless links to each PC on their home or office network are unlikely to look back fondly on the days of 56K (or the not-so-snappy 300 baud of my first modem). Still, even if most Internet users really do have broadband, and (unless you've forsaken a landline telephone completely), dialup is a useful adjunct to even the spiffiest broadband access. And sometimes, it's the only access available. Most city dwellers don't face the distance limits of DSL (or even the geographic limitations of cable service), and cheapskate travelers know that free local calls are more common than hotels with free WiFi. However, wireless access and modems aren't the most common combination (especially when you're talking about laptops with a built-in modem port), and it's not fun being tied to whatever length of phone cord you have to hand. AlwaysOn Wireless's device called the WiFlyer (about $150) combines a wireless access point, a DHCP server, and a modem to make dealing with dialup a bit easier, and tosses in a few other features as well. The WiFlyer is a brilliant device, with some limitations; read on for my review.

c0dyd asks: "Lately, computer attacks have gained much popularity in the news; however, it is not often that we hear of new software, hardware or 'appliances' that combat malicious code attacks and data intrusions. Obviously, the need is present. I've searched thoroughly for network intrusion detection and prevention systems, but the choices and technologies seem somewhat limited or proprietary-- Snort appears an obvious open source solution for intrusion detection but many users many find it lacking in intrusion prevention capabilities. What do you, the experienced network admin, use for detecting intrusions on the network and how does your network react to those intrusions?"

Fraser Cain (Mark Mortimer) writes "Hacking sounds crass. It manifests images of short cuts, jobs poorly done and people most interested in just finishing, no matter what. In the computer industry, sometimes this perfectly portrays hackers. However, for an expert, a hack is the complete opposite. It's a beautiful, well thought resolution that uses minimal effort. Often only those in the know truly appreciate it. Robert and Barbara Thompson in their book, Astronomy Hacks compile tips and techniques for observing the night sky. Their methods seem simple, yet they include detail to show they are experts who are presenting hacks derived from years worth of knowledge." Read on for the rest of Mark's review.

Provataki writes "OSNews' Thom Holwerda posted the first in-depth review of the recently released Zeta 1.0. He goes over installation, impressions, usage, application and hardware support, BFS queries and concludes that yellowTAB's Zeta is the deserving future of BeOS; plus, it's the only one based on the original source code by Be, Inc."

Nuclear Elephant writes "With Verizon's release of the Motorola E815, an improved and EVDO-capable version of the former v710, many v710 enthusiasts have started hacking at it to see what it can do. Surprisingly, many of the hacks which previously did not work on the v710 (such as those from the failed OBEX Hacking Contest) now suddenly do work on the E815, and other hacks which did work on the v710 still work. Among new hacks include the ability to activate OBEX (Object Exchange) for transferring pictures and music to/from the handset via Bluetooth, activating the disabled DUN (Dialup Networking) profile which was previously available on its predecessor, and modding the web browser to allow using any homepage and proxy. One cool existing hack involves the ability to use an alternative PIX messaging gateway to send multimedia, made possible by the reverse engineering of the MMS protocol used. A complete list of modifications can be found here. An unofficial challenge to enable OPP (Object Push Profile) is underway with a prize of $500. Unlike the v710, the Motorola E815 was Bluetooth qualified for both OPP and OBEX."

An anonymous reader asks: "A couple years ago Joel Spolsky wrote an interesting critique of Eric S. Raymond's The Art of Unix Programming wherein Joel provides an interesting (as usual) discussion on the cultural differences between Windows and Unix programmers. As a *nix nerd in my fifth year managing mainframe developers, I need some insight into mainframe programmers. What are the differences between Windows, Unix, and mainframe programmers? What do we all need to know to get along in each other's worlds?"