Brendan Moran wrote: > It turns out it was pretty obvious: > >> -n Starting kernel event manager... >> . >> -n Loading hardware drivers... >> [101] udev_monitor_enable_receiving: bind failed: No such file or >> directory >> error initializing netlink socket >> [101] main: error initializing netlink socket >> udevadm[102]: bind failed: No such file or directory >> >> error: unable to subscribe to udev events > > Checking the source, it appears that having > udev_monitor_enable_receiving fail means that > udev_monitor_new_from_netlink() is already failing. I imagine that I'm > missing a kernel config option, but I'm not sure what it is. Have you taken a look at the udev README? (That's twice lately that I've said that... hmm...) :-)
Attachment:
signature.asc
Description: OpenPGP digital signature