Messages in this thread | | | Date | Tue, 6 Jan 1998 18:30:41 +0100 | From | Harald Koenig <> | Subject | Re: Y2k - Is Linux Ready for the year 2000? |
| |
On Jan 06, Richard B. Johnson wrote:
> > Machines physically have problems. The RTC for example, may not work. > > This may be at least in part a kernel issue. > > Not true. Read the documentation. The current year at offset 0x09, is a > byte in BCD. The current CENTURY at offset 0x32 is a byte in BCD. This > allows time to be kept to 9999. Even the BIOS allows it to be set to > 2099 which is greater than the BIOS time can be kept (2033).
the RTC on my ASUS SP3G switches from Dec 31 1999 to Jan 1 1900.
yes, I can set the date to 2000 in the BIOS setup but this doesn't help for automatic transission (I don't care anyway as the PC is running all the time and I synchronize both the system clock and RTC with a radio clock (but this is still only half of the truth as the radio clock time format (DCF77 in germany) only submits 2 digits for the year so I'll have to check my receiver/decoder programs within the next two years for Y2K-conformance; does anyone know if xntpd with raw dcf77 (parse driver) is Y2K-proof?)).
Harald -- All SCSI disks will from now on ___ _____ be required to send an email notice 0--,| /OOOOOOO\ 24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\ \ \/OOOOOOOOOOOOOOO\ \ OOOOOOOOOOOOOOOOO|// Harald Koenig, \/\/\/\/\/\/\/\/\/ Inst.f.Theoret.Astrophysik // / \\ \ koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
| |