From: Skeptic <per...@br...> - 2011-04-28 11:21:19
|
I have a Huawei USB GSM modem which normally creates 4 ttyUSBn device files where n may be 0..3 or 1..4 depending on if the FTDI USB driver of an Android card is detected last or first. I believed that adding an udev-rule should give me a known device filename if the rule requirements were met - and no device file name if not. Yes, it worked - but I can boot the overo without the hardware attached, and the device filenames are still there! Is this a bug or a feature? I believed udev should populate the /dev catalog only with devices that are present? What have I missed? Here is my rule: DRIVERS=="option", ATTRS{bInterfaceNumber}=="00", NAME="ttyMODEM0" DRIVERS=="option", ATTRS{bInterfaceNumber}=="01", NAME="ttyMODEM1" DRIVERS=="option", ATTRS{bInterfaceNumber}=="02", NAME="ttyMODEM2" DRIVERS=="option", ATTRS{bInterfaceNumber}=="03", NAME="ttyMODEM3" ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="A400g2EY", NAME="ttyAVR" Regards Per -- View this message in context: http://old.nabble.com/udev-and-persistence-of-device-files-tp31495481p31495481.html Sent from the Gumstix mailing list archive at Nabble.com. |