Date: Thu, 1 Feb 2018 14:35:26 -0500 From: "Mikhail T." <mi+b@aldan.algebra.com> To: Stefan Esser <se@freebsd.org> Cc: freebsd-fs@freebsd.org, brendan+freebsd@bbqsrc.net Subject: fusefs and /etc/fstab Message-ID: <42ad9c4b-9017-0955-a550-521f9e2d933d@aldan.algebra.com> In-Reply-To: <cebd24ef-07b6-ebb7-4da3-8f4fcf2f95df@freebsd.org> References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> <cebd24ef-07b6-ebb7-4da3-8f4fcf2f95df@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
For people trying to use fstab to mount fusefs filesystem(s), there is a
problem -- the daemons expecting one argument after the options (the
mount-point), are confused by there being two arguments: the "special"
and the mount-point.
The mount_fusefs(8) recommends using "auto" for the "special" (first
field of the fstab), but that breaks too:
fuse: bad mount point `auto': No such file or directory
I first thought, this problem is specific to smbnetfs, but the program
simply uses FUSE_ARGS_INIT(argc, argv) and otherwise relies on the
libfuse library to process the command-line.
The trick I found to work is to put one of the mount options into the
first field:
-oallow_other /smb fusefs
rw,failok,uid=105,late,mountprog=/opt/bin/smbnetfs
but that's just a hack, of course.
Perhaps, our libfusefs ports can be modified to, upon encountering two
arguments remaining after the options, to either silently ignore the
first one at all times, or only ignore it, if it says "auto"?
Alternatively, maybe, mount_fusefs needs to strip the "special" off
before invoking the specified daemon?
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42ad9c4b-9017-0955-a550-521f9e2d933d>