Very Computer

I own 2 older computers and I run Linux on both of them. One is an ancient
(c. 1993) IBM PC, and the other a 1995 Packrat Bell. Now, the fun
question. I'll have to test both of them for BIOS 2000 compatibility. If
either one fails the simulated 5 minutes to midnight Dec 31 1999 test,
will it cause Linux to crash?

If the motherboard clocks fail the 2000/1900 test and show 1900, I'll have
to backdate the clock 28 years exactly and find in the kernel how the date
is obtained to to have the correction in the kernel for processes to get.
Anyone else already do this backdate operation? If so, is there a HOWTO? I
already know that if I backdate the systems, Winblows software will be 28
years *ed!

--
CAUTION: Email Spam Killer in use. Leave this line in your reply! 152680
                     "A man's car is his battleship"

2106796 bytes of spam mail deleted.           http://www.veryComputer.com/~nospam/

: I own 2 older computers and I run Linux on both of them. One is an ancient
: (c. 1993) IBM PC, and the other a 1995 Packrat Bell. Now, the fun
: question. I'll have to test both of them for BIOS 2000 compatibility. If
: either one fails the simulated 5 minutes to midnight Dec 31 1999 test,
: will it cause Linux to crash?

On none of my systems does a failure of the BIOS to update the century byte
cause the operating system to crash (and I have four different systems that
I have tested.)  Since the date is normally maintained in the kernel, the
Linux date command will show the correct date in the year 2000 *until* the
machine is rebooted, at which point the date will be set back to 1900 until
the BIOS or the operating system changes it.  You may be lucky in your BIOS
that even though it does not change the century byte on the transistion from
1999 to 2000, that if you use the Linux date command to set the year to 2000,
that *will* change the century byte and all is well until the battery for
the clock dies.

Larry

: On none of my systems does a failure of the BIOS to update the century byte
: cause the operating system to crash (and I have four different systems that
: I have tested.)  Since the date is normally maintained in the kernel, the
: Linux date command will show the correct date in the year 2000 *until* the
: machine is rebooted, at which point the date will be set back to 1900 until
: the BIOS or the operating system changes it.  You may be lucky in your BIOS

In my test on my Packrat Bell, the kernel doesn't bother with the century
byte even after the reboot. It's taken care of in the software. :) I now
have to test my ancient IBM with the 486SX-25 in it. Now, that machine
will be interesting, and I'll report my findings like I did in that thread
with my Winblows and Linux Packrat Bell test. That old machine also has an
old (1.2.13) kernel! I'm definite lagging-end here! My Y2K problems will
mostly be found in computers in less-developed countries.

Happy New Year!

--
CAUTION: Email Spam Killer in use. Leave this line in your reply! 152680
                     "A man's car is his battleship"

2106796 bytes of spam mail deleted.           http://www.wwa.com/~nospam/

Lee