http://bugzilla.novell.com/show_bug.cgi?id=598193 http://bugzilla.novell.com/show_bug.cgi?id=598193#c73 --- Comment #73 from Xinwei Hu <xwhu@novell.com> 2010-06-23 10:18:00 UTC --- (In reply to comment #72)
(In reply to commen
This is still true with the latest update, and I think it'll be true in foreseeable future.
This sounds different: https://bugzilla.redhat.com/show_bug.cgi?id=561425#c16
No, it's not. At least not in the git repo yet.
Sure, it's in the repo. All the IMPORT{db} stuff which is not in our package.
Not sure what's IMPORT you are referring to. The latest update to 10-dm.rules in upstream is made about 2 month ago. And that doesn't help to this bug.
-> If 'add|change' triggered by other source, /dev/dm-* will not be removed,
Primary device nodes will never be removed again, because recent udev versions, like the one we ship, refuses to do that, and ignores all the instructions from the device-mapper rules.
all symlinks will be created according to the info from IMPORT{db}. I'd like to know if this is OK from udev's point of view.
The stuff in the current lvm git repo is expected to solve some of the problems. It is surely 'ok' from udev point of view, but I can tell if that is sufficient to solve the current problems, or the right way to handle that from device-mapper's view. I guess it's all still work-in-progress at the device-mapper side at the moment.
If it's OK, I'll try to make this upstream then.
With 'upstream' you mean our Factory package?
Both Factory and device mapper upstream. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.