cosmetic udev glitches

[Simon Thum]

Julien Cristau wrote:
> This is also expected at the moment.  The enumeration of devices gives
> us /dev/input/event* (which evdev can handle), and
> /dev/input/{mouse,kbd}* (which it doesn't).  This results in a couple
> error messages for the latter.  It should be possible to tone those down
> so users don't get scared…
Thanks for the clarification! I applied Peter's MatchDevicePath
"/dev/input/event*" which is probably better than making polite drivers.