topic title: Automounting USB via ROX-Filer
Posts: 1,028
SamK
Joined: 21 Aug 2011
#1
Testing final release installed to internal hard disk on actual hardware i.e. not a VM.

During the beta testing of antiX-13-full, I thought I had read an announcement that the default action is to automount USB upon connection. Is this only for SpaceFM? When using ROX USB devices are not automatically mounted. Does automounting via ROX require manual activation? If so how is it done?

It used to be via
/etc/udev/rules.d/99usb-storage.rules
which is no longer present. Is this deprecated in antiX-13?

There are two files
/etc/udev/rules.d/90-fstab-automount.rules.live
/etc/udev/rules.d/90-usb-semiauto.rules
Both of these are empty, is this as expected?
Alanarchy
Posts 0
Alanarchy
#2
If you want Rox to handle USB automounts you need to - edited out because I was wrong __{{emoticon}}__

If you want Spacefm handling things you need to add

Code: Select all

(sleep 2 && spacefm -d) &


to .xinitrc-custom.
Last edited by Guest on 07 Jun 2013, 01:17, edited 4 times in total.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#3
Alanarchy wrote:If 99-usbstorage.rules is an empty file, you need to fill it with this:


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/mounting-usb-devices-in-rox-t3048.html"
linktext was:"antix.freeforu ms.org/mounting-us ... t3048.html"
====================================
It is not that it is empty, it does not exist. It used to be created as a standard file by the installation process, hence my question about whether it has been deprecated in antiX-13.
Alanarchy
Posts 0
Alanarchy
#4
Sorry! I was trying to multitask before I've had enough coffee __{{emoticon}}__

anticapitalista gives us the choice to use which one we prefer.
Last edited by Guest on 07 Jun 2013, 01:19, edited 1 time in total.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#5
Alanarchy wrote:If you want Rox to handle USB automounts you need to create 99-usbstorage.rules and fill it with this:..
This post, post27827.html?hilit=automount#p27827
introduces some uncertainty about this. It indicates that 99-usbstorage.rules is handled differently in antiX-13 and may not be used at all. As that post was made during the development phase, I am seeking clarification of the final position.
Alanarchy wrote:...so if you choose Rox, you need to create that file.
An alternative way was introduced in antiX-12, post25819.html?hilit=automount#p25819.
Depending upon the answers to my earlier questions, this may now be preferred way to automount USB via ROX.
anticapitalista
Posts: 5,956
Site Admin
Joined: 11 Sep 2007
#6
99-usbstorage.rules is not used in antiX-13.

Instead we have F4 live boot options that will automount or not.
In last beta we had spacefm -d implemented so spacefm would pop open once a device was plugged in, but some users said they would prefer this not to be the default so we removed it for final.

space -d works very well and can be called either by your statup script for the wm or via .xinitrc-custom.

If you use spacefm desktop, do not set the spacefm daemon to run as it will alredy be doing so.

If you want rox to auto open when a device is plugged in follow the steps here:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.com/index.php?title=Howto_articles#auto-start_devices"
linktext was:"http://antix.mepis.com/index.php?title= ... rt_devices"
====================================
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#7
--- never mind ---
Last edited by BitJam on 06 Jun 2013, 12:49, edited 1 time in total.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#8
BitJam wrote:If /etc/udev/rules.d/90-fstab-automount.rules.live is empty then the F4 automount options won't work.
I may have been misled by an unusual and confusing condition of the system.

/etc/udev/rules.d/90-usb-semiauto.rules
is indeed empty

/etc/udev/rules.d/90-fstab-automount.rules.live
contains

Code: Select all

ACTION=="add|change|remove",SUBSYSTEM=="block",KERNEL=="sd*" RUN+="/bin/sh -c '/sbin/make-fstab'"
However, when opening the file the in leafpad the text is not immediately displayed. A mouse click or tap of the spacebar (i.e some action) reveals it. I have also noticed that some file names in ROX-Filer exhibit a similar condition.

I will open a separate topic on the missing text issue to keep this thread on the original topic.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#9
anticapitalista wrote:99-usbstorage.rules is not used in antiX-13.
Thanks for the clarification.
anticapitalista wrote:If you want rox to auto open when a device is plugged in follow the steps here:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.com/index.php?title=Howto_articles#auto-start_devices"
linktext was:"http://antix.mepis.com/index.php?title= ... rt_devices"
====================================
...
2. Add spacefm -d & to your windows manager startup file (no & for icewm)

A better alternative is to add it to .xinitrc-custom so it is set for all windows managers.

3. Restart the windows manager (or logout/login)

4. Plugin usb device and spacefm should open to its contents. If you want rox to open rather than SpaceFM, you'll also want to turn off Settings|Auto Mount|Open Tab
...
Is this meant to pop-open a ROX-Filer window on connection? The USB device is auto-mounted OK but a window does not pop-up.
anticapitalista
Posts: 5,956
Site Admin
Joined: 11 Sep 2007
#10
You might need to logout/login again
Posts: 1,028
SamK
Joined: 21 Aug 2011
#11
anticapitalista wrote:You might need to logout/login again
Rebooted. After logging in at the SLiM screen the desktop is not presented. Killed the X server (ctl+alt+bksp)and logged in as root.

Contrary to the guidance in
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.com/index.php?title="
linktext was:"http://antix.mepis.com/index.php?title="
====================================
... rt_devices
adding the '&' to the command in ~/.xinitrc-custom is needed to display the desktop.

Plugging in a USB stick it is automatically mounted but a ROX-Filer window does not pop-up.
Alanarchy
Posts 0
Alanarchy
#12
Instead we have F4 live boot options that will automount or not.
So that's what that does? I just ignored it. __{{emoticon}}__
space -d works very well and can be called either by your statup script for the wm or via .xinitrc-custom.
I used .xinitrc-custom so spacefm will work no matter which wm I use. I also enabled kernel polling like Ignorant Guru says in the manual.

Code: Select all

99-usbstorage.rules is not used in antiX-13.
I didn't realise that. Sorry to SamK for giving the wrong advice. __{{emoticon}}__
anticapitalista
Posts: 5,956
Site Admin
Joined: 11 Sep 2007
#13
SamK there is a step missing in the instructions. Now correctly edited.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#14
anticapitalista wrote:SamK there is a step missing in the instructions. Now correctly edited.
Confirming this works as expected using the '%m' switch - thanks.

Here the norm is to assign labels to hard disks and USB flash drives. This makes for a more user friendly setup particularly, for novice users or those accustomed to Windows. In this respect mounting via spacefm is presently not as attractive as the previous methods.

When automounting via either
  • /etc/udev/rules.d/99usb-storage.rules
  • which devmon &>/dev/null && which udevil &>/dev/null && devmon & (.xinitrc-custom)
the mountpoint is created using the label value and shown as such in ROX-Filer.

When using spacefm to automount, the mountpoint is created in the generic form of /dev/sdb1. Which is less user friendly. Also when instructing spacefm to autorun ROX (via '%l') it fails with the error message File doesn't exist, or I can't access it: LABELNAME
Posts: 1,062
Dave
Joined: 20 Jan 2010
#15
SamK wrote: When using spacefm to automount, the mountpoint is created in the generic form of /dev/sdb1. Which is less user friendly. Also when instructing spacefm to autorun ROX (via '%l') it fails with the error message File doesn't exist, or I can't access it: LABELNAME
Spacefm makes a mountpoint in the following format for me,
sdb1-USB_NAME-SIZE_OF_USB

I am still using the configuration for V12 though.... I will change to the V13 configs later to verify. However based on this I would quess that the mount point name is configurable in spacefm.

EDIT:
There is a wrapper script for preferred file manager (for the menus and such) based on DESKTOP_CODE and the contents of ~/.antix-session/session.conf. Perhaps we can expand this idea for an update, so if rox is selected it will use the udev rule (or another alternative / set spacefm configs accordingly) and if spacefm is selected it will use spacefm.