Systemd incompatible with mounted /usr

Posted Mar 4, 2011 3:50 UTC (Fri) by mezcalero (subscriber, #45103)
In reply to: Systemd incompatible with mounted /usr by jmorris42
Parent article: Quotes of the week

Well, such an automatism is pointless and wouldn't work anyway, since to mount things in the right order at the right time you need udev around, but the udev rules are the ones needed /usr. Hence you would want to mount /usr both before and after starting udev. Which logic shows is not possible.

Systemd incompatible with mounted /usr

Posted Mar 21, 2011 16:22 UTC (Mon) by gvy (guest, #11981) [Link] (2 responses)

# find /usr -name '*udev*'
[.../usr/share/{vim,doc,man}...]
/usr/libexec/ConsoleKit/run-seat.d/udev-acl.ck

And the rest is under /{etc,lib}/udev here on ALT Linux.

Could you please elaborate on "the udev rules are the ones needed /usr", or perhaps just file a bug proper?

> Hence you would want to mount /usr both before and after starting udev.
> Which logic shows is not possible.
Heh. There's a theory for inventor's problems, you might enjoy reading up on that, as well as on formal logic; see at least http://en.wikipedia.org/wiki/TRIZ -- in this particular case, the "visible" controversy is solved by "doing beforehand", that is, moving udev rules from /usr into root filesystem. No rocket science at all.

Systemd incompatible with mounted /usr

Posted Apr 18, 2011 20:24 UTC (Mon) by nix (subscriber, #2304) [Link] (1 responses)

Some rules (a very few, but perhaps more in time) want the PCI and USB ID databases, as well. Of course this should be fixed by eliminating /usr and annoying everyone who has to reinstall their entire systems, rather than by, I dunno, introducing /share, moving the ID databases there, and leaving a symlink where they came from.

As you know, "do things the hugely inconvenient way" is the new Linux slogan.

Systemd incompatible with mounted /usr

Posted Apr 19, 2011 1:06 UTC (Tue) by jrn (subscriber, #64214) [Link]

I thought the drive to make a /usr -> / symlink possible came from GNU Hurd developers in the hope of making PATH=/bin a viable configuration (and thus simplifying the concept of path resolution for users)?