I followed the instructions I found here:
http://ubuntuforums.org/archive/index.php/t-660515.html:
Code: Select all
We'll show you how to use only one key to open & shut your drive (thanks for the script Rhubarb!!! His post: http://ubuntuforums.org/showthread.php?t=656674 )
First we need to know if you only have one drive or more than one....
If you only have one:
Open Text Editor & paste the following:
#./bin/bash
tray_status=`cat .tray_status.sh`
if [ "$tray_status" == "Closed" ]
then
eject
echo "Open" > .tray_status.sh
elif [ "$tray_status" == "Open" ]
then
eject -t
echo "Closed" > .tray_status.sh
else
eject
echo "Open" > .tray_status.sh
fi
Save the file to your /home as tray_status.sh (note that it matches the info in the script!!!)
Next open a terminal & chmod 755 /home/(your home)/tray_status.sh
chmod 755--The user has read, write and execute permissions; the group and others can only read and execute.
That is the safest way to set permissions on the file.
Next, open up Configuration Editor. I have found that you can't bind this command to F12 (not sure, will need to do more checking).
So we are going to bind the command to F11. I chose command_10, you can use command_1 & modify the rest of the keybinding to match your choice.
In any case, the command should be /home/(your home)/tray_status.sh
Next we'll move to the global_keybindings. Under run_command_10, I used the the F11 key.
I nearly did it that way. In Configuration Editor I changed the key '/apps/metacity/global_keybindings/run_command_1' to '<Control>o' and '/apps/metacity/keybindings_commands/command_1' to '/home/username/tray_status.sh'
Now '<Control>o' opens the drive but does not close it, although the script entered in a shell opens and closes it.
Oh, and by the way: By trying to solve this problem a new error ocured. During the start process a message is displayed, that the file '.dmrc' has incorrect privileges (should be 644). And Amule doesn't start anymore. This is all very strange and I cannot guarantee, that there is really a connection between these problems, but I haven't done anything else deep in the system...
To be honest, I'm really looking forward to the next update of Mint, so that I can redo everything....