linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 18:02:11 +0800	[thread overview]
Message-ID: <1402048931.13997.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20140606094428.GA30975@x2.net.home>

On Fri, 2014-06-06 at 11:44 +0200, Karel Zak wrote:
> On Fri, Jun 06, 2014 at 02:32:39PM +0800, Gui Hecheng wrote:
> > 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. 
> 
>  The kernel is the "ideal place", but it's more dream than anything
>  else... what we use for example for NFS is to maintain FS specific
>  man page in userspace FS package (e.g. nfs-utils).
Ah, thanks for explaining so much to me, I can't agree more.

>  Wouldn't be possible to add the man page to btrfs-progs package? The
>  package is maintained by btrfs guys and I guess all btrfs users have
>  very probably installed the package.
Actually, we just would like to see btrfs "staying with" ext4, xfs and
other fs together. We feel a bit sad that ext4 and xfs both have stuff
in mount.8 but btrfs doesn't.

> > So, If it does not bother you much... 
> 
>  I personally have no problem to maintain information about arbitrary
>  FS in mount.8, the problem are updates. Unfortunately, kernel FS developers
>  don't care about the man page at all and it's very often not up to date.
> 
>  [My experience is very bad. Not sure why, but for many kernel devels
>   commit into Linus' tree is end of their work, they don't care if there
>   is usable userpsace util or docs for users, people like Eric Biederman
>   or Lukas Czerner are rare exception.]
Thanks for sharing the story with me, I really get a lot.

> > And I think there are many btrfs developers who will be
> > glad to continue helping correct the btrfs part.
> 
>  OK, we can try it, if you still prefer mount.8.
Our guys will try our best to keep the mount.8 for btrfs up-to-date.
At least, you have my promise.

Thanks,
-Gui

>     Karel
> 



  reply	other threads:[~2014-06-06 10:07 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
2014-06-06  9:44     ` Karel Zak
2014-06-06 10:02       ` Gui Hecheng [this message]
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=1402048931.13997.10.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).