URL:
Reporter RHNID:
Section: -
Language:
Workaround:

Description: In the "Writing Custom udev Roles" content, please expand content.

Perhaps add some examples from the default shipped rules?
I used to use some of the cdrom rules as examples. Those have used PROGRAM to figure out if it is cd cdrw dvd dvdrw and then SYMLINK+= based on the results. Now I also look through the persistent storage rules reference in the performance test.

Also can we expand on some of the matches used in the case studies?
And/or a summary chart with the common methods:
ACTION match on "add", "change", "remove"
SUBSYSTEM often matched on "block", "scsi"
PROGRAM run any cmd, the result may be evaluated with RESULT
ATTR, ENV, SYMLINK, RUN

During the labs I get asked:
If I am I specifying a virtio_dsk in DRIVERS why do I also need to specify SUBSYSTEM="block"
I am using ATTR (from attribute-walk query) instead of ENV, is that OK?
Do we have to have the ACTION="add"?