My 5ct & how I currently do it (for 6+ years, 2x weather-stations, DMX ir, x10, heat-pump, vents, and three different 1w-bm on a single host):
PL2303(they have no serial# but are working reliable & are cheap) - udev-rules, Port/Bus/Devid: very error prone. Things depend on the reboot-pattern, if you connect one after reboot: surely it gets another Bus/Devid after the next boot..) Upgrading (just for example!) 2.6.32 to 3.x mixes up everything. -> Thats IMHO not acceptable for a long-term, stable system. FT(DI)2/4xxx: we have a serial, a customizable Vendor-Name (not id, it's still FTDI) so owfs (or udev-rule) could search for something specific (or smthg. specific like serial#) could be put into the config. Really, I think the whole thing with /dev/ttyUSBx in *nix is at least as broken as assigning a random COMx under WinDos after every boot. The only method for "anonymous devices" is, as Paul did, to look at bus#/dev# - but they might change after a reboot even without the user doing anything.. And then, if you "probe" them: other things might (will?) fail. IMHO the only reliable method is to look at the Vendor/product-id/name/descr etc. and only probe/init these, anything else could(?) make other things fail. I dont want to dig into details too deep now, but we had really a bunch of headaches (not owfs, Kernel-Bugs!) with an FTDI-based 1w-master. And another big headache with OLA(DMX), just because it scanned "wild" over any ttyUSB available.. With the DS9490 its much easier (as VID/PID are clear, no other devices using the same) - but even this took years to be perfectly fine in owfs, as we learned :) I just ask to not repeat already learned lessons, I (we?) cannot fix the design-problem in Linux with ttyUSB* but maybe handle it carefully, at least by owfs doing things as "automagically" as possible (I'm 100% pro for that!) but not touching other ttyUSB*.. best regards Michael ------------------------------------------------------------------------------ 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
