Re: [PATCH 2/2] Filter out device-mapper devices when doing a udev_trigger.

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

 



On Wed, 2009-10-21 at 14:05 -0400, Chris Lumens wrote:
> > 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 = []
> 
> Will we want to leave this in after device-mapper gets fixed?

Probably not, but I'm not sure. It depends on what solution, if any, is
found for the dm/udev problems.

Dave

> 
> - Chris
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

_______________________________________________
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