State of FUSE on FreeBSD

Ben RUBSON ben.rubson at gmail.com
Tue Aug 8 11:19:35 UTC 2017


> On 08 Aug 2017, at 13:11, Nikolaus Rath <Nikolaus at rath.org> wrote:
> 
> On Aug 08 2017, Ben RUBSON <ben.rubson at gmail.com> wrote:
>>> On 06 Aug 2017, at 19:40, Nikolaus Rath <Nikolaus at rath.org> wrote:
>>> 
>>> On Aug 06 2017, Ben RUBSON <ben.rubson at gmail.com> wrote:
>>>>> On 03 Aug 2017, at 22:22, Julian Elischer <julian at freebsd.org> wrote:
>>>>> 
>>>>> On 3/8/17 7:38 pm, Nikolaus Rath wrote:
>>>>>> Hello,
>>>>>> 
>>>>>> I am the upstream maintainer of libfuse. I'd like to refresh / improve
>>>>>> the FreeBSD support in libfuse. My goal is for libfuse not to require
>>>>>> any FreeBSD specific patches.
>>>>> 
>>>>> Hi, great to hear from you!
>>>>> at $JOB we use libfuse and We have always worried that we don't really
>>>>> have anyone in FreeBSD that really has fuse as a priority.
>>>> 
>>>> Glad to hear from Nikolaus too, seeing that efforts are taken to keep
>>>> libfuse FreeBSD compatible out of the box ! For sure this is great !
>>>> 
>>>> I also hugely use fuse, so having it to work correctly (at least
>>>> bug-free) is mandatory for me.
>>> 
>>> Would you mind testing the newest libfuse release then?
>> 
>> I just tested to compile it out of the box, it seems to fail :
>> https://benrubson.github.io/fuse.log
> 
> So what fails is just one of the examples, that's good news. Worst case
> we can disable it. Can I browse the FreeBSD manpages for fstatat() and
> openat() somewhere? Maybe there are equivalent flags that I could use.

I just dumped them :
https://benrubson.github.io/openat.txt
https://benrubson.github.io/fstatat.txt

Ben


More information about the freebsd-fs mailing list