README: slightly update the section about split /usr

It's fine if /usr is actually on a separate fs. What matters is that it
is mounted early enough. Say so.
This commit is contained in:
Lennart Poettering 2017-11-17 11:39:48 +01:00
parent 01c8938e54
commit 9e93f6f092

20
README
View file

@ -283,16 +283,16 @@ SYSV INIT.D SCRIPTS:
needs to look like, and provide an implementation at the marked places. needs to look like, and provide an implementation at the marked places.
WARNINGS: WARNINGS:
systemd will warn you during boot if /usr is on a different systemd will warn during early boot if /usr is not already mounted at
file system than /. While in systemd itself very little will this point (that means: either located on the same file system as / or
break if /usr is on a separate partition, many of its already mounted in the initrd). While in systemd itself very little
dependencies very likely will break sooner or later in one will break if /usr is on a separate, late-mounted partition, many of
form or another. For example, udev rules tend to refer to its dependencies very likely will break sooner or later in one form or
binaries in /usr, binaries that link to libraries in /usr or another. For example, udev rules tend to refer to binaries in /usr,
binaries that refer to data files in /usr. Since these binaries that link to libraries in /usr or binaries that refer to data
breakages are not always directly visible, systemd will warn files in /usr. Since these breakages are not always directly visible,
about this, since this kind of file system setup is not really systemd will warn about this, since this kind of file system setup is
supported anymore by the basic set of Linux OS components. not really supported anymore by the basic set of Linux OS components.
systemd requires that the /run mount point exists. systemd also systemd requires that the /run mount point exists. systemd also
requires that /var/run is a symlink to /run. requires that /var/run is a symlink to /run.