As of now, a udev "add" event on an existing dm device causes the
device node to be removed from the /dev directory, which is bad.
---
storage/__init__.py | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/storage/__init__.py b/storage/__init__.py
index 0a9dad0..34ea0a5 100644
--- a/storage/__init__.py
+++ b/storage/__init__.py
@@ -71,7 +71,7 @@ def storageInitialize(anaconda):
open("/dev/.in_sysinit", "w")
# XXX I don't understand why I have to do this
- udev_trigger(subsystem="block")
+ udev_trigger(subsystem="block", attr_nomatch="dm/name")
# Set up the protected partitions list now.
if os.path.exists("/dev/live") and \
@@ -517,7 +517,7 @@ class Storage(object):
"""
# When a usb is connected from before the start of the installation,
# it is not correctly detected.
- udev_trigger(subsystem="block")
+ udev_trigger(subsystem="block", attr_nomatch="dm/name")
self.reset()
dests = []
--
1.6.2.5
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
