Date: Tue, 18 Aug 1998 17:28:10 -0500 (EST) From: Alfred Perlstein <bright@www.hotjobs.com> To: Terry Lambert <tlambert@primenet.com> Cc: jbryant@unix.tfs.net, freebsd-hackers@FreeBSD.ORG Subject: Re: proposal to not change time_t Message-ID: <Pine.BSF.3.96.980818172726.17267F-100000@bright.fx.genx.net> In-Reply-To: <199808182040.NAA28432@usr06.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980818172726.17267F-100000>