Just to elaborate, you'll have to access /etc/rc.d/rc.bluetooth.conf. That file has the configurations for bluetooth and what will be running.
The first thing is to check that the bluetooth module is loaded. This should have happened automatically.
lsmod | grep bluetoothIf it gives you some output with the bluetooth module, everything is fine.
Then, because you're using a mouse, edit that script (rc.bluetooth.conf) and set the values for true or false according to what you want running.
I think you want to change HIDD_ENABLE to true, because you're using an input device, such as a mouse. I'm not sure about the other stuff... I think you might need to set some other things to true for the headset.
Then start the bluetooth service (as root):
service bluetooth start
This should load other modules and you should see a message saying that it started hidd, hcid, and passkeys... and whatever else you told it to run.
At this point, doing
hciconfigshould show your bluetooth hardware and say that it is "UP".
If not, you can do something like:
hciconfig hci0 up
You're ready to scan for devices:
hidd --scanWhich will give you an identifier for your mouse.
hidd --connect <address of your mouse>
It it works, great.
I guess you would want it to work after you boot your computer, so you should put "--connect <Address>" in HIDD_OPTIONS inside /etc/rc.d/rc.bluetooth.conf .
(many websites tell you to put the option --server in HIDD_OPTIONS. It's not needed, it's handled by the bluetooth scripts)
Finally, go to VasmCC and in services select the bluetooth service for whatever runlevels you want it running.
Everything should really be more or less automatic. All this stuff is just to check that things are working properly, step by step.
The only things that REALLY need to be done to get the mouse working permanently on boot are: (1) enabling hidd in that file; (2) put your mouse address in the options for hidd; and (3) enable the service in Vasm.
EDIT: if you follow this method, you don't need to make that script executable as bigpaws suggested. That's taken care of. But, as he said, if you want to get the headset going, you most likely will need to fiddle with the asound.conf file, and maybe set some other things to true in the configuration file.