On 03/19/2010 01:16 PM, Kay Sievers wrote: > On Fri, Mar 19, 2010 at 13:12, Alasdair G Kergon <agk@xxxxxxxxxx> wrote: >> E.g. Flagging a device as 'private' as discussed in an earlier mail. > > Sure, that can all be done. Plain udev leaves dm and md devices > completely to the subsystem own rules. It might be other tools which > interfere here, and that might need to be synchronized to match on > some values in the udev properties or sysfs. > > Kay Great. We have the flags in uevents, we have udev properties. We can't put them directly in sysfs because of the reasons we already discussed (it's also extended information related to exact device-mapper subsystem, not easily accessible in the middle of processing from outer space). Do we have these flags/properties available when processing the event originated in the "watch rule" or "udevadm trigger". No. The information is cleared from udev db and inaccessible. That's what we need and what we tried to ask for (besides trying to solve that problem with the ADD event). Peter -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
