diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2014-01-22 15:15:02 +0100 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2014-01-22 15:18:57 +0100 |
| commit | 36a09cf463b68cc56330db43d44e02932c12251b (patch) | |
| tree | e0b1ce511da5e5369c5df2667582cd8617a712a4 /udev | |
| parent | d2956f0a594c0522de925ab3ca47a56a5a09a2c7 (diff) | |
| download | lvm2-36a09cf463b68cc56330db43d44e02932c12251b.tar.gz | |
udev: drop cryptsetup specific rules from 10-dm.rules
These udev flags are set directly in cryptsetup for some
time now so there's no need to have it in our rules then.
See also:
https://code.google.com/p/cryptsetup/source/detail?spec=svn4f14b43a3d3e7310465005c401f37e19f8cb85e6&r=4f14b43a3d3e7310465005c401f37e19f8cb85e6
Diffstat (limited to 'udev')
| -rw-r--r-- | udev/10-dm.rules.in | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/udev/10-dm.rules.in b/udev/10-dm.rules.in index f7088f1d3..2755530bf 100644 --- a/udev/10-dm.rules.in +++ b/udev/10-dm.rules.in @@ -123,8 +123,6 @@ ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*", SYMLINK+="(DM_DIR)/ # We have to ignore further rule application for inappropriate events # and devices. But still send the notification if cookie exists. ENV{DM_UUID}=="mpath-?*", ENV{DM_ACTION}=="PATH_FAILED", GOTO="dm_disable" -ENV{DM_UUID}=="CRYPT-TEMP-?*", GOTO="dm_disable" -ENV{DM_UUID}!="?*", ENV{DM_NAME}=="temporary-cryptsetup-?*", GOTO="dm_disable" # Avoid processing and scanning a DM device in the other (foreign) # rules if it is in suspended state. However, we still keep 'disk' |