Rodolfo,
This did the trick. You would not believe how close I was to working
this out before. I was just missing the "=". Oh well.
The hal version:
peterpan:/etc/hal/fdi/policy# hald --version
HAL package version: 0.5.11
I guess the problem I am experiencing is a bug on the package. Are you
a good person to take this information to the appropriate Team?
I have spent some time attempting to figure out the relationship between
udev and hal. It seems that udev gets things first and passes a result
to hal. Right? I say this because the last udev rule says:
RUN+="socket:/org/freedesktop/hal/udev_event"
It also seems to me that udev sets the group permissions for the mount
command, but the config in gconf (as used by hal) was blanking it out.
If this is right I must say I had lots of trouble working it out because
I cannot figure how to insert and use debug statements to check things,
or where low level logging might go.
If you could assist with a udev rule to permanently mount a usb card for
my user, I would really appreciate it. As I said I have made a few
tentative additions to existing rules and observed no discernible change
in system behavior. I'm looking at:
http://reactivated.net/writing_udev_rules.html
Relevant output from udevinfo -a -p $(udevinfo -q path -n /dev/sdc1)
looking at parent device '/devices/pci0000:00/0000:00:02.1/usb2/2-6':
KERNELS=="2-6"
SUBSYSTEMS=="usb"
DRIVERS=="usb" <===
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bMaxPower}=="200mA"
ATTRS{urbnum}=="370236"
ATTRS{idVendor}=="0930" <==
ATTRS{idProduct}=="6545" <==
ATTRS{bcdDevice}=="0110"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="2"
ATTRS{devnum}=="28"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="TOSHIBA" <===
ATTRS{product}=="TransMemory " <===
ATTRS{serial}=="0220787042A168B4"
BTW, what/why is there a difference between SUBSYSTEM and SUBSYSTEMS?
Regards,
Chris
Rodolfo Martínez wrote:
Hi Chris,
The line should be:
<append key="volume.mount.valid_options" type="strlist">gid=</append>
Note the '=' after 'gid'. The '=' means that HAL accept any value for that key.
And the gconf mount options should include 'gid=1004'.
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.
The only solution for this is to specify the mount options (uid, gid,
etc.) in /etc/fstab. HAL will search for an entry that matches the
device that will be mounted, if none matches, it will mount the device
using the default values/options. The default is to mount the device
on behalf of the user that invoked the mount petition.
The problem is that the device block won't be always the same, it
could be /dev/sdc1, /dev/sdd1 and so on, but this can be easy
addressed with a udev rule, let me know if you need help with this.
BTW, what version of HAL are you using?
--
Rodolfo Martínez
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
