From mboxrd@z Thu Jan  1 00:00:00 1970
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Date: Tue, 28 Jul 2009 17:42:23 -0700
User-Agent: KMail/1.11.4 (Linux/2.6.27-gentoo-r8; KDE/4.2.4; i686; ; )
References: <09c88626d985457ecaa621715f4f1af0@quanstro.net>
In-Reply-To: <09c88626d985457ecaa621715f4f1af0@quanstro.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907281742.23251.corey@bitworthy.net>
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last
	write time'
Topicbox-Message-UUID: 3098ac8e-ead5-11e9-9d60-3106f5b1d025

On Tuesday 28 July 2009 16:50:15 erik quanstrom wrote:
> > #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?
>

My (ill-founded?) reasoning went like this:

* -L is for if "the real time clock is in local time rather than GMT"

* my bios rtc is not set in local time, it is in UTC time

* therefore, I do not want the -L switch passed to aux/timesync


> 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.
>

I do not know. I'll try this though.

Approximately how long is 'some time'? (so I know how long to wait)


> 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.
>

I'll look into this also, thanks for the suggestion.


> >          - 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.
>

Please see below. My experience is indicating a different reality,
or I'm still not interpreting my experience correctly.

Clearly no one's under any obligation to help me see the light, but
I do value the time and effort spent attempting to do so!

And I realize that it's entirely possible I'm just incurably chrono-impaired.


> just as a note, you can make timezones appear instantly by
> 	; timezone = `{cat /adm/timezone/local}
> 	; date
>

Yes I was aware of this, although I did it more naively (cp
 /adm/timezone/local /env/timezone).

My point though is that yes, it makes the timezone change take
effect immediately - and it likewise causes the 'creation time after
last write time' /dev/kprint's to appear instantly as well...

And yet, timezone does not affect venti?


> and you can always get gmt time by
> 	; timezone=() date
>

Good to know - thank you.