From owner-freebsd-hackers Mon Nov 27 16:13:21 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13294 for hackers-outgoing; Mon, 27 Nov 1995 16:13:21 -0800 Received: from multivac.orthanc.com (root@multivac.orthanc.com [204.244.20.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13277 for ; Mon, 27 Nov 1995 16:13:11 -0800 Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7/8.7) with SMTP id QAA23175; Mon, 27 Nov 1995 16:11:51 -0800 (PST) Message-Id: <199511280011.QAA23175@multivac.orthanc.com> X-Authentication-Warning: multivac.orthanc.com: Host lyndon@localhost didn't use HELO protocol From: Lyndon Nerenberg (VE7TCP) To: Terry Lambert cc: hackers@freebsd.org Subject: Re: Where is the documentation for ibcs2? In-reply-to: Your message of "Mon, 27 Nov 1995 16:47:30 MST." <199511272347.QAA19930@phaeton.artisoft.com> Date: Mon, 27 Nov 1995 16:11:49 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk Well, going by your argument the man page for cc(1) should also document the programming language and libraries, n'est ce pas? Should we also incorporate a copy of Stevens in tcp(4)? The man page should document the fact the iBCS2 support exists, give three short examples of how to enable the support (compile into kernel, invoke from sysconfig, load from command line), refer the reader to the non-existent handbook section describing all the ugly details of the implementation, and include a warning that the code is preliminary and shouldn't be used unless you're willing to do some digging into the source code. Call the manpage ibcs2(8) and create a link called sco(4) (or maybe sco(5)?). This makes the two obvious targets for apropos work, and let's people discover fairly easily that SCO support does exist, while making no bones about the fact that its use is not for the timid. --lyndon