gowator - to save you some heartache when you do, this is what I need to do to make it work on Cooker. (maybe it works better in 10.1, but just in case :>)
before calling bluemote, do this as root:
# mknod -m 666 /dev/rfcomm0 c 216 0
# rfcomm bind /dev/rfcomm0 bt.ad.dr.es.so.fp.ho.ne
(you can find the bt address of the phone from hcitool scan)
Now when you run bluemote it'll actually work, as opposed to not talking to the phone at all

. Just super-in-case, I found before I did *anything* with my phone via bluetooth I had to force the two to pair up, which I did by:
# rfcomm connect /dev/rfcomm0 ad.dr.es.so.fp.ho.ne 5
that forces a connection between the two, the phone will detect a new device, ask if you want to pair with it, then ask for the pin (mandrake default 1234). Then you can just ctrl-c the connection. Now they're paired for ever, you only need to do this bit once. I couldn't find a more elegant way to make 'em pair up. You can use gnome-obex-send or kdebluetooth to send files to the phone, you should be able to receive from the phone too but at least in Cooker it's broken. I'm gonna try and get MDK to make all this a lot smoother for the next release. It's still better than it was a year ago, when you had to build half the tools from source