Linux 2.6.0 Expected In Mid-December
Ridgelift writes "CRN is reporting the release of Linux 2.6.0 in mid-December. 'Torvalds, Linux's lead developer and now an OSDL Fellow, and Linux kernel maintainer Andrew Morton this week released the test10 version of Linux 2.6 after a three-year development effort. A final test11 version is expected before they sign off on the production version next month.' Get ready for 'major scalability improvements, faster performance, enhanced support for embedded systems and, to a lesser extent,' a kernel that 'supplies desktop systems with better USB and FireWire support.'"
We're running 2.6.0-test9 on several production machines at work, and we had absolutely no problem, so far, but a huge improvement on performance instead. The only thing one has to care about is that 2.6.0 requires module-init-tools instead of modutils. It's especially important to read the upgrade guide, so that one can easily switch back to 2.4.x even when using modules (not that I would miss 2.4.x, but you never know... not all people will have such flawless upgrade processes as I did).
A monkey is doing the real work for me.
I'm running this new kernel to get full support on whatever IDE chipset my Dell Latitude D600 laptop uses. Combined with the better performance this kernel really rocks.
8 of 13 people found this answer helpful. Did you?
A problem, potentially delaying release? Seems that they don't really know what causes it as of yet...
Have you tried "pci=noacpi" at the boot prompt? I had complete crashes (no kernel panic) when the keyboard was initialized before I tried that. Maybe your problem is related? (This is for a PS/2 type keyboard, BTW.)
I don't think I have any problems with 2.6.0-test9-mm1 at all.
I upgraded to module-init and after that 2.4 wouldn't boot. grr.
/sbin/modinfo, and numerous symlinks to things like lsmod.old exist. There is probably a boot script that detects the kernel version on boot, creates the appropriate links, and then loads up the modules, but nothing in /etc/init.d jumped out at me as the culprit.
Is there a way to have both installed so I could dual boot 2.4 and 2.6?
Gentoo GNU/Linux supports this, and I believe Source Mage does as well.
I run 2.6.0-test10 and 2.6.0-test9-mm5 on numerous Gentoo boxes with no problem, and occasionally switch back to 2.4.22 without difficulties.
I'm not sure how they do it exactly. A quick perusal of module-init-tools and modutils revealed that, for example, bot install
In any event, it is certainly possible have both installed and functional, and to seemlessly move between 2.4.x and 2.6.x kernels.
The Future of Human Evolution: Autonomy
Debian supports 2.4 right now. You get your choice with 'woody'. True the default install CD DOES install 2.2, but if you boot with the BF24 image, you will install the 2.4 kernel. AND 2.4 kernel images ARE in the 'stable' package tree.
It's worth reminding RH/Fedora users that Arjan van de Ven maintains kernel RPMs (including new module RPMs etc), and those with yum and apt can very easily test 2.6 using these files.
Read the readme.txt for full details.
Most notably (for me) is devfs not being actively supported anymore (being shifted in favor of udev).
/dev files that correspond to devices you have connected. But they are moving "back" to the old /dev/sg?1 etc. I much prefer the devfs nameing scheme (what do you do if you have more than 24 hds? The devfs had a solution for that).
Well, the reason devfs is not actively supported is because the maintainer disappeared, and nobody has stepped up to take over the code.
udev seems to solve the problem of only have
Je ne parle pas francais.
There was an effort to write a completely new win32-based replacement for win31, cougar was the codename for the 32-bit DOS kernel, and panther was the win32 core, but panther was canned and cougar was merged into chicago (win95).