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

[Trek]

On Mon, 1 Oct 2018 01:11:30 +0200
Michael Biebl <biebl at debian.org> wrote:

> The only supported way in udev to signal readiness is the sd-notify
> API. My gut feeling is, that having an sd-notify wrapper for
> non-systemd systems (e.g. directly built into start-stop-daemon via
> say an --wait-for-sd-notify switch) would be the cleanest and most
> robust way. This might even benefit other daemons besides udevd.

nice catch, but probably it cannot be done in time for buster freeze

after another code inspection, I wrote a simpler version of the patch,
as it only checks for the existence of the control file

it should be sufficient as udev --daemon forks and exits just after
calling listen_fds(), that creates the control file via bind()

to Bill Brelsford: please, can you try again if this new patch fixes the
problem? thank you!

ciao
-------------- next part --------------
A non-text attachment was scrubbed...
Name: systemd-trigger-wait2.patch
Type: text/x-patch
Size: 1359 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181001/e1934717/attachment-0002.bin>