public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Lowe <agl@wht.com.au>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI
Date: Tue, 20 Nov 2018 12:51:34 +0800	[thread overview]
Message-ID: <505eb8bb-5a43-8fd8-dc04-e77bf9735821@wht.com.au> (raw)

Dear all,
	In the past I had a non UEFI motherboard setup for my Gentoo machine.
The motherboard started failing so I took the opportunity to replace the
motherboard & CPU and also to buy a new SSD thingy to become the home of
my Gentoo install.

	I'm currently running, on a day to day  basis, the older hard disk, on
the new motherboard, but want to speed up the process of getting the new
SSD set up so I can swap over. Rather than booting into the SSD,
starting an emerge, and walking away, in other words, making my machine
useless for any number of hours, am I correct that there is no problem,
vis a vis, old hard disk built on non UEFI machine Vs new SSD built on
UEFI machine, of chrooting[1] from the old environment into new
environment and doing the building whilst I"m doing something productive
within the old environment?

	I just have this little niggling doubt, probably baseless, in the back
of my mind that there maybe something that may cause a problem for the
newly built stuff due to it not being natively booted in UEFI or
something like that when it was built.

	Anyone built their new machines like this who can allay my, probably
baseless, fears?

	Thanks,
		Andrew


[1] Just like in the "Installing the Gentoo base system" part of the
installation doco.


             reply	other threads:[~2018-11-20  4:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  4:51 Andrew Lowe [this message]
2018-11-20  5:12 ` [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI Canek Peláez Valdés
2018-11-20  5:26   ` Andrew Lowe
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=505eb8bb-5a43-8fd8-dc04-e77bf9735821@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