You might already be familiar w/ pmount & ivman. It's a great way to automount your USB keys & such. Let me say that I only automount USB keys - I detest it when cd's &dvd's get automatically mounted.
ivman is *supposed* to be working when you log into your desktop, well for whatever reason it does not on e17. There might be less convoluted ways of getting this done but it works. Here's how to make it happen:
You need the following 3 scripts. Put them all in ~/Scripts.
Be sure to change both instances of <USERNAME> to your actual username!
~/Scripts/startup.desktop
Code: Select all
[Desktop Entry]
Encoding=UTF-8
Name=startup script
Comment=Programming editor
Exec=/home/<USERNAME>/Scripts/startup.sh
Terminal=false
Type=Application
Icon=/usr/share/pixmaps/Sci48M.png
Categories=Application;Development;
~/Scripts/startup.sh
Code: Select all
#!/bin/sh
xmodmap -e 'remove Lock = Caps_Lock'
numlockx on
nvidia-settings -l
conky&
/home/<USERNAME>/Scripts/ivman.sh
~/Scripts/ivman.sh
Code: Select all
if pgrep -U $USER ivman >/dev/null 2>&1; then
exit
else
exec ivman
fi
Now to get all of that to launch on login is pretty simple. Just create an .order file to launch your startup script:
~/.e/e/applications/startup/.order
Code: Select all
/home/<USERNAME>/Scripts/startup.desktop
So what does all of this do?
On login ~/.e/e/applications/startup/.order is read. It points to
/home/<USERNAME>/Scripts/startup.desktop
Which in turn points to:
~/Scripts/startup.sh
Which executes anything in that file like numlock or xmodmap or even another script. If you want to start more or fewer things simply edit ~/Scripts/startup.sh. No need to change anything else. My startup.sh turns numlock on, disable the CAPS lock, starts nvidia settings and conky & executes the ivman.sh script.
*NOTE* The ivman.sh script checks to see if there is already an instance of ivman running as $USER and if not it then starts ivman otherwise it exits. The ivman.sh script was seperated from the ~/Scripts/startup.sh because it was misbehaving and giving unpredictable results.
If you've made it this far you're almost done. You just need to edit a simple text file that tells ivman what do do when a USB key is inserted.
~/.ivman/IvmConfigActions.xml
Add a section like so:
Code: Select all
<!--start Rox filer when USB device is mounted-->
<ivm:Match name="hal.info.category" value="storage">
<ivm:Match name="hal.storage.bus" value="usb">
<ivm:Option name="exec" value="rox /media" />
</ivm:Match>
</ivm:Match>
</ivm:ActionsConfig>
So now try loggin out and back in, you should then have 2 instances of ivman running:
Code: Select all
$ ps aux|grep ivman
ivman 4889 0.0 0.3 4616 1444 ? Ss 2006 0:00 /usr/bin/ivman
glenn 19755 0.0 0.4 4492 1664 ? S 2006 0:00 ivman
Ivman runs as user ivman on boot, then as user on login.
Go ahead and insert a USB key. If all is well you should have rox filer pop up and open to the /media directory. Your USB key will be mounted therein at perhaps usbdisk or similar. To umount the USB key is very simple. Back out of your mounted drive directory and from the /media dir
Right click your USB key mount point>Eject.
Voila! Rox goes away and your USB key is ready to be removed. To be safe please issue mount in a shell to make sure it is umounted before removing your key!
I encourage you to read the ~/.ivman/IvmConfigActions.xml. There is quite alot you can do with it. Obviously you are not required to use rox-filer but I have no idea how well any other file maanger works in this instance.