Re: Re (2): Ownership of pluggable devices.

[recoverym4n@gmail.com]

On Fri, 6 Sep 2013 08:28:23 -0700
peasthope@shaw.ca wrote:

> I've studied this note, installed udisks-glue and modified udisks-glue.conf 
> as described.  
> http://goshawknest.wordpress.com/2013/02/21/how-to-make-usb-disks-readable-by-all-users-on-raspbmc/
> 
> Also noticed this.
> root@dalton:/etc/avahi/services# ps aux | grep "udisks-daemon: p"
> root      4177  0.0  0.0   6352   412 ?        S    Sep05   0:07 udisks-daemon:
> polling /dev/sr0 /dev/sdb
> /dev/sdb is the KingstonUSB; that is a good sign.

I'm not familiar with all these new fancy FreeDesktop gizmos. Still,
this part:

match disks {
 automount = true
 automount_options = { sync, noatime, "dmask=0", "fmask=0"}

Looks like mounting options (and, as I wrote before, tinkering with them
is useless), but this:

 post_insertion_command = "udisks --set-spindown %
device_file --spindown-timeout 1800 --mount %device_file
--mount-options sync,noatime,dmask=0,fmask=0" }

Probably allows insertion of arbitrary command (maybe several), which
will be invoked with root privileges.

IMO, insert chown here, and you're set.


> Nevertheless, if root starts udisks-glue and then the 
> KingstonUSB is plugged, access is again restricted to root as described previously.  
> So I have at least one snag somewhere.

Hmm. In that blog they run udisks-glue with root privileges too.

> Once that is solved, I might invent an /etc/init.d/udisks-glue-start-script.
> 
> Also, 
> *	From: Gregory Nowak <greg@gregn.net>
> *	Date: Thu, 5 Sep 2013 20:07:44 -0700
> > ... don't remember a situation where I had to do chown like this after every mount.
> 
> Might this involve the replacement of hal with u*; still in progress.

YMMV, but I'd never use chown for this purpose. Besides, I haven't
meant you should run chown on each mount, running chown once should be
more than enough.

Reco