From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f6e51149a87d9f897a3969f1eeb6c027@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue, 28 Jul 2009 19:50:15 -0400
To: corey@bitworthy.net, 9fans@9fans.net
In-Reply-To: <200907281542.50518.corey@bitworthy.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last
	write time'
Topicbox-Message-UUID: 3094111a-ead5-11e9-9d60-3106f5b1d025

> #6 - reboot, (first-time login), as glenda:
>          - remove -L switch from $TIMESYNCARGS in /rc/bin/termrc

if the time was already correct modulo timezone, why did you do this?
also, after allowing the machine to run for some time, does timesync
cause the system time (date -n) to jump?  i.e. is the nvram time wrong.

you don't say, but i'm quite sure that on reboot you'll find
that date -n will have jumped by 7 hrs + whatever time
it took to do the reboot.  bios time will not be affected.

>          - as an adm user: cp /adm/timezone/US_Arizona /adm/timezone/local

you should note that this has absolutely zero to do with
timesync, the bios clock or tea in china.  this changes the
human readable time only.  fossil and venti just don't care.

just as a note, you can make timezones appear instantly by
	; timezone = `{cat /adm/timezone/local}
	; date
and you can always get gmt time by
	; timezone=() date

- erik