From: Mike Fedyk <mfedyk@matchmail.com>
To: J Sloan <jjs@lexus.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nasty suprise with uptime
Date: Mon, 29 Oct 2001 15:28:09 -0800 [thread overview]
Message-ID: <20011029152809.H20280@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3BDDBC90.7E16E492@lexus.com> <20011029151036.F20280@mikef-linux.matchmail.com> <3BDDE422.938C1D95@lexus.com>
In-Reply-To: <3BDDE422.938C1D95@lexus.com>
On Mon, Oct 29, 2001 at 03:20:02PM -0800, J Sloan wrote:
> Mike Fedyk wrote:
>
> > On Mon, Oct 29, 2001 at 12:31:12PM -0800, J Sloan wrote:
> > > Say it ain't so! maybe I'm a bit dense, but is the 2.4 kernel also going
> > > to wrap around after 497 days uptime? I'd be glad if someone would
> > > point out the error in my understanding.
> >
> > Ahh, so that's why there haven't been any reports of higher uptimes... ;)
>
> Yes, it all makes sense now -
>
Just imagine the headline:
Kernel 2.6 now allows uptimes higher than 1.47 years!
_Click_Here_
*Click*
.........
The change was origionally included in 2.5.4, which was origionally known as
2.4.14...
;)
next prev parent reply other threads:[~2001-10-29 23:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 20:31 Nasty suprise with uptime J Sloan
2001-10-29 20:40 ` Alan Cox
2001-10-29 20:39 ` J Sloan
2001-10-29 20:47 ` Matthew Dharm
2001-10-29 20:52 ` J Sloan
2001-11-09 0:45 ` Dr. Kelsey Hudson
2001-10-29 21:26 ` David Relson
2001-10-29 23:29 ` Jonathan Briggs
2001-10-30 8:53 ` george anzinger
2001-10-30 13:50 ` Tim Walberg
2001-10-30 14:47 ` GOMBAS Gabor
2001-10-30 15:39 ` Tim Walberg
2001-10-30 16:18 ` GOMBAS Gabor
2001-10-30 22:53 ` Mike Castle
2001-10-30 8:20 ` george anzinger
2001-10-30 9:47 ` bert hubert
2001-10-30 10:37 ` Mike Fedyk
2001-10-30 15:56 ` Chris Meadors
2001-10-30 16:22 ` Laurent de Segur
2001-10-30 21:53 ` [OT] " J Sloan
2001-10-30 22:52 ` Jan Dvorak
2001-10-30 23:25 ` [OT] " J Sloan
2001-10-30 7:46 ` Neale Banks
2001-10-30 7:46 ` Mike Fedyk
2001-10-30 8:15 ` Ville Herva
2001-10-30 8:22 ` Ville Herva
2001-10-30 8:36 ` J. Dow
2001-10-30 9:33 ` Alan Cox
2001-10-30 16:25 ` Matt Bernstein
2001-10-30 19:43 ` Oden Eriksson
2001-10-29 23:10 ` Mike Fedyk
2001-10-29 23:20 ` J Sloan
2001-10-29 23:28 ` Mike Fedyk [this message]
2001-10-30 8:21 ` Ville Herva
2001-10-31 22:36 ` J Sloan
2001-11-01 0:49 ` Gerhard Mack
2001-10-30 8:49 ` george anzinger
2001-10-30 18:17 ` J Sloan
2001-10-30 9:06 ` Alan Cox
2001-10-30 19:19 ` J Sloan
-- strict thread matches above, loose matches on Subject: below --
2001-10-30 16:35 Jesse Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011029152809.H20280@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.