8 Button Logitech Mouse

First you follow this guide www.linux-gamers.net. Then you install xkindkeys. Then you install mvmouse. Then you put a file called .xbindkeysrc containing the code-snippet below in your home-directory.

"xvkbd -xsendevent -text "\[Alt_L]\[Left]""
  b:2
"~/./my_double_click.sh && ~/./my_double_click.sh &"
  b:6

You have to check which button is the thum- and wheelbutton. On my mouse it's button No. 2 and 6. Then you create a file called my_double_click.sh and put the following line in it:

mvmouse +0 +0 1 && mvmouse +0 +0 1 &

It looks as if it will produce 4 clicks but it doesn't. You have to chmod the shell-script to give it execution-rights. my_double_click.sh should also be placed in your home-directory. Then you restart your X server using the ctrl-alt-backspace keys. Log in at the prompt and type $ startx. And that's it!

Could you please be more specific what does what?
Im using xbindkeys, and it look like that it is able to handle mouse buttons (for example with modifiers) But i did not succeeded with 6th and 7th button. Do i really need mousemove?
Thanks

mvmouse is needed for the doubleclick.

evtest is used to test which events belong to which buttons. When I ran it in June it produced a lot of output but now it didn't produce much output at all.

SuSEBurken:~ # evtest /dev/input/event2
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x46d product 0xc01d version 0x2100
Input device name: "Logitech USB-PS/2 Optical Mouse"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 272 (LeftBtn)
Event code 273 (RightBtn)
Event code 274 (MiddleBtn)
Event code 275 (SideBtn)
Event code 276 (ExtraBtn)
Event code 277 (ForwardBtn)
Event code 278 (BackBtn)
Event code 279 (TaskBtn)
Event type 2 (Relative)
Event code 0 (X)
Event code 1 (Y)
Event code 8 (Wheel)
Testing ... (interrupt to exit)

I'm able to program 7 buttons + roll wheel up or down. The button just above the wheel does not respond. You can use this to test

"xvkbd -xsendevent -text "\b""
  b:4

"xvkbd -xsendevent -text "\b""
  b:5

"xvkbd -xsendevent -text "\b""
  b:6

"xvkbd -xsendevent -text "\b""
  b:7

"xvkbd -xsendevent -text "\b""
  b:8

"xvkbd -xsendevent -text "\b""
  b:9

"xvkbd -xsendevent -text "\b""
  b:10

"xvkbd -xsendevent -text "\b""
  b:11

If you install new hardware /etc/X11/xorg.conf might be altered. Then you have to change the mouse section back, so it's good to keep a copy of the old working /etc/X11/xorg.conf somewhere else e.g. in your home directory. When I installed a new video card the OS changed

Section "InputDevice"
Identifier "Mouse[1]"
Driver "evdev"
Option "Protocol" "evdev"
Option "Device" "/dev/input/event2"
Option "Name" "Logitech MX510"
EndSection[/b]

to

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "10"
Option "Device" "/dev/input/mice"
Option "Name" "Logitech USB-PS/2 Optical Mouse"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection[/b]

Right now I'm using 3 clicks instead of 4. It works better. No double openings of folders or applications.

"~/./my_double_click.sh &"
b:6

mvmouse +0 +0 1 && mvmouse +0 +0 1 && mvmouse +0 +0 1 &