public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andries E. Brouwer" <Andries.Brouwer-rh8NL+sEX9E@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	List util-linux-ng
	<util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
	Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
	sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
	Andries Brouwer <Andries.Brouwer-rh8NL+sEX9E@public.gmane.org>
Subject: Re: [RFC] devpts man page update
Date: Mon, 1 Dec 2008 22:08:39 +0100	[thread overview]
Message-ID: <20081201210835.GA14009@ub> (raw)
In-Reply-To: <cfd18e0f0812011205w62f30725m53f4b16cea3272aa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, Dec 01, 2008 at 03:05:47PM -0500, Michael Kerrisk wrote:
> On Mon, Dec 1, 2008 at 2:42 PM, H. Peter Anvin <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> wrote:
> > Add Cc: util-linux-ng
> >
> > Michael Kerrisk wrote:
> >>
> >> The fact that the util-linux(-ng) maintainer includes some kernel
> >> details in the mount(8) man page is not something that I control.
> >> It may or may not be a good idea.
> >>
> >
> > IMNSHO, it's distincly not a good idea.  For one thing, the mount(8) man
> > page is a mess.  Any options that aren't generic across filesystems
> > should be moved out of mount(8) into the filesystem man pages in section 4.
> >
> > The fact that the options are in the mount(8) man page is largely a
> > historical artifact dating back to the early 1990's when Linux only had
> > a handful of filesystems.
> >
> > The way to do that pretty much ends up with:
> >
> > 1. Agree that this is the way to do it.
> > 2. Add the options to section 4.
> > 3. Clean up mount(8).
> >
> > ... in that order.
> 
> If there's consensus (including from the mount(8) man page
> maintainer), I have no objection to this, and I can see some sense in
> it.  The mount options are, after all, kernel interfaces.  Perhaps
> this whole situation arose because once upon a time, the maintainer of
> the mount(8) page and the maintainer of man-pages were the same
> person, Andries, and perhaps he too has an opinion.  (Andries, here's
> a pointer to the thread so far:
> http://article.gmane.org/gmane.linux.man/557/ )

Hi Michael,

At some point in time I cleaned up the messy and incomplete mount docs
and wrote the nicely structured and complete mount(8). Of course as
time passes completeness can be lost, and the page can become unwieldy
because of excessive length. The page I am looking at has roughly 1500
lines, of which roughly 1000 are about filesystem-specific mount options.
Maybe a bit long, but since this length is caused by a list that is
alphabetically sorted and has entries that tend to be only a few dozen
lines long, I do not mind this length so much.

Perhaps Peter complains about something else when he sees a mess?

The goal of a man page author must be convenience of the user.
The information must be clear, precise, concise, easy to find.

I don't know how modern distributions usually present these man pages.
Myself, I read them in the old-fashioned way on an xterm, where no
hyperlinks are available. In such a setting a single page is clearly
more convenient, but there will come a point where it is simply too long.

These filesystem man pages in section 4 do not exist yet, as far as I can see.
What would the names be? Would splitting things up make it easier for the
user to find her info?

Andries

--
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

  parent reply	other threads:[~2008-12-01 21:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 18:17 [RFC] devpts man page update Sukadev Bhattiprolu
     [not found] ` <20081126181732.GA1509-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-11-27 11:38   ` Michael Kerrisk
     [not found]     ` <cfd18e0f0811270338o392daf81kdfd46cec51325891-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-27 19:14       ` H. Peter Anvin
2008-12-01 18:10       ` Sukadev Bhattiprolu
     [not found]         ` <20081201181055.GA12493-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-12-01 19:31           ` Michael Kerrisk
     [not found]             ` <cfd18e0f0812011131g2bbe2d6flb8cc89eaa7f96ad4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-01 19:42               ` H. Peter Anvin
     [not found]                 ` <49343E32.50707-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2008-12-01 20:05                   ` Michael Kerrisk
     [not found]                     ` <cfd18e0f0812011205w62f30725m53f4b16cea3272aa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-01 21:08                       ` Andries E. Brouwer [this message]
2008-12-01 21:35                         ` H. Peter Anvin
2008-12-01 22:39                   ` Karel Zak
     [not found]                     ` <20081201223913.GF2956-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2008-12-01 22:41                       ` H. Peter Anvin
     [not found]                         ` <4934682F.7050305-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2008-12-01 23:00                           ` Karel Zak
     [not found]                             ` <20081201230031.GA26838-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2008-12-01 23:03                               ` H. Peter Anvin
2008-12-01 23:19                               ` H. Peter Anvin

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=20081201210835.GA14009@ub \
    --to=andries.brouwer-rh8nl+sex9e@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=sukadev-r/Jw6+rmf7HQT0dZR+AlfA@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