partitions get mounted with noexec flag against fstab will
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hal (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This is probably hal/pmount related, but I'm really not sure.
There seems to be a problem mounting partitions.
my /etc/fstab.conf contains those line
/dev/sda1 /media/hda1 ntfs-3g exec,noauto,
/dev/sda3 /media/storage vfat exec,noauto,
AFAIK, the noauto will cause the drives to be mounted when gnome starts so that their icon will appear on the desktop.
mount reports
/dev/sda1 on /media/hda1 type fuseblk (rw,noexec,
/dev/sda3 on /media/storage type vfat (rw,noexec,
The noexec flag is set while it should be "exec".
I noticed some options in gconf-editor concerning file systems (system/
Pretty much the same thing happens with an external USB drive.
When I plug my external hard drive (ext3 and vfat partitions on it), I get this
/dev/sdb2 on /media/SG-FAT32 type vfat (rw,nosuid,
/dev/sdb1 on /media/SG-EXT3 type ext3 (rw,noexec,
here, suddenly, the vfat one allows exec while the ext3 has noexec.
Here again, it seems simply impossible to set it up so that it has exec.
Step to reproduce:
Problem A :
- Have a vfat partition on a computer
- set the fstab entry to "exec" and "noauto" for the device
- when you enter gnome after bootup, the device will be mounted as noexec
Problem B :
- Have an external drive with an ext3 partition (no references to it in fstab)
- Plug it in
- It gets mounted as noexec
Current solution :
Unmount the device and remount it with noexec. Works but my Grandmother couldn't do it, plus, it's quite annoying to do it at every boot on a laptop for 4 different partitions.
From ntfs-3g upstream: people keep reporting this problem with mount(8) too and the solution is to put the 'exec' option after the 'user' one. Maybe this helps you too. I don't know if this is by design or a bug in mount(8) but I guess the latter since it keeps confusing people with the unexpected and undesired behaviour.