From owner-freebsd-sparc64@FreeBSD.ORG Fri Jan 23 19:41:58 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 67C9516A4CE for ; Fri, 23 Jan 2004 19:41:58 -0800 (PST) Received: from saturn.criticalmagic.com (saturn.criticalmagic.com [68.213.16.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A489443D1F for ; Fri, 23 Jan 2004 19:41:52 -0800 (PST) (envelope-from richardcoleman@mindspring.com) Received: from mindspring.com (titan.criticalmagic.com [68.213.16.23]) by saturn.criticalmagic.com (Postfix) with ESMTP id F13CA3BD10; Fri, 23 Jan 2004 22:41:51 -0500 (EST) Message-ID: <4011E987.5080205@mindspring.com> Date: Fri, 23 Jan 2004 22:41:59 -0500 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: sparc64@FreeBSD.ORG Subject: Re: 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 Reply-To: richardcoleman@mindspring.com 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:41:58 -0000 Garance A Drosihn wrote: > 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) It sounds to me like we are ready to go. I don't think further waiting will do much good. Good work, by the way. Richard Coleman richardcoleman@mindspring.com