shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-21 13:34:21 +03:00
Code

man: slightly enhance docs about "exitrd" and remove TODO entry for it

Browse Source 
The concept is fairly well established and present in our docs in various
places.

Say that the exitrd is also marked by the presence of /etc/initrd-release.

(cherry picked from commit ace26a511f)
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2024-09-23 11:41:29 +02:00 committed by Luca Boccassi
parent 08cf1c5ce5
commit b78f99e71b
3 changed files with 14 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
TODO
View File

@ -1302,12 +1302,6 @@ Features:
CapabilityQuintet we already have. (This likely allows us to drop libcap
dep in the base OS image)
* add concept for "exitrd" as inverse of "initrd", that we can transition to at
shutdown, and has similar security semantics. This should then take the place
of dracut's shutdown logic. Should probably support sysexts too. Care needs
to be taken that the resulting logic ends up in RAM, i.e. is copied out of
on-disk storage.
* userdbd: implement an additional varlink service socket that provides the
host user db in restricted form, then allow this to be bind mounted into
sandboxed environments that want the host database in minimal form. All

11
man/bootup.xml
View File

@ -344,6 +344,17 @@ systemd-reboot.service | | | |
shutdown phase described above.</para>
</refsect1>
<refsect1>
<title>The exitrd</title>
<para>The "exitrd" is a concept symmetrical to the initrd. When the system manager is shutting down and
<filename>/run/initramfs/shutdown</filename> exists, it will switch root to
<filename>/run/initramfs/</filename> and execute <filename>/shutdown</filename>. This program runs from
the tmpfs mounted on <filename>/run/</filename>, so it can unmount the old root file system and perform
additional steps, for example dismantle complex storage or perform additional logging about the shutdown.
</para>
</refsect1>
<refsect1>
<title>See Also</title>
<para><simplelist type="inline">

6
man/os-release.xml
View File

@ -88,10 +88,10 @@
<refsect2>
<title><filename>/etc/initrd-release</filename></title>
<para>In the <ulink
url="https://docs.kernel.org/admin-guide/initrd.html">initrd</ulink>,
<para>In the <ulink url="https://docs.kernel.org/admin-guide/initrd.html">initrd</ulink>
and exitrd,
<filename>/etc/initrd-release</filename> plays the same role as <filename>os-release</filename> in the
main system. Additionally, the presence of that file means that the system is in the initrd phase.
main system. Additionally, the presence of that file means that the system is in the initrd/exitrd phase.
<filename>/etc/os-release</filename> should be symlinked to <filename>/etc/initrd-release</filename>
(or vice versa), so programs that only look for <filename>/etc/os-release</filename> (as described
above) work correctly.</para>