Bug#908796: udev 240-2: failed to connect to udev daemon (on boot)

[Trek]

On Mon, 21 Jan 2019 16:34:56 +0000
js jb <em2jacks at yahoo.com> wrote:

> I'm surprised at the change between udev_240-2  and udev_240-4, since
> I thought the -4 refers only to the debian revision but it resultedin
> a significant change in the package's usability.

some patches were gracefully backported from the next release by Michael
Biebl: it appears to me (please correct me if I'm wrong) that systemd
uses a rolling release model, so there are not (yet) any point releases
and it's up to the package maintainers to backport the bug fixes

as this bug is a race condition, something that comes up in relation to
the timings when things are executed, there is a chance these patches
changed the timings and the bug don't come up anymore

moreover, one of these patches may be fixed the roots of this race
condition: "sd-device-monitor: fix ordering of setting buffer size"
https://github.com/systemd/systemd/commit/ee0b9e721a368742ac6fa9c3d9a33e45dc3203a2

the buffer was too small to receive all the uevents, if they were not
processed in time by udev

anyway I hope this explained why a debian revision resulted in code
change and thus restored the usability


ciao!