Sorry, Linda, if this seems preachy, its not targeted at you, its as much clarifying the logical steps in my own mind before my first litre of coffee and sugar jolt. On 12/26/2016 09:49 PM, L A Walsh wrote:
Anton Aylward wrote:
Maybe those udev script were simply in /usr/lib/udev or possibly the executable ...
greping, I get:
grep -i /usr/share *
[snip] Noted
---- A few of those are third party scripts, others may have been moved elsewhere. Anyway, those are ones I have now.
Yes, but my point holds. Those are not needed for ... OK, perhaps we have a terminological difference. Perhaps to some, the term 'boot' means *EVERYTHING* between pressing the power on button and seeing the login appear. 'The "*EVERYTHING*" means every last little thing that includes starting up the user space services like SMB, Proftp ((even if it is still 32-bit), Postfix, Apache, /home and all the file systems that the user may have under his/her home directory all mounted, ready, before login. In that case you're going to need /srv mounted as well! On the other hand some of us view 'boot' as very basic. Boot gets you to 'maintenance mode' where you have a very basic system, the shell, a few utilities, perhaps enough to repair your file system. If you've never needed to flutz around in maintenance mode you've been lucky. But its there, the most basic of boots. No file systems other than ROOTFS available. Believe me, it works even if you have /usr as a separate file system. The 'why' is interesting. The very basic boot involves having a runable system - just - in the initrd. Go look at what is delivered in an initrd using 'lsinitrd'. To my mind, the issue with /usr boils down to two things. 1. Is there enough in the initrd to allow systemd to mount /usr? That means one of two things: a) is there a custom unit, something that is like "usr.mount", under /etc/systemd in the initrd that will allow the initrd to mount /usr b) an entry in the /etc/fstab of initrd and the systemd generator that allows it to build the unit to mount /usr and 2. is there stuff in /usr that is essential to the boot process? We've been thinking of specific executables and libraries here, but Linda is right in pointing out that scripts matter too. Are there, for example, units in /usr/lib/systemd that are necessary for the boot process? well OUCH! I've edited this down ... its from my running 13.2 system. YMMV # ls -l /etc/systemd/system total 32 lrwxrwxrwx 1 root root 44 Nov 6 2013 dbus-org.freedesktop.Avahi.service -> /usr/lib/systemd/system/avahi-daemon.service lrwxrwxrwx 1 root root 45 Jul 10 10:13 dbus-org.opensuse.Network.AUTO4.service -> /usr/lib/systemd/system/wickedd-auto4.service lrwxrwxrwx 1 root root 45 Jul 10 10:13 dbus-org.opensuse.Network.DHCP4.service -> /usr/lib/systemd/system/wickedd-dhcp4.service lrwxrwxrwx 1 root root 45 Jul 10 10:13 dbus-org.opensuse.Network.DHCP6.service -> /usr/lib/systemd/system/wickedd-dhcp6.service lrwxrwxrwx 1 root root 45 Jul 10 10:13 dbus-org.opensuse.Network.Nanny.service -> /usr/lib/systemd/system/wickedd-nanny.service lrwxrwxrwx 1 root root 40 Jul 11 2014 default.target -> /usr/lib/systemd/system/runlevel5.target lrwxrwxrwx 1 root root 38 Jul 10 10:13 network.service -> /usr/lib/systemd/system/wicked.service lrwxrwxrwx 1 root root 39 Nov 6 2013 syslog.service -> /usr/lib/systemd/system/rsyslog.service Which gets back to the issue, how many of those are essential for whatever you view as 'boot'? I ask this because those don't appear in the 'lsinitrd'. You might also notice when you run 'lsinitrd' that there is a "/usr" subtree there. So the intird has all that's needed to do the boot even if, in the initrd, some things from /bin are symlinked to /usr/bin (rather than the other way round). So when, exactly does what's in /usr on the disk become essential because its not part of /usr in the initrd? I see earlier on in the 'lsinitrd' output that Drakut includes some modules. Perhaps the issue is in getting the right modules included. For example, I have everything except /boot and SWAP on LVM. That includes the ROOTFS. So the LVM modules needs to be included in initrd. I see, also, that there is a 'usrmount' modules there. Hmm. Need to drill down there.
I think the one that caused probs was a virtual-machine sw-package that had usb drivers (or a script for such) in /usr/share/...
It may be that they've been weeded out of post 13.1 or post 13.2 dists.
-- The reasonable man adapts himself to the world; the unreasonable one persists to adapt the world to himself. Therefore all progress depends on the unreasonable man. --George Bernard Shaw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org