Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
2.4 vs 2.6
2.4 vs 2.6
Is there a reason many people are installing the 2.4 kernel these days, or do they just not know about the linux26 flavor?
"You are therefore strongly advised not to upgrade to a 2.6 kernel as part of the upgrade from woody to sarge. Instead, you should first make sure your system works correctly with either the old kernel or with a 2.4 kernel from sarge and do the upgrade to a 2.6 kernel later as a separate project." (1)
From the above text, I assume the reason is to make sure that one has a smooth upgrade from the previous version, which deployed 2.4 kernel version.
(1) Source: http://www.debian.org/releases/stable/i ... ade-to-2.6
From the above text, I assume the reason is to make sure that one has a smooth upgrade from the previous version, which deployed 2.4 kernel version.
(1) Source: http://www.debian.org/releases/stable/i ... ade-to-2.6
-
- Debian Developer, Site Admin
- Posts: 483
- Joined: 2004-04-06 18:19
- Location: Utrecht, NL
- Contact:
Even now there's still hardware support regression from 2.4 to 2.6. But well, some stuff only works on 2.6, so for new installs, I suggest 2.6.
2.4 is still more stable though, so if stableness is of utmost importance to you, stick with 2.4. There's still some significant bugfixing going on in kernels > 2.6.8 (the 2.6 in Sarge).
2.4 is still more stable though, so if stableness is of utmost importance to you, stick with 2.4. There's still some significant bugfixing going on in kernels > 2.6.8 (the 2.6 in Sarge).
So far I experienced only one major bug that resulted in the (in)famous apci hanging issue. Do you have any idea of how's this going?2.4 is still more stable though, so if stableness is of utmost importance to you, stick with 2.4. There's still some significant bugfixing going on in kernels > 2.6.8 (the 2.6 in Sarge).
domecq wrote:dren, please correct me if I'm wrong, but is there a classification for the kernel version that mentions something about an odd number meaning that it's a test version and an even number meaning that it's the stable one that Guest asked about?
Cheers,
domecq
No thats been discontinued, now.
The development process is so fast in 2.6.x. Maintainers have been keeping their development trees seperate. The sub incremental versions along with -rcx versions are considered test releases (2.6.x.x). But the odds/evens on the minor/incremental dosen't apply anymore in that regard.
When/if 2.7 comes out it will be a stable release branch.
Moving to 2.6 was the best thing i ever did and when bugs have arisen, around the 2.6.9 stage, they were quickly fixed.
Iv'e found the -ckx (Con Koliva) patch to be extreamly good as well. It will also incorporate the more stable aspects from other developer trees.
http://bhhdoa.org.au/pipermail/ck/
http://ck.kolivas.org
The increase in desktop performance is stricking with 2.6 compared to 2.4. Essentually due to a more improved code base,concerning the way the kernel deals with scheduling/latency issues.
2.6 approches drive geometries differently to 2.4. It now deals with it, with an ata-ide spec compliance. It will return a 16 head geometry rather than a 255 head based one. This did cause some problems with programs that were expecting a 255 head geometry (FC3). But that was really a problem with those programs lazily relying on none specification behavour and wont occur any more. But generally you need to make sure all the utilities your using are resent versions. Such as things like module-init-tools etc which is also compatable with the 2.4 modutils approach. So that will be a seamless transition. You just need to install the package. All the fdisk, cfdisk parted type programs are best to update to ensure they are ata-ide spec aware. It just means if there going to muck about with disk geometry issues from user-space then they need to do it correctly rather than resting on a M$ smirfed expectation of 255 heads. But thats all trivial really.
Go for the 2.6, you wont know what you ever did before without it.
jm
Yes, basicly 2.6 is faster, supports newer hardware (ipw2200 to name one) and can manage file transfers better.
The 2.4 kernel is considered more "stable" but I never see any difference.
If you are upgrading an existing instalation of course use the existing kernel tree, but if you are upgrading to Sarge I would recomend a clean install with the 2.6 kernel a LOT of stuff has changed since woody a clean install will most likely run cleaner, have fewer bugs and run faster.
The 2.4 kernel is considered more "stable" but I never see any difference.
If you are upgrading an existing instalation of course use the existing kernel tree, but if you are upgrading to Sarge I would recomend a clean install with the 2.6 kernel a LOT of stuff has changed since woody a clean install will most likely run cleaner, have fewer bugs and run faster.
The only way to aggrandize oneself is to aggrandize others.
-Joseph Smith
-Joseph Smith
-
- Debian Developer, Site Admin
- Posts: 483
- Joined: 2004-04-06 18:19
- Location: Utrecht, NL
- Contact:
A clean install certainly isn't needed. Debian is well known for its in-place upgradability. Whether you're doing a clean install or an upgrade from woody, you can benefit from the new 2.6 kernel anyway. Just in the case of the upgrade, ensure you install it and enable it.
A clean install will ruin all your customisations etc...
A clean install will ruin all your customisations etc...
-
- Debian Developer, Site Admin
- Posts: 483
- Joined: 2004-04-06 18:19
- Location: Utrecht, NL
- Contact:
There can be reasons to do a clean install, like, there were setting put weirdly, etc etc, or mistakes you want to repair and start over. But this has not much to do with upgrade, more like with 'reinstall': install again because you want to 'start over' if things are wrong beyond repair.
You listed as reasons "run cleaner, have fewer bugs and run faster.", and the first reason is at least somewhat true: een upgrade will at times simply leave around configuration files when it's unsure what the upgrade should do, wasting a tiny bit of disk. Also sometimes you'll keep configuration files from the previous version instead of replacing it with a new one -- it all depends on the situation whether this is a good thing or not, that's why mostly you're asked about it every time.
You listed as reasons "run cleaner, have fewer bugs and run faster.", and the first reason is at least somewhat true: een upgrade will at times simply leave around configuration files when it's unsure what the upgrade should do, wasting a tiny bit of disk. Also sometimes you'll keep configuration files from the previous version instead of replacing it with a new one -- it all depends on the situation whether this is a good thing or not, that's why mostly you're asked about it every time.
Ryujin Wrote:
>>
The 2.4 kernel is considered more "stable" but I never see any difference.
>>
More tested i suppose, but still being developmed. Though only in terms of any security issues that might crop up.
When you consider the greater hw support available in the 2.6, and things like sysfs/udev facilities. And the way my desktop flies without a hitch
2.6 is the go ....
The only problem i ever had was around 2.6.8 and oomkill crashes. But i was quite ram limited at the time, and thats all been fixed.
A greater concern with regards to upgrading a system would have more to do with abi issues in terms of gcc and libc6 versioning.
The kernel is quite harmless there really. Unless you have hw were support has been discontiued. But i think that would be rare if at all. Even oss is still supported in 2.6.
jm
>>
The 2.4 kernel is considered more "stable" but I never see any difference.
>>
More tested i suppose, but still being developmed. Though only in terms of any security issues that might crop up.
When you consider the greater hw support available in the 2.6, and things like sysfs/udev facilities. And the way my desktop flies without a hitch
2.6 is the go ....
The only problem i ever had was around 2.6.8 and oomkill crashes. But i was quite ram limited at the time, and thats all been fixed.
A greater concern with regards to upgrading a system would have more to do with abi issues in terms of gcc and libc6 versioning.
The kernel is quite harmless there really. Unless you have hw were support has been discontiued. But i think that would be rare if at all. Even oss is still supported in 2.6.
jm