summaryrefslogtreecommitdiff
path: root/docs/INITRD_INTERFACE.md
diff options
context:
space:
mode:
authorBenjamin Franzke <benjaminfranzke@googlemail.com>2022-05-18 00:05:38 +0200
committerBenjamin Franzke <benjaminfranzke@googlemail.com>2022-05-18 20:34:10 +0200
commit5c90c67a344e05368570367009768cb058a3046d (patch)
tree9a87d3f0d96db5627161b059a8551263d6b9d39b /docs/INITRD_INTERFACE.md
parente4885958dc36080aabbe7efae4348390ff743382 (diff)
downloadsystemd-5c90c67a344e05368570367009768cb058a3046d.tar.gz
docs: use relative links
Allows for links to work both on systemd.io (or forks) and when viewed on https://github.com/systemd/systemd/tree/main/docs Note that the markdown links are converted by jekyll-relative-links[1] to html. This plugin is enabled by default on github pages[2][3]. Due to a bug in jekyll-relative-links – see https://github.com/benbalter/jekyll-relative-links/issues/61 – we need to avoid line-wrapped links when using relative markdown links. [1] https://github.com/benbalter/jekyll-relative-links [2] https://github.blog/2016-12-05-relative-links-for-github-pages/ [3] https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll#plugins
Diffstat (limited to 'docs/INITRD_INTERFACE.md')
-rw-r--r--docs/INITRD_INTERFACE.md12
1 files changed, 5 insertions, 7 deletions
diff --git a/docs/INITRD_INTERFACE.md b/docs/INITRD_INTERFACE.md
index 3898840c56..1e9493cd8a 100644
--- a/docs/INITRD_INTERFACE.md
+++ b/docs/INITRD_INTERFACE.md
@@ -37,11 +37,10 @@ interfaces are currently used by dracut and the ArchLinux initrds.
optionally followed (in `argv[2]`, `argv[3]`, … systemd's original command
line options, for example `--log-level=` and similar.
-* Storage daemons run from the initrd should follow the guide on [systemd
- and Storage Daemons for the Root File
- System](https://systemd.io/ROOT_STORAGE_DAEMONS) to survive properly from the
- boot initrd all the way to the point where systemd jumps back into the initrd
- for shutdown.
+* Storage daemons run from the initrd should follow the guide on
+ [systemd and Storage Daemons for the Root File System](ROOT_STORAGE_DAEMONS.md)
+ to survive properly from the boot initrd all the way to the point where
+ systemd jumps back into the initrd for shutdown.
One last clarification: we use the term _initrd_ very generically here
describing any kind of early boot file system, regardless whether that might be
@@ -70,5 +69,4 @@ systemd. Here are a few terse notes:
* The switch-root operation will result in a killing spree of all running
processes. Some processes might need to be excluded from that, see the guide
- on [systemd and Storage Daemons for the Root File
- System](https://systemd.io/ROOT_STORAGE_DAEMONS).
+ on [systemd and Storage Daemons for the Root File System](ROOT_STORAGE_DAEMONS.md).