fsmithred wrote on 01/09/16 06:17:
...
OS_TYPE=255/255/255
...
My worry is that the OS_TYPE=255/255/255 condition is not distinct
enough to make the action apply exactly and only for scanners. Comparing
with udev rules, you'll find there are more than a few rules for USB
devices, and almost all of them make their classification based on the
vendor/product pair (rather than the capability declarations).
Translated to vdev, it would mean to use match criteria of the form
OS_PRODUCT=$V/$P/$N with $V=vendor, $P=product, $N=version. The value
match processing is literal, and you'd thus need a separate action for
every $V/$P/$N. (Like udev)
Alternatively, one could have the one action (without OS_PRODUCT), and a
new, clever helper to assign access group via a database of
$V/$P/$N->group mappings. Perhaps people previously involved in vdev
development would have a view on this? The helper itself is trivial, but
it'll depend on the database, and the major work would be in preparing
that database (or finding and adapting an already existing one).
Ralph.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
