State of FUSE on FreeBSD

Ben RUBSON ben.rubson at gmail.com
Fri Aug 11 11:51:19 UTC 2017


> On 11 Aug 2017, at 13:24, Nikolaus Rath <Nikolaus at rath.org> wrote:
> 
>>> Ok.. some progress. Now it fails with:
>>> 
>>> # example/hello /mnt
>>> mount_fusefs:
>>> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
>>> on /mnt: No such file or directory
>>> fuse: failed to mount file system: No error: 0
>>> 
>>> Anyone know what this might mean?
>> 
>> Same result with libfuse from sysutils/fusefs-libs ?
> 
> No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something of the
> BSD-specific mount code wasn't merged correctly?
> 
> 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/8f3c800e151d8d8844d851344f85f6baa3ac2d8f

Sounds like mount_fusefs does not get a correct name (ZZZZZZZZZZ*).

Ben


More information about the freebsd-fs mailing list