Thanks for the comment. As is appears that the "exec" option is
supported, I'll close this bug report and fix the fdi file now.
** Changed in: gnome-mount (Ubuntu)
Status: Incomplete => Invalid
--
ntfs-3g doesn't support "exec" option
https://bugs.launchpad.net/bugs/320192
You received th
The 'exec' mount option is of course supported. In fact it's the default
NTFS-3G option. There are over 80 NTFS-3G mount options. These are NTFS-
3G, FUSE user space, FUSE kernel driver and kernel VFS related. The
NTFS-3G man page documents only the NTFS-3G specific mount options, none
of the other
Actually, I looked at the wrong manpage. exec isn't documented in the
man page for ntfs-3g (I looked at the manpage for mount, by accident).
I think I need to clear this up with the upstream ntfs-3g developers
** Changed in: gnome-mount (Ubuntu)
Status: Invalid => Incomplete
--
ntfs-3g d
noexec is actually documented in the manpage, so I appear to be wrong.
I'll close this bug, and correct the ntfs-3g HAL fdi file
** Changed in: gnome-mount (Ubuntu)
Status: Incomplete => Invalid
--
ntfs-3g doesn't support "exec" option
https://bugs.launchpad.net/bugs/320192
You received t
Hi,
That's odd. You might be correct though. I just had a look through the
option parsing code for ntfs-3g, and exec did not appear to be an option
that was parsed, so I assumed that it was not valid. It doesn't appear
in the man page for ntfs-3g either. I'll revisit this again this
afternoon thou
Hi Chris,
What you are reporting makes sense assuming that what you are saying is true,
but why do we already have a patch that appends the "exec" option in that gconf
location if that option isn't supported by ntfs-3g? Are we missing a piece of
the puzzle? Is the purpose of this bug report t
