summaryrefslogtreecommitdiff
path: root/docs/ENVIRONMENT.md
diff options
context:
space:
mode:
authorLuca Boccassi <bluca@debian.org>2022-11-22 01:07:13 +0100
committerGitHub <noreply@github.com>2022-11-22 01:07:13 +0100
commita0c544ee09c735ef3a6e04147c2e03f9dddbd98e (patch)
treeb3dabc9eb62980208ae151c043996cd60d270738 /docs/ENVIRONMENT.md
parent69b31b29a05d81ebf6012b6508b83e57a5ce7144 (diff)
parent2bd051a06db18a41319bdcd0211f592375bbe9b4 (diff)
downloadsystemd-a0c544ee09c735ef3a6e04147c2e03f9dddbd98e.tar.gz
Merge pull request #25379 from keszybz/update-doc-links
Update doc links
Diffstat (limited to 'docs/ENVIRONMENT.md')
-rw-r--r--docs/ENVIRONMENT.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/ENVIRONMENT.md b/docs/ENVIRONMENT.md
index b4aaf10100..32bd9598b7 100644
--- a/docs/ENVIRONMENT.md
+++ b/docs/ENVIRONMENT.md
@@ -188,12 +188,12 @@ 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](BOOT_LOADER_SPECIFICATION.md) 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 contain the usual
- directory hierarchy mandated by the Boot Loader Specification, i.e. the entry
- drop-ins should be placed in
+ [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
+ contain the usual directory hierarchy mandated by the Boot Loader
+ Specification, i.e. the entry drop-ins should be placed in
`/run/boot-loader-entries/loader/entries/*.conf`, and the files referenced by
the drop-ins (including the kernels and initrds) somewhere else below
`/run/boot-loader-entries/`. Note that all these files may be (and are
@@ -384,7 +384,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](DISCOVERABLE_PARTITIONS.md).
+ [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.