LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-06-2009, 03:19 PM   #1
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware
Posts: 1,134

Rep: Reputation: 277Reputation: 277Reputation: 277
Hal, usb, automount, etc.


First off, let me say that I've read, re-read, and again read the sticky re:Hal and 12.0. Many times in the past, and again today.

I've just completed a fresh 12.2 install (having borked a perfect 12.0 install...don't ask.)

Anyway, I have an Archos 605 pmp, and under 12.0, using ivman and pmount, I was, for the most part, able to have my pmp automounted, whether in X or at the cli. This enabled me to do nightly syncs and playlist generation via cron. For the most part, due in large part to the sticky (thanx folks!) I don't recall it being particularly difficult.

However, upon trying to accomplish the same feat in 12.2, I feel defeated. Nothing I tried would work all the time. Formerly, when I plugged in the pmp, it would be read as /dev/sd? and auto-mounted to /media/A605. It's because of this behaviour that I was able to create scripts, and to invoke them via cron.

In 12.2, sometimes the device would be seen as /dev/sda1, and mounted /media/A605; other times mounted as /media/sda1; other times not mounted at all, unless & until I clicked on it in Thunar, or manually mounted it via cli. Unmounting also proved to be an issue. Sometimes pmount would allow it - other times it would error out, saying I wasn't the one who mounted it.

In running ivman, I could see that there were sometimes mounting issues (via pmount); sometimes it wouldn't mount because it was determined that is wasn't a removable device. I could whitelist the pmp in pmount.allow, but it would have to be as /dev/sda1. Labels & UUIDs weren't allowed.

Of course the major issue in this case, besides not being certain that the device was mounted at all, is that I couldn't be sure that the device would be read as /dev/sda1, especially if there were other usb storage devices in play.

Getting to the point - I ended up putting a line in fstab:

Code:
LABEL=A605  /media/A605 auto  auto,users,rw,dmask=0022,fmask=0133 0 0
and I created a udev rule, 99-mount.rules:
Code:
#run mount -a everytime a block device is added/removed
SUBSYSTEM=="block", run+="/bin/mount -a"
This, apparently, does the trick.

I'm curious as to whether this is the way it's all supposed to work, or what I may have missed in the first place, or whether there's any drawbacks to what I've done.

cheers,
 
Old 02-06-2009, 03:26 PM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,062

Rep: Reputation: Disabled
Other possibility: add a 70-persistent-multimedia.rules similar to 70-persistent-cd.rules or 70-persistent-net.rules in /etc/udev/rules.d/

Last edited by Didier Spaier; 02-06-2009 at 05:12 PM.
 
Old 02-07-2009, 09:04 PM   #3
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,443

Rep: Reputation: 73
Just so you know, pmount is a little limited in Slackware 12.2
 
Old 02-07-2009, 11:04 PM   #4
mrclisdue
Senior Member
 
Registered: Dec 2005
Distribution: Slackware
Posts: 1,134

Original Poster
Rep: Reputation: 277Reputation: 277Reputation: 277
Ah, I see. Thank you for pointing that out to me.

Your suggestion about using globs in pmount.all may have sped up resolution for me (had I searched LQ for a solution - what a novel idea, search LQ!)

However, I think when all is said & done, the fstab > udev solution is the tidiest and most reliable.

cheers,
 
Old 02-08-2009, 02:49 AM   #5
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,062

Rep: Reputation: Disabled
About pmount SlackBuild

There has been a discussion on the Slackbuilds-users mailing list about pmount and the problematic detection of removable devices via hal.

It ended up -- as I wished -- that a Slackbuild for pmount is still maintained, but with a warning about that in the README:
Code:
NOTE: It seems that detection of removable devices via hal no longer
works correctly, and pmount also seems unmaintained as of right now.
You should be able to populate /etc/pmount.allow with a list of your
removable devices to work around it; see pmount's man page for more
detailed information.
As a fluxbox user I do find pmount/pumount very useful. There is the content of my /etc/pmount.allow file:
Code:
/dev/sda[1234]
/dev/cdrom
/dev/hdc
/dev/hda4
As you can see you can use pmount for removable and not removable devices as well (/dev/hda4 is a disk partition with an old version of Slackware in it)

Last edited by Didier Spaier; 02-08-2009 at 03:04 AM. Reason: Tyo
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 12, HAL automount arubin Slackware 38 01-27-2009 11:48 AM
Automount - HAL - udev - Xfce - Konqueror - Slackware - help requested Linux.tar.gz Linux - Hardware 5 06-19-2008 09:49 AM
Make HAL automount a disk to a specific place duryodhan Slackware 6 09-27-2007 07:10 AM
automount[10761]: failed to mount /media/.hal-mtab kevkim55 Linux - General 0 06-23-2007 12:29 PM
after update HAL automount doesn't work eddiep Linux - Hardware 4 02-26-2007 01:58 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration