View previous topic :: View next topic |
Author |
Message |
Dralnu Veteran
Joined: 24 May 2006 Posts: 1919
|
Posted: Tue Feb 13, 2007 3:44 am Post subject: Is 2.6.19 safe to use? |
|
|
I know there was a massive bug in 2.6.19 dealing with data corruption, but has this been fixed in the gento-sources version? Before I upgrade, I want to know... _________________ The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner. |
|
Back to top |
|
|
broken_chaos Guru
Joined: 18 Jan 2006 Posts: 370 Location: Ontario, Canada
|
Posted: Tue Feb 13, 2007 3:46 am Post subject: |
|
|
It wouldn't be stabilized unless it was. I believe the bug was also present in older kernels, where it was also fixed. |
|
Back to top |
|
|
Dralnu Veteran
Joined: 24 May 2006 Posts: 1919
|
Posted: Tue Feb 13, 2007 4:08 am Post subject: |
|
|
broken_chaos wrote: | It wouldn't be stabilized unless it was. I believe the bug was also present in older kernels, where it was also fixed. |
I read through a few articles over it. It seemed to them it might have been present, and if it was, it seemed to have been compounded in that kernel. _________________ The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner. |
|
Back to top |
|
|
wyv3rn Apprentice
Joined: 18 Aug 2005 Posts: 154 Location: USA
|
Posted: Tue Feb 13, 2007 5:11 am Post subject: |
|
|
It was an obscure bug that caused data corruption under certain circumstances. It was hardly wide-spread, but the magnitude and difficulty of finding the bug made it newsworthy. If I remember correctly, the bug was introduced in either 2.6.18 (possibly by one of the "stable" 2.6.18.x patches) or 2.6.19. It is fixed in both the latest 2.6.18.x series and >=2.6.19.2. The latest gentoo-sources is based on 2.6.19.3. Kernel 2.6.19 is actually very good now that its had some time to mature. |
|
Back to top |
|
|
Dralnu Veteran
Joined: 24 May 2006 Posts: 1919
|
Posted: Tue Feb 13, 2007 5:14 am Post subject: |
|
|
wyv3rn wrote: | It was an obscure bug that caused data corruption under certain circumstances. It was hardly wide-spread, but the magnitude and difficulty of finding the bug made it newsworthy. If I remember correctly, the bug was introduced in either 2.6.18 (possibly by one of the "stable" 2.6.18.x patches) or 2.6.19. It is fixed in both the latest 2.6.18.x series and >=2.6.19.2. The latest gentoo-sources is based on 2.6.19.3. Kernel 2.6.19 is actually very good now that its had some time to mature. |
Alright. Thanks for the info. I know I heard some nightmarish reports, so I figured I'd double check before upgrading. _________________ The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner. |
|
Back to top |
|
|
|