Package: systemd
Version: 29-1.1
Severity: wishlist
Tags: upstream patch
Hi,
When booting with /usr on a separate partition, systemd tells me
systemd[1]: /usr appears to be on a different file system than /. This
is not supported anymore. Some things will probably break (sometimes even
silently) in mysterious ways. Consult
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more
information.
That seems like a reasonable note for README, but there's not much the
sysadmin can do about it so I can't see what value it adds in dmesg.
How about something like this patch?
It might also make sense for some interested person to file a bug
against initramfs-tools (or udev or whatever he or she considers
broken) and refer to that in README.Debian, so the underlying trouble
can be actually fixed in the simple cases. :)
Thanks,
Jonathan
---
README | 22 +++++++++++-----------
src/main.c | 13 -------------
2 files changed, 11 insertions(+), 24 deletions(-)
diff --git a/README b/README
index cfbcbe7f..0b1c8302 100644
--- a/README
+++ b/README
@@ -69,18 +69,18 @@ WARNINGS:
symlink to /proc/mounts. Please ensure that /etc/mtab is a
proper symlink.
- systemd will warn you during boot if /usr is on a different
- file system than /. While in systemd itself very little will
- break if /usr is on a separate partition many of its
- dependencies very likely will break sooner or later in one
- form or another. For example udev rules tend to refer to
- binaries in /usr, binaries that link to libraries in /usr or
- binaries that refer to data files in /usr. Since these
- breakages are not always directly visible systemd will warn
- about this, since this kind of file system setup is not really
- supported anymore by the basic set of Linux OS components.
+ There can be subtle breakage when /usr is on a different file
+ system than /. While in systemd itself very little will break
+ if /usr is on a separate partition, many of its dependencies
+ very likely will break sooner or later in one form or another.
+ For example, udev rules tend to refer to binaries in /usr,
+ binaries that link to libraries in /usr, or binaries that refer
+ to data files in /usr. Since these breakages are not always
+ directly visible, systemd used to warn about this, since this
+ kind of file system setup is not really supported anymore by
+ the basic set of Linux OS components.
- For more information on this issue consult
+ For more information on this issue, consult
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
ENGINEERING AND CONSULTING SERVICES:
diff --git a/src/main.c b/src/main.c
index 68328b76..5f2401a9 100644
--- a/src/main.c
+++ b/src/main.c
@@ -981,18 +981,6 @@ static void test_mtab(void) {
"Please make sure to replace this file by a symlink to
avoid incorrect or misleading mount(8) output.");
}
-static void test_usr(void) {
-
- /* Check that /usr is not a separate fs */
-
- if (dir_is_empty("/usr") <= 0)
- return;
-
- log_warning("/usr appears to be on a different file system than /.
This is not supported anymore. "
- "Some things will probably break (sometimes even silently)
in mysterious ways. "
- "Consult
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more
information.");
-}
-
static void test_cgroups(void) {
if (access("/proc/cgroups", F_OK) >= 0)
@@ -1188,7 +1176,6 @@ int main(int argc, char *argv[]) {
loopback_setup();
test_mtab();
- test_usr();
test_cgroups();
}
--
1.7.7.rc1
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
