<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
What I do in MiniMyth is use udev to create device symbolic links from the hardware's characteristics (e.g., vendor id, product id, serial number). Once this is done, device can be referred to by the symbolic link, which does not change as it is constructed from the hardware's characteristics. For example, newer versions of udev contain a rules script (60-persistent-input.rules) that does this for input devices.<div class="HOEnZb">
<div class="h5"><br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br><div>Hi Paul</div><div><br></div><div>Ive tried this using udev and have it matched to the remote. I had set it to <span style> </span><span style>REMOTE_DEVICE="</span>/dev/input/remote" in hardware.conf. However, I dont get any output from the remote using irw. </div>
<div><br></div><div>What im having after each boot is change the remote device to /dev/lirc0 or /dev/lirc1 depending on where the remote is placed agains either /sys/class/rc/rc0/ or /sys/class/rc/rc1/</div><div><br></div>
<div>I cant find anywhere to point /sys/class/rc/rc0/ to /dev/input/remote </div>