Multiple logical CPUs on a single physical CPU, or hyperthreading (HT), is a relatively new concept introduced with Intel's Pentium 4 Xeon that lately has been getting a huge amount of support in the Linux kernel. Ingo Molnar started it off in late August 2002, with a patch to add HT-awareness to the scheduler. Many patches have followed since then, and hyperthreading has become quite the mainstream feature.

khttpd is finally going away. After a long and bitter struggle from the moment of its inclusion, the kernel-based web server is gone from 2.5 and will not be back. In spite of the tremendous controversy surrounding this feature, it was not the flame wars that eventually sealed its doom, but the fact that user-space Tux2 is much faster. There is even some talk of putting Tux2 into the kernel as a replacement for khttpd, though many folks object to this on the same grounds that they originally objected to khttpd. Some patent issues also are holding up such an idea, and it looks as though no one really wants to bother fighting it out.

Several new system calls found their way into the kernel in August and September 2002. Among them, clone_startup() on x86 boxes reduces the number of system calls required for thread creation to one. Glibc's fancy pthread code is one big user of this call. The only problem is that the name has not quite been nailed down yet. YMMV.

One cute little tidbit: the PC speaker in post-2.5.31 kernels may now be used as a microphone. This is new and weird. As Jos Hulzink put it on the linux-kernel mailing list, “2.5.32 will go into the history books as the kernel that implemented voice recognition for all AT class computers....”

The struggle for a new kernel configuration system is ongoing. With CML2 apparently out of the running, several new configuration systems have emerged. Among them, “kernel conf” may be the most likely to succeed. Roman Zippel has been working on it steadily and claims his code is nearly completely usable. The rumor is kernel conf is likely to go into the main 2.5 tree, but no official announcement has come out yet.

A new tool, called devlabel, has surfaced from Gary Lerhaupt. It allows consistent access to storage devices via dynamic symlinks, with support for hot plugging. Simply plug in your device, and a symlink appears that may be used to access the device. Unplug the device and the symlink goes away.

—Zack Brown

Scott McNealy dropped the first shoe at LinuxWorld Expo in August 2002. In his keynote address, Sun Microsystems' President and CEO said the company would be announcing a new Linux desktop at its SunNetwork conference in September. When the second shoe dropped at SunNetwork, it didn't appear to match the first. Rather than yet another Linux box, what the company announced was a desktop strategy meant to take advantage of the huge enterprise market for inexpensive and flexible no-name x86 PCs, and for cost savings in general.

The code name for the strategy is Mad Hatter. Here is how Curtis Sasaki, Sun's vice president of engineering, desktop solutions, explains it:

Target customers are cost-conscious companies with large populations of “transaction workers”. But rather than selling droneware for cubicle hives, Mad Hatter's angle is all about individual identity.

“Today CIOs want to know exactly what it costs per user to have e-mail, calendar and a directory account—and what it costs for security”, Sasaki says. What Sun wants is for the enterprise to populate itself with Linux PCs that are personalized at authentication by the user's Java Card, and there appears to be a demand for this. Sasaki says:

This brings us to a whole new classification and an acronym to go with it. “It's not a PC, it's an IdC—an identity computer”, Sasaki says. “Identity is a big deal. It's about getting access to your desktop no matter where you are, based on your credentials.”

Eric Norlin, an analyst at Digital ID World, provides some context:

Sun's intent also is to make a single identity work outside and between companies as well as inside the user's company. Sasaki explains how:

Why now? According to Sasaki, the Linux desktop software stack is finally complete:

Sun will be putting together the first prototypes at its iForce centers before the end of the year and expects the first IdCs to start shipping in the first quarter of 2003.

—Doc Searls

What we can buy today far exceeds what we need to keep up.

—Mike Prince, CIO at Burlington Coat Factory, in Fortune, explaining why he's asking for an IT budget cut after converting to Linux.

Innovation makes enemies of all those who prospered under the old regime, and only lukewarm support is forthcoming from those who would proser under the new. Their support is indifferent partly from fear and partly because they are generally incredulous, never really trusting new things unless they have tested them by experience.

—Nicolo Machiavelli

Microsoft has chosen to make the war against open source a religious one. In doing so it has just managed to highlight it further, meaning IT Directors who wouldn't have ever considered it are now thinking of moving over.

—Dan Kusnetsky, International Data Corp.

Typically people think about things such as BIND and Sendmail, which are very important; but there is a much more practical sense in which both free and open code helped spread the birth of the Internet. That's the decision made in architecting the browser that reveals source. The source is constantly available. People didn't learn HTML just by buying Tim (O'Reilly)'s books first. What they did was steal each other's web pages, made the tweaks they wanted and then bought Tim's books so they could figure out how to do it better the next time around.

—Lawrence Lessig

I say to you that the VCR is to the American film producer and the American public as the Boston strangler is to the woman home alone.

—Jack Valenti, before Congress, 1983

Basically, all the commercial people have their own agenda, and that's very healthy because you want to have these often-conflicting agendas to push the system into something that actually works for everybody.

—Linus Torvalds

If you know how the source code works, you are much more likely to be able to sort out your problems. You will be able to link the software with the OS better. You won't have to spend so much on maintenance; the costs will be lower. It would also cost a lot less to develop the software in-house and get it to work the way you want.

—Retail CIO