Summary: | sys-fs/ntfs3g: please add 'symlink' USE to control /usr/sbin/mount.ntfs symlink creation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry Petrov <dmitry.petroff> |
Component: | Current packages | Assignee: | Patrick McLean <chutzpah> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | base-system, floppym, pacho, ssuominen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=635080 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | symlink USE patch for ntfs3g ebuilds |
Description
Dmitry Petrov
2016-05-16 16:58:20 UTC
Sorry, status change was a misclick. your problem statement doesn't make sense. if you want read-only access, then use the "ro" flag to the options. the symlink makes no difference here. It's kernel read-only ntfs driver versus fuse-driven ntfs-3g. They aren't the same in terms of performance and resource usage. (In reply to Dmitry Petrov from comment #3) i know what drivers you're talking about. my point is, you're doing it wrong: (1) if you want read-only, then you use "ro" (2) the kernel driver, while defaulting to read-only, has read-write support so if your only reason for wanting to drop this symlink is to be lazy and get read-only by default, the answer is "no". (In reply to SpanKY from comment #4) I want to use kernel ntfs driver because: 1) it should be faster 2) it allows mounting of NTFS filesystems by regular users without sudo/suid helpers That's what happen when /usr/sbin/mount.ntfs points to mount.ntfs-3g: $ mount /mnt/win_d/ 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://tuxera.com/community/ntfs-3g-faq/#unprivileged And as soon as /usr/sbin/mount.ntfs is removed, everything is fine. This symlink has great impact on mount behaviour (especially for unprivileged users). It should be optional in my opinion. >so if your only reason for wanting to drop this symlink is to be lazy and get read-only by default, the answer is "no". By the way, this symlink initially added because of someone being too lazy to use "ntfs-3g" filesystem type explicitly. Also there was a question in original bug: https://bugs.gentoo.org/show_bug.cgi?id=374197#c2 - "Would making the mount.ntfs symlink break anything?" It seems like the answer is: "yes, it is". (In reply to Dmitry Petrov from comment #5) if you want to mount things by hand, that's already trivial to do -- use the -i option. thus there is no real impact for users if they want to force ntfs. as for sudo/suid, you do realize mount is already suid right ? as for ntfs-vs-ntfs-3g, ntfs-3g is a superior implementation of the ntfs filesystem, so making it the default even for ntfs entries makes sense. (In reply to SpanKY from comment #6) > if you want to mount things by hand, that's already trivial to do -- use the > -i option. thus there is no real impact for users if they want to force > ntfs. And automatic ntfs mounting from fstab will always use ntfs-3g. There's no way to specify "-i" for fstab. > as for sudo/suid, you do realize mount is already suid right ? Sure it is. But mount.nfst-3g is not. > as for ntfs-vs-ntfs-3g, ntfs-3g is a superior implementation of the ntfs > filesystem, so making it the default even for ntfs entries makes sense. ntfs-3g is a different implementation, which has its own advantages (write support) and disadvantages (may be slower/consume more resources because of fuse). Let me summarize: - my case (manual ntfs mount) is covered by adding "-i" option for mount - manual mounting with ntfs-3g would require suid USE-flag - automatic ntfs-3g should work without any problems - automatic mounting using kernel ntfs driver is not possible (I don't know of any methods to emulate "-i" option from fstab) The latter case is broken by unconditional creation of mount.ntfs symlink. Why don't place this functionality under USE-flag which can even be enabled by default if you think it's appropriate? This seems like a reasonable request to me. As a workaround until this USE flag is added, you could add /usr/sbin/mount.ntfs to INSTALL_MASK. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e88a6eb57790b8e05fa7b11c22f0b0855016fc22 commit e88a6eb57790b8e05fa7b11c22f0b0855016fc22 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2021-11-05 23:10:45 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2021-11-05 23:10:45 +0000 sys-fs/ntfs3g: add 'mount-ntfs' USE flag Closes: https://bugs.gentoo.org/583214 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-fs/ntfs3g/metadata.xml | 1 + sys-fs/ntfs3g/ntfs3g-2021.8.22.ebuild | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) [ebuild U ] sys-fs/ntfs3g-2021.8.22-r1:0/89::gentoo [2021.8.22:0/89::gentoo] USE="acl mount-ntfs%* ntfsprogs xattr -debug -ntfsdecrypt -static-libs -suid" 0 KiB I wanted to disable the flag, but I don't see it in ufed. Why? When? So I have to do it by hand. after adding it for sys-fs/ntfs3g to /etc/portage/package.use/package.use I see in ufed: mount-ntfs (sys-fs/ntfs3g) (Unknown) (In reply to jospezial from comment #10) > I wanted to disable the flag, but I don't see it in ufed. Why? When? > So I have to do it by hand. ufed is probably buggy and has no maintainer. Regardless, this is not a bug in the ntfs3g ebuild. File a separate bug report if you wish. |