Subject: Re: port-i386/4651: Man page describing booting NetBSD from Wind
To: None <tech-userlevel@NetBSD.ORG, woods@web.net>
From: Ty Sarna <tsarna@endicor.com>
List: tech-userlevel
Date: 12/12/1997 14:38:16
In article <m0xgPse-0009vDC@kuma.web.net> you write:
> > I think weshould actually be moving stuff out of /usr/share/doc into
> > manpages, but it's not an easy task.
> 
> That's a *bad* idea.  Manual pages are *references* (or in the odd case
> "cookbooks", such as adduser and diskless).  /usr/share/doc is where
> detailed background docs, implementation docs, user guides, admin
> guides, tutorials, etc. should go.  (I.e. it's volume two!)

My whole point is that's not where they should go -- the documentation
should be together.  That's also why I'm proposing new sections for that
kind of stuff to live in.  It's volume two, so what? If I buy a two book
set, I don't want the first one in 5x9 format and the other in 8.5x11 in
a different layout.  I'd expect the two volumes to look similar, and be
organized in a similar manner.  I'd also expect to find the two volumes
next to each other on the bookshelf.

> If you want more features to make /usr/share/doc easier to use, then
> perhaps something akin to GNU Info needs to be put in place for it,

I fail to see why using two separate mechanisms and locations for
documentation is superior.

> complete with indexing tools, hypertext browsers, etc.  This should be

If we want those features (and I do), we should have them for man pages
too! And it'd be a lot easier to implement that kind of thing if there
was a single mechanism for documentation.