<div class="gmail_quote">On 17 November 2010 02:12, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Nov 16, 2010, at 8:13 AM, Anthony Giggins wrote:<br>
<br>
> Sorry to hijack this thread but I just ran into the changing event id issue so Iooked into /dev/input/by-id/<br>
><br>
> usb-15c2_0036-event-mouse<br>
> usb-15c2_0036-mouse<br>
><br>
> but which device should I use? neither look correct from my understanding<br>
><br>
> I'm currently using /dev/input/event6 I had looked briefly into using udev to symlink based on the usb id but I haven't persued this option.<br>
<br>
</div>ls -l /dev/input/by-id/<br>
<br>
And then find the one that points to /dev/input/event6. I think<br>
you probably have a kernel where the remote events and mouse<br>
events haven't yet been split into separate input devices, and<br>
its probably -event-mouse you're after.<br>
<div class="im"><br>
--<br>
Jarod Wilson<br>
<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a><br>
</div><br></blockquote><div><br>Ahhhh so simple, thanks Jared <br></div></div><br>