From: Ethan Benson <erbenson@alaska•net>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: DST flag in NVRAM revisited (was: Re: NVRAM stuck in DST?)
Date: Thu, 28 Mar 2002 14:28:30 -0900 [thread overview]
Message-ID: <20020328142829.W26309@plato.local.lan> (raw)
In-Reply-To: <20020328171859.4716@mailhost.mipsys.com>; from benh@kernel.crashing.org on Thu, Mar 28, 2002 at 06:18:59PM +0100
On Thu, Mar 28, 2002 at 06:18:59PM +0100, benh@kernel•crashing.org wrote:
> >we should just deal with the RTC exactly how its delt with on x86, if
> >you have windows (or in our case MacOS) you tell hwclock the RTC is in
> >localtime and let it deal with it, if you don't have MacOS/windows you
> >tell it you have the RTC in GMT like its supposed to be and all is well.
>
> Which means that during boot, the kernel will have a wrong (local) time
> instead of UTC. That can be annoying.
only for a short period of time, look at debian woody for how they
invoke hwclock, it ensures this period is short.
but in any event its the price you pay for keeping a broken OS
installed and letting it control the hardware clock. it is certainly
not severe enough to justify all these fragile and broken kludges and
kernel bloat.
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-28 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 7:59 NVRAM stuck in DST? Michel Lanners
2001-12-07 21:38 ` Benjamin Herrenschmidt
2001-12-07 21:39 ` Benjamin Herrenschmidt
2002-03-28 11:28 ` DST flag in NVRAM revisited (was: Re: NVRAM stuck in DST?) Michel Lanners
2002-03-28 13:04 ` Ethan Benson
2002-03-28 16:19 ` Geert Uytterhoeven
2002-03-28 23:31 ` Ethan Benson
2002-03-29 0:47 ` bug: kernel timer added twice at e3259abc Kevin B. Hendricks
2002-03-28 17:18 ` DST flag in NVRAM revisited (was: Re: NVRAM stuck in DST?) benh
2002-03-28 23:28 ` Ethan Benson [this message]
2001-12-07 22:09 ` NVRAM stuck in DST? Greg Noel
2001-12-08 11:24 ` Gabriel Paubert
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=20020328142829.W26309@plato.local.lan \
--to=erbenson@alaska$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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