On Fri, Aug 20, 2010 at 05:31:12PM +0200, Kay Sievers wrote: > On Fri, Aug 20, 2010 at 17:00, Wolfgang Wegner <ww-ml@xxxxxx> wrote: > > On Fri, Aug 20, 2010 at 04:51:44PM +0200, Kay Sievers wrote: > >> The event for the device happens during early boot where you have no > >> chance to mount. Do you run 'udevadm trigger' at bootup? It will > >> re-generate all events so that they can be handled when userspace is > >> running. It would need --action=add for your current rule to match. > > > > The busybox start script (/etc/init.d/rcS) runs my udev start script > > (/etc/init.d/start_udev.sh) which in turn runs udevadm trigger as > > one of the last steps: > > > > [...] > > udevd --daemon --debug > > > > mkdir -p /dev/.udev/queue/ /dev/.udev/rules.d/ > > create_dev_root_rule /dev/.udev/ > > > > udevadm trigger > > As mentioned, add --action=add. Or make the rule match on 'change' too. Thanks, that helped! I was reading the manpage on my debian box, which is using udev-125 and thus the documentation is horribly outdated in some parts, i.e. I was still under the impression --action=add was the default. Thanks for the help, now everything works like a charm and I can think about the proper mount script/command. Best regards, Wolfgang -- 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
