From owner-freebsd-current Tue Jan 5 15:45:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03198 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:45:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03188 for ; Tue, 5 Jan 1999 15:45:49 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id SAA01910; Tue, 5 Jan 1999 18:45:16 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Tue, 5 Jan 1999 18:45:16 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Peter Jeremy cc: current@FreeBSD.ORG Subject: Re: Y2K, Y 2038? In-Reply-To: <99Jan5.205931est.40326@border.alcanet.com.au> 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 Tue, 5 Jan 1999, Peter Jeremy wrote: > Jonathan Smith wrote: > > Deal with it _now_ before the Y2038 Emergency is upon us and > >the world is freaking out over it. Perhaps an introduction of a 64 bit > >time, > A much simpler change is to make time_t an unsigned long - that gives > us another 68 years grace - by which time I doubt many of us will be > overly concerned :-). Cannot do that. Believe it or not, but you should be able to do calculations involving dates prior to 1/1/70. Perhaps if you first moved the Unix epoch back 30-40 years, but then you're back where you started. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message