From owner-freebsd-current Tue Jan 5 02:00:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24536 for freebsd-current-outgoing; Tue, 5 Jan 1999 02:00:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24526 for ; Tue, 5 Jan 1999 02:00:48 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Tue, 5 Jan 1999 20:59:31 +1100 Date: Tue, 5 Jan 1999 21:00:12 +1100 From: Peter Jeremy Subject: Re: Y2K, Y 2038? To: current@FreeBSD.ORG Message-Id: <99Jan5.205931est.40326@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 :-). There was a very similar discussion some months ago regarding the timestamp field in the inode (on -hackers from memory). I don't think the discussion went anywhere fruitful. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message