Am 12.09.2013 14:43, schrieb Mick: >> I don't have that binary. And some page on my way said the >> contrary: set it to empty and let udev (?) do that. > > Ha! Neither do I! > > # ls -la /sbin/hotplug ls: cannot access /sbin/hotplug: No such > file or directory > > I can honestly say that I can't remember filling in this entry when > configuring my kernels, but then how did it get there? >
dunno. Kernel help says about that setting: > Before the switch to the netlink-based uevent source, this was > │ │ used to hook hotplug scripts into kernel device events. It > │ │ usually pointed to a shell script at /sbin/hotplug. > │ │ This should not be used today, because usual systems create > │ │ many events at bootup or device discovery in a very short time > │ │ frame. One forked process per event can create so many > processes > │ │ that it creates a high system load, or on smaller systems > │ │ it is known to create out-of-memory situations during bootup. I also found configs having this: CONFIG_UEVENT_HELPER_PATH="/usr/bin/udevadm" That binary would exist here. I am unsure if I should try that. S
