On Sun, Jul 19, 2009 at 09:33:14PM +0200, Micha Lenk wrote:

The cause for this bug is most probably related to kernel changes.
Strangely enough I can't reproduce it anymore. I have rebooted since filing the bug report, so maybe the udev rules weren't reloaded after installation of libchipcard-tools?

udevinfo -a -p $(udevinfo -q path -n cmm0)
caravan:~# udevinfo -a -p $(udevinfo -q path -n cmm0)
the program '/bin/bash' called 'udevinfo', it should use 'udevadm info <options>', this will stop working in a future release the program '/bin/bash' called 'udevinfo', it should use 'udevadm info <options>', this will stop working in a future release

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

   looking at device '/devices/virtual/cardman_4000/cmm0':
     KERNEL=="cmm0"
     SUBSYSTEM=="cardman_4000"
     DRIVER==""

CU Sascha

--
http://sascha.silbe.org/
http://www.infra-silbe.de/

Attachment: signature.asc
Description: Digital signature

Reply via email to