Date: Fri, 11 Aug 2017 13:51:15 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: Freebsd fs <freebsd-fs@freebsd.org> Subject: Re: State of FUSE on FreeBSD Message-ID: <B6B1B408-A1DB-4D51-BC72-B0FDF3F5A701@gmail.com> In-Reply-To: <8760dufiu2.fsf@vostro.rath.org> References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <A3A6DC54-5FC7-481F-A679-1E247F5B39D6@gmail.com> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <FFFC5806-4C5D-4837-9A71-BDD97D76AF25@gmail.com> <8760dufiu2.fsf@vostro.rath.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 11 Aug 2017, at 13:24, Nikolaus Rath <Nikolaus@rath.org> wrote: >=20 >>> Ok.. some progress. Now it fails with: >>>=20 >>> # example/hello /mnt >>> mount_fusefs: >>> = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>> on /mnt: No such file or directory >>> fuse: failed to mount file system: No error: 0 >>>=20 >>> Anyone know what this might mean? >>=20 >> Same result with libfuse from sysutils/fusefs-libs ? >=20 > No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something of = the > BSD-specific mount code wasn't merged correctly? >=20 > Here's the pull request that I merged: = https://github.com/libfuse/libfuse/pull/189 Current patches can be found in this dir : # cd /usr/ports/sysutils/fusefs-libs/files (do not forget to run the 2 portsnap commands of my previous mail before = if you did not run them yet) As far as I can see, these patches and PR189 are the same. However there were new commits after PR189, perhaps you should test the = lib at this point ? = https://github.com/libfuse/libfuse/tree/8f3c800e151d8d8844d851344f85f6baa3= ac2d8f Sounds like mount_fusefs does not get a correct name (ZZZZZZZZZZ*). Ben=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B6B1B408-A1DB-4D51-BC72-B0FDF3F5A701>