On Monday 27 July 2009 17:35:31 erik quanstrom wrote: > > "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 > > ; man timesync > > TIMESYNC(8) TIMESYNC(8) > > [...] > > -L used with -r to indicate the real time clock is in > local time rather than GMT. This is useful on PCs that > also run the Windows OS. >
I must be stuck in some sort of logic error, so please correct me where I'm wrong: * the Plan 9 installer assumes EDT (UTC -4) * however I live in MST (UTC -7) * thus no matter what, when I set my timezone after the install, the time goes _backward_ X number of hours (EDT is -4, MST is -7; so time goes back by 3 hours) - (this will occur regardless of whether or not -L is used with aux/timesync in termrc) - and so I get those venti errors, due to the fact that previous writes now appear to the system to have occurred in the future. Thanks for baring with me, and I'm probably just being obtuse here - but why doesn't the Plan 9 installer ask and set the appropriate time as one of the first necessary steps of the installation routine?
