Hardware Hotplug Events on Linux: The Gory Details

Developer arcanenibble published a detailed technical deep-dive into how Linux handles hardware hotplug events, covering the full stack from kernel uevents and udev through D-Bus, systemd, and user-space daemon responses. The post explains the difference between kernel uevents, netlink sockets, and udev rules, and shows exactly what happens at each layer when a USB device, NVMe drive, or network card is inserted into a running Linux system. The post accumulated 111 Hacker News points and is useful for kernel developers, embedded engineers, and sysadmins who need to reason about hotplug reliability in production Linux environments.

Key Takeaways

• Covers the complete Linux hotplug stack: kernel uevent → netlink socket → udev daemon → udev rules → D-Bus signals → user-space consumers; explains each layer's role and failure modes
• Distinguishes between kernel-initiated uevents, udevadm synthetic events, and coldplug enumeration at boot — common sources of confusion in embedded and server Linux debugging
• 111 HN points and 5 comments as of March 2, 2026; relevant to kernel module developers, udev rule authors, and engineers debugging device enumeration on headless/embedded Linux

Original source: arcanenibble.github.io