diff --git a/docs/AUTOMATIC_BOOT_ASSESSMENT.md b/docs/AUTOMATIC_BOOT_ASSESSMENT.md index 2fbf86ec6a..b8150b56c3 100644 --- a/docs/AUTOMATIC_BOOT_ASSESSMENT.md +++ b/docs/AUTOMATIC_BOOT_ASSESSMENT.md @@ -9,7 +9,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later systemd provides support for automatically reverting back to the previous version of the OS or kernel in case the system consistently fails to boot. The -[Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting) +[UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting) describes how to annotate boot loader entries with a counter that specifies how many attempts should be made to boot it. This document describes how systemd implements this scheme. @@ -28,7 +28,7 @@ Here's a brief overview of the complete set of components: * The [`systemd-boot(7)`](https://www.freedesktop.org/software/systemd/man/systemd-boot.html) boot loader optionally maintains a per-boot-loader-entry counter described by - the [Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting) + the [UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting) that is decreased by one on each attempt to boot the entry, prioritizing entries that have non-zero counters over those which already reached a counter of zero when choosing the entry to boot. @@ -61,7 +61,7 @@ Here's a brief overview of the complete set of components: ## Details As described in the -[Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting), +[UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/#boot-counting), the boot counting data is stored in the file name of the boot loader entries as a plus (`+`), followed by a number, optionally followed by `-` and another number, right before the file name suffix (`.conf` or `.efi`). diff --git a/docs/BOOT_LOADER_INTERFACE.md b/docs/BOOT_LOADER_INTERFACE.md index 981dd1f551..82dd534a65 100644 --- a/docs/BOOT_LOADER_INTERFACE.md +++ b/docs/BOOT_LOADER_INTERFACE.md @@ -136,7 +136,7 @@ the identifiers as passed in `LoaderEntries`, `LoaderEntryDefault`, names for them in UIs. 1. When boot loader entries are defined through the - [Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/) + [BOOT.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/) files, the identifier should be derived directly from the file name, but with the `.conf` (Type #1 snippets) or `.efi` (Type #2 images) suffix removed. @@ -167,8 +167,8 @@ names for them in UIs. ## Links -[Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification)
-[Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification)
+[UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification)
+[UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification)
[`systemd-boot(7)`](https://www.freedesktop.org/software/systemd/man/systemd-boot.html)
[`bootctl(1)`](https://www.freedesktop.org/software/systemd/man/bootctl.html)
[`systemd-gpt-auto-generator(8)`](https://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html) diff --git a/docs/BUILDING_IMAGES.md b/docs/BUILDING_IMAGES.md index dcae4bb1c9..60b7369a04 100644 --- a/docs/BUILDING_IMAGES.md +++ b/docs/BUILDING_IMAGES.md @@ -66,7 +66,7 @@ boot. For that it's essential to: The [`kernel-install(8)`](https://www.freedesktop.org/software/systemd/man/kernel-install.html) logic used to generate -[Boot Loader Specification Type #1](https://uapi-group.org/specifications/specs/boot_loader_specification/#type-1-boot-loader-specification-entries) +[UAPI.1 Boot Loader Specification Type #1](https://uapi-group.org/specifications/specs/boot_loader_specification/#type-1-boot-loader-specification-entries) entries by default uses the machine ID as stored in `/etc/machine-id` for naming boot menu entries and the directories in the ESP to place kernel images in. This is done in order to allow multiple installations of the same OS on the @@ -207,7 +207,7 @@ it, then format it. in. The `x-systemd.growfs` mount option in `/etc/fstab` is sufficient to enable this logic for specific mounts. Alternatively appropriately set up partitions can set GPT partition flag 59 to request this behaviour, see the - [Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification) + [UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification) for details. If the file system is already grown it executes no operation. 3. Similar, the `systemd-makefs@.service` and `systemd-makeswap@.service` @@ -268,8 +268,8 @@ fields. [`machine-id(5)`](https://www.freedesktop.org/software/systemd/man/machine-id.html)
[`systemd-random-seed(8)`](https://www.freedesktop.org/software/systemd/man/systemd-random-seed.service.html)
[`os-release(5)`](https://www.freedesktop.org/software/systemd/man/os-release.html)
-[Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification)
-[Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification)
+[UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification)
+[UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification)
[`mkosi`](https://github.com/systemd/mkosi)
[`systemd-boot(7)`](https://www.freedesktop.org/software/systemd/man/systemd-boot.html)
[`systemd-repart(8)`](https://www.freedesktop.org/software/systemd/man/systemd-repart.service.html)
diff --git a/docs/ENVIRONMENT.md b/docs/ENVIRONMENT.md index f2a7d25edb..b64d8b0f20 100644 --- a/docs/ENVIRONMENT.md +++ b/docs/ENVIRONMENT.md @@ -234,7 +234,7 @@ All tools: file may be checked for by services run during system shutdown in order to request the appropriate operation from the boot loader in an alternative fashion. Note that by default only boot loader entries which follow the - [Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification) + [UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification) and are placed in the ESP or the Extended Boot Loader partition may be selected this way. However, if a directory `/run/boot-loader-entries/` exists, the entries are loaded from there instead. The directory should @@ -518,7 +518,7 @@ disk images with `--image=` or similar: to load the embedded Verity signature data. If enabled (which is the default), Verity root hash information and a suitable signature is automatically acquired from a signature partition, following the - [Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification). + [UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification). If disabled any such partition is ignored. Note that this only disables discovery of the root hash and its signature, the Verity data partition itself is still searched in the GPT image. @@ -540,7 +540,7 @@ disk images with `--image=` or similar: * `$SYSTEMD_DISSECT_FSTYPE_=` – overrides the file system time to use when mounting the partition of the indicated designator. The `` string shall be one of `ROOT`, `USR`, `HOME`, `SRV`, `ESP`, - `XBOOTLDR`, `TMP`, `VAR` as per the [Discoverable Partitions + `XBOOTLDR`, `TMP`, `VAR` as per the [UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification/). If unspecified the image dissection logic will automatically probe the file system type (subject to `$SYSTEMD_DISSECT_FILE_SYSTEMS`, see above), except @@ -560,8 +560,8 @@ disk images with `--image=` or similar: * `$SYSTEMD_DISSECT_VERITY_GUESS` – takes a boolean. Controls whether to guess the Verity root hash from the partition UUIDs of a suitable pair of data partition and matching Verity partition: the UUIDs two are simply joined and - used as root hash, in accordance with the recommendations in [Discoverable - Partitions + used as root hash, in accordance with the recommendations in [UAPI.2 + Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification). Defaults to true. diff --git a/docs/MOUNT_REQUIREMENTS.md b/docs/MOUNT_REQUIREMENTS.md index c75f7e812d..6ca7bf7cc8 100644 --- a/docs/MOUNT_REQUIREMENTS.md +++ b/docs/MOUNT_REQUIREMENTS.md @@ -11,7 +11,7 @@ This document describes the requirements placed by systemd on the time when various parts of the file system hierarchy must be available and mounted during boot. This document should be read in conjunction with -[Linux File System Hierarchy](https://uapi-group.org/specifications/specs/linux_file_system_hierarchy/), +[UAPI.9 Linux File System Hierarchy](https://uapi-group.org/specifications/specs/linux_file_system_hierarchy/), which describes the role of the mount points discussed here. If the file system backing a mount point is located on external or remote media diff --git a/docs/PORTABLE_SERVICES.md b/docs/PORTABLE_SERVICES.md index 1766865fe0..ec198b4304 100644 --- a/docs/PORTABLE_SERVICES.md +++ b/docs/PORTABLE_SERVICES.md @@ -162,7 +162,7 @@ Specifically, the following requirements are made for an image that can be attac an image with a partition table understood by the Linux kernel with only a single partition defined, or alternatively, a GPT partition table with a set of properly marked partitions following the - [Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification). + [UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification). 3. The image must at least contain one matching unit file, with the right name prefix and suffix (see above). diff --git a/docs/PORTING_TO_NEW_ARCHITECTURES.md b/docs/PORTING_TO_NEW_ARCHITECTURES.md index a4dc6c29dd..63370222e3 100644 --- a/docs/PORTING_TO_NEW_ARCHITECTURES.md +++ b/docs/PORTING_TO_NEW_ARCHITECTURES.md @@ -27,7 +27,7 @@ architecture. partitions. Use `systemd-id128 new -p` to generate new suitable UUIDs you can use for this. Make sure to register your new types in the various functions in `gpt.c`. Also make sure to update the tables in - [Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification) + [UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification) and `man/systemd-gpt-auto-generator.xml` accordingly. 3. If your architecture supports UEFI, make sure to update the `efi_arch` diff --git a/docs/RELEASE.md b/docs/RELEASE.md index 1b7bef0128..cd08db9fb6 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -13,7 +13,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later 4. Update hwdb (`ninja -C build update-hwdb`, `ninja -C build update-hwdb-autosuspend`, commit separately). 5. Update syscall numbers (`ninja -C build update-syscall-tables update-syscall-header`). 6. [RC1] Update library numbers in `meson.build` -7. Update version number in `meson.version` (e.g. from `256~devel` to `256~rc1` or from `256~rc3` to `256`). Note that this uses a tilde (\~) instead of a hyphen (-) because tildes sort lower in version comparisons according to the [version format specification](https://uapi-group.org/specifications/specs/version_format_specification/), and we want `255~rc1` to sort lower than `255`. +7. Update version number in `meson.version` (e.g. from `256~devel` to `256~rc1` or from `256~rc3` to `256`). Note that this uses a tilde (\~) instead of a hyphen (-) because tildes sort lower in version comparisons according to the [UAPI.10 Version Format Specification](https://uapi-group.org/specifications/specs/version_format_specification/), and we want `255~rc1` to sort lower than `255`. 8. Check dbus docs with `ninja -C build update-dbus-docs` 9. Check manpages list with `ninja -C build update-man-rules` 10. Update translation strings (`ninja -C build systemd-pot`, `ninja -C build systemd-update-po`) - drop the header comments from `systemd.pot` + re-add SPDX before committing. If the only change in a file is the 'POT-Creation-Date' field, then ignore that file. diff --git a/docs/ROOTFS_DISCOVERY.md b/docs/ROOTFS_DISCOVERY.md index 8a322a6f9e..1587b2cbf0 100644 --- a/docs/ROOTFS_DISCOVERY.md +++ b/docs/ROOTFS_DISCOVERY.md @@ -15,13 +15,13 @@ components: i.e. [`systemd-boot`](https://www.freedesktop.org/software/systemd/man/latest/systemd-boot.html) that provides interactive and programmatic control of what precisely to boot. It takes care of enumerating all possible boot targets (implementing - the [Boot Loader + the [UAPI.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/)), potentially presenting it to the user in a menu, but otherwise picking an item automatically, implementing boot counting and automatic rollback if desired. -2. A [unified kernel image +2. A [UAPI.5 Unified Kernel Image ("UKI")](https://uapi-group.org/specifications/specs/unified_kernel_image/), i.e. an UEFI PE executable that combines [`systemd-stub`](https://www.freedesktop.org/software/systemd/man/latest/systemd-stub.html), @@ -133,7 +133,7 @@ the same disk. Specifically: ESP as well, in particular below the `/loader/` subdirectory. 2. The UKIs may either be placed in the ESP (below the `/EFI/Linux/` - subdirectory), or in the [Extended Boot Loader + subdirectory), or in the [UAPI.1 Extended Boot Loader Partition](https://uapi-group.org/specifications/specs/boot_loader_specification/#the-partitions) ("XBOOTLDR"), which can be placed on the same disk as the ESP and is also VFAT. XBOOTLDR is an optional concept and it's only *raison d'être* is that @@ -146,7 +146,7 @@ the same disk. Specifically: 3. The `rootfs` is placed on the same disk as the ESP/XBOOTLDR, in a partition marked with a special GPT partition type. Various other well-known types of partitions can be placed next to the `rootfs` and are automatically - discovered and mounted, see the [Discoverable Partitions + discovered and mounted, see the [UAPI.2 Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification/) for details. @@ -179,8 +179,8 @@ each of these resources: [`bootctl`](https://www.freedesktop.org/software/systemd/man/latest/bootctl.html), `efibootmgr` or `kernel-bootcfg`. -2. The `systemd-boot` boot loader may be configured via [`Boot Loader - Specification Type #1`](https://uapi-group.org/specifications/specs/boot_loader_specification/) +2. The `systemd-boot` boot loader may be configured via [UAPI.1 Boot Loader + Specification Type #1](https://uapi-group.org/specifications/specs/boot_loader_specification/) entries to acquire UKIs or similar from other locations. 3. The `initrd` part of the UKI understands the `root=` (and `mount.usr=`) @@ -220,7 +220,7 @@ local disk. This can happen at each of these three components: `rootfs` from HTTP sources](https://www.freedesktop.org/software/systemd/man/latest/systemd-import-generator.html), either in a GPT disk image (specifically: - [DDIs](https://uapi-group.org/specifications/specs/discoverable_disk_image/), + [UAPI.3 DDIs](https://uapi-group.org/specifications/specs/discoverable_disk_image/), with `.raw` suffix) or in a `.tar` file, which are placed in system RAM and then booted into (these downloads can be downloaded in compressed form and are automatically decompressed on-the-fly). This of course requires diff --git a/docs/TPM2_PCR_MEASUREMENTS.md b/docs/TPM2_PCR_MEASUREMENTS.md index b05739a8c7..45ce6091ce 100644 --- a/docs/TPM2_PCR_MEASUREMENTS.md +++ b/docs/TPM2_PCR_MEASUREMENTS.md @@ -17,7 +17,7 @@ to systemd's UEFI-mode measurements, and if the latter are not done the former aren't made either. See -[Linux TPM PCR Registry](https://uapi-group.org/specifications/specs/linux_tpm_pcr_registry/) +[UAPI.7 Linux TPM PCR Registry](https://uapi-group.org/specifications/specs/linux_tpm_pcr_registry/) for an overview of PCRs. systemd will measure to PCRs 5 (`boot-loader-config`), 11 (`kernel-boot`), @@ -108,8 +108,8 @@ trailing NUL bytes). ### PCR 11, `EV_IPL`, PE section name A measurement is made for each PE section of the UKI that is defined by the -[UKI -specification](https://uapi-group.org/specifications/specs/unified_kernel_image/), +[UAPI.5 UKI +Specification](https://uapi-group.org/specifications/specs/unified_kernel_image/), in the canonical order described in the specification. Happens once for each UKI-defined PE section of the UKI, in the canonical UKI diff --git a/man/bootctl.xml b/man/bootctl.xml index cbe735437f..b317d84020 100644 --- a/man/bootctl.xml +++ b/man/bootctl.xml @@ -81,7 +81,7 @@ These commands are available for all boot loaders that implement the Boot + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification, such as systemd-boot. @@ -90,7 +90,7 @@ Shows all available boot loader entries implementing the Boot Loader Specification, as well as any + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification, as well as any other entries discovered or automatically generated by a boot loader implementing the Boot Loader Interface. JSON output may be requested with . @@ -126,7 +126,7 @@ Boot Loader Interface Commands These commands are available for all boot loaders that implement the Boot Loader Specification and the UAPI.1 Boot Loader Specification and the Boot Loader Interface, such as systemd-boot. @@ -152,7 +152,7 @@ boot loader entry. These special IDs are resolved to the current values of the EFI variables LoaderEntryDefault, LoaderEntrySysFail, LoaderEntryOneShot and LoaderEntrySelected, see - Boot Loader Specification for details. + UAPI.1 Boot Loader Specification 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 loader entry for all future boots, but may be used for other operations too. @@ -314,7 +314,7 @@ are applied to file system in the indicated disk image. This option is similar to , but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition - table, following the Discoverable Partitions + table, following the UAPI.2 Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. @@ -444,7 +444,7 @@ Controls creation and deletion of the Boot Loader Specification Type #1 entry + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification Type #1 entry directory on the file system containing resources such as kernel and initrd images during and , respectively. The directory is named after the entry token, as specified with parameter described below, and is @@ -705,7 +705,7 @@ Boot Loader Entries: See Also systemd-boot7 - Boot Loader Specification + UAPI.1 Boot Loader Specification Boot Loader Interface systemd-boot-random-seed.service8 diff --git a/man/coredumpctl.xml b/man/coredumpctl.xml index 9315679f07..fa771a5c40 100644 --- a/man/coredumpctl.xml +++ b/man/coredumpctl.xml @@ -306,8 +306,9 @@ are applied to file system in the indicated disk image. This option is similar to , but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition - table, following the Discoverable Partitions - Specification. For further information on supported disk images, see + table, following the UAPI.2 + Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. diff --git a/man/file-hierarchy.xml b/man/file-hierarchy.xml index 7c5e5e523f..86315cd0ce 100644 --- a/man/file-hierarchy.xml +++ b/man/file-hierarchy.xml @@ -25,12 +25,11 @@ Operating systems using the systemd1 system and - service manager are organized based on a file system hierarchy inspired by UNIX, - as described in - Linux File System Hierarchy. - Additional requirements on when given parts of the hierarchy - must be available during boot are listed in - Mount Requirements. + service manager are organized based on a file system hierarchy inspired by UNIX, as described in UAPI.9 Linux File System + Hierarchy. Additional requirements on when given parts of the hierarchy + must be available during boot are listed in Mount + Requirements. Many of the paths described here can be queried with the diff --git a/man/journalctl.xml b/man/journalctl.xml index 82a0c07bdb..933d56a38e 100644 --- a/man/journalctl.xml +++ b/man/journalctl.xml @@ -193,7 +193,7 @@ option is similar to , but operates on file systems stored in disk images or block devices, thus providing an easy way to extract log data from disk images. The disk image should either contain just a file system or a set of file systems within a GPT partition table, following - the Discoverable Partitions + the UAPI.2 Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. diff --git a/man/kernel-install.xml b/man/kernel-install.xml index 0603292c3e..3327f5c8b8 100644 --- a/man/kernel-install.xml +++ b/man/kernel-install.xml @@ -109,7 +109,7 @@ The third argument directly refers to the path where to place kernel images, initrd images and other resources for - Boot + UAPI.1 Boot Loader Specification Type #1 entries (the "entry directory"). If other boot loader schemes are used the parameter may be ignored. @@ -141,7 +141,7 @@ $BOOT/ENTRY-TOKEN/KERNEL_VERSION/INITRD-FILE. This can also be used to prepend microcode before the actual initrd. It also creates a boot loader entry according to the - Boot Loader Specification + UAPI.1 Boot Loader Specification (Type #1) in $BOOT/loader/entries/ENTRY-TOKEN-KERNEL-VERSION.conf. The title of the entry is the PRETTY_NAME parameter specified in @@ -290,7 +290,7 @@ The <varname>$BOOT</varname> partition - The partition where the kernels and Boot + The partition where the kernels and UAPI.1 Boot Loader Specification snippets are located is called $BOOT. kernel-install determines the location of this partition by checking /efi/, /boot/, and /boot/efi/ in turn. The @@ -310,7 +310,7 @@ Controls creation and deletion of the - Boot Loader Specification + UAPI.1 Boot Loader Specification Type #1 entry directory on the file system containing resources such as kernel and initrd images during and , respectively. The directory is named after the entry token, and is placed immediately below the boot root directory. When @@ -410,7 +410,7 @@ are applied to the file system in the indicated disk image. This option is similar to , but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition - table, following the Discoverable Partitions + table, following the UAPI.2 Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. @@ -504,7 +504,7 @@ bls - Standard Boot Loader + Standard UAPI.1 Boot Loader Specification Type #1 layout, compatible with systemd-boot7: entries in @@ -520,7 +520,7 @@ uki Standard Boot Loader + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification Type #2 layout, compatible with systemd-boot7: unified kernel images under $BOOT/EFI/Linux as @@ -787,7 +787,7 @@ depmod8 systemd-boot7 ukify1 - Boot Loader Specification + UAPI.1 Boot Loader Specification diff --git a/man/loader.conf.xml b/man/loader.conf.xml index ef358f7e68..56026da20d 100644 --- a/man/loader.conf.xml +++ b/man/loader.conf.xml @@ -51,7 +51,7 @@ and type #2 (ESP/EFI/Linux/*.uki and XBOOTLDR/EFI/Linux/*.uki). Those files are described by the - Boot Loader + UAPI.1 Boot Loader Specification. Note: the behaviour of systemd-boot is also influenced by EFI variables. Some of diff --git a/man/repart.d.xml b/man/repart.d.xml index 22d50e2c63..e83ed34f79 100644 --- a/man/repart.d.xml +++ b/man/repart.d.xml @@ -238,7 +238,7 @@ x86 (32-bit, aka i386) and x86-64 (64-bit, aka amd64). Most of the partition type UUIDs listed above are defined in the Discoverable Partitions + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification. @@ -780,7 +780,7 @@ Configures the No-Auto, Read-Only and Grow-File-System partition flags (bit 63, 60 and 59) of the partition table entry, as defined by the Discoverable Partitions Specification. Only + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification. Only available for partition types supported by the specification. This option is a friendly way to set bits 63, 60 and 59 of the partition flags value without setting any of the other bits, and may be set via Flags= too, see above. @@ -1007,7 +1007,7 @@ associated with it. For example, distributions can use this to implement $BOOT as defined in the - Boot Loader + UAPI.1 Boot Loader Specification. Distributions may prefer to use the ESP as $BOOT whenever possible, but to adhere to the spec XBOOTLDR must sometimes be used instead. So, they should create two definitions: the first defining an ESP big enough to hold just the bootloader, and a second for diff --git a/man/standard-options.xml b/man/standard-options.xml index d07ea4a09a..d6d0c52921 100644 --- a/man/standard-options.xml +++ b/man/standard-options.xml @@ -137,7 +137,7 @@ Path to the Extended Boot Loader partition, as defined in the - Boot Loader Specification. + UAPI.1 Boot Loader Specification. If not specified, /boot/ is checked. It is recommended to mount the Extended Boot Loader partition to /boot/, if possible. diff --git a/man/systemctl.xml b/man/systemctl.xml index a290e990e5..eae6442f58 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -1755,7 +1755,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err To load a kernel, an enumeration is performed following the - Boot Loader Specification, + UAPI.1 Boot Loader Specification, and the default boot entry is loaded. For this step to succeed, the system must be using UEFI and the boot loader entries must be configured appropriately. bootctl list may be used to list boot entries, see @@ -2646,7 +2646,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err are applied to file system in the indicated disk image. This option is similar to , but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition - table, following the Discoverable Partitions + table, following the UAPI.2 Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index 927748bdc5..e64f9be57e 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -966,7 +966,7 @@ stored sock 0:8 4213190 - socket:[4213190] ro This command analyzes the specified image policy string, as per systemd.image-policy7. The policy is normalized and simplified. For each currently defined partition identifier (as per the Discoverable + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification) the effect of the image policy string is shown in tabular form. diff --git a/man/systemd-bless-boot.service.xml b/man/systemd-bless-boot.service.xml index eb1d345fb8..715ff6f844 100644 --- a/man/systemd-bless-boot.service.xml +++ b/man/systemd-bless-boot.service.xml @@ -36,15 +36,15 @@ detects that systemd-boot7 style boot counting is used. - Internally, the service operates based on the LoaderBootCountPath EFI variable (of the - vendor UUID 4a67b082-0a4c-41cf-b6c7-440b29bb8c4f), which is passed from the boot loader to the - OS. It contains a file system path (relative to the EFI system partition) of the Boot Loader Specification compliant boot loader entry - file or unified kernel image file that was used to boot up the - system. systemd-bless-boot.service removes the two "tries done" and "tries left" numeric boot - counters from the filename, which indicates to future invocations of the boot loader that the entry has completed - booting successfully at least once. (This service will hence rename the boot loader entry file or unified kernel - image file on the first successful boot.) + Internally, the service operates based on the LoaderBootCountPath EFI variable + (of the vendor UUID 4a67b082-0a4c-41cf-b6c7-440b29bb8c4f), which is passed from the + boot loader to the OS. It contains a file system path (relative to the EFI system partition) of the + UAPI.1 Boot Loader + Specification compliant boot loader entry file or unified kernel image file that was used to boot + up the system. systemd-bless-boot.service removes the two "tries done" and "tries + left" numeric boot counters from the filename, which indicates to future invocations of the boot loader + that the entry has completed booting successfully at least once. (This service will hence rename the boot + loader entry file or unified kernel image file on the first successful boot.) diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml index c465d4f4f3..0924b4ee88 100644 --- a/man/systemd-boot.xml +++ b/man/systemd-boot.xml @@ -39,12 +39,12 @@ Boot entries defined with Boot Loader Specification Type #1 + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification Type #1 description files located in /loader/entries/ on the ESP and the Extended Boot Loader Partition. These usually describe Linux kernel images with associated initrd images, but alternatively may also describe other arbitrary EFI executables. - Unified kernel images, Boot + Unified kernel images, UAPI.1 Boot Loader Specification Type #2, which are executable EFI binaries in /EFI/Linux/ on the ESP and the Extended Boot Loader Partition. @@ -373,11 +373,11 @@ loader.conf5. Boot entry description files following the Boot Loader Specification are read from + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification are read from /loader/entries/ on the ESP and the Extended Boot Loader partition. Unified kernel boot entries following the Boot Loader Specification are read from + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 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 @@ -657,7 +657,7 @@ uki-url http://example.com/somedir/fooos.efi Boot Counting systemd-boot implements a simple boot counting mechanism on top of the Boot Loader Specification, for automatic and unattended + url="https://uapi-group.org/specifications/specs/boot_loader_specification">UAPI.1 Boot Loader Specification, for automatic and unattended fallback to older kernel versions/boot loader entries when a specific entry continuously fails. Any boot loader entry file and unified kernel image file that contains a + followed by one or two numbers (if two they need to be separated by a -), before the .conf or @@ -742,7 +742,7 @@ uki-url http://example.com/somedir/fooos.efi systemd-boot-random-seed.service8 kernel-install8 systemd-stub7 - Boot Loader Specification + UAPI.1 Boot Loader Specification Boot Loader Interface TPM2 PCR Measurements Made by systemd diff --git a/man/systemd-cryptenroll.xml b/man/systemd-cryptenroll.xml index e27ae4288e..7d39426b1c 100644 --- a/man/systemd-cryptenroll.xml +++ b/man/systemd-cryptenroll.xml @@ -84,8 +84,8 @@ , described below. - See Linux TPM - PCR Registry for an authoritative list of PCRs and how they are updated. The table below + See UAPI.7 Linux + TPM PCR Registry for an authoritative list of PCRs and how they are updated. The table below contains a quick reference, describing in particular the PCRs modified by systemd. @@ -218,7 +218,7 @@ through the certificates measured into PCR 7. Validation through certificates hashes is typically preferable over validation through direct measurements as it is less brittle in context of OS/firmware updates: the measurements will change on every update, but signatures should remain unchanged. See the - Linux TPM PCR + UAPI.7 Linux TPM PCR Registry for more discussion. diff --git a/man/systemd-dissect.xml b/man/systemd-dissect.xml index c52de5f454..669cea96f4 100644 --- a/man/systemd-dissect.xml +++ b/man/systemd-dissect.xml @@ -93,7 +93,7 @@ OS disk images containing a GPT partition table envelope, with partitions marked - according to the Discoverable Partitions + according to the UAPI.2 Discoverable Partitions Specification. OS disk images containing just a plain file-system without an enveloping partition @@ -144,7 +144,7 @@ Mount the specified OS image to the specified directory. This will dissect the image, determine the OS root file system — as well as possibly other partitions — and mount them to the specified directory. If the OS image contains multiple partitions marked with the Discoverable Partitions Specification + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification multiple nested mounts are established. This command expects two arguments: a path to an image file and a path to a directory where to mount the image. @@ -421,7 +421,7 @@ or ) the file systems contained in the OS image are automatically grown to their partition sizes, if bit 59 in the GPT partition flags is set for partition types that are defined by the Discoverable Partitions Specification. This + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification. This behavior may be switched off using . File systems are grown automatically on access if all of the following conditions are met: @@ -492,7 +492,7 @@ specifies a path to a file with the Verity data to use for the OS image, in case it is stored in a detached file. It is recommended to embed the Verity data directly in the image, using the Verity mechanisms in the Discoverable Partitions Specification. + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification. @@ -651,7 +651,7 @@ systemd-nspawn1 systemd.exec5 systemd.v7 - Discoverable Partitions Specification + UAPI.2 Discoverable Partitions Specification mount8 umount8 fdisk8 diff --git a/man/systemd-firstboot.xml b/man/systemd-firstboot.xml index 26ce757174..86a85f0bf2 100644 --- a/man/systemd-firstboot.xml +++ b/man/systemd-firstboot.xml @@ -117,7 +117,7 @@ are applied to file system in the indicated disk image. This is similar to but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition table, following the - Discoverable Partitions + UAPI.2 Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. diff --git a/man/systemd-gpt-auto-generator.xml b/man/systemd-gpt-auto-generator.xml index 00a6b11234..398076abc7 100644 --- a/man/systemd-gpt-auto-generator.xml +++ b/man/systemd-gpt-auto-generator.xml @@ -36,7 +36,7 @@ (XBOOTLDR), and swap partitions and creates mount and swap units for them, based on the partition type GUIDs of GUID partition tables (GPT). See UEFI Specification, chapter 5 for more details. It implements the Discoverable + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification. Note that this generator has no effect on non-GPT systems. It will also not create mount point @@ -138,7 +138,7 @@ … Root partitions for other architectures / - The first partition with the type UUID matching the architecture, located on the same disk as the ESP used for booting, is used as the root file system /. For the full list and constant values, see Discoverable Partitions Specification. + The first partition with the type UUID matching the architecture, located on the same disk as the ESP used for booting, is used as the root file system /. For the full list and constant values, see UAPI.2 Discoverable Partitions Specification. SD_GPT_HOME @@ -252,7 +252,7 @@ Mount and automount units for the EFI System Partition (ESP) and Extended Boot Loader Partition (XBOOTLDR) are generated on EFI systems. If the disk contains an XBOOTLDR partition, as defined in the - Boot Loader + UAPI.1 Boot Loader Specification, it is made available at /boot/. This generator creates an automount unit; the mount will only be activated on-demand when accessed. The mount point will be created if necessary. @@ -354,7 +354,7 @@ automatic discovery of the root partition based on GPT partition information is enabled. This is a superset of root=gpt-auto, as it automatically configures Verity partitions (including signature-based setup) following the logic defined for that in the Discoverable + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification/">UAPI.2 Discoverable Partitions Specification. Moreover it takes the configured image policy and image filter into account for all partition types, including the root file system. root=dissect will wait for the factory reset phase to be completed if it is in effect before activating the root file diff --git a/man/systemd-id128.xml b/man/systemd-id128.xml index 27ad753048..d8f49ca3d7 100644 --- a/man/systemd-id128.xml +++ b/man/systemd-id128.xml @@ -96,7 +96,7 @@ version 255. var-partition-uuid prints a UUID which, following the Discoverable + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification, should be used as the GPT partition UUID for /var/, being derived from the GPT partition type, keyed by the local /etc/machine-id. Added in version 257. diff --git a/man/systemd-import-generator.xml b/man/systemd-import-generator.xml index 9435650d81..b09ea93f1a 100644 --- a/man/systemd-import-generator.xml +++ b/man/systemd-import-generator.xml @@ -128,7 +128,7 @@ from downloaded disk images. This is only supported for raw disk images. Note when this option is used with the purpose of mounting a disk image conforming to the - Discoverable + UAPI.3 Discoverable Disk Image Specification as root file system, and the automatic GPT partition discovery logic as implemented by systemd-gpt-auto-generator8 diff --git a/man/systemd-measure.xml b/man/systemd-measure.xml index 755d84fe47..ce19840088 100644 --- a/man/systemd-measure.xml +++ b/man/systemd-measure.xml @@ -34,7 +34,7 @@ systemd-measure is a tool that may be used to pre-calculate and sign the expected TPM2 PCR 11 values that should be seen when a Linux Unified Kernel Image + url="https://uapi-group.org/specifications/specs/unified_kernel_image/">UAPI.5 Unified Kernel Image (UKI) based on systemd-stub7 is booted up. It accepts paths to the ELF kernel image file, initrd image file, devicetree file, kernel diff --git a/man/systemd-mountfsd.service.xml b/man/systemd-mountfsd.service.xml index 81d02d3d4f..7cc607c4c5 100644 --- a/man/systemd-mountfsd.service.xml +++ b/man/systemd-mountfsd.service.xml @@ -33,7 +33,7 @@ file descriptors for the file systems contained therein to clients, via a Varlink IPC API. The disk images provided must contain a raw file system image or must follow the Discoverable + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification/">UAPI.2 Discoverable Partitions Specification. Before mounting any file systems authenticity of the disk image is established in one or a combination of the following ways: diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index ed0acc6937..d5e50d8d6d 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -327,14 +327,12 @@ partition of type 0fc63daf-8483-4772-8e79-3d69d8477de4. - A GUID partition table (GPT) with a marked - root partition which is mounted as the root directory of the - container. Optionally, GPT images may contain a home and/or - a server data partition which are mounted to the appropriate - places in the container. All these partitions must be - identified by the partition types defined by the Discoverable - Partitions Specification. + A GUID partition table (GPT) with a marked root partition which is mounted as the + root directory of the container. Optionally, GPT images may contain a home and/or a server data + partition which are mounted to the appropriate places in the container. All these partitions must + be identified by the partition types defined by the UAPI.2 + Discoverable Partitions Specification. No partition table, and a single file system spanning the whole image. diff --git a/man/systemd-stub.xml b/man/systemd-stub.xml index d098804dc1..2b40c1e561 100644 --- a/man/systemd-stub.xml +++ b/man/systemd-stub.xml @@ -170,7 +170,7 @@ or credentials) or bind encryption to booted kernels. For further details about the UKI concept, see the UKI specification. + url="https://uapi-group.org/specifications/specs/unified_kernel_image/">UAPI.5 UKI specification. @@ -806,7 +806,7 @@ systemd.exec5 systemd-creds1 systemd-sysext8 - Boot Loader Specification + UAPI.1 Boot Loader Specification Boot Loader Interface ukify1 systemd-measure1 diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml index 050e21fafc..b5ab6826a2 100644 --- a/man/systemd-sysext.xml +++ b/man/systemd-sysext.xml @@ -90,7 +90,7 @@ Plain directories or btrfs subvolumes containing the OS tree Disk images with a GPT disk label, following the Discoverable Partitions Specification + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification Disk images lacking a partition table, with a naked Linux file system (e.g. erofs, squashfs or ext4) diff --git a/man/systemd-sysusers.xml b/man/systemd-sysusers.xml index 29d02f26e0..5c299169eb 100644 --- a/man/systemd-sysusers.xml +++ b/man/systemd-sysusers.xml @@ -76,8 +76,8 @@ are applied to file system in the indicated disk image. This is similar to but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition table, following the - Discoverable Partitions - Specification. For further information on supported disk images, see + UAPI.2 + Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. diff --git a/man/systemd-tmpfiles.xml b/man/systemd-tmpfiles.xml index e4794c3f16..815dcd88d6 100644 --- a/man/systemd-tmpfiles.xml +++ b/man/systemd-tmpfiles.xml @@ -264,7 +264,7 @@ are applied to file system in the indicated disk image. This is similar to but operates on file systems stored in disk images or block devices. The disk image should either contain just a file system or a set of file systems within a GPT partition table, following the - Discoverable Partitions + UAPI.2 Discoverable Partitions Specification. For further information on supported disk images, see systemd-nspawn1's switch of the same name. diff --git a/man/systemd-vmspawn.xml b/man/systemd-vmspawn.xml index 7b26bec067..7fd19671cb 100644 --- a/man/systemd-vmspawn.xml +++ b/man/systemd-vmspawn.xml @@ -196,7 +196,7 @@ Set the linux kernel image to use for direct kernel boot. If a directory type image is used and was omitted, vmspawn will search for boot loader entries according to the - Boot Loader Specification assuming + UAPI.1 Boot Loader Specification assuming XBOOTLDR to be located at /boot and ESP to be /efi respectively. If no kernel was installed into the image then the image will fail to boot. @@ -210,7 +210,7 @@ Set the initrd to use for direct kernel boot. If the supplied is a - Boot Loader Specification + UAPI.1 Boot Loader Specification Type #2 entry, then this argument is not required. If no initrd was installed into the image then the image will fail to boot. @@ -739,7 +739,7 @@ $ ssh root@vsock/$my_vsock_cid -i /run/user/$UID/systemd/vmspawn/machine-*-syste mkosi1 machinectl1 importctl1 - Boot Loader Specification + UAPI.1 Boot Loader Specification diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index b2e3ae369b..ebf8b1df6a 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -174,9 +174,9 @@ or loopback file instead of a directory. The device node or file system image file needs to contain a file system without a partition table, or a file system within an MBR/MS-DOS or GPT partition table with only a single Linux-compatible partition, or a set of file systems within a GPT partition table - that follows the - - Discoverable Partitions Specification. + that follows the UAPI.2 + Discoverable Partitions Specification. When DevicePolicy= is set to closed or strict, or set to auto and DeviceAllow= is diff --git a/man/systemd.image-filter.xml b/man/systemd.image-filter.xml index f5a8a811da..eb16fce519 100644 --- a/man/systemd.image-filter.xml +++ b/man/systemd.image-filter.xml @@ -24,7 +24,7 @@ Description In systemd, whenever a disk image (DDI) implementing the Discoverable + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 Discoverable Partitions Specification is activated, a filter may be specified controlling which partitions to consider for mounting. Such a disk image dissection filter is a string that contains per-partition-type patterns, separated by colons (:). The individual rules consist of a partition diff --git a/man/systemd.image-policy.xml b/man/systemd.image-policy.xml index 36a8395bf0..6d91669ef1 100644 --- a/man/systemd.image-policy.xml +++ b/man/systemd.image-policy.xml @@ -24,13 +24,13 @@ Description In systemd, whenever a disk image (DDI) implementing the Discoverable - Partitions Specification is activated, a policy may be specified controlling which partitions to - mount and what kind of cryptographic protection to require. Such a disk image dissection policy is a - string that contains per-partition-type rules, separated by colons (:). The individual - rules consist of a partition identifier, an equal sign (=), and one or more flags - which may be set per partition. If multiple flags are specified per partition they are separated by a - plus sign (+). + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 + Discoverable Partitions Specification is activated, a policy may be specified controlling which + partitions to mount and what kind of cryptographic protection to require. Such a disk image dissection + policy is a string that contains per-partition-type rules, separated by colons + (:). The individual rules consist of a partition identifier, an equal sign + (=), and one or more flags which may be set per partition. If multiple flags are + specified per partition they are separated by a plus sign (+). The partition identifiers currently defined are: , , , , , , diff --git a/man/systemd.v.xml b/man/systemd.v.xml index cee351448c..9bdf775378 100644 --- a/man/systemd.v.xml +++ b/man/systemd.v.xml @@ -81,7 +81,7 @@ The variable part of the filenames in the .v/ directories are filtered and compared primarily with a version comparison, implementing Version Format + url="https://uapi-group.org/specifications/specs/version_format_specification/">UAPI.10 Version Format Specification. However, additional rules apply: diff --git a/man/sysupdate.d.xml b/man/sysupdate.d.xml index 13dcd09775..0f1862b13c 100644 --- a/man/sysupdate.d.xml +++ b/man/sysupdate.d.xml @@ -84,8 +84,8 @@ A file https://download.example.com/foobarOS_47.root.xz should be downloaded, decompressed and written to a previously unused partition with GPT partition type UUID 4f68bce3-e8cd-4db1-96e7-fbcaf984b709 for x86-64, as per Discoverable Partitions - Specification. + url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">UAPI.2 + Discoverable Partitions Specification. Similarly, a file https://download.example.com/foobarOS_47.verity.xz should be downloaded, decompressed and written to a previously empty partition with GPT partition type @@ -93,7 +93,7 @@ for x86-64 root file systems). Finally, a file https://download.example.com/foobarOS_47.efi (a - unified kernel, as per Boot Loader + unified kernel, as per UAPI.1 Boot Loader Specification Type #2) should be downloaded, decompressed and written to the $BOOT file system, i.e. to EFI/Linux/foobarOS_47.efi in the ESP or XBOOTLDR partition. @@ -368,21 +368,21 @@ @aGPT partition flag NoAutoEither 0 or 1 - Controls NoAuto bit of the GPT partition flags, as per Discoverable Partitions Specification; only relevant if target resource type chosen as partition + Controls NoAuto bit of the GPT partition flags, as per UAPI.2 Discoverable Partitions Specification; only relevant if target resource type chosen as partition @g GPT partition flag GrowFileSystem Either 0 or 1 - Controls GrowFileSystem bit of the GPT partition flags, as per Discoverable Partitions Specification; only relevant if target resource type chosen as partition + Controls GrowFileSystem bit of the GPT partition flags, as per UAPI.2 Discoverable Partitions Specification; only relevant if target resource type chosen as partition @r Read-only flag Either 0 or 1 - Controls ReadOnly bit of the GPT partition flags, as per Discoverable Partitions Specification and other output read-only flags, see ReadOnly= below + Controls ReadOnly bit of the GPT partition flags, as per UAPI.2 Discoverable Partitions Specification and other output read-only flags, see ReadOnly= below @@ -681,12 +681,12 @@ If set to root, esp, xbootldr, the specified Path= will be resolved relative to the mount point of the corresponding partition, as defined by the - Boot Loader + UAPI.1 Boot Loader Specification. If set to boot, the specified Path= will be resolved relative to the mount point of the $BOOT partition (i.e. the ESP or XBOOTLDR), as defined by the - Boot Loader + UAPI.1 Boot Loader Specification. If set to explicit, the specified Path= will be @@ -753,7 +753,7 @@ overall PartitionFlags= flags setting and the individual flag settings PartitionNoAuto= and PartitionGrowFileSystem= are used (or the wildcards for them), then the latter override the former, i.e. the individual flag bit overrides the - overall flags value. See Discoverable + overall flags value. See UAPI.2 Discoverable Partitions Specification for details about these flags. Note that these settings are not used for matching, they only have effect on newly written @@ -767,7 +767,7 @@ Controls whether to mark the resulting file, subvolume or partition read-only. If the target type is partition this controls the ReadOnly partition flag, as per - Discoverable Partitions + UAPI.2 Discoverable Partitions Specification, similar to the PartitionNoAuto= and PartitionGrowFileSystem= flags described above. If the target type is regular-file, the writable bit is removed from the access mode. If the @@ -987,7 +987,7 @@ TriesDone=0 InstancesMax=2 The above installs a unified kernel image into the $BOOT partition, as per - Boot Loader + UAPI.1 Boot Loader Specification Type #2. This defines three possible patterns for the names of the kernel images, as per Automatic Boot Assessment, and ensures when installing new kernels, they are set up with 3 tries left. No more than two parallel diff --git a/man/ukify.xml b/man/ukify.xml index 0f953cd94d..829761642d 100644 --- a/man/ukify.xml +++ b/man/ukify.xml @@ -47,7 +47,7 @@ ukify is a tool whose primary purpose is to combine components (usually a kernel, an initrd, and the systemd-stub7 UEFI - stub) to create a Unified + stub) to create a UAPI.5 Unified Kernel Image (UKI) — a single PE binary that boots the system. When the UKI is executed, the stub extracts and boots the embedded linux kernel. The UKI can be started directly by the firmware or through a boot loader. When used with qemu, a UKI can also