Its'a feature, not a bug -- the date vs. hwclock part, that is. I just
checked and found that my system does the same thing. Never noticed before
(never tried any flags with hwclock before, in fact). So I read the man
pages, and as it turns out, the -u flag does NOT have the same meaning in
the two apps.
In date, the -u flag asks for a conversion from local time to GMT (the name
we old fogies remember for Universal Time). In hwclock, the -u flag tells
the app that the hardware clock is set for GMT and asks for a conversion
from GMT to local time. (This isn't in the man page for hwclock, BTW, but it
is in the man page for clock(8).)
Ya learn something new every day ....
Don't know about the other questions ... sorry.
At 11:18 PM 4/27/99 +0000, Pankil Richards wrote:
>I'm having problems setting the correct time on my system (Mandrake
>5.3).
>
>The commands "date" and "hwclock" give the identical time, i.e.,
>19:07:06.
>
>However, the commands "date -u" and "hwclock -u" give two very different
>times, i.e., 23:07:06 UTC and 15:07:06, respectively. (Shouldn't both
>these -u type commands give identical UTC times?)
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
