It is not possible for users to mount NTFS volumes with ntfs3g-2009.4.4. Trying to do so results in: Unprivileged user can not mount NTFS block devices using the external FUSE library. Either mount the volume as root, or rebuild NTFS-3G with integrated FUSE support and make it setuid root. Please see more information at http://ntfs-3g.org/support.html#unprivileged This is the result of the ebuild now passing "--with-fuse=external" to the ntfs3g configure script (this was not the case in previous ebuilds.) I think the right solution is to make this a USE flag (for example "external-fuse") and, if enabled, inform the user that this will break user mount capabilities. (I've marked this bug's severity as "major" since there's no workaround I know of and in some environments, users being able to mount without root access is important.)
Created attachment 201891 [details, diff] ntfs3g-2009.4.4-r1.ebuild.patch Patch that implements the "external-fuse" USE flag proposal in the current ebuild. I didn't make it a default flag ("+external-fuse") because the ebuild is still EAPI=0.
Added external-fuse USE flag in new EAPI=2 version of ebuild.
Calculating dependencies... done! [ebuild N ] sys-fs/fuse-2.7.4 [ebuild U ] sys-fs/ntfs3g-2009.4.4 [2009.3.8] USE="external-fuse%*" why is flag on by default? I have fuse in kernel , why is this trying to change by set up and pull in extra packages? Also in view of comments about non priveleged user in the original report this is not what I require. Is this the right choice?
having added this to /etc/portage/package.use it is still trying to pull in the fuse package. Calculating dependencies... done! [ebuild N ] sys-fs/fuse-2.7.4 [ebuild U ] sys-fs/ntfs3g-2009.4.4 [2009.3.8] USE="-external-fuse%" This needs reopening until it works correctly.
