The following short transcript is from adapting the udevadm
invocation in http://wiki.debian.org/udev to investigate
1394 support in my Squeeze system. Two questions.
* What exactly is meant by "device specified by the devpath" in
the output? According to the udevadm man page, devpath is
the value assigned to --path; but that parameter is not present
in the command below. No devpath is specified.
* What exactly is '/class/ieee1394_protocol/raw1394'?
/class is not a directory in the filesystem and /dev/raw1394
is the only 1394 device I've found.
Thanks for any ideas, ... Peter E.
======= transcript=======
joule:/dev# udevadm info --name=/dev/raw1394 --attribute-walk
Udevinfo 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 '/class/ieee1394_protocol/raw1394':
KERNEL=="raw1394"
SUBSYSTEM=="ieee1394_protocol"
DRIVER==""
joule:/dev# ls /class
ls: cannot access /class: No such file or directory
joule:/dev#
======= transcript=======
--
Carnot is down, waiting for installation of NetBSD.
Personal site works; http://members.shaw.ca/peasthope/ .
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/171056555.58853.401...@heaviside.invalid
