Date: Thu, 09 Oct 2008 08:17:57 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Eitan Adler <eitanadlerlist@gmail.com> Cc: andrew clarke <mail@ozzmosis.com>, freebsd-questions@FreeBSD.org Subject: Re: uptime 2 years! Message-ID: <44y70y7yiy.fsf@lowell-desk.lan> In-Reply-To: <48ECF908.5080100@gmail.com> (Eitan Adler's message of "Wed\, 08 Oct 2008 14\:16\:40 -0400") References: <DAC3662D-4B24-4986-87C3-7113A070A575@ahm-inc.com> <20081008162153.GA80866@icarus.home.lan> <20081008164540.GA78500@ozzmosis.com> <48ECF908.5080100@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eitan Adler <eitanadlerlist@gmail.com> writes: > andrew clarke wrote: >> >> Is FreeBSD 7.1 2038-proof? ;-) >> > > As far as I know the amd64 version is (anyone care to verify/correct?) All 64-bit platforms have 64-bit time_t, so that covers most of the possible problems. Even on 32-bit platforms, the major filesystems use 64-bit times, so the data is good to go on 64-bit systems. And in theory it should be possible to change time_t to unsigned, and get another two-thirds of a century out of it... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y70y7yiy.fsf>