I agree about dealing with regressions like this - fixing the kernel in haste would probably have slipped the release date, and most people really don't need TCP timestamps, so it's fine for it to be fixed in a later update - people who do need timestamps (on long fat networks such as satellite links) can enable it quite easily after any routers have been fixed.
Most people should be running 8.04 not 8.10 in any case - as the first release after an LTS release, 8.10 is going to be more risky (hence the 'Intrepid', just like the 'Edgy' for 6.10).
I don't normally run a new Ubuntu release in production until a month or two has elapsed in any case.
Posted Oct 29, 2008 14:56 UTC (Wed) by drag (subscriber, #31333)
[Link]
THe problem is that if you install Ubuntu and your behind a buggy router then you may run into severe issues when trying to update your system.
In order to download the "fixed" kernel you need to be able to get on the Internet. If you can't get on the internet due to a "broken" kernel then how exactly are you suppose to solve your problem?
Catch-22.
The _only_ effective fix for Ubuntu, at this point, is to include the "fixed" kernel with the installer.
And I can understand if they can't pull it off. But it's going to suck for some people that they can't.
(Of course, I am fully aware that it's not Linux being broken, just the environment that Linux is expected to operate in has buggy network hardware sometimes)
Networking change causes distribution headaches
Posted Oct 29, 2008 15:00 UTC (Wed) by drag (subscriber, #31333)
[Link]
*ooops*
that's what I get for not reading it to the end. They are a lot smarter then me, after all.