Do a "man" on "hwclock". You will see options for adjusting the epoch value
of the clock.
I am not sure if this will fix your problem since I have not updated my
Alcor to the 6.X
stream yet.
Internally, mail has been floating that says on RH 6.1 systems you need to
check the
"date" and then use the "hwclock" to ensure it is correct.
NOTE: I do not know the affects of "hwclock" on the actual hardware clock.
But maybe the
-get/set...epoch options will help.
If you try it, let us all know.
Tim
-----Original Message-----
From: Metod Kozelj [mailto:metod.kozelj@rzs-hm.si]
Sent: Thursday, January 13, 2000 9:17 AM
To: Linux-alpha mailing list
Subject: boot from SRM & system date
Hello,
today I installed linux (RH 6.1) on an alcor system (AlphaStation 600
5/333). Mostly it works right except for system date. It seems that linux
takes wrong UNIX epoch from SRM. date shows some date in 2068, which is
exactly one epoch (2**31 secs) too late.
I wouldn't like to mess with SRM date settings for a while, since for now
this machine has to be dual-boot and I'd like to have correct time under
Digital Unix.
I wonder though, how would one set the epoch to Linux kernel.
BTW, if I run ntpdate, it corrects clock by some seconds, so it seems that
it doesn't know about epoch.
Some ideas?
Regards,
Mkx
---- perl -e 'print
$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:28 EST