Re: udev doesn't know about devices further up the tree.

[Kay Sievers <kay.sievers@vrfy.org>]

On Fri, 2006-06-16 at 09:05 +0100, Simon Huggins wrote:
> I wrote my first udev rule the other day.
> 
> It reads:
> KERNEL="sd*", PROGRAM="/home/huggie/bin/camera %k", SYMLINK+="%c"
> where bin/camera does:
> DEV=$1
> DISK=`echo $DEV|sed -e 's/.*\(sd.\).*/\1/;'`
> udevinfo -a -p /block/$DISK/$DEV|grep manuf|grep PENTAX >/dev/null 2>&1 && \
>         echo camera && exit 0
> 
> i.e. basically if the usb device (or any device because I'm not that
> fussy) above the block device is made by PENTAX then echo camera
> otherwise I just echo $DEV back again.
> 
> But it strikes me as a bug that I have to spawn out of udevd to run
> udevinfo in order to just name the device based on what it is.
> 
> 
> Why aren't SYSFS attributes from higher up the device path available
> somehow when writing rules?

Adding a single SYSFS attribute:
  SYSFS{vendor}="PENTAX"
or
  SYSFS{manufacturer}="PENTAX"

should do it and will try to find the value on all devices up the chain,
but you can't mix SYSFS, BUS or ID values from different devices.

Kay



_______________________________________________
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