David Wright wrote:
>
> Quoting Ed Cogburn ([EMAIL PROTECTED]):
> >
> > This isn't exactly true. You can keep your hardware clock on local,
> > and you can tell Linux to use local time (keeping it from messing
> > around). Linux does not set my hardware clock to GMT at shutdown, it
> > sets it with local time, which is what I want because I use ntpdate to
> > update date/time every time I bring up a net connection. Sure,
> > setting up GMT is the Unix(TM) thing to do, but why bother? It knows
> > my timezone, handles daylight savings automatically, and it stays
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> How does it do this? If it changes the hardware clock, I call this
> messing around. The trouble is, the Broken OS also messes around
> and suddenly you've jumped two hours instead of one.. (If it doesn't
> change the hardware clock, then it's not running local time, is it.)
I'll look at this when I have some time, but when my machine shuts
down I see a message saying "hardware clock being updated" or
something like that. This behavior may be part of the ntpdate
package, I didn't consider that possibility.
--
"It is dangerous to be right when the government is wrong." - Voltaire
Ed C.
