<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 2013-04-10, at 5:15 AM, Mike Perkins wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Have you tried:<br><br>jt@myth:/dev/v4l$ udevadm info -a -p $(udevadm info -q path -n /dev/v4l/hdpvr1)<br><br>That might tell you if the symlink you created is doing the right thing.</span></blockquote></div><div><br></div><div>Even more helpful is:</div><div><br></div><div> udevadm test $(udevadm info -q path -n /dev/v4l/hdpvr1)</div><div><br></div><div>In the spew of output look at the "DEVLINKS=" line for what links are being created. You can quickly iterate through various attributes in your rules and see what effect each has.</div><div><br></div><div>The other helpful one is "trigger" which actually executes the rules for a given device, no rebooting required.</div><div><br></div><div>- George</div></body></html>