From owner-freebsd-questions@FreeBSD.ORG Thu Oct 9 12:18:02 2008 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD13A1065687 for ; Thu, 9 Oct 2008 12:18:02 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id B237D8FC18 for ; Thu, 9 Oct 2008 12:18:02 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 29951 invoked from network); 9 Oct 2008 12:18:02 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Oct 2008 12:18:02 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id 8B73C28449; Thu, 9 Oct 2008 08:17:58 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id C47601CD86; Thu, 9 Oct 2008 08:17:57 -0400 (EDT) To: Eitan Adler References: <20081008162153.GA80866@icarus.home.lan> <20081008164540.GA78500@ozzmosis.com> <48ECF908.5080100@gmail.com> From: Lowell Gilbert Date: Thu, 09 Oct 2008 08:17:57 -0400 In-Reply-To: <48ECF908.5080100@gmail.com> (Eitan Adler's message of "Wed\, 08 Oct 2008 14\:16\:40 -0400") Message-ID: <44y70y7yiy.fsf@lowell-desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: andrew clarke , freebsd-questions@FreeBSD.org Subject: Re: uptime 2 years! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@FreeBSD.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2008 12:18:03 -0000 Eitan Adler 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/