Bug#908796: udev (with sysvinit) fails to find devices at boot

Trek trek00 at inbox.ru
Wed Oct 3 12:20:38 BST 2018


thanks to Bill Brelsford, the last test confirmed we are in the worst
situation: udev is running, the control file is created, but udev is
not ready to listen new events

so we must to rethink about the 791944 bug: it was caused because udev
no longer removes the control file on stop

we have at least three options to workaround it:

1) revert the 791944 patch, create a new init.d/udev-clear script to
remove the control file and run it just after sendsigs (this will
restore the old well tested behavior) 

2) revert the 791944 patch, remove the control file on stop in
init.d/udev, stop it after sendsigs and remove udev from the Should-Stop
header in any script, probably cryptdisks, mdadm and lvm2 (this could
break any script that depends on udev and not distributed by debian)

3) do not revert, but start with udevd --background and create the
pidfile using pidof udevd (this could break if there are more than one
process of udevd)

what do you think about?

thanks for your time
Trek




More information about the Pkg-systemd-maintainers mailing list