From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 50676@debbugs.gnu.org
Subject: bug#50676: [core-updates-frozen] Image production is broken.
Date: Wed, 22 Sep 2021 12:37:00 +0200 [thread overview]
Message-ID: <87wnn8hp6b.fsf@gnu.org> (raw)
In-Reply-To: <87a6k7tyik.fsf@gnu.org> (Mathieu Othacehe's message of "Mon, 20 Sep 2021 08:57:39 +0000")
Howdy!
Mathieu Othacehe <othacehe@gnu.org> skribis:
>> drops me in the GRUB rescue shell right from the start, but I think
>> that’s because the command surprisingly builds an EFI image, as can be
>> seen from the generated genimage.cfg:
>
> Yep, that would be because of the Grub stripping issue. Regarding the
> EFI, both the qcow2 and the efi-raw image types produce "hybrid" images
> that have "grub" installed in the MBR-gap and "grub-efi" in the ESP
> partition. This way, those images can be used both on legacy BIOS based
> machines as well as on more modern UEFI machines.
Oh I hadn’t realized there was this fancy hybridation thing.
> Now the image types names can be confusing, and we could rename efi-raw
> and qcow2 to pc-hybrid-raw and pc-hybrid-qcow2 respectively.
OTOH the beauty of those hybrid images is precisely that one doesn’t
need to know that it’s hybrid. Dunno, no strong opinion!
Thanks for explaining,
Ludo’.
next prev parent reply other threads:[~2021-09-22 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 15:09 bug#50676: [core-updates-frozen] Image production is broken Mathieu Othacehe
2021-09-19 22:37 ` Ludovic Courtès
2021-09-20 8:57 ` Mathieu Othacehe
2021-09-20 12:52 ` Mathieu Othacehe
2021-09-22 10:37 ` Ludovic Courtès [this message]
2021-09-24 22:55 ` Ludovic Courtès
2021-09-26 19:40 ` Mathieu Othacehe
2021-09-27 15:57 ` Ludovic Courtès
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=87wnn8hp6b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50676@debbugs.gnu.org \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.