shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity

udev: drop cryptsetup specific rules from 10-dm.rules

Browse Source 
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
This commit is contained in:
Peter Rajnoha 2014-01-22 15:15:02 +01:00
parent d2956f0a59
commit 36a09cf463
2 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
WHATS_NEW_DM
View File

@ -1,5 +1,6 @@
Version 1.02.85 - Version 1.02.85 -
=================================== ===================================
Drop cryptsetup specific rules from 10-dm.rules - cryptsetup sets them.
Version 1.02.84 - 20th January 2014 Version 1.02.84 - 20th January 2014
=================================== ===================================

2
udev/10-dm.rules.in
View File

@ -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 # We have to ignore further rule application for inappropriate events
# and devices. But still send the notification if cookie exists. # 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}=="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) # Avoid processing and scanning a DM device in the other (foreign)
# rules if it is in suspended state. However, we still keep 'disk' # rules if it is in suspended state. However, we still keep 'disk'