Home > Developer, Linux/Unix, Operating Systems > Linux Kernel 2.6.27 Released, Linus offers some behind the scenes info too!

Linux Kernel 2.6.27 Released, Linus offers some behind the scenes info too!

October 11th, 2008 Leave a comment Go to comments

Linus just released Linux Kernel 2.6.27 to the stable tree after 9 release candidate releases. Some highlights include:

2.6.27 add a new filesystem (UBIFS) optimized for “pure” flash-based storage devices, the page-cache is now lockless, much improved Direct I/O scalability and performance, delayed allocation for ext4, multiqueue networking, an alternative hibernation implementation based on kexec/kdump, data integrity support in the block layer for devices that support it, a simple tracer called ftrace, a mmio tracer, sysprof support, extraction of all the in-kernel’s firmware to /lib/firmware, XEN support for saving/restorig VMs, improved video camera support, support for the Intel wireless 5000 series and RTL8187B network cards, a new ath9k driver for the Atheros AR5008 and AR9001 family of chipsets, more new drivers, improved support for others and many other improvements and fixes.

You can read more about the changes on Linux Kernel Newbies guide on Linux 2.6.27.

If you’ve been looking into the very heavily publicised and incredibly serious Intel Network adapter e1000 corruption bug then you’ll be glad to know that it seems that its fixed (which was initially put into 2.6.27 -rc9). If you grabbed any of the Ubuntu Intreprid Pre-releases then you may have been affected – though later the modules were black-listed.

Now that Linus has started blogging, he gives a unique glimpse into the release process and how it differs from that of his previous company Transmeta.

So I tagged the release five hours ago, and during the few days before that I had barely a score of commits to merge. But now that I have cut the release, my mailbox is starting to come alive with merge requests for the next version – with thousands of commits queuing up for merging in just a few hours, as opposed to the slow trickle in the days that went before.

This is all exactly as it should be, of course, but it still feels bass-ackwards, in that people always talk about the death-march to a release, and how you’re supposed to take a well-deserved vacation after the release.

For example, when I worked for Transmeta, the hardware people would basically take a month off after doing a tape-out. That seems somewhat natural just deserts. But when it comes to Linux development the “tape-out” of making a release acts the other way around. The calm was before, now comes the week or two of crazy merging.

Read more on his blog post about On Making Releases. One wonders when he actually takes any form of vacation to relax without carrying around a lappy.

{lang: 'en-GB'}
  1. No comments yet.
  1. No trackbacks yet.