John Conover wrote:
> udevadm info -a -p $(udevadm info -q path -n /dev/video0):
>
> looking at device
> '//devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1.4/1-1.4.1.4:1.0/video4linux/video0':
> KERNEL=="video0"
> SUBSYSTEM=="video4linux"
> DRIVER==""
> ATTR{index}=="0"
> ATTR{dev_debug}=="0"
> ATTR{name}=="UVC Camera (046d:081b)"
>
> /etc/udev/rules.d/25-webcam.rules:
>
> KERNEL=="video[0-9]*", \
> SUBSYSTEM=="video4linux", \
> SUBSYSTEMS=="usb", \
> ATTRS{idVendor}=="046d", \
> ATTRS{idProduct}=="081b", \
> SYMLINK+="video-webcam"
>
> erratically fails, with /dev/video-webcam ln -s to /dev/video0, and
> the camera on /dev/video1, (after PNP.)
>
> Is "SUBSYSTEMS=="usb"" the issue in the rule?
SUBSYSTEM
Match the subsystem of the event device.
SUBSYSTEMS
Search the devpath upwards for a matching device subsystem name.
I've seen lots of rules use SUBSYSTEM and none use SUBSYSTEMS.
I don't think you need to specify KERNEL, either. Just let the
SYMLINK+= create the /dev/video-webcam for you.
-dsr-
