From owner-freebsd-bugs Wed Jan 13 21:48:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20756 for freebsd-bugs-outgoing; Wed, 13 Jan 1999 21:48:42 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from gongshow.masterplan.org (masterplan.powersurfr.com [24.108.38.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20746 for ; Wed, 13 Jan 1999 21:48:41 -0800 (PST) (envelope-from jbg@masterplan.org) Received: from infomat (infomat.precident.com [192.168.4.2]) by gongshow.masterplan.org (8.8.8/8.8.8) with SMTP id WAA11845 for ; Wed, 13 Jan 1999 22:47:29 -0700 (MST) (envelope-from jbg@masterplan.org) Message-Id: <199901140547.WAA11845@gongshow.masterplan.org> From: jbg@masterplan.org (Jason George) To: freebsd-bugs@FreeBSD.ORG Subject: RE: Year 2000 Compliance Organization: The Master Plan Always Fails... Date: Thu, 14 Jan 1999 05:47:48 GMT Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As a complete aside, I was doing some fast hackery today with a Compaq 486/25 (the ugly ones with the built-in monitor) which does NOT have a Y2K-compliant BIOS (ie - 01/01/00 in the CMOS clock turns into January 01/80 under DOS). I have run 1999->2000 "rollovers" with FreeBSD 2.2.8+ on a lot of different hardware that is Y2K-compliant. I haven't encountered a problem yet. I decided to try a rollover on the non-compliant Compaq. I had never done this before, figuring there was no point. I was quite surprised in my results. The Compaq, while running 2.2.8+, rolled over correctly! y2k# date Fri Dec 31 23:53:22 MST 1999 y2k# date Sat Jan 1 00:00:03 MST 2000 y2k# A reboot into the BIOS screen yields a 01/01/00 CMOS date, a reboot under DOS yields a 01/01/80 system date, and a reboot into FreeBSD yields 01/01/2000. Is this just luck? Am I playing with fire here? Have I stumbled onto a new possible source for cheap NATD packet filters for the new millenium? :-) --Jason j.b.georgeieee.org jbgmasterplan.org >> However as the Millennium approaches ye might want to consider to upgrade >> to the latest stable version around Summer to be even more sure that if any >> problems were found they will be fixed by then. >> >> According to core, every version greater than 2.2.6 (so 2.2.7 and onwards >> is truely believed to be 2000 compliant). >> >> I hope this satisfies yer question? > >It does indeed - many thanks. > > >Michael. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message