A sencence like "The system manager does, a, b, c, which is really d, and e.",
it is generally understood that the manager also does "e". This can be
quite confusing if the manager cannot do "e", in our case unmount the file
system on which it is sitting.
Similary, we cannot "fall back to x if it is missing", since "it" in that
sentence means "x".
necessary file systems and spawning all configured services.</para>
<para>On shutdown, the system manager stops all services, unmounts all non-busy file systems (detaching
- the storage technologies backing them), and then (optionally) jumps into the exitrd, which is backed by
- tmpfs, and unmounts/detaches the remaining file systems, including the real root. As a last step,
- the system is powered down.</para>
+ the storage technologies backing them), and then (optionally) jumps into the exitrd. The exitrd is backed
+ by tmpfs and unmounts/detaches the remaining file systems, including the real root. As a last step, the
+ system is powered down.</para>
<para>Additional information about the system boot process may be
found in
precedence over <filename>/usr/lib/os-release</filename>.
Applications should check for the former, and exclusively use its
data if it exists, and only fall back to
- <filename>/usr/lib/os-release</filename> if it is missing.
- Applications should not read data from both files at the same
- time. <filename>/usr/lib/os-release</filename> is the recommended
+ <filename>/usr/lib/os-release</filename> if that is missing.
+ Applications should not combine the data from both files.
+ <filename>/usr/lib/os-release</filename> is the recommended
place to store OS release information as part of vendor trees.
<filename>/etc/os-release</filename> should be a relative symlink
to <filename>/usr/lib/os-release</filename>, to provide