One of our members (I cannot mention his name as it was private email) experienced a Y2K failure. Specificially he reported that "hwclock -r" which, I believe, reads the HW clock failed on his RH5.2 system with a 2.2 kernel. I reported this problem this past summer. I also observed it on RH5.1 with a standard kernel. I found the bug in hwclock.c and produced a fix (which I have somewhere). This problem prevents changing the HW clock when it is in this broken state (having the century stuck at "19" with the year "00"). The problem will not happen if you build the RTC (Real Time Counter) into your kernel as this causes hwclock to take a different path around the broken code. You can update your kernel after experiencing the problem and then hwclock will start working. Be mindful of system time so that "make" does not get confused. (This different path corrects for a bad century byte in the broken CMOS clock.) In any case, the program I wrote (that I mentioned on 12/30/1999) corrects the century byte in systems with a broken CMOS clock. Invoking this program a single time after your system has transitioned to 2000 (or after setting the clock back to the old century) will fix the probelm. No reboot is needed. The URL appears below. Please let me know how it works. ftp://ftp.mindspring.com/users/cavu/century.c [Y2K clock fix for Linux] Bob Toxen [EMAIL PROTECTED] http://www.cavu.com http://www.cavu.com/sunset.html [Sunset Computer] Fly-By-Day Consulting, Inc. "Don't go with a fly-by-night outfit!" Failure is not an option! It comes bundled with all Microsoft products (in my opinion). "Linux, a better way to go!"
