From 99d51ed9391704da9b3397e395ec8829b6a737be Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 21 Sep 2021 17:28:16 +0200 Subject: [PATCH] man: document the new systemd-boot drop-in driver dir logic --- man/systemd-boot.xml | 28 ++++++++++++++++++++-------- 1 file changed, 20 insertions(+), 8 deletions(-) diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml index 823f2d54405..b7b06bd5eb2 100644 --- a/man/systemd-boot.xml +++ b/man/systemd-boot.xml @@ -280,17 +280,29 @@ usually mounted to /efi/, /boot/ or /boot/efi/ during OS runtime. It also processes files on the Extended Boot Loader partition which is typically mounted to /boot/, if it - exists. systemd-boot reads runtime configuration such as the boot timeout and default + exists. + + 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 and the - Extended Boot Loader partition. Unified kernel boot entries following the loader.conf5. + + Boot entry description files following the Boot Loader Specification are read from - /EFI/Linux/ on the ESP and the Extended Boot Loader partition. Optionally, a random - seed for early boot entropy pool provisioning is stored in /loader/random-seed in - the ESP. + /loader/entries/ on the ESP and the Extended Boot Loader partition. + + Unified kernel boot entries following the Boot Loader Specification are read from + /EFI/Linux/ on the ESP and the Extended Boot Loader partition. + + Optionally, a random seed for early boot entropy pool provisioning is stored in + /loader/random-seed in the ESP. + + During initialization, sd-boot automatically loads all driver files placed in + the /EFI/systemd/drivers/ directory of the ESP. The files placed there must have an + extension of the EFI architecture ID followed by .efi (e.g. for x86-64 this means a + suffix of x64.efi). This may be used to automatically load file system drivers and + similar, to extend the native firmware support.