On 25/11/14 04:04 PM, Scott Ferguson wrote:
On 26/11/14 08:03, Rick Macdonald wrote:
Well, many hours of googling, and running grep on my entire filesystem,
have failed me this time.
I'm running up-to-date wheezy.
DE?
Sorry, I don't know what DE means! It's an i386 desktop that's been
running Debian since the 0.93 days in the mid-90's before Buzz was
released (OK, it's gone through some hardware upgrades ;-).
How does one override or change to options fuse gives to ntfs-3g (if I
have that right)?
I have an NTFS filesystem on a USB-connected hard drive. With nothing in
fstab, it gets auto-mounted as /media/WinBackup:
syslog:
Nov 25 12:56:17 timshel ntfs-3g[16915]: Version 2012.1.15AR.5 external
FUSE 29
Nov 25 12:56:17 timshel ntfs-3g[16915]: Mounted /dev/sdg2 (Read-Write,
label "WinBackup", NTFS 3.1)
Nov 25 12:56:17 timshel ntfs-3g[16915]: Cmdline options:
rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077,fmask=0177
Nov 25 12:56:17 timshel ntfs-3g[16915]: Mount options:
rw,nosuid,nodev,uhelper=udisks,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdg2,blkdev,blksize=4096
Nov 25 12:56:17 timshel ntfs-3g[16915]: Global ownership and permissions
enforced, configuration type 7
According to the fuse man page, /etc/fuse.conf only supports mount_max
and user_allow_other.
I can mount it manually by adding the following entry to fstab (which
somehow inhibits the automount), but I'd much rather have it auto mount
whenever I plug it in.
Without knowing more about your "Wheezy" the easiest option is probably
to create a custom udev rule.
I'll look into that, but I hope to understand something about
fuse/ntfs-3g since I've come this far.
LABEL=WinBackup /media/WinBackup ntfs
rw,nosuid,nodev,uhelper=udisks,allow_other,nonempty,relatime,default_permissions,blkdev,umask=0000
0 0
What does "allow_other" do?
allow_other (man mount.fuse) lets users other than the one who mounted
the filesystem access files. You'd think that's all I need, but it's
already on the mount command line. The problem seems to be the dmask &
fmask values restrict access regardless.
Why "umask=0000" (instead of 0022)?
Why not "uid=$username,gid=users"
All the options were copied from the mount options in the syslog above.
I removed the ones that mount didn't like (blkdev and fsname). I wanted
to start with what (I think) fuse is giving ntfs-3g on it's command line
(not that that's a valid thing to do).
"fuse" doesn't seem to be a binary executable, and I can't find where
these command line args are coming from when mount is called.
Do you want to retain and use standard Windows permissions?
How many people will need access to the disk?
Nobody else uses the machine, but I need the permissions opened up. When
my WinXP server died I moved my videos to my Linux desktop. I usually
use Serviio but thought I'd give Plex a try (Plex doesn't support XP so
I couldn't give it a try until now). Plex runs as user "plex" and cannot
read any of the files on this USB disk when mounted under my account
with mode 600 permissions. Plex has an option to let the client delete
videos, so while testing I chose 0000. I could tell Plex to run as me,
but that's no good because its files are installed under
/var/lib/plexmediaserver, and if I change the ownership of those it
would likely break upgrading Plex when the next deb file is released.
Rick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/547521cd.4090...@timshel.ca
