Ever wondered why a certain rule doesn't get run? Ever got confused (or disgusted) by udev rules format?
Well, despite all the udev clutter, there are many useful tools in the udev package, which help to understand udev's behavior and decision making. I'm still far from knowing all the tricks, but here are some things that I've learned recently:
Note: the udev tools got changed several times during the last 5 years. I'll cover here the latest version (149), and the older, RHEL/CENTOS5 version.
1. udevadm info: get all info available to udev about a certain device (or all devices):
# udevadm info -e (RHEL5: udevinfo -e)
Try it.. amazing, eh? You can use each detail to write udev rules to match these devices.