shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-03 05:18:09 +03:00
Code

man: reword some awkward sentences

Browse Source
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2022-10-13 22:30:48 +02:00
parent 8d3b7d2fd3
commit 1485925d2d
2 changed files with 10 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
catalog/systemd.catalog.in
View File

@ -144,7 +144,7 @@ might still be busy with completing start-up.
Kernel start-up required @KERNEL_USEC@ microseconds. Kernel start-up required @KERNEL_USEC@ microseconds.
initrd start-up required @INITRD_USEC@ microseconds. Initrd start-up required @INITRD_USEC@ microseconds.
Userspace start-up required @USERSPACE_USEC@ microseconds. Userspace start-up required @USERSPACE_USEC@ microseconds.

24
man/bootup.xml
View File

@ -202,22 +202,16 @@ emergency.service | | |
<refsect1> <refsect1>
<title>Bootup in the initrd</title> <title>Bootup in the initrd</title>
<para>The initrd implementation can be set up using systemd as well. In this case, boot up inside the <para>Systemd can be used in the initrd as well. It detects the initrd environment by checking for the
initrd follows the following structure.</para> <filename>/etc/initrd-release</filename> file. The default target in the initrd is
<filename>initrd.target</filename>. The bootup process is identical to the system manager bootup until
the target <filename>basic.target</filename>. After that, systemd executes the special target
<filename>initrd.target</filename>.
<para>systemd detects that it is run within an initrd by checking Before any file systems are mounted, the manager will determine whether the system shall resume from
for the file <filename>/etc/initrd-release</filename>. hibernation or proceed with normal boot. This is accomplished by
The default target in the initrd is <filename>systemd-hibernate-resume@.service</filename> which must be finished before
<filename>initrd.target</filename>. The bootup process begins <filename>local-fs-pre.target</filename>, so no filesystems can be mounted before the check is complete.
identical to the system manager bootup (see above) until it
reaches <filename>basic.target</filename>. From there, systemd
approaches the special target <filename>initrd.target</filename>.
Before any file systems are mounted, it must be determined whether
the system will resume from hibernation or proceed with normal boot.
This is accomplished by <filename>systemd-hibernate-resume@.service</filename>
which must be finished before <filename>local-fs-pre.target</filename>,
so no filesystems can be mounted before the check is complete.
When the root device becomes available, When the root device becomes available,
<filename>initrd-root-device.target</filename> is reached. <filename>initrd-root-device.target</filename> is reached.