> On Thu, Jul 2, 2009 at 18:27, Ron Rindjunsky<rindjon@xxxxxxxxxxxxxx> wrote: > > I have written a udev rule to run a script when a particular tty is created. > > This tty (named ttyYY0) is created when i insert a device into the > > SDIO slot in my laptop. > > When inserting the device into a living system, ttyYY0 is created and > > script is always run, but during boot time, with the device already in > > the slot, script is not run. (although even when it fails i do see the > > ttyYY0 in the file system). > > My udev rule looks like this: > > KERNEL=="ttyYY0", ACTION=="add", SUBSYSTEM=="tty", RUN+="my_script.sh" > > udevd version is 141 > > Anyone can help with this issue? > > At bootup, all device events need to be re-triggered when userspace is > ready to handle them. It's usually done with "udevadm trigger". That > should catch your device, as it would be plugged in at that time. > > Kay isn't the triggering suppose to be a system's build in capability after udev got loaded? why and where should i, as a rule's writer, invoke the udevadm trigger? Ron Ron -- 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
