[216] in SIPB bug reports

home help back first fref pref prev next nref lref last post

Re: SIPB man page organization

daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Mon Oct 10 16:31:05 1988

Date: Mon, 10 Oct 88 16:31:00 EDT
From: Theodore Ts'o <tytso@ATHENA.MIT.EDU>
To: <jik@ATHENA.MIT.EDU>
Cc: bug-sipb@ATHENA.MIT.EDU
In-Reply-To: Jonathan I. Kamens's message of Mon, 10 Oct 88 16:01:34 EDT,
Reply-To: tytso@athena.mit.edu
   From: <jik@ATHENA.MIT.EDU>
   Date: Mon, 10 Oct 88 16:01:34 EDT

   This is broken.  It makes it harder to keep the manual pages
   up-to-date, harder to find a man page when you're not sure it appears
   in the SIPB locker, and harder to make updates to software from
   off-site without screwing up the manual pages.

I would think that the current system is easier, since you only have to
look in one place: /usr/sipb/man/{man,cat}l, instead of eight different
subdirectories for each section.  Or are you complaining about the
number of files in /usr/sipb/man/{man,cat}l?

   Does anyone have any objections to my reorganizating the manual page
   tree into sections, and making as many of the man pages as possible
   links to the source directories instead of actual copies of the man
   page, which could get out of synch with the copies in the source
   directories?

Wait a sec.... aren't the sources in sipbsrc, which isn't necessarily
(read: hardly ever, by normal users) mounted at the same time as the
sipb filesystem?  Making the man pages links to the copies in the source
directories would require the sipbsrc be attached when you're trying to
read a man page.  This to me seems wrong.

						- Ted

home help back first fref pref prev next nref lref last post