Slashdot Mirror
Linux 2.6.0 Kernel Released
thenextpresident writes "It's here! Just updated on kernel.org, the Linux 2.6.0 kernel has finally arrived! We've been waiting a long time for this, and it had been rumored it was going to be released tonight. Well, it's here indeed. Happy downloading." There's also a changelog online for this long-awaited update.
If you put a .0 kernel on your cluster at work, expect to lose your grants and your job.
my sig's at the bottom of the page.
The Changelog is only the changes from 2.6.0-test11 to 2.6.0, which isn't very illuminating at all.
Did I say that preempt would be working like clockwork?
No, if you install this kernel on anything but a test box, you're stoopid...You should wait till the minor releases are at least a month or 2 apart before you EVEN consider upgrading to a 2.6 kernel...or better yet, wait for Fedora Core 2 in April...
No, not really...I didn't say "wait till 2.6.10" or some arbitrary number...but the longer time between updates implies more stability and less intrusive bugs...it happens with all software...many ppl haven't even upgraded to Solaris 9 yet...and 10 is due out soon...
Software has bugs...it's a fact...and newly released software is bound to have some hairy ones...at ~2 months time, there will either be a new minor release or a lot of ppl complaining if it's still unstable...
It's not a M$ thing...it's good administration...it's also why some ppl are still using 2.2 or even 2.0 kernels...
You do however have a point, I think. Microsoft has been mocked about their inflated version numbering scheme. Linux is doing just the opposite. The convention for software X.Y.Z is:
X - major release
Y - incremental release with additional features
Z - release featuring only bugfixes
Had Linux adopted that system we would not have had the pointless 2.6 vs. 3.0 discussion on when changes are "big enough".
Major releases equals major numbers, simple. It is not like we will be running out of numbers by using up a new major one every two years or so.
- El riesgo siempre vive - Private J. Vasquez
If both ide-cd and ide-scsi are used as a module, I don't see why you can't just load and unload the correct modules when you want to change modes.
But OTOH, why would you want to do that anyway? With ide-scsi, you can do everything you need to do with the drive, I don't see why you can't just use that mode all the time.
"But Windows can seemlessly change between SCSI-emulation and IDE, without requiring boottime option (allthough a reboot is required for installation)."
This sounds very unlikely to me. I admit, I don't really know, having not owned a windows computer in a few years...but I can't see any conceivable way this could be true. Does windows have some right-click option on the drive letter that has a check-box for "use scsi-emulation" or something?
I think it is much much more likely that either a)windows leaves the drive in scsi-emu mode all the time, or b)windows loads normal ide stuff, and nero/roxio/whatever loads up the scsi-emu.
The big question is "can you really tell windows to turn scsi-emu on/off?" I doubt it.
Given a choice between free speech and free beer, most people will take the beer.