All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] boot/systemd-boot: new package
Date: Sat, 15 Dec 2018 11:49:31 +0100	[thread overview]
Message-ID: <20181215104931.GD2625@scaer> (raw)
In-Reply-To: <87imzvax4i.fsf@dell.be.48ers.dk>

Peter, All,

On 2018-12-15 11:43 +0100, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>  > Also, I wonder if it ever makes sense to provide systemd-boot to
>  > non-systemd init systems to begin with.
> One feature of systemd-boot that some people (E.G. me) might find
> interesting even if they do not use systemd as init system is the fact
> that it comes with an EFI stub loader that allows you to combine Linux
> kernel, hardcoded command line and initramfs into a single (potentially
> signed) EFI PE image with objcopy:
> 
> objcopy \
>   --add-section .cmdline=cmdline --change-section-vma .osrel=0x20000 \
>   --add-section .linux=linux --change-section-vma .linux=0x30000 \
>   --add-section .initrd=initrd --change-section-vma .initrd=0x3000000 \
>   stubx64.efi linux.efi
> 
> For some use cases (E.G. if these are not built by the same defconfigs
> or for A/B boot with different Linux command line) this late binding may
> be preferable to just building a Linux kernel with compile time
> hardcoded command line and embedded initramfs.

Ok, then it makes sense we can have systemd-boot without systemd init.

Let's try to find a solution for that, then.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2018-12-15 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 11:42 [Buildroot] [PATCH v2 1/1] boot/systemd-boot: new package james.hilliard1 at gmail.com
2018-12-15  8:58 ` Yann E. MORIN
2018-12-15  9:12   ` James Hilliard
2018-12-15 10:27     ` Yann E. MORIN
2018-12-15 10:43       ` Peter Korsgaard
2018-12-15 10:47         ` James Hilliard
2018-12-15 10:49         ` Yann E. MORIN [this message]
2018-12-15 10:43       ` James Hilliard
2018-12-15 11:00         ` Yann E. MORIN
2018-12-15 11:09           ` James Hilliard
2018-12-15 13:47             ` Yann E. MORIN

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=20181215104931.GD2625@scaer \
    --to=yann.morin.1998@free.fr \
    --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.