https://bugzilla.novell.com/show_bug.cgi?id=772286 https://bugzilla.novell.com/show_bug.cgi?id=772286#c1 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #1 from Neil Brown <nfbrown@suse.com> 2012-09-12 07:50:30 UTC --- (sorry for the delay in getting to this). I think I have discovered the problem, and the magic incantation which makes the problem disappear. Please edit "/etc/init.d/boot.md", find a line near the top which reads: # Required-Start: boot.udev boot.rootfsck and add the string udev-trigger to the end (with a 'space' to separate it from the previous word). boot.md uses "udevadm settle" to wait for all udev events to complete, but thes requires that the events have been triggered. In the old sysv-init world, the script "/etc/init.d/boot.udev" would start udev and trigger the events. As boot.md "Requires" "boot.udev", it wouldn't run until the triggering had happened. In the new "systemd" world, there are two separate services, boot.udev and udev-trigger. boot.md needs to wait for both. I suspect that we need to do a little more than just that change for a complete solution as it will probably confuse sysvinit. Frederic: you are our resident systemd person. What do you suggest here? Is just adding "udev-trigger" correct? Might it confuse sysvinit? Would we care? I just tried booting with sysvinit and it works, but if I run "insserv boot.md" it complains: FATAL: service udev-trigger has to be enabled to use service boot.md as expected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.