Fedora default installs with a shim + grub bootloader on EFI platforms, yet has been shipping systemd-boot in various forms for a number of releases. There are a few howto's which describe how to replace grub with systemd-boot with varying levels of functionality. This should be easier with a formalized default method that can be built upon. This proposal aims to complete the work started with anaconda (inst.sdboot), kickstart (bootloader --sdboot) such that the "everything" media can install a grub free machine.
Owners, do not implement this work until the FESCo vote has explicitly ended. The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.
REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the devel list thread linked above.
+1, will be great to have this option for users who don't want / need GRUB.
+1
+1 because I think this is generally very useful. I have various qualms about implementation details, but nothing blocking.
It doesn't attempt to create unified kernel images, so the existing dnf update, kdumpctl, and make install in a kernel source directory should all work.
I tried to explain this on the mailing list, but this text is still in the Change page. This description is severely misleading: dnf update should work completely fine with UKIs. Kernel make install would also work completely fine if we did ln -sf --relative /usr/bin/kernel-install /usr/sbin/installkernel. I don't know about kdumpctl. I would very much prefer if this was reworded, because users will be confused by the current text.
dnf update
make install
ln -sf --relative /usr/bin/kernel-install /usr/sbin/installkernel
kdumpctl
possibly adding additional space to the EFI system partition during partitioning to guarantee there is sufficient space for the number of bootable kernels active on the machine (~100MB each should be more than sufficient)
Hmm, and what about the XBOOTLDR a.k.a. /boot? If things are set up properly, kernel-install will place kernels there, not in ESP.
/boot
kernel-install
After a week, this is: APPROVED (+4, 0, 0)
Metadata Update from @zbyszek: - Issue tagged with: pending announcement
Announced.
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)