From owner-freebsd-chat Wed Nov 19 10:08:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA06247 for chat-outgoing; Wed, 19 Nov 1997 10:08:07 -0800 (PST) (envelope-from owner-freebsd-chat) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA06230 for ; Wed, 19 Nov 1997 10:08:03 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA10766; Wed, 19 Nov 1997 11:08:01 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA05380; Wed, 19 Nov 1997 11:07:58 -0700 Date: Wed, 19 Nov 1997 11:07:58 -0700 Message-Id: <199711191807.LAA05380@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Stephen Roome Cc: freebsd-chat@freebsd.org Subject: Re: Tell the world about Year 2000 Compliance In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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. :) Seriously, almost all unix programs store times/date as milliseconds since 1970, so they don't have a Y2K problem, but they have the Year 2038 problem. However, it's hoped that by the time this comes about the number used to store the time will be bumped to a much bigger #, making the problem go away. However, if that doesn't happen *OR* the programs in question aren't recompiled, the problem will be the same for them in 2038. However, by then I won't care since I'll be old and grey. :) :) :) Nate