Date: Sat, 2 Jun 2001 20:44:24 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: jdp@polstra.com Cc: arch@freebsd.org Subject: Re: time_t definition is worng Message-ID: <200106030044.UAA58011@khavrinen.lcs.mit.edu> In-Reply-To: <200106022049.f52Kn1W35106@vashon.polstra.com> References: <200106012318.f51NI8w38590@bunrab.catwhisker.org> <200106021739.f52Hd9V03943@earth.backplane.com> <20010602124732.F31257@dragon.nuxi.com> <20010602222626.A26556@student.uu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <200106022049.f52Kn1W35106@vashon.polstra.com> you write: >Since only the kernel mess with the filesystem bits directly, the fact >that a 32-bit time_t is used in FFS needn't be a show-stopper for >moving to a 64-bit type in userland. According to Kirk, the space in FFS that is now used by microsecond timestamps was originally originally put there to prepare for 64-bit time_t. If we made such a change now, we would be stuck translating inode formats back and forth for the forseeable future. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106030044.UAA58011>