Re: Problem with udev device identification
El 2011-04-22 a las 17:04 -0400, Sebastian Lara escribió: (resending to the list) El viernes 22 de abril de 2011, Camaleón (...) There must be a string that uniquely identifies the converters despite the device being attached on them... for instance, how about the serial number? This value shouldn't be shared between the tree devices at all :-? Yes. I can even change some serial values but we need to replicate this in several machines. And what's the problem, exactly? :-? You should be able to: 1/ Globally identify the converters by some attribute shared between all of them (such as vendor, device...). 2/ Uniquely identify converters by some attribute not being shared between all of them (such as serial number). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110423110704.ga4...@stt008.linux.site
Re: Problem with udev device identification
On Wed, 20 Apr 2011 17:21:41 -0400, Sebastian Lara wrote: I have three different serial devices connected to three usb-serial converters (FTDI USB-RS232). If I connect them, I get the generic device names /dev/ttyUSBx as expected. When I try to write some udev rules, udevadm shows me the same output for the three devices except in some device serial id attributes. Those serial id's will change on every device so if I use a different usb-serial converter, my rules won't work anymore. So, I need a way to communicate with the specific device connected to the serial converters and identify it by its response. (...) There must be a string that uniquely identifies the converters despite the device being attached on them... for instance, how about the serial number? This value shouldn't be shared between the tree devices at all :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.04.22.15.25...@gmail.com
Problem with udev device identification
Hi everyone, I have three different serial devices connected to three usb-serial converters (FTDI USB-RS232). If I connect them, I get the generic device names /dev/ttyUSBx as expected. When I try to write some udev rules, udevadm shows me the same output for the three devices except in some device serial id attributes. Those serial id's will change on every device so if I use a different usb-serial converter, my rules won't work anymore. So, I need a way to communicate with the specific device connected to the serial converters and identify it by its response. Writing udev rules HOWTO, says the following about using PROGRAM functionality to call an external program to name devices: PROGRAM is used for running programs which produce device names (and they shouldn't do anything other than that). When those programs are being executed, the device node has not yet been created, so acting upon the device in any way is not possible, Rule example: SUBSYSTEM==usb, PROGRAM=/bin/device_namer %k, SYMLINK+=%c so I can't write to /dev/ttyUSBx from there to identify the device. Then, I have the RUN functionality, but it seems that it can't create a new SYMLINK as udev won't get RUN's output. Rule example: SUBSYSTEM==usb, RUN=/bin/program Can I instruct udev from that RUN script to create the symlink? Or can I create that symlink by hand from there? Thanks -- Sebastián Lara Menares Ingeniería Civil Electrónica Universidad de Concepción -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikPy+t3=jccytk6dm3xjsfteyo...@mail.gmail.com
