From owner-freebsd-hackers Tue Aug 18 14:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29112 for freebsd-hackers-outgoing; Tue, 18 Aug 1998 14:27:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29103 for ; Tue, 18 Aug 1998 14:27:55 -0700 (PDT) (envelope-from bright@www.hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id RAA17884; Tue, 18 Aug 1998 17:28:10 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 18 Aug 1998 17:28:10 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Terry Lambert cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: proposal to not change time_t In-Reply-To: <199808182040.NAA28432@usr06.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG don't we all have to bite the bullet and newfs every so often? ;) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's BSD. -- http://www.freebsd.org/ > How do you propose to deal with the fact that the file timestamp > for FFS is a 32 bit value, and the spare fields that were intended > to be used to resolve the 2039 bug have been stolen to store > nanoseconds? > > Ie: how do you plan to deal with disk files created after 2039? > > > How do you plan to deal with Linux EXT2FS and other FS's that > failed to consider the issue in their design in the first place? > You can't claim compliance fo something you don't control; you > have to simply note it as an exception. > > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message