From: Bill Davidsen <davidsen@tmr.com>
To: Christian Borntraeger <kernel@borntraeger.net>
Cc: "Markus Hästbacka" <midian@ihme.org>, linux-kernel@vger.kernel.org
Subject: Re: Uptime counter
Date: Wed, 04 Feb 2004 11:24:40 -0500 [thread overview]
Message-ID: <40211CC8.7030204@tmr.com> (raw)
In-Reply-To: <200402012202.07204.kernel@borntraeger.net>
Christian Borntraeger wrote:
> Markus Hästbacka wrote:
>
>>Hi list,
>>I wonder does any kernel branch have a uptime counter that doesn't stop
>>counting at 497 days? Or is a patch needed for the job to
>>2.{0,2,4,6} kernel?
>
>
> In 2.6 there is no 497 days limit, as jiffies are now 64 bit.
>
> By the way: Having a machine with more than 497 days of uptime normally
> shows a serios lack of security awareness..
Think embedded systems...
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2004-02-04 16:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 20:41 Uptime counter Markus Hästbacka
2004-02-01 20:51 ` Matti Aarnio
2004-02-01 22:07 ` Ludootje
2004-02-01 21:20 ` Matthew Reppert
2004-02-01 20:52 ` Måns Rullgård
2004-02-01 21:02 ` Christian Borntraeger
2004-02-01 21:16 ` Markus Hästbacka
2004-02-01 21:27 ` David Weinehall
2004-02-01 21:34 ` Markus Hästbacka
2004-02-01 21:44 ` David Weinehall
2004-02-01 22:07 ` Markus Hästbacka
2004-02-01 22:19 ` David Weinehall
2004-02-01 22:42 ` Markus Hästbacka
2004-02-01 21:56 ` Guillermo Menguez Alvarez
2004-02-01 22:36 ` Paul Jakma
2004-02-01 22:59 ` Markus Hästbacka
2004-02-01 23:04 ` David Weinehall
2004-02-02 7:20 ` Markus Hästbacka
2004-02-02 7:24 ` David Weinehall
2004-02-02 8:59 ` Markus Hästbacka
2004-02-01 23:47 ` Wakko Warner
2004-02-01 21:33 ` Tomasz Torcz
2004-02-01 22:10 ` Ludootje
2004-02-02 17:54 ` Valdis.Kletnieks
2004-02-02 18:37 ` Mike Fedyk
2004-02-04 16:24 ` Bill Davidsen [this message]
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=40211CC8.7030204@tmr.com \
--to=davidsen@tmr.com \
--cc=kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox