On Mon, Aug 03, 2026 at 10:13:23AM +0200, Alessandro Vesely via Dng wrote:
> Hi
>
> On Tue 07/Jul/2026 13:56:56 +0200 Alessandro Vesely wrote:
> > after a (successful) boot, dmesg shows lines like the following:
> >
> > [ 1.037451] udevd[225]: starting version 3.2.14
> > [ 2.041066] random: crng init done
> > [ 2.042598] udevd[227]: starting eudev-3.2.14
> >
> > That middle log is printed by random.c:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/
> > drivers/char/random.c#n738
> >
> > The udevd init file stays at /etc/rcS.d/S02udev.
>
> In order to better understand the issue, I added an 'x' on the she-bang line
> of both udev and eudev in /etc/init.d/, so that they read
>
> #!/bin/sh -ex
>
> However, the output remains the same, both on screen and in dmesg:
>
> [ 1.029490] Run /init as init process
> [ 1.029543] with arguments:
> [ 1.029545] /init
> [ 1.029547] with environment:
> [ 1.029548] HOME=/
> [ 1.029549] TERM=linux
> [ 1.064359] udevd[221]: starting version 3.2.14
> [ 2.096511] random: crng init done
> [ 2.098060] udevd[222]: starting eudev-3.2.14
>
> How come command lines are not shown?
apparently there are 2 init scripts concerned with some "udevd":
/etc/init.d/eudev
/etc/init.d/udev
The second belongs to initscripts and is a gift from debian that
should be disabled by not having /lib/systemd/systemd-udevd
The first, which for me is the S02 link, is the one in use.
Sometimes that takes time, for example when it involves network
configuration (due to some allow-hotplug declaration) and the DHCP
response is slow, but alos other reasons.
To trace udevd, you may need to instrument the init script with a
"udevadmin monitor 2>&1 &" or something similar.
Ralph.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
> _______________________________________________
> Dng mailing list
> Dng@???
> Manage your subscription: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> Archive: https://lists.dyne.org/lurker/list/dng.en.html