Hello Rodolfo,
Replied earlier, but its gone somewhere. I looked at the doco. Thanks for the reference. Did you update it just for me? [Thanks.] I used the doco to add a local rule for accepting guids in the mount command, as configured via gconf. A mount controlled by goconf now accepts a guid where as it did not before (I had already tried to fiddle with gconf). But, the group is still set to root after the mount.
gconf mount options for vfat now are:
[shortname=mixed,uid=,gid=]
In user-options.fdi I have:
   <match key="volume.fsusage" string="filesystem">
     <match key="volume.fstype" string="vfat">
<append key="volume.mount.valid_options" type="strlist">usefree</append>
       <append key="volume.mount.valid_options" type="strlist">gid</append>
     </match>
   </match>

On a related but different topic, how do I force hal to always mount the usb card as me (chris). I am not the only user on the console, I have to play round robin and a game of chance for the card to be mounted under my uid.

Thanks and regards,
Chris.

Rodolfo Martínez wrote:
Hi Chris,

The "Changing default mount options" section at
http://www.linuxfromscratch.org/blfs/view/cvs/general/hal.html may
help.


--
Rodolfo Martínez



On Mon, Apr 12, 2010 at 6:39 AM, Chris Perry <[email protected]> wrote:
Hello,
I have used Debian for over a decade and can work most things out.  But I
have a problem.
I use a usb memory card to take a rsync backup of my most important files
every day.  This used to work perfectly.

I recently upgraded from etch to lenny.  After ironing out some wrinkles I
am left with one insoluble problem:

The usb memory card is always auto mounted with group ownership of root at
the mount point.  This stops me from refreshing the cards contents.

In etch ownership after auomount would be chris:perry  This is as expected
and worked fine.
In lenny ownership after automount is chris:root  This is the problem.

My primary group is still perry, btw.

I have googled and searched far and wide, I cannot find posts that describe
adequately how hal and then udev get themselves sorted and apply some action
to perform the mount.  I cannot work out where the action is defined in the
system config.  I cannot work anything out, I've not been so stumped in a
long time.

I have determined the following work-around to use after automount has
completed:
umount /media/TOSHIBA
mkdir /media/TOSHIBA
mount -t vfat -o
rw,nosuid,nodev,uhelper=hal,shortname=lower,uid=1000,gid=1004 /dev/sdc1
/media/TOSHIBA

I am not able to determine the output of mount for the same device in etch.
 My backup etch partition has passed on.

If someone can point me at the right doco, or desribe how this works, I
would appreciate it.
Thanks and regards,
Chris.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to