From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix@gnu.org
Subject: Re: Installing Guix System on an external hard drive
Date: Fri, 15 Nov 2019 17:23:35 +0100 [thread overview]
Message-ID: <20191115172335.7e3b9002@kompiuter> (raw)
In-Reply-To: <87bltdgpos.fsf@devup.no>
On Fri, 15 Nov 2019 15:49:23 +0100
Marius Bakke <mbakke@fastmail.com> wrote:
> Did you get the same error when you mounted at /boot/efi?
Yes.
> If you want the USB drive to be 'portable', i.e. not tied to a single
> system, you can not use 'grub-efi-bootloader'. The reason is that
> grub-efi relies on updating UEFI firmware variables *on the running
> system*, to make the newly installed bootloader show up in the UEFI
> boot menu.
>
> For the same reason, it is not possible to use it on a non-UEFI
> system.
>
> It would be good to have a 'grub-standalone-bootloader' procedure that
> would write a self-contained UEFI firmware executable to a standard
> location, similar to what Guix does for disk images:
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/vm.scm?id=4dcf32b56b824efcdb181c9f4cc7ee6c8a0ba125#n399
>
> Would you like to try implementing it?
Well, I could try as a Scheme learning exercise, but it would take me
some time, because I'm a fresh Guile coder and the only thing I know
about UEFI is that it has a buggy implementation on my motherboard and
GRUB goes to hell :)
Any hint where could I start?
Jan Wielkiewicz
next prev parent reply other threads:[~2019-11-15 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 22:25 Installing Guix System on an external hard drive Jan Wielkiewicz
2019-11-13 6:53 ` Efraim Flashner
2019-11-13 15:28 ` Jan
2019-11-13 19:15 ` Jan
2019-11-13 19:55 ` Efraim Flashner
2019-11-15 14:49 ` Marius Bakke
2019-11-15 16:23 ` Jan [this message]
2019-11-19 23:14 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191115172335.7e3b9002@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).