Slashdot Mirror
Future of 2.4 and 2.6 Kernels
Blair16 writes "According to this article on C|Net, not everybody is chomping at the bit for the new Linux 2.6.0 kernel. Marcelo Tosatti, the appointed deputy for the 2.4 kernel is not expecting to make any non-crucial additions to the popular kernel, saying that all new projects should be pumped into the new 2.6. This has upset some people who are not quite willing to move to so-called untested software. Some of their claims seem legitimate, but I wonder if all these people will really be left in the cold?"
From the linked email:
Having that mentioned, I pretend to: - Fix pending problems which might required more intrusive modifications during 2.4.24. New drivers will be accept during this period (for example, Cyclades PC300 driver, input userlevel driver support, or other sane driver which might come up). - From 2.4.25 on, fix only critical/security problems.
Heh, so that solves the issue of being a kernel maintainer with little time on your hands, only pretend to do stuff :)
From the story text:
. This has upset some people who are not quite willing to move to so-called untested software. Some of their claims seem legitimate, but I wonder if all these people will really be left in the cold
Seriously, are people expecting major changes and new features to be added to a kernel that is supposed to be the stable branch? Doesnt this stuff belong in 2.6? or hell, even 2.7? I for one wouldnt like my kernel to constantly have new and untested features when its supposed to be production capable!
I don't know, but shouldn't someone actually test it to become tested? This is the way Open Source works, everyone should help developing the software, even non-programmers, by testing, and I guess the kernel team won't release something for production until it is ready for.
The IT section color scheme sucks.
Hasn't this discussion been held before? Stable kernel remain just that - Stable.
New features always go in new releases. Since 2.6 is around the corner, any new feature need to go in 2.7 now. Big deal. Move along, nothing new or interesting to see here.
Of course people want new features AND stability.
Pretty funny.
If the "well tested" 2.4 kernel were to be adding new features, such new features might risk making it unstable, therefore the time-tested status it has would have to be restarted.
If 2.6 isn't "well tested" enough for your production servers, wait a while. The test of time will perform itself... of course, if you want the new features, you'll just have to take the plunge because somebody's gotta do the testing...
Marcello's position means that the 2.4.x will become much more solid than any Linux kernel has ever been. As new hardware is introduced, there will be pressure to accept drivers to support popular hardware. I expect that Marcello will accept drivers as necessary for 2.4.x to run on popular hardware -- after all, such new drivers impose minimal risk on users without such hardware. I welcome this development, but will keep on open mind as time prove its merit or lack thereof.
Their example is of people who are using XFS with a 2.4 kernel. These people are (according to CNet) "upset" because XFS won't get added to 2.4. Now just think about this for a second: they are using XFS with 2.4 right now! So obviously, they are not being prevented from doing what they want. The whole issue (which CNet is trying to make out as a big deal) is that these people wish they didn't have to perform an extra step (applying a third-party patch). I hardly think it's going to kill these people to keep on doing what they have been doing for a little while longer (i.e. until they decide that the 2.6 series is sufficiently tested that they're willing to trust it). No one is being "left in the cold".
Actually, to be fair to CNet, they're only mildly misrepresenting the situation. The major source of confusion and misrepresentation is (as usual) the slashdot summary.
This has upset some people who are not quite willing to move to so-called untested software. Some of their claims seem legitimate, but I wonder if all these people will really be left in the cold.
This is really not true, since almost ALL the features in the 2.6 branch are available as patches for the 2.4. The 2.4 branch has achieved a nice level of maturity and adding a lot of new stuff to it now makes no sense.
The people complaining should learn the magic of open source. They should realise that at any desirable time they can start mantaining their own tree with their desired features. Hell, starting a new tree is not even necessary since there is such a big variety of 2.4 trees around that the feature they want is most likely already beeing supported by someone else in one of them.
The big deal is the 2.4 kernel was receiving massive changes (i.e. completely new VM system) in the 2.4.1x range. It really took a while for 2.4 to become a reliable platform. People are scared of the same thing happening here.
Isn't the joy of the OSS model, that if this were truely a problem, a group of users (presumable corperations interested in the viability of thier 2.4 kernel) could get together to create and maintain a patch for the 2.4 kernel that would back port more then just the critical updates from 2.6? I thought that the whole point of having an open model was to allow everyone to mess with the code to make it fit their needs. I know there is always a fear of forking, and that someone will bring up the issue, but there are many patches some like the -ac patch even get posted on kernel.org.
There has alwasy been a gap between the needs of buisness for stable and realiable software and the desire of enthusiests for the latest and greatest. as Linux continues to gain share in diverse markets, I antisipate that the number of patches will likewize increase, making a kernel that can meet the needs of several different types of users.
JFMILLER
Strive to make your client happy, not necessarly give them what they ask for