This utility will go over your system and extract a lot of information, enough information that you should be able to rebuild the system almost exactly as it was. That's probably a little more detail than I'd be comfortable with putting on a web site, but great to print out and put in your system's notebook (your systems do have notebooks, right?). Requires: BASH and standard UNIX tools.
—David A. Bandel
Shortly after the kernel's Halloween feature-freeze, Guillaume Boissiere decided to put together some statistics on the incorporation of features into the 2.5 tree. He examined almost the entire history of the 2.5 development cycle, starting in early 2002. He created seven possible status categories for any given feature: planning, started, alpha, beta, ready for inclusion, pending inclusion and fully merged. His first progress chart (Figure 1) shows the percentage of features in each category. The second progress chart (Figure 2) shows the actual number of features in each category, changing over time. Without making any claim to complete accuracy, the graphs are interesting, if for no other reason than to observe how seriously most developers took the drive toward feature-freeze. Note also the hump of work done over the summer, followed by a complete end to new feature planning. That hump of activity corresponds roughly to the time when the decision was made to freeze by November.
To facilitate the movement from feature-freeze to actual 2.6 (or 3.0) release, the Open Source Development Lab (OSDL) donated labor and equipment to maintain a Bugzilla bug-tracking database for the Linux kernel at bugzilla.kernel.org. Support for this was initially strong among developers, but it tapered off a bit when big guns, like David S. Miller, found duplicate entries and frivolous reports made the system, at least in its original form, more trouble than it was worth. No one wanted to give up on it, however, and a concerted effort seems to be underway to bring the bug database to a usable state.
In more debugging news, Linus Torvalds indicated for the first time he might be willing to accept patches into the kernel to support a kernel-based debugger. Traditionally, Linus' stance has been that real programmers debug from source files. While not actually explaining the reason for his change of policy, he now seems to think that a kernel debugger running across a network would be a good feature to let into the kernel. Don't look for it in the next stable series, however, as he was careful to make this statement after the feature-freeze had passed.
A new read-only compressed filesystem, along the lines of cramFS, emerged in late October and targets the 2.4 kernel. SquashFS claims to be faster and to produce tighter compression than either zisoFS or cramFS. The author, Phillip Lougher, wanted to address some of the limitations of other compressed filesystems, particularly in the areas of maximum file size, maximum filesystem size and maximum block size.
And speaking of filesystems, does anyone remember xiaFS? In 1993 it was regarded, along with ext2fs, as a serious contender for world domination. In fact, the two filesystems leapt into public use within a few weeks of one another. For a while it even looked as though xiaFS had taken the lead. By 1994, however, it had essentially dropped off the map, and a few years later it was actually dropped from the official kernel tree. In 2000, Linus remarked that it would be fun to have it back. Finally, just after the Halloween freeze Carl-Daniel Hailfinger asked if this offer was still good. Linus said sure, and even offered to make an exception to the feature-freeze, if Carl could deliver the patches.
- diff -u: What's New in Kernel Development
- Divx# Watch The Other Woman Full HD Online Streaming Viooz
- Numerical Python
- Use Linux as a SAN Provider
- Why Python?
- NSA: Linux Journal is an "extremist forum" and its readers get flagged for extra surveillance
- Great Scott! It's Version 13!
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- RSS Feeds
- Tech Tip: Really Simple HTTP Server with Python