From: Mike Castle <dalgoda@ix.netcom.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nasty suprise with uptime
Date: Tue, 30 Oct 2001 14:53:40 -0800 [thread overview]
Message-ID: <20011030145340.A2024@thune.mrc-home.com> (raw)
In-Reply-To: <E15yJD1-0003uO-00@the-village.bc.nu> <3BDDBE89.397E42C0@lexus.com> <20011029124753.F21285@one-eyed-alien.net> <4.3.2.7.2.20011029172525.00bb2270@mail.osagesoftware.com> <3BDDE642.8000901@acm.org> <3BDE6A80.3A68A44E@mvista.com>
In-Reply-To: <3BDE6A80.3A68A44E@mvista.com>
On Tue, Oct 30, 2001 at 12:53:20AM -0800, george anzinger wrote:
> Jonathan Briggs wrote:
> > A 32 bit uptime patch should also include a new kernel parameter that
> > could be passed from LILO: uptime. Then you could test the uptime patch
> > by passing uptime=4294967295
>
> NO NO NO!
>
> First uptime is a conversion of jiffies. Second, the POSIX standard
> wants a CLOCK_MONOTONIC which, by definition, can not be set. Jiffies
I believe that at least some SVR4 systems allow you to set lbolt, either
during runtime or at boot.
You have to be able to do that to test things. Like drivers (last I check,
NCR still crashes upon wrap around), or utilities that monitor the uptime
so they can remind you that a reboot is necessary soon (so that you don't
crash).
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
next prev parent reply other threads:[~2001-10-30 22:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 20:31 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 [this message]
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
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
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=20011030145340.A2024@thune.mrc-home.com \
--to=dalgoda@ix.netcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®