Date: Fri, 2 Feb 2018 11:50:25 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Martin Simmons <martin@lispworks.com> Cc: "Mikhail T." <mi+b@aldan.algebra.com>, freebsd-fs <freebsd-fs@freebsd.org>, brendan+freebsd@bbqsrc.net Subject: Re: fusefs and /etc/fstab Message-ID: <CA%2BtpaK29s7Ui3=7g_9xYNSDBhc2iT8RSvhPuVY0Ejn6-WC7Ccw@mail.gmail.com> In-Reply-To: <201802021712.w12HC1m8012695@higson.cam.lispworks.com> References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> <cebd24ef-07b6-ebb7-4da3-8f4fcf2f95df@freebsd.org> <42ad9c4b-9017-0955-a550-521f9e2d933d@aldan.algebra.com> <201802021712.w12HC1m8012695@higson.cam.lispworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 2, 2018 at 11:12 AM, Martin Simmons <martin@lispworks.com> wrote: > >>>>> On Thu, 1 Feb 2018 14:35:26 -0500, Mikhail T said: > > > > 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 > > Yes, but mount doesn't run mount_fusefs when processing /etc/fstab. > You can use mountprog option. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK29s7Ui3=7g_9xYNSDBhc2iT8RSvhPuVY0Ejn6-WC7Ccw>