From owner-freebsd-sparc64@FreeBSD.ORG Mon Feb 16 20:06:17 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 05C5816A4CE for ; Mon, 16 Feb 2004 20:06:17 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E608443D2D for ; Mon, 16 Feb 2004 20:06:16 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 35DAB234; Mon, 16 Feb 2004 22:06:16 -0600 (CST) Date: Mon, 16 Feb 2004 22:06:16 -0600 From: Tillman Hodgson To: sparc64@freebsd.org Message-ID: <20040217040616.GL12181@seekingfire.com> References: <40306CE7.6080104@mindspring.com> <20040216193108.GE12181@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.6i Subject: Re: Back to the Future - 64-bit time_t on sparc64 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: Tue, 17 Feb 2004 04:06:17 -0000 On Mon, Feb 16, 2004 at 04:27:21PM -0500, Garance A Drosihn wrote: > For this specific update (going from 32-bTT to 64-bTT), there is > just a slight increase in risk by running the installworld_oldk > script. If you follow the directions, and if you are ONLY making > the update from 32-bTT to 64-bTT (as described in the directions), > then the risk is pretty close to zero. If you think you're going > to do the 64-bTT change, and AT THE SAME TIME also 'cvsup' another > three weeks-worth of other changes to 5.2-current, then the risk > could be much more serious. I figured as much. I'm currently upgrading to the latest -CURRENT in 32-bTT mode. I'm also going through my ports to see if I can weed out any that I don't need anymore in order to save time reocmpiling later. > This is described in a little detail in the UPDATING.64BTT file. Speaking of which, in that document you mention the problem with portupgrade and note that you have a prebuilt package available for download. Is that necessary, or will a portupgrade of portupgrade itself generally compile fine (allowing one to use the newly compiled version of portupgrade to get the rest of the ports done)? -T -- Page 2: Unix today is nothing less than a worldwide culture, comprising many tools, ideas and customs. - Harley Hahn, _The Unix Companion_