No, DEVPATH isn't as stable as the physical path. ....Ok, I'm probably confused here, what exactly is the problem that this is trying to solve?Providing physical IDs that are, in common usage, stable: "minor" config changes don't break the IDs ... like adding and removing other USB controllers, enabling or disabling their drivers, reboooting, and so on.But, as you state, even your definition of USB_PATH is not guaranteed to be stable.
"Stable" is a relative term, not an absolute one, for one thing! Also: how would any of those changes cause USB_PATH to change? Certainly USB_PATH is stable in the face of rmmod/modprobe of any host controller driver, unlike DEVPATH for example.
Yes, I'm arguing the "correct" one. But it's not DEVPATH, sinceSo, let us not start to depend on something that is "almost stable" for most people. If we go down that path, we will end up implementing two different solutions, the "easy" one, and then eventually, the "correct" one. I'd rather just implement the "correct" one now, which can be done with DEVPATH and the files located in that directory.
it's something using more stable identifiers; and stable IDs don't
seem to be provided there.
How are you suggesting DEVPATH be used to get the stable IDs,
instead of the USB "bus numbers"? Maybe there's a useful middle
ground here; were you thinking some tool would turn $DEVPATH and
such into stable IDs? I don't care so much what the identifiers
are, but numbers that change when you do something as routine as
adding a driver or controller just don't seem good for managing
configurations.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
