Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 29 Oct 2001 17:26:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 29 Oct 2001 17:25:52 -0500 Received: from dsl-65-186-161-49.telocity.com ([65.186.161.49]:58121 "EHLO nic.osagesoftware.com") by vger.kernel.org with ESMTP id ; Mon, 29 Oct 2001 17:25:32 -0500 Message-Id: <4.3.2.7.2.20011029172525.00bb2270@mail.osagesoftware.com> X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 29 Oct 2001 17:26:06 -0400 To: Linux kernel From: David Relson Subject: Re: Nasty suprise with uptime In-Reply-To: <3BDDC193.BCB00D84@lexus.com> In-Reply-To: <3BDDBE89.397E42C0@lexus.com> <20011029124753.F21285@one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Let's assume you have the counter changed to 32 bits - RIGHT NOW (tm). Build a kernel, install it, reboot. It'll be over a year (approx Jan 2003) before the change will be noticeable... Methinks that's a long time to wait for a result :-) David At 04:52 PM 10/29/01, J Sloan wrote: >Matthew Dharm wrote: > > > No, but there are a couple of applicable Linux policies: > > (1) If it breaks, you get to keep both halves. > > (2) If it's broken, fix it yourself. > >hmm, maybe I'll send in an uptime patch and >see what sort of feedback I get... > >Gotta get those 1000 day uptimes to silence >the bsd bigots! > >cu > >jjs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/