Hi Chris,
On Fri, 23 Jan 2009, Chris Coulson wrote:
> I'm currently working on packaging the latest ntfs-3g release for
> inclusion in Ubuntu.
Do you mean version 2009.1.1? That would be really great, thanks! :-)
Historically Ubuntu always has an older NTFS-3G driver included and we get
lots of problem reports from Ubuntu users which are already solved in
the newer releases:
http://ntfs-3g.org/releases.html
> Because of some changes to HAL recently, I have to package a HAL fdi file
> with it, to modify some properties on NTFS volumes in HAL so that we can
> automatically mount them with the ntfs-3g driver. As part of this, I have
> to tell HAL exactly what mount options are valid.
>
> I'm unsure whether ntfs-3g supports the "exec" mount option. It is not
> documented in the man-page and I had a quick look through the code and
> it didn't look like a valid option. The only reason I ask this is
> because the solution to "Why does Wine crash" on your support page [1]
> suggests to mount the volume with "exec", and this had me wondering
> whether it actually supports it. I just wanted to clear this up before I
> package it.
Accidently, I've just seen your post 2 minutes after you made it in the
Ubuntu bug tracking system and it's already answered.
https://bugs.launchpad.net/ubuntu/+source/gnome-mount/+bug/320192/comments/5
------------------------------------------------------------------------->
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
ones like, 'exec'.
The supported mount options always depend on the NTFS-3G version, the FUSE
user space version, FUSE kernel module version and the kernel version. But
users should never neet to know more then perhaps some of the NTFS-3G
specific one and the general kernel options (uid, gid, exec, suid, etc).
Please also not blame NTFS-3G for the current problem. It is HAL. We tried
hard to push for a trivial and transparent solution but the HAL maintainer
decided to make life much harder for everybody:
http://lists.freedesktop.org/archives/hal/2008-October/012366.html
http://lists.freedesktop.org/archives/hal/2008-October/012368.html
Notice, how I predicted that the HAL changes will break many distributions:
"See e.g. Danny's recent reverted patch. The next HAL release will break at
least all Ubuntu and Fedora based distros (about 12 million users) not
being able to automount NTFS. Again."
HAL is historically a highly unreliable and confusing solution. Afaik, much
better alternatives are being worked on.
Btw, the latest NTFS-3G release (2009.1.1) has built-in, transparent UTF-8
support and the locale= option is ignored for filename conversion. The
locale= option didn't work in many cases eve if it was correctly passed to
NTFS-3G (and that is a glibc problem but that's another very long story).
<----------------------------------------------------------------------------
Sorry about the too fast reply ;-)
Szaka
--
NTFS-3G: http://ntfs-3g.org
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
