From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 23 19:25:54 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FEF016A4CE; Fri, 23 Jan 2004 19:25:54 -0800 (PST) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9759A43D39; Fri, 23 Jan 2004 19:25:52 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i0O3PpO2003107; Fri, 23 Jan 2004 22:25:51 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: Date: Fri, 23 Jan 2004 22:25:50 -0500 To: sparc64@FreeBSD.ORG From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: 64-bit time_t on sparc64 -- what's left to do? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2004 03:25:54 -0000 So, what more needs to be done before we flip the switch to a 64-bit time_t on sparc64? My thoughts would be to: 1) commit the UPDATING.64BTT and installworld_nk files to /usr/src (so it is easier for people to try it). 2) do something with the cvsup64btt-without-gui-16.1h.tbz so it's where it needs to be for people to get to it. (I'm still not quite sure what is appropriate for that) 2a) [wait at least a few days for more feedback] 3) commit the real change to /usr/src/sys/sparc64/include/_types.h and a short blurb in /usr/src/UPDATING which tells sparc64 users that they must read UPDATING.64BTT 4) cross our collective fingers... Right now I'm assuming that "I'm done", unless someone tells me there's some additional steps I should be working on, or tells me of a problem with the installworld_nk script. I don't know how many people have tried that script yet, but I do know a few have and it has worked for them. I do have ideas on how we could make this transition even safer, but I'm certain it will take me at least two more weekends to debug those ideas. Key phrase: "at least two"... (this is bcc'ed to -current, but I expect any discussion to happen on the -sparc64 mailing list) -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu