man: add remote-*.targets to the bootup sequence

I think this makes it easier to see the difference between local and remote
mounts.

Make the graph a bit narrower while at it.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2019-12-18 10:32:03 +01:00
parent 4186441bbd
commit f71502c49f

View file

@ -92,49 +92,59 @@
<!-- note: do not use unicode ellipsis here, because docbook will replace that <!-- note: do not use unicode ellipsis here, because docbook will replace that
with three dots anyway, messing up alignment --> with three dots anyway, messing up alignment -->
<programlisting>local-fs-pre.target <programlisting> cryptsetup-pre.target
| |
v (various low-level v
(various mounts and (various swap (various cryptsetup API VFS mounts: (various cryptsetup devices...)
fsck services...) devices...) devices...) (various low-level (various low-level mqueue, configfs, | |
| | | services: udevd, API VFS mounts: debugfs, ...) v |
v v v tmpfiles, random mqueue, configfs, | cryptsetup.target |
local-fs.target swap.target cryptsetup.target seed, sysctl, ...) debugfs, ...) | (various swap | | remote-fs-pre.target
| | | | | | devices...) | | | |
\__________________|_________________ | ___________________|____________________/ | | | | | v
\|/ | v local-fs-pre.target | | | (network file systems)
v | swap.target | | v v |
sysinit.target | | v | remote-cryptsetup.target |
| | | (various low-level (various mounts and | | |
____________________________________/|\________________________________________ | | services: udevd, fsck services...) | | remote-fs.target
/ | | | \ | | tmpfiles, random | | | /
| | | | | | | seed, sysctl, ...) v | | /
v v | v v | | | local-fs.target | | /
(various (various | (various rescue.service | | | | | | /
timers...) paths...) | sockets...) | \____|______|_______________ ______|___________/ | /
| | | | v \ / | /
v v | v <emphasis>rescue.target</emphasis> v | /
timers.target paths.target | sockets.target sysinit.target | /
| | | | | | /
v \_________________ | ___________________/ ______________________/|\_____________________ | /
\|/ / | | | \ | /
v | | | | | | /
basic.target v v | v | | /
| (various (various | (various | |/
____________________________________/| emergency.service timers...) paths...) | sockets...) | |
/ | | | | | | | | |
| | | v v v | v | |
v v v <emphasis>emergency.target</emphasis> timers.target paths.target | sockets.target | |
display- (various system (various system | | | | v |
manager.service services services) v \_______ | _____/ rescue.service |
| required for | \|/ | |
| graphical UIs) v v v |
| | <emphasis>multi-user.target</emphasis> basic.target <emphasis>rescue.target</emphasis> |
| | | | |
\_________________ | _________________/ ________v____________________ |
\|/ / | \ |
v | | | |
<emphasis>graphical.target</emphasis></programlisting> v v v |
display- (various system (various system |
manager.service services services) |
| required for | |
| graphical UIs) v v
| | <emphasis>multi-user.target</emphasis>
emergency.service | | |
| \_____________ | _____________/
v \|/
<emphasis>emergency.target</emphasis> v
<emphasis>graphical.target</emphasis></programlisting>
<para>Target units that are commonly used as boot targets are <para>Target units that are commonly used as boot targets are
<emphasis>emphasized</emphasis>. These units are good choices as <emphasis>emphasized</emphasis>. These units are good choices as