From: Andreas Dilger <adilger-xsfywfwIY+M@public.gmane.org>
To: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mount(8) manpage and filesystem-specific options
Date: Wed, 26 Nov 2008 13:05:26 -0700 [thread overview]
Message-ID: <20081126200526.GX3186@webber.adilger.int> (raw)
In-Reply-To: <20081126105444.GO2961-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
On Nov 26, 2008 11:54 +0100, Karel Zak wrote:
> On Tue, Nov 25, 2008 at 11:15:58PM -0500, Christoph Hellwig wrote:
> > Currently the mount(8) manpages which is contained inside util-linux
> > has a list of mount options for various filesystem. Now the filesystems
> > are in the kernel tree and can change options without affecting the
> > mount binary, and of course do so frequently. This means these options
> > are frequently out of date. All these options also make the manpage
>
> Yes, you're right.
>
> > quite large and harder to read. What do peope think about adding a
> > (section 4?) manpage for every common filesystem in the man-pages
>
> Something like this is on my wish list for long time ;-)
I see on my system that there are already mount.nfs(8) and mount.cifs(8)
man pages, but this is because /sbin/mount.{nfs,cifs} are separate binaries.
I DO think that it makes sense to have separate mount.{fstype} man pages
to clean up the mount(8) man page. I've also thought that this page is
a huge mess.
<aside>
I never know what man section to put a new man page in, because the
descriptions of the section numers isn't given in the man(1) man page
itself, nor in any document in SEE ALSO.
</aside>
> The FS specific options are already documented in the kernel
> Documentation/ directory. I have no strong opinion about it, but I
> think the best solution is to maintain this docs on one place only.
> The place should be in the kernel tree otherwise developers will
> ignore the docs... (it's pretty simple to reject kernel patches
> without proper Documentation/ update).
I would be happy do just put the mount.ext{2,3,4}(4) man pages into
linux/Documentation/filesystems/{man?} and have the ext{2,3,4} docs
refer to them for the mount options.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-26 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 4:15 mount(8) manpage and filesystem-specific options Christoph Hellwig
[not found] ` <20081126041558.GA9251-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-11-26 10:54 ` Karel Zak
[not found] ` <20081126105444.GO2961-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2008-11-26 20:05 ` Andreas Dilger [this message]
2008-11-26 20:46 ` Chuck Lever
[not found] ` <20081126200526.GX3186-RIaA196FMs1uuQVovAj/GogTZbYi8/ss@public.gmane.org>
2008-11-26 23:03 ` Karel Zak
2008-11-28 21:03 ` Michael Kerrisk
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=20081126200526.GX3186@webber.adilger.int \
--to=adilger-xsfywfwiy+m@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@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 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).