From owner-freebsd-stable Mon Jun 4 18:10:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id 6D47337B401 for ; Mon, 4 Jun 2001 18:10:29 -0700 (PDT) (envelope-from bsddiy@163.net) Received: from William ([192.168.1.98]) by mail.viasoft.com.cn (8.9.3/8.9.3) with ESMTP id JAA02300; Tue, 5 Jun 2001 09:05:36 +0800 Date: Tue, 5 Jun 2001 09:15:20 +0800 From: David Xu X-Mailer: The Bat! (v1.48f) Personal Reply-To: bsddiy@163.net Organization: Viasoft X-Priority: 3 (Normal) Message-ID: <83608845.20010605091520@163.net> To: Jonathan Chen Cc: Matt Dillon , John Polstra , stable@FreeBSD.ORG, Subject: Re[4]: time_t definition is worng In-reply-To: <20010605094735.C40392@itouchnz.itouch> References: <200106012015.NAA17134@freeway.dcfinc.com> <200106012052.f51KqBT29871@vashon.polstra.com> <200106012149.f51LnI289480@earth.backplane.com> <20010605094735.C40392@itouchnz.itouch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Jonathan, Tuesday, June 05, 2001, 5:47:35 AM, you wrote: JC> On Fri, Jun 01, 2001 at 02:49:18PM -0700, Matt Dillon wrote: >> : >> :No, time_t is and always has been 32 bits on all FreeBSD platforms. >> : >> :I agree with Matt that it would be nice if it were 64 bits at least on >> :64-bit platforms. Unfortunately, practically speaking it's too late >> :to make that change now. >> : >> :John >> :-- >> : John Polstra jdp@polstra.com >> >> Not being a user of the alpha port, I can't disagree. But if I were >> I would consider fixing the alpha port now and get it over with >> rather then later. time_t was one of the few things that transported >> naturally to 64 bit platforms, and yet it still managed to get fracked >> up in FreeBSD. This IA32 change from long to int only makes things >> even MORE fracked up then they already were and is a huge mistake. >> >> Rather then further break the IA32 port, if consistency is a goal then >> the alpha port should be fixed instead. JC> When the FreeBSD-alpha port was being done, Satoshi (IIRC) suggested JC> that time_t be made a long for the Alpha; which was a great idea to fix JC> the Epoch-end bug, at least for 64-bit systems. After some discussion, JC> this was not done 'cos Terry Lambert pointed out that the UFS filesystem JC> code depended on a 32-bit time_t. JC> I have no idea just how true this is today, but if it still is so, time_t JC> has to be 32-bit until the UFS code is fixed. JC> Cheers. how about userland time_t becomes 64bits and kernel UFS still has 32bits time_t? this is safe until year beyonds 2038. I believe UFS 32bits time_t will be fixed before 2038 :). this way we needn't applications be recompiled when UFS 32bits time_t changed to 64bits. -- David Xu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message