| 1 |
On Thu, 27 Oct 2016 10:25:39 -0400 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> It would be nice if standards like USB incorporated some kind of GUID. |
| 5 |
> I ended up having to write a udev rule for a pl2303 RS232 adapter to |
| 6 |
> tie it to a specific USB port precisely so that I could have more than |
| 7 |
> one and know which one talked to which device. |
| 8 |
> |
| 9 |
> I'd argue that the udev network interface names were a better (if |
| 10 |
> painful to transition to) solution to a problem created by somebody |
| 11 |
> else. Being able to use wildcards in configuration files is probably |
| 12 |
> an adequate solution for those who are using a single device. |
| 13 |
> |
| 14 |
|
| 15 |
You mean like a device serial number? Which is totally part of the USB |
| 16 |
standard, but many devices don’t bother to include one because they |
| 17 |
would have to be serially programmed in the factory? If your device has |
| 18 |
a serial number, you can generally see it as a udev attribute and use |
| 19 |
it to set up meaningful persistent names for multiple |
| 20 |
otherwise-identical devices. |
| 21 |
-- |
| 22 |
Christopher Head |
Archives