many thanks for the answers.
Marc
Jon Peatfield wrote:
On Wed, 30 Jun 2010, Gasser Marc wrote:
Hi,
when I insert a disc in my cdrom on SL51 it is
mounted automatically with option noexec (autofs is not running, no
entry
for /dev/cdrom in fstab).
How can I change this behaviour, e.g. I'd like to have it
in exec mode.
Here is part of a message I wrote (a long time ago when sl5 was new)
that was going to eventually get turned into something suitable for
putting in our user docs. Hopefully it makes sense in this somewhat
raw form:
...
starting with the device (CD in this case) not mounted:
$ mount | grep hdc
$ gnome-mount --no-ui -d /dev/hdc
gnome-mount 0.5
$ mount | grep hdc
/dev/hdc on /media/K3b data project type iso9660
(ro,noexec,nosuid,nodev,uid=5272)
so that is what hal will do by default, but it *can* be adjusted - on
the command-line at least:
$ gnome-mount --no-ui --unmount -d /dev/hdc
gnome-mount 0.5
$ gnome-mount --no-ui --extra-mount-options exec -d /dev/hdc
gnome-mount 0.5
$ mount | grep hdc
/dev/hdc on /media/K3b data project type iso9660 (ro,nosuid,nodev)
$ gnome-mount --no-ui --unmount -d /dev/hdc
gnome-mount 0.5
$ gnome-mount --no-ui --extra-mount-options exec,uid=5272 -d /dev/hdc
gnome-mount 0.5
$ mount | grep hdc
/dev/hdc on /media/K3b data project type iso9660
(ro,nosuid,nodev,uid=5272)
hal (and hence gnome-mount which is a fairly trivial wrapper round it)
will allow some options to be specifified to override it's defaults
but not things that it consideres 'bad' like 'suid'...
$ gnome-mount --no-ui --unmount -d /dev/hdc
gnome-mount 0.5
$ gnome-mount --no-ui --extra-mount-options exec,suid,uid=5272 -d
/dev/hdc
gnome-mount 0.5
$ mount | grep hdc
<nothing>
Now you can also use the gnome-mount command to set gconf values for
specific volumes to have extra options, e.g.
...
to set the gconf setting to have the expected uid I ran (as you):
gnome-mount -t -v -h
/org/freedesktop/Hal/devices/volume_uuid_FEAA9FBD26ED9B92 \
--write-settings --mount-options exec
where the path ending volume_uuid_FEAA9FBD26ED9B92 is the HAL UDI
unique identifier for the volume so should match this one volume, and
after remounting the disk volume we see...
I have a fairly simple python script which will show the hal UDI paths
for currently connected devices (and other status about removable
devices) if that is of any interest to anyone.
I expect things to be very different in sl6 since devicekit replaces
parts of hal.
-- Jon
