Linux Kernel 2.2.26 -- 2.2 is not dead!
midianus writes "Marc-Christian Petersen released Linux Kernel version 2.2.26. The release includes several security fixes. After Alan Cox released the previous 2.2 kernel, 2.2.25 in March of 2003, he began a one year sabbatical to study for an MBA in August of the same year and handed over the Maintainership of 2.2 to Marc-Christian."
2.0.? is not dead either. Their 2.0.40 was released only two and a half weeks ago.
If someone fixes a bug in 2.4 or 2.6 that was also present in 2.2, it makes sense to fix it in 2.2 as well. That's one of the jobs of the 2.2 maintainer.
Actually, starting Debian Woody Netinst with bf24 gives you a 2.4 kernel. So, since it's an update to the DEFAULT kernel (linux, instead of bf24), it'll probably hit security.debian.org.
The organization of releases is a subjective matter, at the discretion of the maintainer.
Without specific context, the number of revisions is meaningless.
I use Debian and love it, but let's not be too misleading here. It took a couple weeks for Firefox to get into unstable, and kernel 2.6.0 was still the newest option even for a while after 2.6.2 had been released. Unstable is great, but it's not always up-to-date (it took a year for XFree86 4.3 to get in, although that's a whole other can of worms...).
It's hard to be religious when certain people are never incinerated by bolts of lightning.
If you need a more secured, more stable, even faster, better SMP support, IDE LBA48 support, LFS support, IPSec support, HTB support, IPVS support etc. enabled kernel with many more features and important fixes, please use my 2.2-secure tree.
You may find more informations about it at http://www.wolk-project.de.
2.2.26
- CAN-2004-0077: behave safely in case of do_munmap() failures in mremap(2)
- CAN-2003-0984:
/dev/rtc can leak parts of kernel memory to unprivileged users (2.4 backport) - CAN-2003-0244: hashing exploits in network stack (David S. Miller)
- update_atime() performance improvement (2.4 backport) (Solar Designer)
- ability to swapoff after a device file might have been re-created
- MAINTAINERS correction for Kernel 2.2 and 2.2 fixes (me)
- fixed some typos (Solar Designer, me)
Sorry, had to edit that a bit to get it past the lameness filter. Most (all?) of the other patches here came from Solar Designer.Mielipiteet omiani - Opinions personal, facts suspect.
Really, kernel releases in the Linux world are more related to how fast the kernel gets to the point of stability than anything else. If you look at the history of the 2.4 kernel, you see that there were a lot of early problems with areas like the memory manager which caused a lot of releases in an attempt to get the problems taken care of. 2.4 really didn't stabilize in most people's eyes until 2.4.15 or so. Plus, once a new stable kernel comes out, the old stable enters a sort of maintenance mode. Few, if any, new drivers, and almost entirely security and bug fixes.
Marxism is the opiate of dumbasses