Note:
when the script is launched in an interactive session (ie, from a terminal), it prints its output on the standard output (ie, the terminal). When it's launched in a not-interactive session (for instance, from an hotkey), it shows its output in a notification bubble.

There is a configuration file, /etc/default/samsung-scripts, for users with a netbook different from NC10, where various options can be configured. Open the file in a text editor and follow the instructions to customize it.

I'm considering to create a new package on my repository containing all these scripts, mapping them to some keys combinations... but I don't know what keys combinations to use (others might not like my preferences, so I don't want to force anyone to use them).

I like to use the FN-F3, FN-F7 and FN-F8 keys for launching the applications I mostly use, so I use a 4-keys combination for every script (in order to avoid keybinding conflicts with the software I use... damn eclipse, it already uses all the best key combinations! ):

t -> CPU Temperature
g -> CPU Governors
b -> Bluetooth
w -> Webcam

What do you think about them? Are they good to be the defaults for everyone?

Please consider a little donation to keep the 'Linux On My Samsung' project up and running. Thank you!

I prefer the gnome applet for cpu governors. This way I have a visual indicator for the current governor.
Just do dpgk-reconfigure gnome-applets and allow the cpu frequency scaling applet to run with root privileges.

Well, I'm adding a new package to my repository, nc10-scripts, containing the 'cpuscaling.sh', 'cputemp.sh', 'btonoff.sh' and 'wconoff.sh' scripts. They are mapped globally to the following keybindings:
t -> CPU Temperature
g -> CPU Governors
b -> Bluetooth
w -> Webcam
Furthermore, new rules are automatically added to /etc/sudoers in order to run the scripts that need admin rights.

This package is optional (this is the reason why it's already on the repository), so if you want to use it you have to manually install it with the command

PS:
Scripts are globally mapped in metacity as command_3, command_4, command_5, command_6.
If you already have a local configuration in your user home for hotkeys, this has the precedence over the global one.
These are the files where local configuration for hotkeys is stored

You have two options: you can delete both files (this will delete all other custom hotkeys too, so you have to reconfigure them), or you can edit both files and delete the sections referring to all the above command_* numbers.

While updating packages for kernel 2.6.27-14, I was thinking that it would be better to have all scripts in the same package (well, at least for me, for mantaining them ), so I removed 'wlonoff.sh' and 'lcdonoff.sh' scripts respectively from 'linux-backports-modules' and 'gnome-power-manager' packages and putted them into 'nc10-scripts' package.

Hi everyone !
First of all, thanks Voria for all your work !
I just completed an install of Jaunty beta on my NC10, but the scripts don't work.
I added your repository to the sources.list and installed the nc10-scripts package.
All your scripts are in /usr/bin, they do work when I call them with the Terminal but the mapping doesn't seem to work.
I checked in Gconf if the mapping was Ok (it is), I checked the visudo file to see if I had the permissions to run these scripts and it's OK too.

In Jaunty you have to enable the 'Commands' plugin in the 'compiz configuration settings manager' in order to activate and use the metacity bindings.
You can install the compiz configuration settings manager with the command