Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Jan 2010 13:01:52 +0000
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        nightrecon@hotmail.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Converting i386 to amd64
Message-ID:  <4B4B2140.5020202@infracaninophile.co.uk>
In-Reply-To: <hif4om$amo$1@ger.gmane.org>
References:  <hif4om$amo$1@ger.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig78525F145935713F58380BA7
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Michael Powell wrote:
> Greetings everyone:
>=20
> This is probably a pretty dumb question, but it's never really come up =
for=20
> me before. I am at a crossroads with regard to some hardware upgrades, =
and=20
> for a couple of them I have been putting off making the change to 64 bi=
t.=20
> These are server boxen with no concerns for desktop use.
>=20
> Is it possible to change an i386 install to amd64 without needing to st=
art=20
> from scratch? I was poking around reading some stuff, and ran across th=
is in=20
> in /usr/src/Makefile:
>=20
> # If TARGET=3Dmachine (e.g. ia64, sparc64, ...) is specified you can
> # cross build world for other machine types using the buildworld target=
,
> # and once the world is built you can cross build a kernel using the
> # buildkernel target.
>=20
> Does this mean I can achieve the desired effect with "make buildworld=20
> TARGET=3Damd64", et al? It would be a tremendous time-saver for me.
>=20
> Of course I would follow with a portupgrade -fa and rebuild all ports=20
> afterward.
>=20
> Thanks in advance for the wielding of any clue sticks.  :-)

This sort of process /is/ possible, but it is a lot more involved than
you're anticipating.  Unless you're the sort of person that likes doing
terribly complicated and risky procedures for the hell of it, you are=20
going to be better off just starting from scratch and reinstalling using
an AMD64 .iso.  It's going to be quicker to reinstall anyhow.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW


--------------enig78525F145935713F58380BA7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAktLIUYACgkQ8Mjk52CukIzcGQCeJyjdbtfxEUWb9fTZNL0UDhfU
k74AoII+RQPeP0USBEdZQhQG5OUPs7uN
=RfrD
-----END PGP SIGNATURE-----

--------------enig78525F145935713F58380BA7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B4B2140.5020202>