From: Ethan Benson <erbenson@alaska•net>
To: Linux/PPC Development <linuxppc-dev@lists•linuxppc.org>
Subject: Re: DST flag in NVRAM revisited (was: Re: NVRAM stuck in DST?)
Date: Thu, 28 Mar 2002 14:31:17 -0900 [thread overview]
Message-ID: <20020328143117.X26309@plato.local.lan> (raw)
In-Reply-To: <Pine.GSO.4.21.0203281718540.4979-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Thu, Mar 28, 2002 at 05:19:56PM +0100
On Thu, Mar 28, 2002 at 05:19:56PM +0100, Geert Uytterhoeven wrote:
>
> Perhaps someone can writes a utility to `patch' MacOS to treat the hardware
> clock being in GMT/UTC/Zulu time? I did a similar thing for AmigaOS many many
> years ago.
or if you want a macos only use OSX, it has no problems with the
hardware clock set to UTC, at least the beta did not.
(i tinkered with the beta, at the time my machine had no trace of
MacOS 8/9 and my nvram contains no macos cruft, that is the timezones
and DST fields are null, OSX showed the proper time, and it never
reset the hardware clock to localtime.)
--
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:31 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 [this message]
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
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=20020328143117.X26309@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