Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'

[Corey <corey@bitworthy.net>]

On Monday 27 July 2009 15:52:28 erik quanstrom wrote:
> > ls -l /386/bin/venti
> >
> > reboot
> >
> >
> > ... but the changes I applied to arena.c do show up; which
> > leads me to believe my changes aren't being used by the
> > system.
>
> no you're not missing anything except for the sleezy trick.
> venti is built into the kernel.  you will also need to rebuild
> your kernel.
>

Cool - that did the trick.


So, I edited the offending line in arena.c to output the arena->ctime and
arena->wtime, and it appears to resemble the situation Lyndon explained:

"I suspect what's happening is the motherboard clock is set in
the future, you are formatting venti based on that time, and then later
firing up timesync which interprets the RTC as local time. If your RTC is
set to UTC and you're in the western hemisphere, the RTC clock will be
ahead of your local time."


... it's kindofa bummer that apparently I can't setup fossil+venti during
the plan 9 install process without hosing up venti when I change my
timezone appropriately to get the correct time on the machine...

So I guess I either:

* keep the machine on UTC, which allows me to install fossil+venti
  during installation

... or:

* set up venti manually after the install, and after I've set the timezone


I"m surprised this issue doesn't seem to show up more often. I've only seen
two different instances of this brought up on 9fans.

This person asked what seems a reasonable question, but was not answered:

http://article.gmane.org/gmane.os.plan9.general/39933

He points out:

"[...] perhaps the option of changing the timezone needs to be included in
the install script if venti is to be installed."


Cheers, and thanks for the assistance guys!