From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 23 14:59:21 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED7D416A41F; Fri, 23 Dec 2005 14:59:21 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B7AF43D60; Fri, 23 Dec 2005 14:59:21 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-222-80-189.jan.bellsouth.net [68.222.80.189]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 50ACDDE; Fri, 23 Dec 2005 08:59:20 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 75D2561C21; Fri, 23 Dec 2005 08:59:19 -0600 (CST) Date: Fri, 23 Dec 2005 08:59:19 -0600 From: "Matthew D. Fuller" To: Guy Helmer Message-ID: <20051223145919.GH63497@over-yonder.net> References: <20051222220752.GB45319@ip.net.ua> <43AC0D3F.5050902@palisadesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43AC0D3F.5050902@palisadesys.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: amd64@freebsd.org Subject: Re: Updating i386 in-place to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2005 14:59:22 -0000 On Fri, Dec 23, 2005 at 08:44:15AM -0600 I heard the voice of Guy Helmer, and lo! it spake thus: > Ruslan Ermilov wrote: > > >Yesterday, I was playing updating the i386 6.0-STABLE in-place to > >amd64 (the system was initially running on i386 core, then the disk > >was moved to the Opteron server). It succeeded, but there were > >some fun. The idea I had is to: > > Wow, I'm impressed. I was trying to do an automated, in-place i386 > to amd64 upgrade (without source, though) back in August and never > got to the point of successfully booting an amd64 kernel running > i386 binaries. I did get a good idea, though, that I never followed > up on: Matthew Fuller suggested hijacking the swap partition for a > temporary amd64 root partition (message id > 20050809124756.GA27425@over-yonder.net). Yeah, I like the extra safety margin that gave. I had a known-good i386 partition to boot while I made sure the amd64 one booted, and then a known-good (and pure) amd64 one to fall back on if I screwed up blatting the amd64 stuff over the real partitions. And it gave me an excuse to track down all the loader variables that needed to be set to boot off a different partition, which I've now re-forgotten (2 of 'em, I think, needed to be changed?) I never managed to get the amd64 kernel to load anything i386 in the boot path, either init (for multiuser) or sh (for single-user). This was 5.4, I think (maybe 5.3). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.