Re: system clock workaround
On Thu, 25 May 2000, Owen G. Emry wrote:
> My firewall machine (a trusty old 486 DX4) has a bios that doesn't like the
> year 2000. It isn't a major problem but several things (e.g. make)
> complain, so is there an easy workaround?
> I assume I can just set the real-time clock to, say, 1990, and have the
> internal clock set itself to the RTC + ten years on bootup. What do I have
> to change to accomplish this, or is there a better solution altogether?
I had exactly the same problem with one of my machines. (AWARD-Bios,
switched the year back to 1994 on every reboot since 2000, Unicore offered
me an upgrade for about 50$, hell, that's more than the whole machine
is worth! ;-). I also thought about a solution like the one you mentioned,
until I found out that on potato hwclock there is an option --badyear.
This tells hwclock that it has to manage a faulty BIOS-year-setting. It
then will set it four years back (to be able to cope with leap years), but
set system time on bootup correctly, so everything works fine. So, if you
have potato installed, read the manpage of hwclock.
If you have slink, you can either upgrade the whole system or try
to get an upgrade for hwclock.