Hm, I'm not sure about this. I don't see anything in udev or udisks
which would issue events on bdi devices, and usually they originate
from the kernel. Does this also appear in udevadm monitor --kernel?
> First, shouldn't udev only be issuing 'change' events and not 'remove'
> events?
In general it should mirror whatever the kernel sends, including
removal ones. However, in this "trigger" case if should only
synthesize change events, of course. I don't believe that this bdi
remove event is originating from udev itself.
> Second what exactly is 'bdi'? I can't seem to find a lot of
> information on it.
Scott Talbert [2010-07-19 4:00 -0000]: virtual/ bdi/0:21 (bdi)
> UDEV [1277516625.070541] remove /devices/
Hm, I'm not sure about this. I don't see anything in udev or udisks
which would issue events on bdi devices, and usually they originate
from the kernel. Does this also appear in udevadm monitor --kernel?
> First, shouldn't udev only be issuing 'change' events and not 'remove'
> events?
In general it should mirror whatever the kernel sends, including
removal ones. However, in this "trigger" case if should only
synthesize change events, of course. I don't believe that this bdi
remove event is originating from udev itself.
> Second what exactly is 'bdi'? I can't seem to find a lot of
> information on it.
Me neither, www.mjmwired. net/kernel/ Documentation/ ABI/testing/ sysfs-class- bdi
http://
was the closest thing I found.
Martin www.piware. de
--
Martin Pitt | http://
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)