chmod is a command used to change the permissions on a file, including whether the file can be executed (which is what ‘x’ stands for).

Let’s say you have a script called sens.sh in which you’ve placed the commands you want to run. To make it so it can be executed, you run — in a terminal — the command chmod +x sens.sh (if you’re in the same folder) or chmod +x /home/patrick/sens.sh. Then you can run it with ./sens.sh or /home/patrick/sens.sh, and you can add it to GNOME’s “Startup Applications” so it is launched whenever the graphical interface is. To do that, you add a new entry pointing to the script you made (and on which you ran chmod +x), for example: http://imgur.com/KJ4hk.png

You can also toggle whether a file can be executed by going to Properties -> Permissions for the file: http://imgur.com/6IA6m.png

Hope that helps!

I can’t find a good answer to your questions, but this might help you a little:

# xinput get-feedbacks "Razor DeathAdder"
1 feedback class
PtrFeedbackClass id=0
	accelNum is 2
	accelDenom is 1
	threshold is 4

# xinput set-ptr-feedback "Razor DeathAdder" 0 2 1

# xinput get-feedbacks "Razor DeathAdder"
1 feedback class
PtrFeedbackClass id=0
	accelNum is 2
	accelDenom is 1
	threshold is 0

The lower the treshold (the first value in the command), the more sensitive the mouse is. This value can’t go below 0, it seems.

Alternatively, for high(er) sensitivity without acceleration:

# xinput set-ptr-feedback "Razor DeathAdder" 0 0 1

# xinput get-feedbacks "Razor DeathAdder"
1 feedback class
PtrFeedbackClass id=0
	accelNum is 0
	accelDenom is 1
	threshold is 0

Any ideas to force it to values smaller than 1?

Any assistance is appreciated.