Bentley said:
I’m no fan of Poettering, but this is justified/explained
on the FreeDesktop wiki. Basically,
/usris not a problem with
systemd, but with other things in Linux land —
systemd is only reporting it.
What's sad is the complete and utter lack of cooperation between the different projects that make up "the Linux OS".
The
systemd folks know there's an issue, but they won't work with the community to find out what needs to be moved to / in order for separate
/usr to work.
The
udev folks don't seem to care if they spam the
/usr filesystem and that it breaks things for others.
The PCI ID database folks don't seem to care if they spam the
/usr filesystem when there's consumers under
/ that need access to it.
And so on and so forth.
That's the nice thing about FreeBSD: it's developed as a whole, so if something is developed that needs to access resources under
/usr very early in the boot sequence, then solutions to make it work are looked at.
Would it really be that hard for the
systemd folks to add a "critical filesystems" checkpoint, and to add
/usr to that? Every other
init system out there can handle that ... except
systemd it seems.
