Stability is as much of a statistic as an opinion. It may work very good on your machine but horrible on others. Some people don't trust software until it's been out in the wild for awhile. I should say that do_mremap was an embrassasing first major bug.
This may sound like a nit-pick, but I'm not sure where to put this; I would like to try the 2.6 kernel, but it no longer supports the hardware I use under 2.4, and I don't have time to fix things.
My hard discs are in a RAID-0 on a Highpoint HPT-374 controller. Because this is a software ATA-RAID solution, Linux RAID doesn't read it.
Because the ataraid stuff in 2.4 was basically a device mapper for ATA-RAID only, it's been removed pending a rewrite built on the new device-mapper stuff. No one's done the rewrite, so my 2.6 kernel can't read its root partition; I'm about to experiment with manual devicemapper setups (using dmsetup), then running EVMS2 on top of these nodes, but I don't know if it'll work.
OK. EVMS 2 won't read device-mapper volumes, but fdisk showed that the principle is sound. Next thing is to work out how to write an EVMS plugin to read the disc layout and generate EVMS volumes.
Well, if new kernel would support everything that 2.4 does + new stuff, it would finally end in doom. The kernel sources would grow so big that it would be inpossible to maintain everything. Or not probably in one 2.4->2.6, but imagine like 2.4->3.0, the source would be BIG.
So there really are good reasons for removing stuff from kernel, nothing is removed without any good reason.
--
Regards,
Markus
I will try 2.6 when Nvidia will release a driver for my graphical card. (I know there is a patch somewhere on the net to use it, but I prefer official driver.). Until that, I stick with 2.4, which is very stable for me.
www.minion.de is the place to get nvidia 2.6 drivers. Also keep in mind that only a very small part (the kernel module) must be updated, not the whole driver. The site seems to be semi-officially the unofficial driver site.
It's easy to have multiple kernels installed, in such way that you can choose which one to use at boot. If I were you I would just try it out, and if it turns out to be unstable then switch back to 2.4. I don't think that graphic drivers should stop you from using 2.6.
1.0-5336 offers official support for 2.6. Looking at the code, I think NVIDIA just merged in minion.de's patches for the interface, and cleaned up something in the binary-only parts (it no longer OOPSes - it was never a big performance hit, just damn annoying in the logs).
IT'S NOT STABLE YET?!?!??
IT'S STABLE!!!
*sigh*
Stability is as much of a statistic as an opinion. It may work very good on your machine but horrible on others. Some people don't trust software until it's been out in the wild for awhile. I should say that do_mremap was an embrassasing first major bug.
grammar police
"splitted"??
i learnded me some good english.
Past term for split
Surely you meant "splat" ?
re: Past term for split
FWIW: I've corrected the grammar...
Missing option
This may sound like a nit-pick, but I'm not sure where to put this; I would like to try the 2.6 kernel, but it no longer supports the hardware I use under 2.4, and I don't have time to fix things.
Missing options ?!?
Hi
Really? There was removed so much drivers ?
Is there a list somewhere ?
I always thought new Kernel's will support all what it suppported
up till then plus new hardware, and of course improvements.
Regards
Anes
My hard discs are on ataraid, and no-one's fixed them yet
My hard discs are in a RAID-0 on a Highpoint HPT-374 controller. Because this is a software ATA-RAID solution, Linux RAID doesn't read it.
Because the ataraid stuff in 2.4 was basically a device mapper for ATA-RAID only, it's been removed pending a rewrite built on the new device-mapper stuff. No one's done the rewrite, so my 2.6 kernel can't read its root partition; I'm about to experiment with manual devicemapper setups (using dmsetup), then running EVMS2 on top of these nodes, but I don't know if it'll work.
Follow up
OK. EVMS 2 won't read device-mapper volumes, but fdisk showed that the principle is sound. Next thing is to work out how to write an EVMS plugin to read the disc layout and generate EVMS volumes.
re: Missing options ?!?
Well, if new kernel would support everything that 2.4 does + new stuff, it would finally end in doom. The kernel sources would grow so big that it would be inpossible to maintain everything. Or not probably in one 2.4->2.6, but imagine like 2.4->3.0, the source would be BIG.
So there really are good reasons for removing stuff from kernel, nothing is removed without any good reason.
--
Regards,
Markus
More options
Some more options would be "Tried it but didn't do everything i wanted/was used to in 2.4" and "Haven't had the time to test it yet".
Nvidia driver
I will try 2.6 when Nvidia will release a driver for my graphical card. (I know there is a patch somewhere on the net to use it, but I prefer official driver.). Until that, I stick with 2.4, which is very stable for me.
www.minion.de is the place to
www.minion.de is the place to get nvidia 2.6 drivers. Also keep in mind that only a very small part (the kernel module) must be updated, not the whole driver. The site seems to be semi-officially the unofficial driver site.
It's easy to have multiple kernels installed, in such way that you can choose which one to use at boot. If I were you I would just try it out, and if it turns out to be unstable then switch back to 2.4. I don't think that graphic drivers should stop you from using 2.6.
2.6 support
NVidia announced 2.6 support recently somewhere..
Yep.
1.0-5336 offers official support for 2.6. Looking at the code, I think NVIDIA just merged in minion.de's patches for the interface, and cleaned up something in the binary-only parts (it no longer OOPSes - it was never a big performance hit, just damn annoying in the logs).