That you are using a USB mouse and that /dev/input/mice is you device for it.
It is not technically a bug. If you were to read the description on that particular page... it does mention some things.
Ironically, it is a matter of figuring out which is left from the list, eliminating Serial, PS/2, GPM-data, IBM-busmouse and Sun Mouse (kybd connected mouse):- /dev/psaux
- /dev/ttyS0
- /dev/ttyS1
- /dev/ttyS2
- /dev/ttyS3
- /dev/input/mice
- /dev/atibm
- /dev/sunmouse
- /dev/gpmdata
This leaves you with /dev/input/mice only. Of course we all *knew* that.--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @
iwetheyNo matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
Keyboard not responding
- (drewk)
- (18)
- Dec. 6, 2004, 10:13:28 PM EST
