From: Nikolaus Rath <Nikolaus-BTH8mxji4b0@public.gmane.org>
To: Keno Fischer <keno-9DCaDmOhoh+8M3too/+dENBPR1lH4CV8@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fuse.4: Add new file describing /dev/fuse
Date: Sat, 10 Dec 2016 13:13:45 -0800 [thread overview]
Message-ID: <87vaurbi7q.fsf@vostro.rath.org> (raw)
In-Reply-To: <20161210072018.GA5267-9DCaDmOhoh+8M3too/+dENBPR1lH4CV8@public.gmane.org> (Keno Fischer's message of "Sat, 10 Dec 2016 02:20:18 -0500")
Hi,
On Dec 10 2016, Keno Fischer <keno-9DCaDmOhoh+8M3too/+dENBPR1lH4CV8@public.gmane.org> wrote:
> This is my writeup of a basic description of /dev/fuse after playing with
> it for a few hours today. It is of course woefully incomplete, and since
> I neither have a use case nor am working on this code, I will not be
> in a position to expand it in the near future. However, I'm hoping this
> could still serve as a handy reference for others looking at this interface.
That's great! It makes me wonder:
At the moment, libfuse ships a mount.fuse(8) manpage that documents both
the mount options that can be passed to the kernel, and the pseudo-mount
options that can be used when using libfuse (but that are actually
implemented in userspace).
Would it make sense to remove everything kernel related from
mount.fuse(8) and move it into linux-manpages?
Here's the manpage I'm talking about:
https://github.com/libfuse/libfuse/blob/master/doc/mount.fuse.8
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Nikolaus Rath <Nikolaus@rath.org>
To: Keno Fischer <keno@juliacomputing.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fuse.4: Add new file describing /dev/fuse
Date: Sat, 10 Dec 2016 13:13:45 -0800 [thread overview]
Message-ID: <87vaurbi7q.fsf@vostro.rath.org> (raw)
In-Reply-To: <20161210072018.GA5267@juliacomputing.com> (Keno Fischer's message of "Sat, 10 Dec 2016 02:20:18 -0500")
Hi,
On Dec 10 2016, Keno Fischer <keno@juliacomputing.com> wrote:
> This is my writeup of a basic description of /dev/fuse after playing with
> it for a few hours today. It is of course woefully incomplete, and since
> I neither have a use case nor am working on this code, I will not be
> in a position to expand it in the near future. However, I'm hoping this
> could still serve as a handy reference for others looking at this interface.
That's great! It makes me wonder:
At the moment, libfuse ships a mount.fuse(8) manpage that documents both
the mount options that can be passed to the kernel, and the pseudo-mount
options that can be used when using libfuse (but that are actually
implemented in userspace).
Would it make sense to remove everything kernel related from
mount.fuse(8) and move it into linux-manpages?
Here's the manpage I'm talking about:
https://github.com/libfuse/libfuse/blob/master/doc/mount.fuse.8
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-12-10 21:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 7:20 [PATCH] fuse.4: Add new file describing /dev/fuse Keno Fischer
2016-12-10 7:20 ` Keno Fischer
[not found] ` <20161210072018.GA5267-9DCaDmOhoh+8M3too/+dENBPR1lH4CV8@public.gmane.org>
2016-12-10 14:17 ` Michael Kerrisk (man-pages)
2016-12-10 14:17 ` Michael Kerrisk (man-pages)
[not found] ` <96577e95-953c-994c-1dbb-2b4c92c1d2c4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-10 21:03 ` Keno Fischer
2016-12-10 21:03 ` Keno Fischer
[not found] ` <CABV8kRxw+Dps3iMi8GJOUiegUdxFBuaMF-icy=z0=faKUNi4SA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-11 9:27 ` Michael Kerrisk (man-pages)
2016-12-11 9:27 ` Michael Kerrisk (man-pages)
2016-12-10 21:13 ` Nikolaus Rath [this message]
2016-12-10 21:13 ` Nikolaus Rath
[not found] ` <87vaurbi7q.fsf-sKB8Sp2ER+yL2G7IJ6k9tw@public.gmane.org>
2016-12-10 21:19 ` Keno Fischer
2016-12-10 21:19 ` Keno Fischer
2016-12-11 9:28 ` Michael Kerrisk (man-pages)
2016-12-11 9:28 ` Michael Kerrisk (man-pages)
[not found] ` <1557a45c-8282-d181-1533-0204895ddc9b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-11 15:31 ` Nikolaus Rath
2016-12-11 15:31 ` Nikolaus Rath
2016-12-11 18:16 ` Michael Kerrisk (man-pages)
[not found] ` <cd39e8cf-d59b-d485-2a01-85751a298bb5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-11 19:55 ` Nikolaus Rath
2016-12-11 19:55 ` Nikolaus Rath
2016-12-12 6:21 ` Michael Kerrisk (man-pages)
2016-12-13 17:49 ` Nikolaus Rath
2016-12-13 17:49 ` Nikolaus Rath
2016-12-14 7:25 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vaurbi7q.fsf@vostro.rath.org \
--to=nikolaus-bth8mxji4b0@public.gmane.org \
--cc=keno-9DCaDmOhoh+8M3too/+dENBPR1lH4CV8@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.