X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fbootup.xml;h=6bd22ef476c73743e6a441fc9691f45ddf48451c;hb=9e5f0f92915b777308797294c6e103e430957b5d;hp=e29c1a016796a0309e147fdf7a737e5ad874452e;hpb=8284608198887230a1ac7f6ada9affeed3f437fb;p=elogind.git
diff --git a/man/bootup.xml b/man/bootup.xml
index e29c1a016..6bd22ef47 100644
--- a/man/bootup.xml
+++ b/man/bootup.xml
@@ -44,7 +44,7 @@
bootup
- The System Bootup Process
+ System bootup process
@@ -53,7 +53,7 @@
A number of different components are involved in the
system boot. Immediately after power-up, the system
BIOS will do minimal hardware initialization, and hand
- control over to a boot loader stored on a persistant
+ control over to a boot loader stored on a persistent
storage device. This boot loader will then invoke an
OS kernel from disk (or the network). In the Linux
case this kernel now (optionally) extracts and
@@ -111,7 +111,7 @@
target units are available, as listed on
systemd.special7.
- The follow chart is a structural overview of
+ The following chart is a structural overview of
these well-known units and their position in the
boot-up logic. The arrows describe which units are
pulled in and ordered before which other units. Units
@@ -147,18 +147,18 @@
v
basic.target
|
- _________________/| emergency.service
- / | |
- | | v
- v v emergency.target
- (various system (various system
- services services)
- required for |
- graphical UIs) v
- | multi-user.target
- | |
- | _________________/
- |/
+ __________________________________/| emergency.service
+ / | | |
+ | | | v
+ v v v emergency.target
+ display- (various system (various system
+ manager.service services services)
+ | required for |
+ | graphical UIs) v
+ | | multi-user.target
+ | | |
+ \_______________ | _________________/
+ \|/
v
graphical.target
@@ -173,6 +173,79 @@
to them.
+
+ Systemd in the Initrd
+ If the initrd creation tool used the services provided
+ by systemd, the default target in the initrd is the
+ initrd-fs.target. The process is the same as above until the basic.target is reached.
+ Systemd now continues to the initrd.target. If the root device could be mounted
+ on /sysroot, the sysroot.mount unit is active and the initrd-root-fs.target is reached.
+ initrd-parse-etc.service scans /sysroot/etc/fstab for the /usr mountpoint and for entries
+ marked with the x-initrd.mount option set. If these mountpoint are
+ mounted in /sysroot, the initrd-fs.target is reached.
+ The initrd-cleanup.service isolates to the initrd-switch-root.target,
+ where cleanup services can run. At the very last end
+ initrd-switch-root.service is activated, which will cause
+ the system to switch root to /sysroot.
+
+
+
+ (same as above)
+ :
+ :
+ v
+ basic.target
+ | emergency.service
+ ______________________/| |
+ / | v
+ | sysroot.mount emergency.target
+ | |
+ | v
+ | initrd-root-fs.target
+ | |
+ | v
+ | initrd-parse-etc.service
+ (custom initrd services) |
+ | v
+ | (sysroot-usr.mount and
+ | various mounts marked
+ | with fstab option
+ | x-initrd.mount)
+ | |
+ | v
+ | initrd-fs.target
+ | |
+ \______________________ |
+ \|
+ v
+ initrd.target
+ |
+ v
+ initrd-cleanup.service
+ isolates to
+ initrd-switch-root.target
+ |
+ v
+ ______________________/|
+ / |
+ | initrd-udevadm-cleanup-db.service
+ | |
+ (custom initrd services) |
+ | |
+ \______________________ |
+ \|
+ v
+ initrd-switch-root.target
+ |
+ v
+ initrd-switch-root.service
+ |
+ v
+ switch-root
+
+
+
+
System Manager Shutdown
@@ -219,7 +292,8 @@ systemd-reboot.service systemd-poweroff.service systemd-halt.service syste
systemd1,
boot7,
systemd.special7,
- systemd.target5
+ systemd.target5,
+ dracut8