Slashdot Mirror
Kernel Pool Is Back For 2.6
Manuka writes: "Win Fabulous Prizes and the recognition of your peers! (well, OK, maybe not the latter). As it's become somewhat of a tradition, tummy.com is now taking bets for the release date of the next production Linux kernel. Congratulations to Bill Wendling who won the pool for 2.4." Hey waitaminute, I don't even have a Slashdot shirt, never mind a VA Polo -- where do you get these?! Of course, Linus has promised a shortening release cycle, so bet accordingly.
I don't think time_t even supports the year I'm thinking of.
- I don't care if they globalize against free speech. All my best free thoughts are done in my head.
Releasing less incremental updates makes it easier on users, developers and distributors, in that if they need a feature like, for example, a new VM, they can just blanketly tell users they need Linux 2.4. If the new VM was released for 2.2, you'd have to require people to have a 2.2.27 kernel or newer. That doesn't sound too difficult, but it soon becomes a major headache. `I have 2.2.26 and it doesn't work for me'. Remember, most current Linux users don't match the profile of most future Linux users.
/dev/dvd, despite the fact they have DVD support in their new 2.2.50, my app might fail if it was looking for /dev/dvd [which it should be].
As it is now, bleedign edge folk can get incremental updates via odd kernels.
A new release neatly bundles all those incremental changes. 2.4 is a known quantity. A minor release isn't, becuase nobody can afford to keep track of the incremental updates in each release. If a user needs DVD support for my game, I tell them to get 2.4. I could tell them to get a 2.2.50 if it had those features, but better to break everything in their distribution at one time rather than cause many small annoying issues. Eg, since their 2.2.7 distro didn't create
The standard file system shouldn't be dictated by the kernel at all. The current ext2isms in the kernel vfs code should be hunted down and eliminated, but not replaced by Reiserisms. Let the distros and users decide which fs they want to use; the kernel should be completely fs neutral.
There's no "we" in team, only "me"
I'm betting on two weeks after the next time it's featuredon the vaporware list.... ;-)
S.t.e.v.e.
Of course, Linus has promised a shortening release cycle, so bet accordingly.
Oh really? Is this like the time he said that in 1999 about 2.4? Not bashing or anything, I think Linus should release when he thinks it's ready, I'm just saying that you might want to bet on it (ha ha).
My other