You can create a file /etc/udev/rules.d/65-dmsetup.rules, which will override the file in /lib/udev/rules.d/.
In lucid this seems to be handled completely differently (and much better imho):
From /lib/udev/rules.d/56-lvm.rules:
# Use DM name and split it up into its VG/LV/layer constituents.
IMPORT{program}="/sbin/dmsetup splitname --nameprefixes --noheadings --rows $env{DM_NAME}"
(this creates the DM_VG_NAME, DM_LV_NAME and DM_LV_LAYER environment variables)
And then, in /lib/udev/rules.d/60-persistent-storage-lvm.rules:
You can create a file /etc/udev/ rules.d/ 65-dmsetup. rules, which will override the file in /lib/udev/rules.d/.
In lucid this seems to be handled completely differently (and much better imho):
From /lib/udev/ rules.d/ 56-lvm. rules:
# Use DM name and split it up into its VG/LV/layer constituents. program} ="/sbin/ dmsetup splitname --nameprefixes --noheadings --rows $env{DM_NAME}"
IMPORT{
(this creates the DM_VG_NAME, DM_LV_NAME and DM_LV_LAYER environment variables)
And then, in /lib/udev/ rules.d/ 60-persistent- storage- lvm.rules:
ENV{DM_ VG_NAME} =="?*", ENV{DM_ LV_NAME} =="?*", ENV{DM_ LV_LAYER} =="", SYMLINK+ ="$env{ DM_VG_NAME} /$env{DM_ LV_NAME} "