This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig92540013CB3CC87A951EA889
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Alan McKinnon wrote:
> OK, so it's 32 bit on an amd64 you'll be doing
> =20
Initially yes, I'll look into 64bit as need arises.....
> I would reconfigure the kernel and include things that you know ought t=
o=20
> be there. Then move the disks over and see if it boots. Rinse, repeat, =
> till it does.
> =20
Well, more likely, break the mirror, pull a disk, and test on the new=20
machine, if it works, great, take the old machine down, and move the=20
remaining disk across and drop onto the network, and start the process=20
to change the cflags and emerge -e world...
If not, then most likely move the disk back, let the mirror rebuild, and =
do a fresh install on new disks...
> Now the existing system should work with your new hardware and you can =
> update your CFLAGS and 'emerge -e world' at your leisure.
>
> That's the theory at least anyway :-)
>
> =20
Well, exactly. That is the theory. I want to know the likelihood of=20
success. I know that using mtune=3Dk6-2 means it won't run on anything=20
before a k6-2, and most likely not on anything Intel, due to the symbols =
and optimisations used. What I want is some idea of the chance it will=20
run on a *later* AMD processor. Will an Athlon honour the k6-2=20
optimisations?
--------------enig92540013CB3CC87A951EA889
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH+4kcYSRPRMC0Fr4RAqU7AJwJiHmU+AemrVIBn9Say6tdg/SwbACfXo56
zgGetwlJUrcrVD+KF19WFB8=
=wXe2
-----END PGP SIGNATURE-----
--------------enig92540013CB3CC87A951EA889--
--
gentoo-user@lists.gentoo.org mailing list