> Alister Waller wrote:
>
> I have software that relies on a BIOS date and time. (software name is not
> important)
That's okay. Lots of people use MS Bob. ;) I has the same trouble the other
night, and didn't notice until someone emailed me with the short message,
"Marty! Remember it's 88 miles per hour!"
Ahem.
> I reboot, change the bios date and time to be correct - boot, the Linux
> date and time are now wrong so I change them....guess what my bios date and
> time are wrong again.
> Is there something I am missing......
Try the hwclock command.
hwclock --set "blahblahblah" (that one's obvious)
hwclock --hctosys (hardware clock -> system time)
hwclock --systohc (system time -> hardware clock)
You might want to check your battery if it's an oldish machine too, just in
case.
- Jeff
-- [EMAIL PROTECTED] ------------------------------- http://linux.conf.au/ --
Ye shall be cursed to fall in love so easily, and yet be so
cold of heart as never to express it.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
