Some of these already have man pages under another name. I'd suggest a
simple ".so man1/whatever.1" for these so that the existing page is used.
ash.static => ash (statically linked version, I'd imagine - no
difference in usage)
fsck.ext2 => e2fsck
insmod.static => insmod (statically linked version again I think)
mkfs.ext2 => mke2fs
quotaoff => quotaon
nxterm => xterm (well, pretty similar)
[ => test
bzip2recover => bzip2
cc => gcc
gmake => make
gneqn => eqn (I presume)
perl5.* => perl
wish* => wish
For example, man1/wishx.1 could contain:
.so man1/wish.1
which would cause the man page for "wish" to be displayed for "man wishx".
The following already have Texinfo information ("info topic") which could be
turned into a man page:
install-info
aclocal
autoconf (I think)
autoheader (I think)
automake (I think)
autoreconf (I think)
autoscan (I think) - for all these see the source packages.
gettext
gettextize
m4
makeinfo
msgcmp (probably)
msgcomm (probably)
msgfmt (probably)
msghack (probably)
msgmerge (probably)
msgunfmt (probably)
xgettext
For these, blame GNU for discontinuing man page support. There are probably
quite a few more.
Hope this helps.
- Andrew
On Wed, 20 Oct 1999, deb wrote:
> Hi all.
>
> It has recently come to my attention that there are a -large- number of
> Linux programs/commands that do not have man pages. As many of you know,
> man pages are the first place that most people look when they need help
> and documentation. In the most recent release of RH, for example, there
> are 744 such man pages that are missing. This, in my opinion, is a big
> problem.
