Bastian Blank wrote: > On Fri, Oct 16, 2009 at 11:55:55PM +0200, Bastian Blank wrote: >> On Fri, Oct 16, 2009 at 11:43:52PM +0200, Bastian Blank wrote: >>> Okay. What about point 1 of my list? This still probes device-mapper >>> devices. > > | - Probe for partitions, aka open, on all block devices with a (small) > | blacklist. This can be only allowed with a whitelist, as several > | device types may not be queried from add events or not at all, like > | several dm subtypes. > >> This patch should use an apropriate whitelist.
So, here is a status update on this issue: What happened so far is, that I removed the blkid call for dm devices. I also dropped the devkit-disks-dm-export prober altogether and instead rely on the information setup by dmsetup/cryptsetup. The last bit is the devkit-disks-part-id prober. Unfortunately I can't just drop this prober completely for all dm/md devices, as you might have partitioning information on such a device. Discussing with upstream, 95-devkit-disks.rules was changed to only act on "change" events (and not "add|change") and I additionally added a rule to skip devices where DM_HIDE==1 is set. The latest state is at http://git.debian.org/?p=pkg-utopia/devicekit-disks.git;a=summary and I plan to upload that soonish as 009-1. Hopefully this addresses your remaining complaints in a sufficient manner so the conflicts in dmsetup can be removed again. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
