From: Andrew Lowe <agl@wht.com.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI
Date: Tue, 20 Nov 2018 13:26:14 +0800 [thread overview]
Message-ID: <ef0d3e00-2f0e-593f-d4b7-556e5ae64fdd@wht.com.au> (raw)
In-Reply-To: <CADPrc83p5EGBtNM4LQSfhfXHBT_1Zfzj-MpzLxxofUAtJnGXcg@mail.gmail.com>
On 20/11/18 13:12, Canek Peláez Valdés wrote:
> On Mon, Nov 19, 2018 at 10:51 PM Andrew Lowe <agl@wht.com.au
> <mailto:agl@wht.com.au>> wrote:
>>
>> Dear all,
<snip>
...
...
<snip>
>
> I've done this exact same scenario two or three times by now. However, I
> don't recompile anything, I just rsync the old drive into the new one,
> and then I chroot (or, more often, I systemd-nspawn) into it and update
> the old configuration where necesary. Unless you change from Intel to
> AMD it should be fine (and even then it could be fine, depending on your
> CFLAGS).
>
> Also, have a live USB around to boot into it for emergencies.
>
> Regards.
> --
> Dr. Canek Peláez Valdés
> Profesor de Carrera Asociado C
> Departamento de Matemáticas
> Facultad de Ciencias
> Universidad Nacional Autónoma de México
Canek,
Thanks for the reply. I've fiddled & "optimised" the old install enough
that I want a fresh start so will be compiling. I'm going older AMD to
newer AMD and always have a stick with SysRescue on it within easy reach.
Hopefully all goes well,
Andrew
next prev parent reply other threads:[~2018-11-20 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 4:51 [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI Andrew Lowe
2018-11-20 5:12 ` Canek Peláez Valdés
2018-11-20 5:26 ` Andrew Lowe [this message]
2018-11-20 9:16 ` Neil Bothwick
2018-11-20 9:29 ` Andrew Lowe
2018-11-20 10:51 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef0d3e00-2f0e-593f-d4b7-556e5ae64fdd@wht.com.au \
--to=agl@wht.com.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox