These kernel updates have very little to do with Linux / UNIX uptime or
avaiablbility and everything to do with legacy equipment skirting the TCP RFC.
A little research on the Unbutu threads reveals:
-----
Details about Linux kernel regression
Version 2.6.27 of the Linux kernel changed the order of options in TCP
headers. While this change was RFC-compliant, it was found that some old
routers and consumer DSL modems would not route traffic for these systems when
TCP timestamps were enabled. As a workaround, TCP timestamps were disabled via
sysctl..
-----
A desktop is not a server and by definition has dissimilar software, workloads
and requirements. The long touted and unequaled UNIX uptimes are typically
based on a long history of server workloads.
For example, a heavily loaded, money making production server:
[r...@xxxxxxx root]# uptime
08:44:19 up 490 days, 21:17, 3 users, load average: 4.37, 2.89, 2.31
Regards:
Eric Wilson
>
> I'm getting sick of it wanting to reboot personally also. I've got too
> much crap open to reboot. Firefox isn't going to remember which window
> was where, the random floating text documents won't be where I left
> them, and what happened to the days when the 'nix crowd touted uptime?
>
> On Fri, Jan 30, 2009 at 1:29 AM, Sean Burns <[email protected]> wrote:
>>
>> I'm on my third kernel update for Intrepid in as many days.
>> Seems weird. Others too? All for 2.6.27.11-generic also.
>> --
>> Fri, 30 Jan 2009 01:28:01 -0600
>>
>> >
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Central West End Linux Users Group (via Google Groups)
Main page: http://www.cwelug.org
To post: [email protected]
To subscribe: [email protected]
To unsubscribe: [email protected]
More options: http://groups.google.com/group/cwelug
-~----------~----~----~----~------~----~------~--~---
