Github messages for voidlinux
 help / color / mirror / Atom feed
From: jirutka <jirutka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gummiboot: split *.efi.stub into subpackage
Date: Mon, 12 Jul 2021 12:27:02 +0200	[thread overview]
Message-ID: <20210712102702.2fsEDk1BPJqF2svSPX7TvGVjhs6n-3Ed6ZyBtq0JMrU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31878@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

New comment by jirutka on void-packages repository

https://github.com/void-linux/void-packages/pull/31878#issuecomment-878162363

Comment:
> Why would someone not want the full package?

Because you don’t need any bootloader to boot Linux from UEFI. However, to fully utilize SecureBoot, it’s needed to bundle Linux kernel and initramdisk into a single UEFI executable; there’s where `*.efi.stub` file from the gummiboot package is needed (and only the efi stub, not the gummiboot bootloader).

> And if we want to merge this PR, it should also include a fix to dracut-uefi to depend on the new subpackage.

Yeah, you’re right, I’m gonna added it now.

  parent reply	other threads:[~2021-07-12 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-10  1:18 [PR PATCH] " jirutka
2021-07-12  6:19 ` ericonr
2021-07-12 10:27 ` jirutka [this message]
2021-07-12 10:38 ` [PR PATCH] [Updated] " jirutka
2021-07-12 10:39 ` jirutka
2021-07-12 10:40 ` [PR PATCH] [Updated] " jirutka
2021-07-14 14:46 ` [PR REVIEW] " ericonr
2021-07-14 14:51 ` [PR PATCH] [Updated] " jirutka
2021-07-14 14:51 ` [PR REVIEW] " jirutka
2021-07-14 14:59 ` [PR PATCH] [Merged]: " ericonr

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=20210712102702.2fsEDk1BPJqF2svSPX7TvGVjhs6n-3Ed6ZyBtq0JMrU@z \
    --to=jirutka@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).