[PATCH 2/2] Call udev_trigger with "change", not "add", to populate udev db. (#531052)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The reason this matters is that device-mapper devices' udev rules
don't respond to "add" events.
---
 storage/__init__.py |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/storage/__init__.py b/storage/__init__.py
index 0a9dad0..f11ae33 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", action="change")
 
     # 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", action="change")
         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

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux