That's a good Y3K trick ! Here in the US, 03/01/2000 would be March 1, 2000
( Let's see, we're still
in January on Earth I think) ! Well, I guess 03/01/2000 makes more sense
than 01/03/2000
( as does the Metric system - e.g. 1km=1000 m vs. 1mile=1876 yds or
whatever). It would be even better for 28/12/1999 ( what month would 28 be
on Pluto ) ?
Hehe
"Thomas Ribbrock \(Design/DEG\)" <[EMAIL PROTECTED]> on 01/17/2000 02:02:03
AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: RH 5.0 and 5.2 and 486's
On Fri, Jan 14, 2000 at 11:32:17PM -0500, Larry Mintz wrote:
> Did Y2K effect anyone running RH Linux 5.0/5.2 on a 486 based system ?
Not a 486, but a 386, but that's an old machine, too... :-)
Yep, I had problems with a Dell 333P (386/33) running RHL 5.2. When I
switched on for the first time on 03/01/2000, its hardware clock was
lagging as usual (it was still thinking it was 28/12/1999...), so I
reset the clock using date and hwclock under Linux. Bad move, as I found
out, as on next bootup, the machine had forgotten all it knew about its
hardrive and the BIOS date had reverted to 1991(?!).
I then set the date manually in BIOS to 03/01/2000 and reconfigured the
HD info. Since then, the machine is working perfectly. (Except for that
frigging slow clock... I'll get chrony to take care of that... :-/ ).
However, this will differ from machine to machine, depending on BIOS and
the implementation of the clock, so YMMV.
Cheerio,
Thomas
--
"Look, Ma, no obsolete quotes and plain text only!"
Thomas Ribbrock | http://www.bigfoot.com/~kaytan | ICQ#: 15839919
"You have to live on the edge of reality - to make your dreams come
true!"
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
