Galen, you are correct! So long as the device is attached AFTER the udev rule is in place, it will work properly. If you create or change the udev rule with the device attached, you will need to either restart the service or simply unplug and reconnect the device. This makes sense, I just wished I had realized it earlier when I was trying to flash the ROM on my Android phone... It would have saved me some time and frustration...
Live and learn. Thanks for pointing this out, Jason On Tue, Sep 20, 2011 at 2:37 PM, Galen Seitz <[email protected]> wrote: > Jason Barnett wrote: > > try adding a udev rule with the following lines in it: > > > > SUBSYSTEM=="usb", SYSFS{idVendor}=="*0bb4*", MODE="0666" > > SUBSYSTEM=="usb", ATTRS{idVendor}=="*0bb4*", MODE="0666" > > > > of course change the 0bb4 with the vendor ID of your device. You will > also > > need to restart the udev service (or reboot) to get the new rules to take > > effect. > > I could easily be wrong, but I don't think a restart is needed. > > "Assuming you are on a recent kernel with inotify support, udev will > automatically monitor your rules directory and automatically pick up > any modifications you make to the rule files." > http://reactivated.net/writing_udev_rules.html#testing > > -- > Galen Seitz > [email protected] > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
