Bodo Moeller wrote:
>
> On Tue, Mar 14, 2000 at 12:47:54AM +0100, Richard Levitte - VMS Whacker wrote:
>
> >> On Solaris, section 1s ("SunOS Specific Commands") contains
> >> make, and section 3s is about "Standard I/O functions".
> >> There may be additional meanings on other systems, of
> >> course.
>
> > In that case, 1ssl, 3ssl, 5ssl and 7ssl to make it separate and quite
> > compatible?
>
> >> On both systems where I tried it (Debian and Solaris), you
> >> cannot have files foo.1s and foo.1 in the same directory in
> >> the same manual pages directory tree. (Well, you can have
> >> them in the same directory, but "man -a foo" will find only
> >> one of the files.) The directory should be called man1s to
> >> solve this conflict. (Such directory names are standard on
> >> Solaris; they are not standard on Debian, but they work
> >> there too.)
>
> > In that case, man1ssl and so on?
>
> I guess this should work. (Unless some other SSL toolkit uses
> the same scheme ... Also, OpenSSL isn't only about SSL --
> but "os" surely isn't a particularly good acronym.)
On Linux, 'man 1ssl passwd' finds x/man1ssl/passwd.1ssl
as long as x is on $MANPATH (or default), while simply
storing passwd.1ssl under /usr/man/man1 will silently
display the wrong passwd.1 page. I guess that's a bug in
man (man-1.5g-6.src.rpm, Tue 14 Sep 1999. RH 6.1 alpha).
FreeBSD comes with some /usr/share/man1/man1aout/*1aout files.
On Solaris the command is 'man -s1ssl passwd', I guess.
I'd say having an ssl extension on both directory and filename
wouldn't harm, even when keeping them under $SSLDIR/man/.
VMS, HP/UX, AIX, IRIX, TrueCompaq ??
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
