Commit 013d8a39 authored by Lennart Poettering's avatar Lennart Poettering
Browse files

man: introduce bootup(7)

parent eab367b9
......@@ -462,6 +462,7 @@ MANPAGES = \
man/systemd.journal-fields.7 \
man/kernel-command-line.7 \
man/daemon.7 \
man/bootup.7 \
man/runlevel.8 \
man/telinit.8 \
man/halt.8 \
<?xml version='1.0'?> <!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
This file is part of systemd.
Copyright 2012 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <>.
<refentry id="bootup">
<refpurpose>The System Bootup Process</refpurpose>
<para>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
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
executes an initial RAM disk image (initrd) such as
which looks for the root file system. After the root
file system is found and mounted the initrd hands over
control to the system manager (such as
stored on the OS image which is then responsible for
probing all remaining hardware, mounting all necessary
file systems and spawning all configured
<para>On shutdown the system manager stops all
services, unmounts all file systems (detaching the
storage technologies backing them), and then
(optionally) jumps back into the initrd code which
unmounts/detaches the root file system and the storage
it resides on. As last step the system powered down.</para>
<para>Additional information about the system boot
process may be found in
<title>System Manager Bootup</title>
<para>At boot, the system manager on the OS image is
responsible for initializing the required file
systems, services and drivers that are necessary for
operation of the system. On
systems this process is split up in various discrete
steps which are exposed as target units. (See
for detailed information about target units.) The
boot-up process is highly parallelized so that the
order in which specific target units are reached is not
deterministic, but still adheres to a limited amount
of ordering structure.</para>
<para>When systemd starts up the system it will
activate all units that are dependencies of
<filename></filename> (as well as
recursively all dependencies of these
dependencies). Usually
<filename></filename> is simply an alias
of <filename></filename> or
<filename></filename> depending on
whether the system is configured for a graphical UI or
only for a text console. To enforce minimal ordering
between the units pulled in a number of well-known
target units are available, as listed on
<para>The follow 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
near the top are started before units nearer to the
bottom of the chart.</para>
(various mounts and (various swap (various cryptsetup
fsck services...) devices...) devices...) (various low-level (various low-level
| | | services: udevd, API VFS mounts:
v v v tmpfiles, random mqueue, configfs, seed, sysctl, ...) debugfs, ...)
| | | | |
\__________________|_________________ | ___________________|____________________/
/ | \
| | |
v | v
(various | rescue.service
sockets...) | |
| | v
v | <emphasis></emphasis> |
| |
\_________________ |
_________________/| emergency.service
/ | |
| | v
v v <emphasis></emphasis>
(various system (various system
services services)
required for |
graphical UIs) v
| <emphasis></emphasis>
| |
| _________________/
<para>Target units that are commonly used as boot
targets are <emphasis>emphasized</emphasis>. These
units are good choices as goal targets, for
example by passing them to the
<varname>systemd.unit=</varname> kernel command line
option (see
or by symlinking <filename></filename>
to them.</para>
<title>System Manager Shutdown</title>
<para>System shutdown also consists of various target
units with some minimal ordering structure
<programlisting> (conflicts with (conflicts with
all system all file system
services) mounts, swaps,
| cryptsetup
| devices, ...)
| |
v v
| |
\_______ ______/
\ /
(various low-level
__________________________/ \_____________________
/ | | \
| | | |
v v v v
reboot.service poweroff.service halt.service kexec.service
| | | |
v v v v
<emphasis></emphasis> <emphasis></emphasis> <emphasis></emphasis> <emphasis></emphasis></programlisting>
<para>Commonly used system shutdown targets are <emphasis>emphasized</emphasis>.</para>
<title>See Also</title>
......@@ -845,7 +845,8 @@
......@@ -1231,7 +1231,8 @@
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment