Roman Bysh wrote:
In response to the devs reminding me of my 80's partition config:
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken> And let's clarify a few things:
1. It isn't systemd's fault. systemd works fine with /usr on a separate file system.
Quote from the page you mention: .... the reason systemd is broken, apparently: Quite a number of programs these days hook themselves into the early boot process at various stages. A popular way to do this is for example via udev rules. The binaries called from these rules are sometimes located on /usr/bin, or link against libraries in /usr/lib, or use data files from /usr/share. If these rules fail udev will proceed with the next one, however later on applications will then not properly detect these udev devices or features of these devices. Here's a short, very in-comprehensive list of software we are aware of that currently is not able to provide the full set of functionality when /usr is split off: 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, the locale logic of most programs and a lot of other stuff. ---- Here's the problem...He's mentioning 'user space' programs, ALL should have a ***pre-req**/dependency, on "localfs" -- which would include mounting all of the local hard disks. THEN you proceed to bring up the next dependency --- which...at some point -- what if people have /usr on a network? usually network is brought up, then network disks, THEN you can really start with programs... AT least this is the way its been done for decades...and now the systemd author says...well to get greater speed, we can't be waiting for all those dependencies... so lets just require that /usr already be mounted so we can run everything at once rather than in a 'makefile' like fashion.... It really sounds like the design of systemd is fundamentally flawed -- he wants a completely different starting environment before he brings up services... It really sounds like systemd is NOT meant to be a boot manager, but a **service** manager (Like MS's service's control panel). But it needs all the basic functions up and running so it can start it's services that all depend on basic items being there (like /usr, udev, network disks...etc...)... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org