util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Steve Kenton <skenton@ou.edu>,
	util-linux@vger.kernel.org,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 1/1] Update mount options for UDF
Date: Thu, 1 Mar 2018 12:08:51 +0100	[thread overview]
Message-ID: <20180301110851.tc7erpwy3duhvzxw@ws.net.home> (raw)
In-Reply-To: <20180228220319.ccosidfzrdlowwqu@pali>

On Wed, Feb 28, 2018 at 11:03:19PM +0100, Pali Rohár wrote:
> On Wednesday 28 February 2018 14:32:20 Jan Kara wrote:
> > On Wed 28-02-18 14:08:28, Karel Zak wrote:
> > > On Tue, Feb 27, 2018 at 12:44:07PM -0600, Steve Kenton wrote:
> > > > Signed-off-by: Steve Kenton <skenton@ou.edu>
> > > > Acked-by: Jan Kara <jack@suse.cz>
> > > > ---
> > > >  sys-utils/mount.8 | 89 +++++++++++++++++++++++++++++++++++++++++--------------
> > > >  1 file changed, 67 insertions(+), 22 deletions(-)
> > > 
> > > Applied, thanks.
> > > 
> > > Jan, what about to create udf(5) man page? We already have fs-specific
> > > man pages (e.g. ext4, tmpfs, nfs, btrfs, ...). It's usually maintained
> > > within fs-specific tools (e.g. ext4 -> e2fsprogs) or together with
> > > standard man-pages (CC: to Michael).
> > 
> > I'm fine with that. Pali is actually the maintainer of udf-tools so if he
> > is willing to take the manpage there, it's probably the best place.
> 
> Is udftools the best place for kernel udf mount options? Because
> userspace udftools are not needed for kernel udf driver, nor for
> mounting existing udf filesystem.

This is reason why Michael is in CC: :-)

> For me it looks like that kernel drivers should have its documentation
> in kernel itself...
> 
> Anyway, I have not know yet that there is e.g. ext4 manpage which
> describe mount options. I was always looking into mount.8 manpage for
> filesystem mount parameters.

There is no extN stuff anymore in mount.8.

> The only missing filesystem in mount.8 is nfs, but that is probably
> because mount uses mount.nfs helper.

Unfortunately, it's nothing unusual that mount.8 is ignored by FS
devels and not up to date... so the idea is keep FS docs near to 
the FS developers to improve things ;-) 

For example NFS developers have decided to maintain it in nfs-utils,
extN in e2fsprogs, tmpfs and procfs in Michaels' man-pages, etc.

Anyway, I have no problem to maintain UDF (or another) mount options 
in mount.8. It's your choice. Your patches for mount.8 are welcomed.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2018-03-01 11:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 18:44 [PATCH 1/1] Update mount options for UDF Steve Kenton
2018-02-28 13:08 ` Karel Zak
2018-02-28 13:32   ` Jan Kara
2018-02-28 22:03     ` Pali Rohár
2018-03-01 11:08       ` Karel Zak [this message]
2018-03-01 17:24         ` Pali Rohár
2018-04-19 15:25           ` Pali Rohár
2018-04-20  8:27             ` Karel Zak
2018-05-06 10:35       ` Michael Kerrisk (man-opages)
2018-05-06 11:15         ` Pali Rohár
2018-08-08 13:52           ` Pali Rohár
2018-08-13 10:01             ` Karel Zak

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=20180301110851.tc7erpwy3duhvzxw@ws.net.home \
    --to=kzak@redhat.com \
    --cc=jack@suse.cz \
    --cc=mtk.manpages@gmail.com \
    --cc=pali.rohar@gmail.com \
    --cc=skenton@ou.edu \
    --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).