From owner-freebsd-ports@FreeBSD.ORG  Sun Jun 17 14:59:21 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 0F0D116A468;
	Sun, 17 Jun 2007 14:59:21 +0000 (UTC)
	(envelope-from mandrews@bit0.com)
Received: from mindcrime.bit0.com (bit0.com [207.246.88.211])
	by mx1.freebsd.org (Postfix) with ESMTP id BF50213C455;
	Sun, 17 Jun 2007 14:59:20 +0000 (UTC)
	(envelope-from mandrews@bit0.com)
Received: from localhost (localhost.bit0.com [127.0.0.1])
	by mindcrime.bit0.com (Postfix) with ESMTP id 559D9730024;
	Sun, 17 Jun 2007 10:43:04 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bit0.com
Received: from mindcrime.bit0.com ([127.0.0.1])
	by localhost (mindcrime.bit0.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b+iPZLDaGgld; Sun, 17 Jun 2007 10:43:01 -0400 (EDT)
Received: from localhost (localhost.bit0.com [127.0.0.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mindcrime.bit0.com (Postfix) with ESMTP;
	Sun, 17 Jun 2007 10:43:01 -0400 (EDT)
Date: Sun, 17 Jun 2007 10:43:01 -0400 (EDT)
From: Mike Andrews <mandrews@bit0.com>
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20070616222413.GA29804@rot13.obsecurity.org>
Message-ID: <20070617104023.V50590@bit0.com>
References: <6f50eac40706151829g64b8a8abg798f97449c05888f@mail.gmail.com>
	<f4veun$kq4$2@sea.gmane.org>
	<20070616030328.GA17075@rot13.obsecurity.org>
	<f50dkg$m71$1@sea.gmane.org>
	<20070616201921.GA29173@rot13.obsecurity.org>
	<20070616205234.GN2268@deviant.kiev.zoral.com.ua>
	<20070616222413.GA29804@rot13.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-stable@freebsd.org,
	Ivan Voras <ivoras@fer.hr>, freebsd-ports@freebsd.org
Subject: Re: Upgrading to amd64 requires recompilation of ports?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2007 14:59:21 -0000

On Sat, 16 Jun 2007, Kris Kennaway wrote:

>>> I may have had to use the statically linked /rescue to do some things,
>>> I don't remember.  It's not completely trivial, but someone who knows
>>> their way around a FreeBSD system can do it.
>> We did it by using miniroot on swap partition of the system disk.
>> This approach has an advantage of keeping at least one good bootable
>> base system installation in any moment. Also, it allows move in both
>> directions, i.e. i386 <-> amd64.
>
> Yeah, that's a neat trick to remember.  Another trick for doing
> i386->amd64 is to install your new world into a DESTDIR, tar it up,
> put the tarball onto the root filesystem, boot the new amd64 kernel
> into single-user mode and use /rescue/tar to spam the amd64 tarball
> over the i386 world.

I've used the miniroot-on-swap approach before.  Another trick I used this 
week (when I had to do four i386->amd64 migrations) was to build a 
netbootable amd64 system, PXE-boot that, and then installworld to the 
local disks that way.