From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5 v5] boot/systemd-boot: new package
Date: Mon, 31 Dec 2018 13:43:05 +0100 [thread overview]
Message-ID: <87pnthsw86.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181226214100.GK14286@scaer> (Yann E. MORIN's message of "Wed, 26 Dec 2018 22:41:00 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> So it would be good to make sure we have a really solid use-case for
>> adding this complexity.
> Peter, care to elaborate your position, since you were advocating also
> for it, earlier? ;-)
One interesting feature it has is that it can bundle the bootloader,
kernel, initramfs and kernel command line into a single EFI binary,
which can be handy for E.G. A/B boot and EFI secure boot.
But with that said, if upstream does not make it easy to build it
seperately, then I'm OK with only allowing it if systemd is built.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-12-31 12:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 8:52 [Buildroot] [PATCH 0/5 v5] systemd-boot: new simple EFI bootloader replacing gummmiboot (branch yem/systemd-boot) Yann E. MORIN
2018-12-26 8:52 ` [Buildroot] [PATCH 1/5 v5] package/meson: never try to run generated target binaries Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 2/5 v5] package/meson: fix CPU familly Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 3/5 v5] core/pkg-infra: allow meson packages to specify custom build rules Yann E. MORIN
2018-12-26 11:36 ` James Hilliard
2018-12-26 12:06 ` Yann E. MORIN
2018-12-27 4:21 ` James Hilliard
2018-12-27 8:23 ` Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 4/5 v5] package/systemd: enable building of systemd-boot Yann E. MORIN
2018-12-26 8:52 ` [Buildroot] [PATCH 5/5 v5] boot/systemd-boot: new package Yann E. MORIN
2018-12-26 9:33 ` Yann E. MORIN
2018-12-26 21:23 ` Thomas Petazzoni
2018-12-26 21:37 ` James Hilliard
2018-12-26 21:43 ` Thomas Petazzoni
2018-12-26 21:52 ` James Hilliard
2018-12-26 21:41 ` Yann E. MORIN
2018-12-26 22:07 ` James Hilliard
2018-12-26 22:12 ` James Hilliard
2018-12-26 22:52 ` James Hilliard
2018-12-27 1:27 ` James Hilliard
2018-12-27 8:49 ` Yann E. MORIN
2018-12-27 9:07 ` James Hilliard
2018-12-27 9:11 ` Yann E. MORIN
2018-12-27 9:13 ` James Hilliard
2018-12-27 10:40 ` Yann E. MORIN
2018-12-27 10:42 ` James Hilliard
2018-12-27 10:57 ` Yann E. MORIN
2018-12-27 11:01 ` James Hilliard
2018-12-29 9:35 ` Yann E. MORIN
2018-12-29 10:50 ` James Hilliard
2018-12-29 11:38 ` Yann E. MORIN
2018-12-29 11:43 ` James Hilliard
2018-12-30 8:44 ` James Hilliard
2018-12-31 10:16 ` Yann E. MORIN
2018-12-31 10:24 ` James Hilliard
2018-12-31 10:36 ` Yann E. MORIN
2018-12-31 12:43 ` Peter Korsgaard [this message]
2019-01-10 23:47 ` Arnout Vandecappelle
2019-01-11 5:59 ` Yann E. MORIN
2019-01-11 6:47 ` James Hilliard
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=87pnthsw86.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.