It’s nothing to worry about. It’s just verbosity from the initramfs. udev is your device manager, and it has to create the device special files through which userspace can communicate with the hardware. These device special files live on a devtmpfs, a virtual-memory-based filesystem that gets mounted at /dev during the boot process.
The fact that you may not be seeing that on the other laptop could be due to a whole variety of reasons, such as…
having the quiet boot parameter in /etc/default/grub, which suppresses boot-time verbosity;
Thanks for the feedback. I was questioning because both laptops have verbose startups (quiet not set in Grub configuration file) so I can easily see if a service fails or something marked red. To be honest it is getting harder to see things (age) + I have an SSD in the machine
Based on talking to other people in the forums it seems I should use the command "journalctl -b " to look for boot error messages. Should I be using a different command so I could research the messaging I mentioned?
… shortly after booting ─ you may need to do that with sudo ─ but what you are seeing is not an error message. It’s only verbosity of what the initramfs is doing.
It’s also kernel-dependent, by the way. Newer kernels might be more verbose.
