From owner-freebsd-chat Wed Nov 19 12:36:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA23804 for chat-outgoing; Wed, 19 Nov 1997 12:36:58 -0800 (PST) (envelope-from owner-freebsd-chat) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA23795 for ; Wed, 19 Nov 1997 12:36:54 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id PAA08739; Wed, 19 Nov 1997 15:36:29 -0500 (EST) Date: Wed, 19 Nov 1997 15:36:29 -0500 (EST) From: John Fieber To: Nate Williams cc: Stephen Roome , freebsd-chat@FreeBSD.ORG Subject: Re: Tell the world about Year 2000 Compliance In-Reply-To: <199711191807.LAA05380@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Nate Williams wrote: > > Finally, what's being done (if any?) to insure that FreeBSD _IS_ and > > _REMAINS_ Year 2000 compliant... e.g. New packages/ports etc. > > The non-use of Cobol. :) I was a little alarmed to find the "2000 compliant" banner. On what basis is the claim made other than the non-use of Cobol? Some time back I grepped the source tree and found a number of places where two digit dates were having 1900 blindly added to them--the internal representation was okay, but stored representations may have problems. These may not be serious problems and they may not be widespread, but I find it a little disturbing how frequently Unixheads brush aside the problem as something that only affects other systems. That sort of arrogance is bound to backfire at some point. Has anyone actually set their system clock forward and done extensive testing? -john