jprzybylski |
11-14-2013 02:52 PM |
Quote:
Originally Posted by Alien Bob
(Post 5064433)
As far as I know, SystemD does not support /usr being a separate filesystem unless you yourself ensure that it gets mounted before SystemD starts (i.e. you need to mount it in the initrd). See http://freedesktop.org/wiki/Software...usr-is-broken/ for a piece of arrogance barfed up by our favourite Slackware destroyer.
|
Now, see, most days I don't mind systemd too much, but then they have things like this:
Quote:
Here's a short, very in-comprehensive list of software we are aware of that currently are not able to provide the full set of functionality when /usr is split off and not pre-mounted at boot: udev-pci-db/udev-usb-db and all rules depending on this (using the PCI/USB database in /usr/share), PulseAudio, NetworkManager, ModemManager, udisks, libatasmart, usb_modeswitch, gnome-color-manager, usbmuxd, ALSA, D-Bus, CUPS, Plymouth, LVM, hplip, multipath, Argyll, VMWare, the locale logic of most programs and a lot of other stuff.
|
And I think - why not just mount the stuff on fstab first? And who wants to run this stuff before filesystems come up? hplip? Really? Is it a problem that their core init program is linked to all this stuff, and this stuff is on /usr? How about not making the init linked to all this and, after processing fstab, start the bigger part of systemd? Seems easier than changing a 40-something-year-old concept.
But then I read this, and I get it. The word 'Solaris' appears 12 times. Compatibility to other Unixes/Linuxes translates to Solaris. Upstream is Solaris. Despite our closer cousins in BSD, they don't get mentioned once. It's an enterprise move so that Oracle doesn't need to try so hard to port our software.
In the end, if the technical reasons don't make sense, it's because they're made after the fact - it's really about the politics.
But now I'm being mean. I still want to see good stuff come out of these SlackBuilds!
EDIT: Heh, we were still on page 2 when I started that... whoops...
|