From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: Karel Zak <kzak@redhat.com>
Cc: <util-linux@vger.kernel.org>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] mount: add btrfs to mount.8
Date: Fri, 6 Jun 2014 14:32:39 +0800 [thread overview]
Message-ID: <1402036359.17740.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20140605080311.GW9000@x2.net.home>
On Thu, 2014-06-05 at 10:03 +0200, Karel Zak wrote:
> On Thu, Jun 05, 2014 at 10:05:19AM +0800, Gui Hecheng wrote:
> > Based on Documentation/filesystems/btrfs.txt
> >
> > Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
> > ---
> > sys-utils/mount.8 | 186 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 186 insertions(+)
>
> Thanks, but I'm not sure this is the right way. It would be better to
> create BTRFS specific btrfs.5 man page and maintain it together with
> another BTRFS stuff rather then within util-linux. In the mount.8
> should be only a note about btrfs.5.
>
> My long time goal is to remove all FS specific sections (at least for
> mainstream filesystems) from mount.8, because we duplicate effort
> here. The primary and well maintained is usually kernel
> Documentation/filesystems/ and unfortunately FS developers don't care
> about mount.8 at all.
>
> The ideal solution would be to generate the FS man pages from kernel
> docs (for example from asciidoc etc.)
>
> See 6 years old discussions: http://marc.info/?t=122767310200002&r=1&w=2
>
Hi Karel,
Thanks your comments. I do agree that this is *not* the best way. I
think that your long time goal is really exciting to the FS developers.
But for now, there are btrfs *users* complaining that they cannot find
any help by refering to the mount manpage when they want to mount their
btrfs. Actually, not every btrfs user have the mood to check the
Documentation/filesystems/btrfs.txt or anywhere else when they just want
to use a simple mount cmd.
I think that adding the btrfs stuff into mount.8 do a certain help to
the common btrfs users. By the way, I've checked the recent commmits of
util-linux tree and found that there are still enthusiastic contributers
making really meaningful changes to the mount.8.
So, If it does not bother you much...
Our btrfs users are really looking forward to a more kind and helpful
mount manpage for btrfs. And then they will feel really happy that they
could mount their btrfs in various ways easily as they like *just as the
ext4 users do*. And I think there are many btrfs developers who will be
glad to continue helping correct the btrfs part.
Thanks
-Gui
> Karel
>
next prev parent reply other threads:[~2014-06-06 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 2:05 [PATCH] mount: add btrfs to mount.8 Gui Hecheng
2014-06-05 8:03 ` Karel Zak
2014-06-06 6:32 ` Gui Hecheng [this message]
2014-06-06 9:44 ` Karel Zak
2014-06-06 10:02 ` Gui Hecheng
2014-06-06 10:03 ` Karel Zak
2014-06-06 10:03 ` Gui Hecheng
2014-06-06 15:52 ` Eric Sandeen
2014-06-07 13:41 ` Christoph Hellwig
2014-06-09 14:09 ` Eric Sandeen
2014-06-09 14:22 ` Karel Zak
2014-06-11 22:09 ` Eric Sandeen
2014-06-06 10:17 ` Karel Zak
2014-06-09 6:26 ` Gui Hecheng
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=1402036359.17740.33.camel@localhost.localdomain \
--to=guihc.fnst@cn.fujitsu.com \
--cc=kzak@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=util-linux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).