I confirm the bug. This prevent me to start/restart udev, and i'm not in a container.
On Sun, 2 Dec 2018 09:00:07 +0000 Jamie Heilman <ja...@audible.transient.net> wrote: > The logic change in the init script to check for a writable /sys is > backwards; udev *should* start if /sys if writable. I don't have experience with container, so can't tell if the logic is backwards, it looks to me that /sys directory is read/execute only in my Debian, but 'test -w' performed by root exit 0.. # cat /home/ombra/udevtest.txt Script started on 2018-12-02 14:36:45+01:00 root@lorenz:~# ls -l / | grep sys dr-xr-xr-x 12 root root 0 Dec 2 14:20 sys root@lorenz:~# test -w /sys root@lorenz:~# echo $? 0 root@lorenz:~# exit exit Script done on 2018-12-02 14:37:37+01:00 I suspect this is breaking the boot sequence in non-systemd installs, can you please revert to using "ps" for this test untill you sort it out? Thanks, Lorenzo
