I found a blog posting that expresses my sentiments on Lucid's udev exactly:
http://shallowsky.com/blog/linux/kernel/lucid-udev.html This is good enough to quote. I love how if you give the udevadm info arguments in the wrong order, -p -a, it means something else and gives an error message. I love how udevadm test doesn't actually test the same rules udev will use, so it's completely unrelated to anything. I love the complete lack of documentation on things like string matching and how the numeric order is handled. I love how you can't match both the device name (a string) and the USB IDs in the same rule, because one is SUBSYSTEMS=="scsi" and the other is SUBSYSTEMS=="usb". Finally, I love how there's no longer any way to test udev rules on a running system -- if you want it to actually create new devices, you have to reboot for each new test. service udev restart and udevadm control --reload-rules don't touch existing devices. Gives me that warm feeling like maybe I'm not missing out on the full Windows experience by using Linux. -- ATTR{class} rules in /etc/udev/rules.d/ no longer work https://bugs.launchpad.net/bugs/606524 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
