cbagger01

Group: Members
Posts: 4264
Joined: Oct. 2003 |
 |
Posted: Feb. 27 2006,06:06 |
 |
The biggest "gotcha" for me is when I switch from a PC that has a USB mouse over to a PC that has a PS/2 mouse.
If I remember, I can fix the problem at boot type by typing:
dsl xsetup
Otherwise, I must press CTRL-ALT-DEL and then type xsetup.sh and reconfigure and then startx
In theory, if knoppix mouse autodetection was right 100% of the time, it would be possible to use the output of the autodetection to help with the mouse selection for the .xserverrc
In other words, use autdetection information in /etc/sysconfig/ to dynamically build an .xserverrc that uses the correct pointing device.
Or maybe just default to specifying the generic mouse device symlink:
/dev/mouse
Just a thought.
|