On Sat, Jan 21, 2012 at 23:44, William Hubbs <w.d.hubbs@xxxxxxxxx> wrote: > On Tue, Jan 17, 2012 at 08:25:07PM +0100, Piotr Karbowski wrote: >> After starting udev on the /dev which is devtmpfs the udev does not >> 'take over' already created nodes unless I add in the udev's init script >> >> 'udevadm trigger --type=devices --action=change' >> >> right after >> >> 'udevadm trigger --type=devices --action=add' > > I had asked about this myself here (this is actually a gentoo bug report > and Piotr has now brought it to this list). I also researched the > systemd services and found that our inig script is using the correct > startup sequence to bring up udev. In other words, Piotr is using a > workaround which isn't the correct fix. > > Can anyone point the right direction for getting this fixed? I guess it's some Gentoo-specific bug. Almost everybody just does: 'udevadm trigger --type=devices --action=add' once at bootup and nothing else. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
