Re: udev or kernel broken with rsdl 0.30 patch

[Andreas Jellinghaus <aj@leogic.com>]

Am Freitag, 16. März 2007 13:48 schrieb Kay Sievers:
> > what exactly is "wait_for_sysfs"? I'm asking because it shows up in the
> > udevd log right before openct is started / should be started. I thought
> > it would take care of problems like this? or does it only check the
> > basedir, and not the subdirs / files in the dirs to be present or
> > something like that?
>
> It waits for what you ask it to wait for. This may work:
>   SUBSYSTEM="usb", KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceProtocol"

I tried it like this:
BUS!="usb", ACTION!="add", GOTO="openct_usb_rules_end"

KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceClass"
KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceSubClass"
KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceProtocol"

SYSFS{bInterfaceClass}="0b", SYSFS{bInterfaceSubClass}="00", 
SYSFS{bInterfaceProtocol}="00" RUN+="/lib/udev/openct_usb"

LABEL="openct_usb_rules_end"

i.e. with extra lines in the config file. is that correct? now I have a 50/50
chance that openct_usb run (I plugged in&out 15 times for testing).
and I get lots of warnings during boot because some usb hardware
doesn't have these attributes. is there a way to restrict them to 
everything that has a usb device file?

Thanks, Andreas

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel