One possibly interesting thing that I've noticed about this is when I look at the output of 'udevadm monitor' while running the 'udevadm trigger --subsystem-match=block --action=change' command which causes /proc to go away, it shows this line (which it doesn't show if I run the 'udevadm trigger --subsystem-match=block --action=change' command any other time):
First, shouldn't udev only be issuing 'change' events and not 'remove' events? Second what exactly is 'bdi'? I can't seem to find a lot of information on it.
One possibly interesting thing that I've noticed about this is when I look at the output of 'udevadm monitor' while running the 'udevadm trigger --subsystem- match=block --action=change' command which causes /proc to go away, it shows this line (which it doesn't show if I run the 'udevadm trigger --subsystem- match=block --action=change' command any other time):
UDEV [1277516625.070541] remove /devices/ virtual/ bdi/0:21 (bdi)
First, shouldn't udev only be issuing 'change' events and not 'remove' events? Second what exactly is 'bdi'? I can't seem to find a lot of information on it.
Scott