diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml
index 0a1543d590..5cd8a38152 100644
--- a/man/systemd-boot.xml
+++ b/man/systemd-boot.xml
@@ -25,47 +25,50 @@
Description
- systemd-boot or sd-boot is a simple
- UEFI boot manager, previously known as gummiboot. It provides
- a graphical menu to select the entry to boot and an editor for the kernel command
- line. systemd-boot is only useful on machines using UEFI.
-
+ systemd-boot (short: sd-boot) is a simple UEFI boot manager. It
+ provides a graphical menu to select the entry to boot and an editor for the kernel command line. systemd-boot
+ supports systems with an UEFI firmware only.
- systemd-boot loads information from the EFI system partition (ESP), usually
- mounted at /boot, /efi, or
- /boot/efi. Configuration file fragments, kernels, initrds,
- other EFI images need to reside on the ESP. Linux kernels must be built with
- to be able to be directly executed as an EFI
- image. systemd-boot will automatically list other boot entries registered as EFI boot
- variables, and a list of kernels from configuration files following the Boot Loader
- Specification located under /loader/entries/ on the
- ESP.
+ systemd-boot loads boot entry information from the EFI system partition (ESP), usually mounted at
+ /boot, /efi, or /boot/efi during OS
+ runtime. Configuration file fragments, kernels, initrds and other EFI images to boot generally need to reside on
+ the ESP. Linux kernels must be built with to be able to be directly executed as an
+ EFI image. During boot systemd-boot automatically assembles a list of boot entries from the following
+ sources:
- kernel-install8
- may be used to copy kernel images onto the ESP and to generate entries compliant
- with the Boot Loader Specification.
- bootctl1
- may be used from a running system to locate the ESP, list available entries, and
- install systemd-boot itself.
+
+ Boot entries defined with Boot Loader
+ Specification description files located in /loader/entries/ on the ESP. These
+ usually describe Linux kernel images with associated initrd images, but alternatively may also describe
+ arbitrary other EFI executables.
- systemd-boot will provide information about the time spent in UEFI firmware
- using the
- Boot Loader Interface.
- This information can be displayed using
+ Unified kernel images following the Boot
+ Loader Specification, as executable EFI binaries in
+ /EFI/Linux/ on the ESP
+
+ The Microsoft Windows EFI boot manager, if installed
+
+ The Apple MacOS X boot manager, if installed
+
+ The EFI Shell binary, if installed
+
+ A reboot into the UEFI firmware setup option, if supported by the firmware
+
+
+ kernel-install8 may be
+ used to copy kernel images onto the ESP and to generate description files compliant with the Boot Loader
+ Specification. bootctl1 may be
+ used from a running system to locate the ESP, list available entries, and install systemd-boot itself.
+
+ systemd-boot will provide information about the time spent in UEFI firmware using the Boot Loader Interface. This
+ information can be displayed using
systemd-analyze1.
-
- Configuration
-
- systemd-boot reads configuration like the timeout and default entry from
- /loader/loader.conf on the ESP and from EFI variables. See
- loader.conf5.
-
-
-
Key bindingsThe following keys may be used in the boot menu:
@@ -171,7 +174,7 @@
789
- Entry number 1 .. 9
+ Boot entry number 1 … 9
@@ -219,6 +222,21 @@
+
+ Files
+
+ The files systemd-boot reads generally reside on the UEFI ESP which is usually mounted to
+ /boot/, /efi/ or /boot/efi during OS
+ runtime. systemd-boot reads runtime configuration such as the boot timeout and default entry from
+ /loader/loader.conf on the ESP (in combination with data read from EFI variables). See
+ loader.conf5. Boot entry
+ description files following the Boot Loader
+ Specification are read from /loader/entries/ on the ESP. Unified kernel boot entries
+ following the Boot
+ Loader Specification are read from /EFI/Linux/ on the ESP.
+
+
See Also