“After 6 months of careful integration and testing, I’m happy to announce availability of Linux 2.4.35,” 2.4 maintainer Willy Tarreau announced on the lkml. This is the second stable 2.4 kernel released since Willy became the 2.4 kernel maintainer nearly a year ago in August of 2006. Source level changes can be viewed through the linux-2.4 gitweb interface.
2.4 branch is still used in servers, firewalls and routing machines.
Most of the changes are bug fixes and Willy announced that he’ll not accept back portings of new features for the latest hardware.
I think it’s a good policy. Just make it solid as a rock
Agreed.
So instead of a fork of the kernel mention in a article a couple of days ago, wouldn’t keeping the 2.4 produce the same affect? I don’t believe the kernel should be forked, when we got the 2.4 that is rock solid for servers, etc.
“””
So instead of a fork of the kernel mention in a article a couple of days ago, wouldn’t keeping the 2.4 produce the same affect?
“””
No. 2.6 represents a huge body of work intended to improve operation on desktops, servers, and embedded. Servers and embedded devices which are still using 2.4 are typically machines which were put into service or designed when 2.4 was not so ancient and dated.
As a friendly heads up, “effect” is the word you meant to use. When one thing “affects” another, it creates an “effect” upon that thing. A very common error.
Debian Sarge shipped by default with 2.4 and has been rock solid for me. I still have many servers running it.
Everyone claims that Debian is outdated and that they need the latest and greatest. I need stuff to keep working, day in and day out.
I do eventually change to newer technologies, but I tend to stay behind the leading edge and I have never regretted doing so. Security errata and support for newer hardware is one of the few good reasons to often move to newer distributions.
I don’t really follow the kernel tracking all that much but that gitweb interface is pretty slick. Usually I just go to http://www.kernel.org then click on the changelog to read any changes but gitweb has the patches and date in a nice pretty format. I guess I’m a simple person.
Yeah, that is pretty nice. Clean. We keep a single file full of release notes for our projects that everyone edits and refreshes on a per cycle basis. I don’t really like doing that. We should all use the commenting in CVS and just report on it to see what has been changing. Then again you get a lot of comments in CVS like “…” or “asdfsadf” or “fixed it.”
Looks like a good kernel for embedded systems or very old PCs. Slackware used to use 2.4 kernels, now it uses 2.6 ones, I think.
“””
Slackware used to use 2.4 kernels, now it uses 2.6 ones, I think.
“””
Yes. Slackware entered the 21st century 25 days ago with the release of the 2.6.21.5 kernel-based Slackware 12.0.
nice to see that some people still uses 2.4 kernels, and that some people still improve it.
On the end it’s good for us as customers, maybe my next DVD-Player runs the bug-fixed kernel? who knows…