From fc53809803cd2bc2434e312b19a18fa36776da12 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 12 Jun 2024 05:50:40 +0200 Subject: Adding upstream version 256. Signed-off-by: Daniel Baumann --- man/bootup.xml | 63 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 32 insertions(+), 31 deletions(-) (limited to 'man/bootup.xml') diff --git a/man/bootup.xml b/man/bootup.xml index c872b13..c942bab 100644 --- a/man/bootup.xml +++ b/man/bootup.xml @@ -1,6 +1,6 @@ + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> @@ -31,13 +31,12 @@ boot loader will then invoke an OS kernel from disk (or the network). On systems using EFI or other types of firmware, this firmware may also load the kernel directly. - The kernel (optionally) mounts an in-memory file system, often generated by dracut8, which - looks for the root file system. Nowadays this is implemented as an "initramfs" — a compressed CPIO - archive that the kernel extracts into a tmpfs. In the past normal file systems using an in-memory block - device (ramdisk) were used, and the name "initrd" is still used to describe both concepts. It's the boot - loader or the firmware that loads both the kernel and initrd/initramfs images into memory, but the kernel - which interprets it as a file system. + The kernel (optionally) mounts an in-memory file system, which looks for the root file system. + Nowadays this is implemented as an "initramfs" — a compressed CPIO archive that the kernel extracts into + a tmpfs. In the past normal file systems using an in-memory block device (ramdisk) were used, and the + name "initrd" is still used to describe both concepts. It's the boot loader or the firmware that loads + both the kernel and initrd/initramfs images into memory, but the kernel which interprets it as a file + system. systemd1 may be used to manage services in the initrd, similarly to the real system. @@ -313,21 +312,23 @@ emergency.service | | | v final.target | - ___________________________/ \_________________ - / | | \ - | | | | - v | | | -systemd-reboot.service | | | - | v | | - | systemd-poweroff.service | | - v | v | - reboot.target | systemd-halt.service | - v | v - poweroff.target | systemd-kexec.service - v | - halt.target | - v - kexec.target + ___________________________/ \_________________________________ + / | | | \ + | | | | | + v | | | | +systemd-reboot.service | | | | + | v | | | + | systemd-poweroff.service | | | + v | v | | + reboot.target | systemd-halt.service | | + v | v | + poweroff.target | systemd-kexec.service | + v | | + halt.target | systemd-soft-reboot.service + v | + kexec.target | + v + soft-reboot.target Commonly used system shutdown targets are emphasized. @@ -345,14 +346,14 @@ systemd-reboot.service | | | See Also - - systemd1, - boot7, - systemd.special7, - systemd.target5, - systemd-halt.service8, - dracut8 - + + systemd1 + boot7 + systemd.special7 + systemd.target5 + systemd-halt.service8 + systemd-soft-reboot.service8 + -- cgit v1.2.3