sure... thats why its called plan9 from outer space :)
--
cinap
--- Begin Message ---
On Sat, 27 Jun 2009 05:36:55 -0300
"Federico G. Benavento" <[email protected]> wrote:
> timezones?
I've never heard of a timezone that could make a 9 year difference. Maybe on
Pluto. ;)
>
> On Sat, Jun 27, 2009 at 4:46 AM, Ethan Grammatikidis<[email protected]>
> wrote:
> > On Fri, 26 Jun 2009 17:39:12 -0700
> > John Floren <[email protected]> wrote:
> >
> >> On Fri, Jun 26, 2009 at 4:57 PM, erik quanstrom<[email protected]>
> >> wrote:
> >> >> > > The script runs at boot, the echo tells me that much, but the time
> >> >> > > is not set, perhaps as if timesync -r is not working. To be
> >> >> > > specific the date a few minutes after booting is Sun Jan 2
> >> >> > > 18:30:36 GMT 2000.
> >> >> >
> >> >> > i believe timesync is setting the system clock from /dev/rtc, not the
> >> >> > other way
> >> >> > around.
> >> >>
> >> >> Yeah, that's what I expect timesync to do, but it's doing something
> >> >> strange instead.
> >> >
> >> > i wouldn't classify doing what the man page says it does
> >> > as something "really strange". if you want the converse,
> >> > then just execute "date -n >/dev/rtc".
> >> >
> >> > - erik
> >> >
> >> >
> >>
> >> I'm pretty sure he's *trying* to get the time from /dev/rtc, not
> >> trying to set it.
> >>
> >
> > You'd be right.
> >
> > I've found I don't seem to need timesync, the system time & /dev/rtc alike
> > seem to stay in sync with the host without it, but I'm still curious why
> > timesync -r should mess up the system time so badly.
> >
> > Perhaps /dev/rtc and the system time are linked on some architectures, so
> > that setting one sets the other and so timesync -r gets in a mess. Just a
> > guess.
> >
> > --
> > Ethan Grammatikidis
> > The lyf so short, the craft so long to lerne. -- Chaucer
> >
> >
>
>
>
> --
> Federico G. Benavento
>
--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer
--- End Message ---
