Removing the "change" event would mean that dmraid would not get picked
up on various devices that need to be constructed a piece at a time,
etc.

Why does the change event get triggered in the first place?  This could
be the inotify watch udev holds - in which case changing dmraid to only
open the block device for reading (not writing) would be sufficient.
It's very unlikely dmraid actually needs write support

-- 
dmraid causes udev event feedback loop in Lucid
https://bugs.launchpad.net/bugs/534743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to