> USB_PATH=usb-02:00.0-1.4
> DEVPATH=root/pci0/00:03.0/02:00.0/usb1/1-1/1-1.4/1-1.4:0
>
> Such physical IDs are the only solution for distinguishing N (>1)
> devices that are otherwise identical (no serial numbers etc).
> It's how people use almost every kind of I/O device, except
> that they can't (yet) set up "hands-off admin" with USB.
>
>
> The basic problem with $DEVPATH is its use of the USB "bus number".
> It changes easily in the face of those minor config changes, and
> doesn't correspond directly to any physical reality that a sysadmin
> controls. The PCI slot_name doesn't have those disadvantages(*),
> so for PCI based controllers that's a much more useful bus ID.
What is specific about USB in that regard?
It would seem to me that you'd better export something that stays
the same across reboot, but don't call it USB_something.
DEVPATH indeed seems to be an inferior choice, because you
need extra knowledge to extract a permanent path out of it.
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about
your web server security? Click here for a FREE Thawte
Apache SSL Guide and answer your Apache SSL security
needs: http://www.gothawte.com/rd523.html
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
