topic title: Automounting USB via ROX-Filer
anticapitalista
Posts: 5,956
Site Admin
Joined: 11 Sep 2007
#16
I get the same as Dave.

Here is a snapshot.

Are you sure the disk is labelled?
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#17
i just checked, and spacefm mounts per Dave and Anti. rox will go /dev/sdb* with no label though.

for automounting, you might want to try devmon. its including with udevil (and antiX) and uses udevil to do the mounts. You can also set it to launch a window at the mount point.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://igurublog.wordpress.com/downloads/script-devmon/"
linktext was:"http://igurublog.wordpress.com/downloads/script-devmon/"
====================================



***edit**** I take it back. I get different behavior in spacefm with the same key. i haven't figured out the circumstances yet, but sometimes its like anti desribed, and sometims is /media/sdb*. weird.
anticapitalista
Posts: 5,956
Site Admin
Joined: 11 Sep 2007
#18
My screenshot is rox and all the sticks I have are labelled like the one in the screenshot.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#19
If spacefm uses pmount for the mounting you get /dev/sd**. If you modify it to use udevil, you get the more verbose naming per Dave's post above.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#20
Reporting Success.
The following three scenarios work OK here with USB devices containing single and multiple file systems.

Scenario 1
Mode
ROX-IceWM

Objectives
  • Automount USB drive(s) upon connection
  • Mountpoint(s) to be file system label(s)
  • Pop open ROX-Filer
~/.xinitrc-custom
spacefm -d &

SpaceFM
Devices-->Settings-->Autorun-->On Mount
rox %m
Devices-->Settings-->Autorun-->Mount Command
Blank (autodetection)


Results
  • Drive(s) automatically mounted upon connection
  • ROX-Filer pops open
  • Label mountpoint(s) created

    Code: Select all

    blkid -o list

device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda1  ext4    SYSTEM   /              86bab6c0-738d-4a7f-8461-cb7c10053adf
/dev/sda2  ext4    HOME     /home          2f7d67c8-a67d-4468-9c41-7f97dc1dde41
/dev/sdb1  ext4    USB-RED  /media/USB-RED de1839f4-e552-478d-9039-87d8130c16dd
Scenario 2
Mode
ROX-IceWM

Objectives
  • Automount USB drive(s) upon connection
  • Mountpoint(s) to be file system label(s)
  • Pop open SpaceFM
~/.xinitrc-custom
spacefm -d &

SpaceFM
Devices-->Settings-->Autorun-->On Mount
spacefm %m
Devices-->Settings-->Autorun-->Mount Command
Blank (autodetection)


Results
  • Drive(s) automatically mounted upon connection
  • SpaceFM pops open
  • Label mountpoint(s) created

    Code: Select all

    blkid -o list

device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda1  ext4    SYSTEM   /              86bab6c0-738d-4a7f-8461-cb7c10053adf
/dev/sda2  ext4    HOME     /home          2f7d67c8-a67d-4468-9c41-7f97dc1dde41
/dev/sdb1  ext4    USB-RED  /media/USB-RED de1839f4-e552-478d-9039-87d8130c16dd

Scenario 3
Mode
Space-IceWM

Objectives
  • Automount USB drive(s) upon connection
  • Mountpoint(s) to be file system label(s)
  • Pop open ROX-Filer
~/.xinitrc-custom
#spacefm -d &

SpaceFM
Devices-->Settings-->Autorun-->On Mount
rox %m
Devices-->Settings-->Autorun-->Mount Command
Blank (autodetection)


Results
  • Drive(s) automatically mounted upon connection
  • ROX-Filer pops open
  • Label mountpoint(s) created

    Code: Select all

    blkid -o list

device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda1  ext4    SYSTEM   /              86bab6c0-738d-4a7f-8461-cb7c10053adf
/dev/sda2  ext4    HOME     /home          2f7d67c8-a67d-4468-9c41-7f97dc1dde41
/dev/sdb1  ext4    USB-RED  /media/USB-RED de1839f4-e552-478d-9039-87d8130c16dd
anticapitalista
Posts: 5,956
Site Admin
Joined: 11 Sep 2007
#21
Good work SamK and thanks for presenting it so clearly.

A question, why enable spacefm -d in ~/.xinitrc-custom and not the start file of the wm?

I used to use ~/.xinitrc-custom but when messing about with SpaceFM desktop and forgetting about disabling spacefm -d in ~/.xinitrc-custom gives no desktop.
Posts: 1,028
SamK
Joined: 21 Aug 2011
#22
anticapitalista wrote:A question, why enable spacefm -d in ~/.xinitrc-custom and not the start file of the wm?
It was a question of convenience. At the early stages of the investigation I wanted to compare against a known working position i.e.

Code: Select all

which devmon &>/dev/null && which udevil &>/dev/null && devmon &
It was simpler to add the SpaceFM command there also.

My interest at that time was in establishing a method rather than its ultimate implementation. Although I did not test running from the WM startup file I see no reason why it will not work in that way.

Using either location presents mirror images of advantages and disadvantages.
Via ~/.xinitrc-custom
Advantage=WM independent (one entry applies to all WMs)
Disadvantage=Divorced from all other startup commands

Via ~/.WM/starup
Advantage=Included with all other startup commands
Disadvantage=WM dependent (a separate entry for each WM)

I suppose it becomes a question of which you (as project leader) prefer.

If you choose the WM startup method and would like me to amend the earler post (reporting success) to reflect this let me know.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#23
SamK, Interesting stuff...could you tell which protocol (ie: udevil, mount, or pmount) was being used for the mounting?

***edit*** i ran spacefm -d from a terminal with the mount options in spacefm set to autodetect, and it runs udevil.