Date: Fri, 23 Dec 2005 21:35:39 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: amd64@freebsd.org Subject: Re: Updating i386 in-place to amd64 Message-ID: <20051223193539.GA31874@ip.net.ua> In-Reply-To: <20051223145919.GH63497@over-yonder.net> References: <20051222220752.GB45319@ip.net.ua> <43AC0D3F.5050902@palisadesys.com> <20051223145919.GH63497@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 23, 2005 at 08:59:19AM -0600, Matthew D. Fuller wrote: > 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: > >=20 > > >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). >=20 > 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?) >=20 Nope, just one, always visible with kenv(1) when I forget it: vfs.root.mountfrom=3D"ufs:/dev/ad0a" Or "boot -a" in loader(8). > 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). >=20 Well, this "somehow" works now. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDrFGLqRfpzJluFF4RAoH8AJ9LDZInGPjXA2RlD9KT9EHpsZfMgQCcCyYQ auDE3GsOtqrC+RMS2sWp4Bg= =mCMc -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051223193539.GA31874>