From owner-freebsd-sparc64@FreeBSD.ORG Mon Feb 16 11:31:09 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 3978C16A4CE for ; Mon, 16 Feb 2004 11:31:09 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25D3943D1F for ; Mon, 16 Feb 2004 11:31:09 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 7B502234; Mon, 16 Feb 2004 13:31:08 -0600 (CST) Date: Mon, 16 Feb 2004 13:31:08 -0600 From: Tillman Hodgson To: sparc64@freebsd.org Message-ID: <20040216193108.GE12181@seekingfire.com> References: <40306CE7.6080104@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40306CE7.6080104@mindspring.com> 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: Mon, 16 Feb 2004 19:31:09 -0000 On Mon, Feb 16, 2004 at 02:10:31AM -0500, Richard Coleman wrote: > Garance A Drosihn wrote: > > > >Well, I have done more typing and testing, and it looks like I > >can reliably upgrade a 32-bit time_t system to 64-bit time_t > >even for people who install from NFS-mounted partitions. > > > >I have also expanded the instructions for updating, and tried > >to make them more useful and informative. So there is now the > >writeup, and two useful scripts: > > > >http://people.freebsd.org/~gad/time-64/UPDATING.64BTT > >http://people.freebsd.org/~gad/time-64/installworld_oldk > >http://people.freebsd.org/~gad/time-64/installworld_newk > > > >The 'oldk' script is only needed for installing via NFS mounts. > >The 'newk' script is recommended for anyone doing this upgrade. [Sorry for replying to your reply to Garance rather than replyign directly; I've lost his original email.] When you say "installing via NFS mounts", are you referring to /usr/obj? The reason that I ask that my /usr/src is remote but my /usr/obj is local. If /usr/src being remote marks me as doing an NFS install for the purposes of these scripts, what are the disadvantages (if any) of use the _oldk script? > >Adventurous people are invited to try this for installs on any > >system, and let me know how it goes I plan up upgrade caliban.rospa.ca in the near future and I'll report back how it goes. -T -- The truth of a proposition has nothing to do with its credibility. And vice versa. - Robert Heinlein