From owner-freebsd-hackers Wed Dec 2 10:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20075 for freebsd-hackers-outgoing; Wed, 2 Dec 1998 10:24:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20070 for ; Wed, 2 Dec 1998 10:24:31 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id NAA05090 for ; Wed, 2 Dec 1998 13:24:17 -0500 (EST) Date: Wed, 2 Dec 1998 13:24:17 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-hackers@FreeBSD.ORG Subject: Year 2k and PC hardware Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Having recently visited the web pages of a number of the hardware vendors of machines I run FreeBSD on, I am a little concerned about some of the older machines. For example, Gateway 2000 refers to BIOS fixes for >= pentium machines that fix the bios access functions for the real time clock. However, they note that the fix does not apply if the OS attempts to access the RTC directly (I'm not sure what this means -- I don't know how the RTC is implemented on PC machines). Similarly, Dell suggested the download of a BIOS upgrade for machines that were 486-class. Needless to say, it appears that no one was particularly interested in how 386-class machines fared. While FreeBSD itself may behave correctly for year 2k problems (presumably the large majority of dates are manipulated and stored as seconds since epoch), it's not clear that it will behave happily on all hardware. I was wondering if anyone had done any testing with FreeBSD on various hardware platforms to see if it did the right thing? We certainly use both newer and older machines with FreeBSD, and incorrect behavior would be most unfortunate. :) With older machines, we don't have duplicates of the machines in all cases, so testing them may be difficult. It might also just be time to retire our 386 machines, but they are very convenient to have around. (I was also unhappy to see that my bank is not very Y2k-ready just yet :( ) Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message