WadeWayne wrote: ⤴Tue Apr 13, 2021 5:50 am
Should I replace
defaults
with
uid=wadewayne,gid=wadewayne
[ ... ]
Iff you want files and directories on that NTFS filesystem to appear and by treated by Linux as being owned by wadewayne:wadewayne, yes.
WadeWayne wrote: ⤴Tue Apr 13, 2021 5:50 am
[ ... ] and
fmask=133,dmask=022
?
If you don't care for the standard all-access permissions that are set by default, yes. If nothing else has an
ls -l
not scream at you so much visually...
As the mentioned man page details,
fmask
and
dmask
together are a more focussed version of
umask
and determine which permissions are
not present on respectively files and directories. On Linux permission 644 for files (rw-r--r--) and 755 (rwxr-xr-x) for directories are "the most normal"; the suggested 133 resp. 022 are their octal complements. Feel free to not have these options or adjust them to liking but the suggested values have things behave more or less sanely even on NTFS.
Code: Select all
UUID=9EB6973BB697133F /mnt/sda3 ntfs-3g noexec,uid=wadewayne,gid=wadewayne,fmask=133,dmask=022
Note; I tend to use type
ntfs-3g
instead of plain
ntfs
due to historically latter being a read-only kernel-based filesystem driver, former the same NTFS-3G userspace FUSE filesystem driver as today --- even though these days and on Ubuntu/Mint
ntfs
is in fact a mere alias for
ntfs-3g
. It's still sightly too soon in the context of Linux as a whole to not at least be aware of that historic difference.
The
noexec
parameter makes it so that execute permissions on files are actually ignored
anyway (and certainly makes for a reason to then also as a matter of consistency set the fmask as per above). Why you'd want it is as a poor man's security measure: it disallows blindly executing in Linux something e.g. downloaded in Windows. Take it out if you don't care for it --- and if indeed you don't, perhaps have the fmask be e.g. 755 as well, of course.