I have an AS255/300 with DU/Tru64Unix (4.0D) on one hard drive and
AlphaLinux (RH7.1) on the other.
As I transition from DU to Linux, I find myself booting back and forth
between the two OSs. Unfortunately, each time I reboot, the date/time
gets changed slightly (Linux --> DU) or significantly (DU --> Linux).
Here's a typical scenario:
o Boot Linux
o Reset the software date/time with "# date ..."
o Reset the hardware date/time with "# hwclock --systohc"
o (Use Linux for a while)
o Boot DU
During booting, the following message appears on the console:
"... Preposterous time in TOY clock ..."
After booting, the time is off anywhere from 5 to 40 minutes
o Reset the date/time with "# date ..."
o (Use DU for a while)
o Boot back into Linux
Taking a "peek" in single user mode, the date/time is *way*
ahead in time ... usually with a year of something like 2049.
(I thought the use of "hwclock" was supposed to fix this
behavior as described in various axp-list emails ...)
Note, however, that if I repeatedly reboot into just Linux (DU never
gets control), the date/time are fine. This makes me wonder if the
shutdown/reboot sequence in DU (just before it reboots into Linux)
isn't messing with the clock settings.
Any help with this problem will be *most* appreciated!
--
Prof Kenneth H Jacker khj_at_cs.appstate.edu
Computer Science Dept www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC 28608 USA
Received on Tue Aug 14 2001 - 17:08:34 NZST