On 04/29/2009 10:46 PM, Kay Sievers wrote:
>> TEST=="dm", ENV{DM_NAME}="$attr{dm/name}", ENV{DM_UUID}="$attr{dm/uuid}"
>> TEST!="dm", IMPORT{program}="/sbin/dmsetup info -j %M -m %m -c --nameprefixes --noheadings --rows -o name,uuid"
>
> Wasn't there something that added the DM_* variables to the kernel
> directly? I remember seing something a while back. If that is still
> planned or possible, maybe you can just do thes both rules only if the
> values are not set?
>
> ENV{DM_NAME}="", ENV{DM_NAME}="$attr{dm/name}", ...
> ENV{DM_NAME}="", IMPORT{program}= ...
I think these are multipath uevents only. But uevents for plain
DM devices don't have these vars set. But yes, we can save a little
time in that particular situation.
>> ENV{DM_NAME}=="?*", NAME="$kernel", SYMLINK+="mapper/$env{DM_NAME}"
>
> NAME="$kernel" is the default, it's not needed.
..ok
> Yeah, looks great.
Thanks! :)
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
