From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Gummiboot fixup
Date: Wed, 20 Mar 2019 14:46:35 +0100 [thread overview]
Message-ID: <875zsdek04.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAOR3GqXSxZw3m+OD3FLCFOR0Gi-v3zNJGe2+3Bhy7R6av7LVhQ@mail.gmail.com> (Esben Haabendal's message of "Wed, 20 Mar 2019 13:59:49 +0100")
>>>>> "Esben" == Esben Haabendal <esbenhaabendal@gmail.com> writes:
> On Tue, Mar 19, 2019 at 7:56 PM Peter Korsgaard <peter@korsgaard.com> wrote:
>> Out of interest, what is the use case for using gummiboot? We recently
>> added systemd-boot support, so I was considering removing gummiboot as
>> it is dead upstream.
>>
>> Notice that you currently cannot enable systemd-boot without the rest of
>> systemd, so that may be a disadvantage.
>>
> In this case, I am upgrading a system which is currently using gummiboot.
> Switching to systemd-boot does not seem to bring anything meaningful
> improvements,
> as gummiboot does the job of booting the system.
Ok. Out of interest, what is gummiboot adding over just directly booting
a Linux kernel with CONFIG_EFI_STUB?
> And yes, this is not a systemd system, and transforming the entire
> system to systemd is clearly a big thing compared to just fixing
> building of gummiboot.
> I would prefer if we could keep gummiboot support in buildroot for now.
Fine by me. Will you add yourself to DEVELOPERS for gummiboot?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-03-20 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 11:28 [Buildroot] [PATCH 0/3] Gummiboot fixup Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 1/3] gummiboot: use new official upstream git repository Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 2/3] gummiboot: upgrade to last commit before being removed Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 3/3] gummiboot: fix compatibility with newer glibc versions Esben Haabendal
2019-03-19 21:02 ` Thomas Petazzoni
2019-03-19 18:56 ` [Buildroot] [PATCH 0/3] Gummiboot fixup Peter Korsgaard
[not found] ` <CAOR3GqXSxZw3m+OD3FLCFOR0Gi-v3zNJGe2+3Bhy7R6av7LVhQ@mail.gmail.com>
2019-03-20 13:46 ` Peter Korsgaard [this message]
[not found] ` <CAOR3GqU17TUskOwG_8DfwrcEt_AJcqzgD8=5j1c2Wa+LVveeSg@mail.gmail.com>
2019-03-20 14:36 ` Peter Korsgaard
2019-03-20 15:03 ` Esben Haabendal
2019-03-20 16:30 ` Peter Korsgaard
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=875zsdek04.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 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.