diff options
Diffstat (limited to 'upstream/fedora-rawhide/man7/bootup.7')
| -rw-r--r-- | upstream/fedora-rawhide/man7/bootup.7 | 44 |
1 files changed, 20 insertions, 24 deletions
diff --git a/upstream/fedora-rawhide/man7/bootup.7 b/upstream/fedora-rawhide/man7/bootup.7 index 3c82f20d..643f7fc1 100644 --- a/upstream/fedora-rawhide/man7/bootup.7 +++ b/upstream/fedora-rawhide/man7/bootup.7 @@ -1,5 +1,5 @@ '\" t -.TH "BOOTUP" "7" "" "systemd 255" "bootup" +.TH "BOOTUP" "7" "" "systemd 256~rc3" "bootup" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -28,8 +28,7 @@ A number of different components are involved in the boot of a Linux system\&. I or \m[blue]\fBGRUB\fR\m[]\&\s-2\u[1]\d\s+2) stored on a persistent storage device\&. This 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\&. .PP -The kernel (optionally) mounts an in\-memory file system, often generated by -\fBdracut\fR(8), which looks for the root file system\&. Nowadays this is implemented as an "initramfs" \(em 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\*(Aqs 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" \(em 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\*(Aqs 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\&. \fBsystemd\fR(1) may be used to manage services in the initrd, similarly to the real system\&. .PP @@ -301,21 +300,23 @@ System shutdown with systemd also consists of various target units with some min v final\&.target | - ___________________________/ \e_________________ - / | | \e - | | | | - v | | | -systemd\-reboot\&.service | | | - | v | | - | systemd\-poweroff\&.service | | - v | v | - \fIreboot\&.target\fR | systemd\-halt\&.service | - v | v - \fIpoweroff\&.target\fR | systemd\-kexec\&.service - v | - \fIhalt\&.target\fR | - v - \fIkexec\&.target\fR + ___________________________/ \e_________________________________ + / | | | \e + | | | | | + v | | | | +systemd\-reboot\&.service | | | | + | v | | | + | systemd\-poweroff\&.service | | | + v | v | | + \fIreboot\&.target\fR | systemd\-halt\&.service | | + v | v | + \fIpoweroff\&.target\fR | systemd\-kexec\&.service | + v | | + \fIhalt\&.target\fR | systemd\-soft\-reboot\&.service + v | + \fIkexec\&.target\fR | + v + \fIsoft\-reboot\&.target\fR .fi .if n \{\ .RE @@ -335,12 +336,7 @@ systemd\-shutdown binary), which will unmount any remaining file systems, kill any remaining processes and release any other remaining resources, in a simple and robust fashion, without taking any service or unit concept into account anymore\&. At that point, regular applications and resources are generally terminated and released already, the second phase hence operates only as safety net for everything that couldn\*(Aqt be stopped or released for some reason during the primary, unit\-based shutdown phase described above\&. .SH "SEE ALSO" .PP -\fBsystemd\fR(1), -\fBboot\fR(7), -\fBsystemd.special\fR(7), -\fBsystemd.target\fR(5), -\fBsystemd-halt.service\fR(8), -\fBdracut\fR(8) +\fBsystemd\fR(1), \fBboot\fR(7), \fBsystemd.special\fR(7), \fBsystemd.target\fR(5), \fBsystemd-halt.service\fR(8), \fBsystemd-soft-reboot.service\fR(8) .SH "NOTES" .IP " 1." 4 GRUB |