Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Aug 2017 04:22:03 +0800
From:      Julian Elischer <julian@freebsd.org>
To:        Nikolaus@rath.org
Cc:        freebsd-ports@freebsd.org, freebsd-fs@freebsd.org
Subject:   Re: State of FUSE on FreeBSD
Message-ID:  <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org>
In-Reply-To: <87y3r0ankb.fsf@vostro.rath.org>
References:  <87y3r0ankb.fsf@vostro.rath.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

Rick Maclem has looked at it a little, as have a few people (see the 
commit logs)
but generally as long as it more or less works, people tend to steer
clear of it.

For us libfuse "just worked" so we haven't touched it.
We had to touch the kernel part of fuse a little so remove some overly 
restrictive
permission checks, and fix some issues to do with page boundaries 
(from memory)
but nothing in the library.

> After taking a look at
> https://github.com/freebsd/freebsd/tree/master/sbin/mount_fusefs,
> https://svn.freebsd.org/ports/head/sysutils/fusefs-libs/, and
> https://github.com/libfuse/libfuse/issues/173, it seems to me that:
>
> - A lot of upstream code that was actually intended to support FreeBSD
>    is actually patched out when libfuse is installed via ports.
>
> - The mount.fusefs and fusermount binaries are not installed from
>    libfuse at all, and are instead provided by a "sysutils/fusefs-libs"
>    package(?)
that may be possible, We just mount by doing calls to the library in 
our code
so I haven't looked at it.
> - Some additional patches are necessary to get libfuse to work.
>
>
> Is that correct so far, or am I looking at the wrong place?
>
>
> If so, my tentative plan would be to:
>   
> - Not build fusermount and mount.fusefs on FreeBSD at all. This would
>    allow getting rid of mount_bsd.c (and the corresponding patch)
>    completely.
I don't think I've ever seen them used.
>    
> - Integrate the helper.c patch upstream using #ifdefs
>
> - As far as I can tell, the mount_util.[ch] patch is a no-op that should
>    be dropped anyway.
>
>
> Personally, I don't use FreeBSD and I don't have an easy way to test on
> FreeBSD either. So I would appreciate any input.
got vmware or Xen or virtualBox or HyperV?

we provide a bunch of virtual images.

>
>
> Best,
> -Nikolaus
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39c45819-2754-ed73-a0e7-681969f58de7>