On Wed, 2011-06-08 at 16:08 -0400, Nathan Williams wrote:
> The udev strategy used by ModemManager, as expressed in
> 80-mm-candidate.rules, expects "add" events to be emitted at startup
> when device rules have been processed (said events usually being
> generated by "udevadm trigger"). However, s
The udev strategy used by ModemManager, as expressed in
80-mm-candidate.rules, expects "add" events to be emitted at startup
when device rules have been processed (said events usually being
generated by "udevadm trigger"). However, since udev-152, "udevadm
trigger" generates "change" events instead
