On 24 Sep 2014, at 16:21, Tomasz Torcz <to...@pipebreaker.pl> wrote:
> On Wed, Sep 24, 2014 at 04:09:23PM +0200, Ekkehard Pofahl wrote:
>> 2014-09-24 12:29 GMT+02:00 Colin Law <clan...@gmail.com>:
>>
>>> unplug a linkUSB and plug it straight back in then it may change
>>
>>
>> Agreed. But plugging and unplugging is usually not done on a "production"
>> system. After reboot you should see the same configuration every time ?
>
> There's no guarentee, USB inherently dynamic bus. Using persistent device
> names (/dev/serial/by-id/ etc.) is the only sane way.
or by udev rules. For my LinkUSB I use
SUBSYSTEM=="tty", \
ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="XXXXXXXX", \
SYMLINK+="linkUSB0", GROUP="owfs"
where I got the XXXXXXXX serial number by inspecting the output of
udevadm info -n /dev/ttyUSB0 -a
so udev setups a symlink from /dev/linkUSB0 to the correct /dev/ttyUSB<n>
The same /dev/ttyUSB<n> is accessible as
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_XXXXXXXX-if00-port0
but I prefer the shorter "ad hoc" one.
Both the custom /dev/linkUSB0 and the default /dev/serial/... are in charge of
udev, so on openWRT you have to check if udev is installed and its
configuration files.
(On my debian system there is a /lib/udev/rules.d/60-persistent-serial.rules
that handles links in /dev/serial/...)
Stefano------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
