From owner-freebsd-current Fri Jan 1 15:55:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09900 for freebsd-current-outgoing; Fri, 1 Jan 1999 15:55:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nyc-ny79-34.ix.netcom.com (nyc-ny79-34.ix.netcom.com [209.109.229.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09886 for ; Fri, 1 Jan 1999 15:55:52 -0800 (PST) (envelope-from spork@nyc-ny79-34.ix.netcom.com) Received: from spork (helo=localhost) by nyc-ny79-34.ix.netcom.com with local-esmtp (Exim 2.05 #1) id 0zwEO8-00036o-00; Fri, 1 Jan 1999 18:53:52 -0500 Date: Fri, 1 Jan 1999 18:53:52 -0500 (EST) From: Spike Gronim Reply-To: sporkl@ix.netcom.com To: "Steven P. Donegan" cc: current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 Jan 1999, Steven P. Donegan wrote: > Is current Y2K functional? What about 2038? (when time_t struct goes > bonkers on seconds since Jan 1, midnight, 1970)? FreeBSD itself should remain functional on Y2K. Read www.freebsd.org/y2kbug.html for more info. In 2038 32 bit systems are going to run out of room to keep counting seconds. This is 38 years off, and will hopefully be fixed by then. -Spike Gronim sporkl@ix.netcom.com The majority only rules those who let them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message