On 2012-12-25, Michael Mol wrote: > Now, question: could I not create a "/usr" service and make things > dependent on /usr come after it's been mounted? That seems the single, core > missing piece.
This suffices for /usr on regular partitions. The problem is with more complex stuff which, I assume (assume, because nobody who actually has that setup has actually explained what happens), requires device files which are not present under /dev by default, and, even if /dev is already mounted once init is started, it only has a handful of default files. The additional, non-default files for most of the stuff are nowadays created through udev, and so you need to have udevd running and processing events to populate /dev. Thus: - The already existing "rules will silently fail" problem will not be solved, as some events will get processed before you have a chance to mount /usr - The "udev won't work because it is under /usr" issue, which seems to be the case of udev since it got merged with systemd (once again I'm assuming here, from a bug report)), well, this one is not easy to solve unless you copy the udev tools to / or to some initr*, or you install udev to /. But, of course, for /usr on regular partitions, just issuing "mount /usr" before starting udevd works. -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/