Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Aug 2017 20:58:07 +0200
From:      Nikolaus Rath <Nikolaus@rath.org>
To:        freebsd-fs@freebsd.org
Subject:   Re: Status of FUSE in FreeBSD kernel
Message-ID:  <8760dudj9c.fsf@vostro.rath.org>
In-Reply-To: <878tiqdjtc.fsf@vostro.rath.org> (Nikolaus Rath's message of "Fri, 11 Aug 2017 20:46:07 %2B0200")
References:  <878tiqdjtc.fsf@vostro.rath.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 11 2017, Nikolaus Rath <Nikolaus@rath.org> wrote:
> Hello,
>
> Is there some resource that gives an overview of the features supported
> by the FUSE kernel module in FreeBSD?
>
> For example, I am wondering if the EINVAL error that I'm getting when
> sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error
> on my side, or because the FreeBSD kernel just doesn't support it.
>
> I expect to encounter the same question for a number of other functions,
> e.g. the other FUSE_NOTIFY_* requests.

Another example: calling 'mknod' or 'mkfifo' on a FUSE mountpoint
doesn't seem to make it through to the filesystem, the kernel returns
-EINVAL instead.

Is that a problem with the filesystem, or not supported by the kernel?

Thanks!
-Nikolaus

--=20
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2=
=AB



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8760dudj9c.fsf>