From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 12 14:28:15 2004 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24AE016A4D0 for ; Mon, 12 Jan 2004 14:28:15 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAF8143D3F for ; Mon, 12 Jan 2004 14:28:13 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i0CKR0LJ001994 for ; Mon, 12 Jan 2004 15:27:00 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Mon, 12 Jan 2004 15:26:59 -0500 To: freebsd-ppc@FreeBSD.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Interest in 64-bit time_t for PPC port? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2004 22:28:15 -0000 The sparc64 port is looking to switch it's time_t definition from 32-bit to 64-bit. No effort at backwards-compatibility, we'll just do a hard-and-fast switch. With a little luck, we may do that this month. We would have to do it before 5.3, or we would have to let it wait until 6.0 (at which point we *will* have to provide backwards-compatibility). We believe we can do that now, because there aren't all that many sparc64 users, and most of them would rather get this change out- of-the-way right now. Would this make sense for the PPC port, too? I am not running freebsd/ppc on anything yet, so I don't think my opinion on this counts for much. If it does seem like a good idea, the writeup in http://people.freebsd.org/~gad/time-64/UPDATING.64BTT and the script in: http://people.freebsd.org/~gad/time-64/installworld_nk should give all the details on what would need to be done. The writeup is not perfect, but it does include a complete and explicit list of the steps which every user should follow to perform the 64-bit update. But it's half-written for people who are *testing* that change (and the installworld_nk script), and half-written as if the change has already taken place. As background, I'll note that the amd64 and ia64 ports are already using a 64-bit time_t. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu