From owner-freebsd-current Sat Jan 2 14:29:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08558 for freebsd-current-outgoing; Sat, 2 Jan 1999 14:29:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arnold.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08553 for ; Sat, 2 Jan 1999 14:29:13 -0800 (PST) (envelope-from leif@swimsuit.internet.dk) Received: from localhost (leif@localhost) by arnold.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id XAA00418; Sat, 2 Jan 1999 23:26:53 +0100 (CET) (envelope-from leif@arnold.swimsuit.internet.dk) Date: Sat, 2 Jan 1999 23:26:51 +0100 (CET) From: Leif Neland To: Matt Curtin cc: sporkl@ix.netcom.com, "Steven P. Donegan" , 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 2 Jan 1999, Matt Curtin wrote: > Spike Gronim writes: > > > 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. > > We'll run out of seconds on 32 bit systems well before 38 years from > now. Consider that some banks are now offering 35 year mortgages, and > that it will be necessary to perform date calculations to the end of > those loans. > > The wishful thinking about it being "fixed by then" is common, but > doesn't really fly. Fixing the problem in the OS isn't a *huge* deal. > (One could change the time() to return a 64 bit value.) The result, > of course, would be dealing with all of the software that expects > time() to return a 32 bit value. Well, instead of changing time(), another function ltime() could be made, which returned 64 bit value instead. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message