2013-11-13 13:06:13 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
2015-06-18 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2013-11-13 13:06:13 +04:00
2021-12-13 20:27:20 +03:00
<refentry id= "bootctl" conditional= 'HAVE_GNU_EFI'
2015-02-04 05:14:13 +03:00
xmlns:xi="http://www.w3.org/2001/XInclude">
<refentryinfo >
<title > bootctl</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > bootctl</refentrytitle>
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
<refname > bootctl</refname>
2020-10-13 14:40:21 +03:00
<refpurpose > Control EFI firmware boot settings and manage boot loader</refpurpose>
2015-02-04 05:14:13 +03:00
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
2018-06-15 09:40:12 +03:00
<command > bootctl</command>
<arg choice= "opt" rep= "repeat" > OPTIONS</arg>
<arg choice= "req" > COMMAND</arg>
2015-02-04 05:14:13 +03:00
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2020-10-13 14:40:21 +03:00
<para > <command > bootctl</command> can check the EFI firmware and boot loader status, list and manage
available boot loaders and boot loader entries, and install, update, or remove the
<citerefentry > <refentrytitle > systemd-boot</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> boot
loader on the current system.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
2018-06-15 09:40:12 +03:00
<refsect1 >
2020-10-13 14:40:21 +03:00
<title > Generic EFI Firmware/Boot Loader Commands</title>
<para > These commands are available on any EFI system, regardless of the boot loader used.</para>
2018-06-15 09:40:12 +03:00
2020-10-13 14:40:21 +03:00
<variablelist >
2018-06-15 09:40:12 +03:00
<varlistentry >
<term > <option > status</option> </term>
2022-04-04 11:13:16 +03:00
<listitem > <para > Shows brief information about the system firmware, the boot loader that was used to
boot the system, the boot loaders currently available in the ESP, the boot loaders listed in the
firmware's list of boot loaders and the current default boot loader entry. If no command is
2022-04-04 11:45:47 +03:00
specified, this is the implied default.</para>
<para > See the example below for details of the output.</para>
</listitem>
2018-06-15 09:40:12 +03:00
</varlistentry>
2020-10-13 14:40:21 +03:00
2022-04-04 11:13:16 +03:00
<varlistentry >
<term > <option > reboot-to-firmware</option> <optional > <replaceable > BOOL</replaceable> </optional> </term>
<listitem > <para > Query or set the "Reboot-Into-Firmware-Setup" flag of the EFI firmware. Takes a
boolean argument which controls whether to show the firmware setup on next system reboot. If the
argument is omitted shows the current status of the flag, or whether the flag is supported. This
controls the same flag as <command > systemctl reboot --firmware-setup</command> , but is more low-level
and allows setting the flag independently from actually requesting a reboot.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > systemd-efi-options</option> <optional > <replaceable > STRING</replaceable> </optional> </term>
<listitem > <para > When called without the optional argument, prints the current value of the
<literal > SystemdOptions</literal> EFI variable. When called with an argument, sets the variable to
that value. See
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> for the
meaning of that variable.</para> </listitem>
</varlistentry>
</variablelist>
2020-10-13 14:40:21 +03:00
</refsect1>
<refsect1 >
<title > Boot Loader Specification Commands</title>
<para > These commands are available for all boot loaders that implement the <ulink
url="https://systemd.io/BOOT_LOADER_SPECIFICATION">Boot Loader Specification</ulink> and/or the <ulink
url="https://systemd.io/BOOT_LOADER_INTERFACE">Boot Loader Interface</ulink> , such as
<command > systemd-boot</command> .</para>
<variablelist >
<varlistentry >
<term > <option > list</option> </term>
<listitem > <para > Shows all available boot loader entries implementing the <ulink
url="https://systemd.io/BOOT_LOADER_SPECIFICATION">Boot Loader Specification</ulink> , as well as any
other entries discovered or automatically generated by a boot loader implementing the <ulink
2022-04-04 11:45:47 +03:00
url="https://systemd.io/BOOT_LOADER_INTERFACE">Boot Loader Interface</ulink> .
JSON output may be requested with <option > --json=</option> .</para>
2022-03-23 18:08:36 +03:00
2022-04-04 11:45:47 +03:00
<para > See the example below for details of the output.</para>
2022-03-23 18:08:36 +03:00
</listitem>
2020-10-13 14:40:21 +03:00
</varlistentry>
<varlistentry >
<term > <option > set-default</option> <replaceable > ID</replaceable> </term>
<term > <option > set-oneshot</option> <replaceable > ID</replaceable> </term>
2021-10-28 13:15:33 +03:00
<listitem > <para > Sets the default boot loader entry. Takes a single boot loader entry ID string or a glob
pattern as argument. The <option > set-oneshot</option> command will set the default entry only for the next boot,
2022-04-04 11:13:16 +03:00
the <option > set-default</option> will set it persistently for all future boots.</para>
2020-10-13 13:25:59 +03:00
2022-04-04 11:13:16 +03:00
<para > Optionally, the boot loader entry ID may be specified as one of: <option > @default</option> ,
2020-10-13 13:25:59 +03:00
<option > @oneshot</option> or <option > @current</option> , which correspond to the current default boot loader
entry for all future boots, the current default boot loader entry for the next boot, and the currently booted
boot loader entry. These special IDs are resolved to the current values of the EFI variables
<varname > LoaderEntryDefault</varname> , <varname > LoaderEntryOneShot</varname> and <varname > LoaderEntrySelected</varname> ,
see <ulink url= "https://systemd.io/BOOT_LOADER_SPECIFICATION" > Boot Loader Specification</ulink> for details.
These special IDs are primarily useful as a quick way to persistently make the currently booted boot loader
entry the default choice, or to upgrade the default boot loader entry for the next boot to the default boot
2021-10-28 14:00:13 +03:00
loader entry for all future boots, but may be used for other operations too.</para>
<para > If set to <option > @saved</option> the chosen entry will be saved as an EFI variable
on every boot and automatically selected the next time the boot loader starts.</para>
<para > When an empty string ("") is specified as an ID, then the corresponding EFI variable will be unset.
2020-10-13 13:25:59 +03:00
</para> </listitem>
2020-10-13 14:40:21 +03:00
</varlistentry>
2021-10-04 12:25:50 +03:00
<varlistentry >
<term > <option > set-timeout</option> <replaceable > TIMEOUT</replaceable> </term>
<term > <option > set-timeout-oneshot</option> <replaceable > TIMEOUT</replaceable> </term>
<listitem > <para > Sets the boot loader menu timeout in seconds. The <option > set-timeout-oneshot</option>
command will set the timeout only for the next boot. See
<citerefentry > <refentrytitle > systemd.time</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
for details about the syntax of time spans.</para>
<para > If this is set to <option > menu-hidden</option> or <option > 0</option> no menu is shown and
the default entry will be booted immediately, while setting this to <option > menu-force</option>
disables the timeout while always showing the menu. When an empty string ("") is specified the
bootloader will revert to its default menu timeout.</para> </listitem>
</varlistentry>
2020-10-13 14:40:21 +03:00
</variablelist>
</refsect1>
<refsect1 >
<title > <command > systemd-boot</command> Commands</title>
<para > These commands manage the <command > systemd-boot</command> EFI boot loader, and do not work in
conjunction with other boot loaders.</para>
<variablelist >
2018-06-15 09:40:12 +03:00
<varlistentry >
2018-06-22 21:19:27 +03:00
<term > <option > install</option> </term>
2018-06-15 09:40:12 +03:00
2019-02-12 18:22:31 +03:00
<listitem > <para > Installs <command > systemd-boot</command> into the EFI system partition. A copy of
<command > systemd-boot</command> will be stored as the EFI default/fallback loader at
<filename > <replaceable > ESP</replaceable> /EFI/BOOT/BOOT*.EFI</filename> . The boot loader is then added
to the top of the firmware's boot loader list.</para> </listitem>
2018-06-15 09:40:12 +03:00
</varlistentry>
<varlistentry >
2018-06-22 21:19:27 +03:00
<term > <option > update</option> </term>
2018-06-15 09:40:12 +03:00
2018-06-22 21:19:27 +03:00
<listitem > <para > Updates all installed versions of
<citerefentry > <refentrytitle > systemd-boot</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> , if the
available version is newer than the version installed in the EFI system partition. This also includes the EFI
default/fallback loader at <filename > <replaceable > ESP</replaceable> /EFI/BOOT/BOOT*.EFI</filename> . The boot
loader is then added to end of the firmware's boot loader list if missing.</para> </listitem>
2018-06-15 09:40:12 +03:00
</varlistentry>
<varlistentry >
<term > <option > remove</option> </term>
2018-06-22 21:19:27 +03:00
<listitem > <para > Removes all installed versions of <command > systemd-boot</command> from the EFI system partition
and the firmware's boot loader list.</para> </listitem>
2018-06-15 09:40:12 +03:00
</varlistentry>
2019-08-01 18:15:59 +03:00
<varlistentry >
<term > <option > is-installed</option> </term>
<listitem > <para > Checks whether <command > systemd-boot</command> is installed in the ESP. Note that a
single ESP might host multiple boot loaders; this hence checks whether
<command > systemd-boot</command> is one (of possibly many) installed boot loaders — and neither
whether it is the default nor whether it is registered in any EFI variables.</para> </listitem>
</varlistentry>
2019-07-22 15:19:33 +03:00
<varlistentry >
<term > <option > random-seed</option> </term>
<listitem > <para > Generates a random seed and stores it in the EFI System Partition, for use by the
<command > systemd-boot</command> boot loader. Also, generates a random 'system token' and stores it
persistently as an EFI variable, if one has not been set before. If the boot loader finds the random
seed in the ESP and the system token in the EFI variable it will derive a random seed to pass to the
OS and a new seed to store in the ESP from the combination of both. The random seed passed to the OS
is credited to the kernel's entropy pool by the system manager during early boot, and permits
userspace to boot up with an entropy pool fully initialized very early on. Also see
2019-07-22 19:13:26 +03:00
<citerefentry > <refentrytitle > systemd-boot-system-token.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> .</para>
<para > See <ulink url= "https://systemd.io/RANDOM_SEEDS" > Random Seeds</ulink> for further
information.</para> </listitem>
2019-07-22 15:19:33 +03:00
</varlistentry>
2018-06-15 09:40:12 +03:00
</variablelist>
</refsect1>
2019-10-08 18:58:44 +03:00
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
<varlistentry >
<term > <option > --esp-path=</option> </term>
<listitem > <para > Path to the EFI System Partition (ESP). If not specified, <filename > /efi/</filename> ,
<filename > /boot/</filename> , and <filename > /boot/efi/</filename> are checked in turn. It is
recommended to mount the ESP to <filename > /efi/</filename> , if possible.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --boot-path=</option> </term>
<listitem > <para > Path to the Extended Boot Loader partition, as defined in the <ulink
url="https://systemd.io/BOOT_LOADER_SPECIFICATION">Boot Loader Specification</ulink> . If not
specified, <filename > /boot/</filename> is checked. It is recommended to mount the Extended Boot
Loader partition to <filename > /boot/</filename> , if possible.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -p</option> </term>
<term > <option > --print-esp-path</option> </term>
<listitem > <para > This option modifies the behaviour of <command > status</command> . Only prints the path
to the EFI System Partition (ESP) to standard output and exits.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -x</option> </term>
<term > <option > --print-boot-path</option> </term>
<listitem > <para > This option modifies the behaviour of <command > status</command> . Only prints the path
to the Extended Boot Loader partition if it exists, and the path to the ESP otherwise to standard
output and exit. This command is useful to determine where to place boot loader entries, as they are
preferably placed in the Extended Boot Loader partition if it exists and in the ESP otherwise.</para>
<para > Boot Loader Specification Type #1 entries should generally be placed in the directory
<literal > $(bootctl -x)/loader/entries/</literal> . Existence of that directory may also be used as
indication that boot loader entry support is available on the system. Similarly, Boot Loader
Specification Type #2 entries should be placed in the directory <literal > $(bootctl
-x)/EFI/Linux/</literal> .</para>
<para > Note that this option (similar to the <option > --print-booth-path</option> option mentioned
above), is available independently from the boot loader used, i.e. also without
<command > systemd-boot</command> being installed.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --no-variables</option> </term>
<listitem > <para > Do not touch the firmware's boot loader list stored in EFI variables.</para> </listitem>
</varlistentry>
2019-11-19 18:33:22 +03:00
<varlistentry >
<term > <option > --graceful</option> </term>
bootctl: tweak "bootctl update" to be a NOP when boot loader is already current and --graceful is given
Previously, the "bootctl update" logic would refrain from downrgading a
boot loader, but if the boot loader that is installed already matched
the version we could install we'd install it anyway, under the
assumption this was effectively without effect. This behaviour was handy
while developing boot loaders, since installing a modified boot loader
didn't require a version bump.
However, outside of the systems of boot loader developers I don't think
this behaviour makes much sense: we should always emphasize doing
minimal changes to the ESP, hence when an update is supposedly not
necessary, then don't do it. Only update if it really makes sense, to
minimize writes to the ESP. Updating the boot loader is a good thing
after all, but doing so redundantly is not.
Also, downgrade the message about this to LOG_NOTICE, given this
shouldn't be a reason to log.
Finally, exit cleanly in this cases (or if another boot loader is
detected)
2021-07-02 16:16:52 +03:00
<listitem > <para > Ignore failure when the EFI System Partition cannot be found, when EFI variables
cannot be written, or a different or newer boot loader is already installed. Currently only applies
to random seed and update operations.</para> </listitem>
2019-11-19 18:33:22 +03:00
</varlistentry>
2021-03-17 20:58:07 +03:00
<varlistentry >
bootctl: update to new kernel-install semantics
This makes a bunch of closely related changes:
1. The "entry-token" concept already introduced in kernel-install is now
made use of. i.e. specifically there's a new option --entry-token=
that can be used to explicitly select by which ID to identify boot
loader entries: the machine ID, or some OS ID (ID= or IMAGE_ID= from
/etc/os-release, or even some completely different string. The
selected string is then persisted to /etc/kernel/entry-token, so that
kernel-install can find it there.
2. The --make-machine-id-directory= switch is renamed to
--make-entry-directory= since after all it's not necessarily the
machine ID the dir is named after, but can be any other string as
selected by the entry token.
3. This drops all code to make automatic changes to /etc/machine-info.
Specifically, the KERNEL_INSTALL_MACHINE_ID= field is now more
generically implemented in /etc/kernel/entry-token described above,
hence no need to place it at two locations. And the
KERNEL_INSTALL_LAYOUT= field is not configurable by user switch or
similar anyway in bootctl, but only read from
/etc/kernel/install.conf, and hence copying it from one configuration
file to another appears unnecessary, the second copy is fully
redundant. Note that this just drops writing these fields, they'll
still be honoured when already set.
2022-02-10 20:01:36 +03:00
<term > <option > --make-entry-directory=yes|no</option> </term>
<listitem > <para > Controls creation and deletion of the <ulink
url="https://systemd.io/BOOT_LOADER_SPECIFICATION">Boot Loader Specification</ulink> Type #1 entry
directory on the file system containing resources such as kernel images and initial RAM disk images
during <option > install</option> and <option > remove</option> , respectively. The directory is named
after the entry token, as specified with <option > --entry-token=</option> parameter described below,
and is placed immediately below the <varname > $BOOT</varname> root directory (i.e. beneath the file
system returned by the <option > --print-boot-path</option> option, see above). Defaults to
<literal > no</literal> .</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --entry-token=</option> </term>
<listitem > <para > Controls how to name and identify boot loader entries for this OS
installation. Accepted during <option > install</option> , and takes one of <literal > auto</literal> ,
<literal > machine-id</literal> , <literal > os-id</literal> , <literal > os-image-id</literal> or an
arbitrary string prefixed by <literal > literal:</literal> as argument.</para>
<para > If set to <option > machine-id</option> the entries are named after the machine ID of the running
system (e.g. <literal > b0e793a9baf14b5fa13ecbe84ff637ac</literal> ). See
2021-05-10 20:03:49 +03:00
<citerefentry > <refentrytitle > machine-id</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
details about the machine ID concept and file.</para>
bootctl: update to new kernel-install semantics
This makes a bunch of closely related changes:
1. The "entry-token" concept already introduced in kernel-install is now
made use of. i.e. specifically there's a new option --entry-token=
that can be used to explicitly select by which ID to identify boot
loader entries: the machine ID, or some OS ID (ID= or IMAGE_ID= from
/etc/os-release, or even some completely different string. The
selected string is then persisted to /etc/kernel/entry-token, so that
kernel-install can find it there.
2. The --make-machine-id-directory= switch is renamed to
--make-entry-directory= since after all it's not necessarily the
machine ID the dir is named after, but can be any other string as
selected by the entry token.
3. This drops all code to make automatic changes to /etc/machine-info.
Specifically, the KERNEL_INSTALL_MACHINE_ID= field is now more
generically implemented in /etc/kernel/entry-token described above,
hence no need to place it at two locations. And the
KERNEL_INSTALL_LAYOUT= field is not configurable by user switch or
similar anyway in bootctl, but only read from
/etc/kernel/install.conf, and hence copying it from one configuration
file to another appears unnecessary, the second copy is fully
redundant. Note that this just drops writing these fields, they'll
still be honoured when already set.
2022-02-10 20:01:36 +03:00
<para > If set to <option > os-id</option> the entries are named after the OS ID of the running system,
i.e. the <varname > ID=</varname> field of
<citerefentry > <refentrytitle > os-release</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
(e.g. <literal > fedora</literal> ). Similar, if set to <option > os-image-id</option> the entries are
named after the OS image ID of the running system, i.e. the <varname > IMAGE_ID=</varname> field of
<filename > os-release</filename> (e.g. <literal > vendorx-cashier-system</literal> ).</para>
<para > If set to <option > auto</option> (the default), the <filename > /etc/kernel/entry-token</filename>
file will be read if it exists, and the stored value used. Otherwise if the local machine ID is
initialized it is used. Otherwise <varname > IMAGE_ID=</varname> from <filename > os-release</filename>
will be used, if set. Otherwise, <varname > ID=</varname> from <filename > os-release</filename> will be
used, if set.</para>
<para > Unless set to <literal > machine-id</literal> , or when
<option > --make-entry-directory=yes</option> is used the selected token string is written to a file
<filename > /etc/kernel/entry-token</filename> , to ensure it will be used for future entries. This file
is also read by
<citerefentry > <refentrytitle > kernel-install</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
in order to identify under which name to generate boot loader entries for newly installed kernels, or
to determine the entry names for removing old ones.</para>
<para > Using the machine ID for naming the entries is generally preferable, however there are cases
where using the other identifiers is a good option. Specifically: if the identification data that the
machine ID entails shall not be stored on the (unencrypted) <varname > $BOOT</varname> partition, or if
the ID shall be generated on first boot and is not known when the entries are prepared. Note that
using the machine ID has the benefit that multiple parallel installations of the same OS can coexist
on the same medium, and they can update their boot loader entries independently. When using another
identifier (such as the OS ID or the OS image ID), parallel installations of the same OS would try to
use the same entry name. To support parallel installations, the installer must use a different entry
token when adding a second installation.</para> </listitem>
2021-03-17 20:58:07 +03:00
</varlistentry>
2019-10-08 18:58:44 +03:00
<xi:include href= "standard-options.xml" xpointer= "no-pager" />
2022-03-23 18:08:36 +03:00
<xi:include href= "standard-options.xml" xpointer= "json" />
2019-10-08 18:58:44 +03:00
<xi:include href= "standard-options.xml" xpointer= "help" />
<xi:include href= "standard-options.xml" xpointer= "version" />
</variablelist>
</refsect1>
2021-11-30 00:44:01 +03:00
<refsect1 >
<title > Signed .efi files</title>
<para > <command > bootctl</command> <option > install</option> and <option > update</option> will look for a
<command > systemd-boot</command> file ending with the <literal > .efi.signed</literal> suffix first, and copy
that instead of the normal <literal > .efi</literal> file. This allows distributions or end-users to provide
signed images for UEFI SecureBoot.</para>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > Exit status</title>
2018-06-15 09:40:12 +03:00
<para > On success, 0 is returned, a non-zero failure code otherwise.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
2018-06-25 16:08:24 +03:00
<refsect1 >
<title > Environment</title>
2019-02-12 18:22:31 +03:00
<para > If <varname > $SYSTEMD_RELAX_ESP_CHECKS=1</varname> is set the validation checks for the ESP are
relaxed, and the path specified with <option > --esp-path=</option> may refer to any kind of file system on
any kind of partition.</para>
<para > Similarly, <varname > $SYSTEMD_RELAX_XBOOTLDR_CHECKS=1</varname> turns off some validation checks for
the Extended Boot Loader partition.</para>
2018-06-25 16:08:24 +03:00
</refsect1>
2022-04-04 11:45:47 +03:00
<refsect1 >
<title > Examples</title>
<example >
<title > Output from <command > status</command> and <command > list</command> </title>
<programlisting > $ <command > bootctl status</command>
System:
Firmware: UEFI 2.40 (<replaceable > firmware-version</replaceable> ) ← firmware vendor and version
Secure Boot: disabled (setup) ← secure boot status
TPM2 Support: yes
Boot into FW: supported ← does the firmware support booting into itself
Current Boot Loader: ← details about sd-boot or another boot loader
Product: systemd-boot <replaceable > version</replaceable> implementing the <ulink
url="https://systemd.io/BOOT_LOADER_INTERFACE">Boot Loader Interface</ulink>
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✓ Boot loader sets ESP information
ESP: /dev/disk/by-partuuid/01234567-89ab-cdef-dead-beef00000000
File: └─/EFI/systemd/systemd-bootx64.efi
Random Seed: ← random seed used for entropy in early boot
Passed to OS: yes
System Token: set
Exists: yes
Available Boot Loaders on ESP:
ESP: /boot/efi (/dev/disk/by-partuuid/01234567-89ab-cdef-dead-beef00000000)
File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 251
File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 251
Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/…
File: └─/EFI/systemd/systemd-bootx64.efi
Title: Fedora
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/…
File: └─/EFI/fedora/shimx64.efi
Title: Linux-Firmware-Updater
ID: 0x0002
Status: active, boot-order
Partition: /dev/disk/by-partuuid/…
File: └─/EFI/fedora/fwupdx64.efi
Boot Loader Entries:
$BOOT: /boot/efi (/dev/disk/by-partuuid/01234567-89ab-cdef-dead-beef00000000)
Default Boot Loader Entry:
type: Boot Loader Specification Type #1 (.conf)
title: Fedora Linux 36 (Workstation Edition)
id: …
source: /boot/efi/loader/entries/<replaceable > entry-token</replaceable> -<replaceable > kernel-version</replaceable> .conf
version: <replaceable > kernel-version</replaceable>
machine-id: …
linux: /<replaceable > entry-token</replaceable> /<replaceable > kernel-version</replaceable> /linux
initrd: /<replaceable > entry-token</replaceable> /<replaceable > kernel-version</replaceable> /initrd
options: root=…
</programlisting>
<programlisting > $ <command > bootctl list</command>
Boot Loader Entries:
type: Boot Loader Specification Type #1 (.conf)
title: Fedora Linux 36 (Workstation Edition) (default) (selected)
id: …
source: /boot/efi/loader/entries/<replaceable > entry-token</replaceable> -<replaceable > kernel-version</replaceable> .conf
version: <replaceable > kernel-version</replaceable>
machine-id: …
linux: /<replaceable > entry-token</replaceable> /<replaceable > kernel-version</replaceable> /linux
initrd: /<replaceable > entry-token</replaceable> /<replaceable > kernel-version</replaceable> /initrd
options: root=…
type: Boot Loader Specification Type #2 (.efi)
title: Fedora Linux 35 (Workstation Edition)
id: …
source: /boot/efi/EFI/Linux/fedora-<replaceable > kernel-version</replaceable> .efi
version: <replaceable > kernel-version</replaceable>
machine-id: …
linux: /EFI/Linux/fedora-<replaceable > kernel-version</replaceable> .efi
options: root=…
type: Automatic
title: Reboot Into Firmware Interface
id: auto-reboot-to-firmware-setup
source: /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
</programlisting>
<para > In the listing, <literal > (default)</literal> specifies the entry that will be
used by default, and <literal > (selected)</literal> specifies the entry that was
selected the last time (i.e. is currently running).</para>
</example>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > See Also</title>
<para >
2018-06-15 08:25:22 +03:00
<citerefentry > <refentrytitle > systemd-boot</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry> ,
2018-10-12 15:00:20 +03:00
<ulink url= "https://systemd.io/BOOT_LOADER_SPECIFICATION" > Boot Loader Specification</ulink> ,
2019-07-22 15:19:33 +03:00
<ulink url= "https://systemd.io/BOOT_LOADER_INTERFACE" > Boot Loader Interface</ulink> ,
<citerefentry > <refentrytitle > systemd-boot-system-token.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
2015-02-04 05:14:13 +03:00
</para>
</refsect1>
2013-11-13 13:06:13 +04:00
</refentry>
