morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-14 00:14:32 +09:00
Code Issues Packages Projects Releases Wiki Activity

doc: mention 'exitrd' term

Browse Source
This commit is contained in:
Lennart Poettering
2025-06-04 14:50:07 +02:00
parent 959d7f1759
commit 59fe8d74b5
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/ROOT_STORAGE_DAEMONS.md
View File

@@ -26,12 +26,13 @@ this needs to be set up by the initrd, i.e. on Fedora by Dracut. In newer
systemd versions tear-down of the root file system backing is also done by the
initrd: after terminating all remaining running processes and unmounting all
file systems it can (which means excluding the root file system) systemd will
jump back into the initrd code allowing it to unmount the final file systems
(and its storage backing) that could not be unmounted as long as the OS was
still running from the main root file system. The job of the initrd is to
detach/unmount the root file system, i.e. inverting the exact commands it used
to set them up in the first place. This is not only cleaner, but also allows
for the first time arbitrary complex stacks of storage technology.
jump back into the initrd code (this code shall hereby be called the *exitrd*)
allowing it to unmount the final file systems (and its storage backing) that
could not be unmounted as long as the OS was still running from the main root
file system. The job of the exitrd is to detach/unmount the root file system,
i.e. inverting the exact commands it used to set them up in the first
place. This is not only cleaner, but also allows for the first time arbitrary
complex stacks of storage technology.
Previous attempts to handle root file system setups with complex storage as
backing usually tried to maintain the root storage with program code stored on