From: rendaw <7e9wc56emjakcm@s.rendaw.me>
To: "Marius Bakke" <mbakke@fastmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Gábor Boskovits" <boskovits@gmail.com>
Cc: 35380-done@debbugs.gnu.org
Subject: bug#35380: disk-image fails to install efi grub
Date: Fri, 3 May 2019 22:18:01 +0900 [thread overview]
Message-ID: <2aac4477-7895-4dbe-0a54-24ff69d17de7@s.rendaw.me> (raw)
In-Reply-To: <87d0l0fqlq.fsf@fastmail.com>
On 5/3/19 7:17 AM, Marius Bakke wrote:
> It would be great to have UEFI support in the <virtual-machine> record,
> mainly for system tests, but I doubt that is what rendaw is after :-)
Yeah, ideally I'd like secure boot from the flashed media but failing
that I'd at least like to be moving closer to it (boot without having to
enable legacy boot).
> That means you can't just take an operating system hard drive from one
> EFI system to another.
I'm absolutely not an expert on UEFI, and it's likely I'm
misinterpreting some of the more subtle points you wrote, but do you
have more information on the NVRAM restriction? I've found a fair
amount of references to making secure boot and UEFI capable media (USB
and CD) around the web so I'm surprised it's not possible to make a
portable UEFI image. Wouldn't that make it difficult to install UEFI
bootloaders on blank systems?
next prev parent reply other threads:[~2019-05-03 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 16:06 bug#35380: disk-image fails to install efi grub rendaw
[not found] ` <handler.35380.B.155594918611499.ack@debbugs.gnu.org>
2019-04-22 17:11 ` bug#35380: Acknowledgement (disk-image fails to install efi grub) rendaw
2019-04-25 8:44 ` bug#35380: disk-image fails to install efi grub Ludovic Courtès
2019-04-25 10:27 ` rendaw
2019-05-01 20:19 ` Ludovic Courtès
2019-05-02 9:05 ` Gábor Boskovits
2019-05-02 15:16 ` Ludovic Courtès
2019-05-02 22:17 ` Marius Bakke
2019-05-03 13:18 ` rendaw [this message]
2019-05-03 15:10 ` Marius Bakke
2019-05-04 3:42 ` rendaw
2019-05-04 14:34 ` 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=2aac4477-7895-4dbe-0a54-24ff69d17de7@s.rendaw.me \
--to=7e9wc56emjakcm@s.rendaw.me \
--cc=35380-done@debbugs.gnu.org \
--cc=boskovits@gmail.com \
--cc=ludo@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).