[systemd-devel] [systemd-commits] 3 commits - .gitignore Makefile.am src/bootchart src/core src/efi-boot-generator src/shared

Frederic Crozat fcrozat at suse.com
Mon Jan 21 04:05:23 PST 2013


Le lundi 21 janvier 2013 à 12:03 +0100, Kay Sievers a écrit :
> On Mon, Jan 21, 2013 at 7:29 AM, Andrey Borzenkov <arvidjaar at gmail.com> wrote:
> 
> >> commit f4ce2b3e5ce93b83f14f8785e205ebb5a9b8c1df
> >> Author: Lennart Poettering <lennart at poettering.net>
> >> Date:   Mon Jan 21 01:02:53 2013 +0100
> >>
> >>     efi: add efi boot generator that automatically mounts the ESP to /boot
> >
> > Has something changed? ESP has always been mounted on /boot/efi, and
> > mounting it on /boot is plain wrong; ESP is shared resource for all OS
> > installed, not private space to place files of this specific
> > installation.
> 
> The Linux kernel acts as an EFI boot loader, if copied to the ESP it
> can be directly executed by the EFI firmware.
> 
> The initramfs and the kernel live in a vendor sub-directory in the ESP
> and are read directly by EFI code, and there is no need for grub2, any
> other additional filesystem driver, raid, network setup, or whatever
> additional code people think they would need to bring up all sorts of
> systems.
> 
> The kernel itself with the initramfs can boot everything, has all the
> filesystem access which is ever needed, there is no need for anything
> else on EFI machines. Even the craziest setups can boot directly out
> of the firmware that way.
> 
> It's the simplest and most efficient setup a system can have.

But this setup is not shim loader/"Secure Boot" compatible. And it will
force most (if not all) distributions to probably "patch" (or disable)
this generator so it behave as it is expected by them (ie /boot/efi).

-- 
Frederic Crozat <fcrozat at suse.com>
SUSE



More information about the systemd-devel mailing list