kill moused (started by devd) before the kill -TERM $$ in my
$firewall_script the system goes to single user mode as expected.
Is this my fault? Adding killall moused to be able to go to single
user mode seems strange.
Thank you,
Nicolas
--
http://www.rachinsky.de/nicolas
Hi,
i patched ums.c to support up to 31 mouse buttons (changed button type
to int and set MAX_BUTTONS to 31) so far the patch is working.
Now i have a problem with the moused it ignores buttons 6 and 7 and 15
of my Logitech MediaPlay mouse. And i cant find the reason, somehow it
isnt handled
Hi,
Will Andrews [EMAIL PROTECTED] wrote:
These patches:
1) Modify the spic(4) driver to support additional Sony
Vaio laptop models.
2) Add support to moused(8) for the spic(4) driver.
3) Do not break world or kernel/LINT builds. :-)
4) Work. :-)
(1
Vaio laptop models.
2) Add support to moused(8) for the spic(4) driver.
3) Do not break world or kernel/LINT builds. :-)
4) Work. :-)
(1) was submitted by Akira Funahashi-san [EMAIL PROTECTED].
(2) was submitted by Juriy Goloveshkin [EMAIL PROTECTED].
I adjusted
the problem: When my mouse (actully a trackball, a PS/2 Logitech
TrackMan Marble) is unplugged from the system, it ceases to remember how to
send a signal to the system (I assume some initialization is being done by
moused when it starts up). So, when I switch over to my second system and
back over
In message [EMAIL PROTECTED] Dave
Howland writes:
: pain, albeit not completely unbearable. Anyone have any theories on how we
: could get moused to a) detect the mouse being unplugged and reinserted and
: b) reinitialize the mouse after this happens? Here's some fun info type
: stuff (in case
6 matches
Mail list logo