diff options
author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-11-14 09:44:39 +0100 |
---|---|---|
committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-11-21 12:26:35 +0100 |
commit | db81144428d7af1b10eb332dde9708e8d136ebe1 (patch) | |
tree | abbc20abaab4bf13898b23a781e62817bb541fbb /docs/BUILDING_IMAGES.md | |
parent | 244c2a8344c01e94cd9bdf835de998b89bc53179 (diff) | |
download | systemd-db81144428d7af1b10eb332dde9708e8d136ebe1.tar.gz |
tree-wide: BLS and DPS are now on uapi-group website
Diffstat (limited to 'docs/BUILDING_IMAGES.md')
-rw-r--r-- | docs/BUILDING_IMAGES.md | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/BUILDING_IMAGES.md b/docs/BUILDING_IMAGES.md index 955dd90e55..1a96ed0083 100644 --- a/docs/BUILDING_IMAGES.md +++ b/docs/BUILDING_IMAGES.md @@ -67,14 +67,14 @@ 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](BOOT_LOADER_SPECIFICATION.md) 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 same system -without conflicts. However, this is problematic if the machine ID shall be -generated automatically on first boot: if the ID is not known before the first -boot it cannot be used to name the most basic resources required for the boot -process to complete. +[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 +same system without conflicts. However, this is problematic if the machine ID +shall be generated automatically on first boot: if the ID is not known before +the first boot it cannot be used to name the most basic resources required for +the boot process to complete. Thus, for images that shall acquire their identity on first boot only, it is required to use a different identifier for naming boot menu entries. To allow @@ -203,8 +203,8 @@ 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](DISCOVERABLE_PARTITIONS.md) for - details. If the file system is already grown it executes no operation. + [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` services can format file systems and swap spaces before first use, if they @@ -267,8 +267,8 @@ fields. [`machine-id(5)`](https://www.freedesktop.org/software/systemd/man/machine-id.html)<br> [`systemd-random-seed(8)`](https://www.freedesktop.org/software/systemd/man/systemd-random-seed.service.html)<br> [`os-release(5)`](https://www.freedesktop.org/software/systemd/man/os-release.html)<br> -[Boot Loader Specification](BOOT_LOADER_SPECIFICATION.md)<br> -[Discoverable Partitions Specification](DISCOVERABLE_PARTITIONS.md)<br> +[Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification)<br> +[Discoverable Partitions Specification](https://uapi-group.org/specifications/specs/discoverable_partitions_specification)<br> [`mkosi`](https://github.com/systemd/mkosi)<br> [`systemd-boot(7)`](https://www.freedesktop.org/software/systemd/man/systemd-boot.html)<br> [`systemd-repart(8)`](https://www.freedesktop.org/software/systemd/man/systemd-repart.service.html)<br> |