From owner-freebsd-hackers  Mon Nov 27 17:31:15 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id RAA18594
          for hackers-outgoing; Mon, 27 Nov 1995 17:31:15 -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 RAA18588
          for <hackers@freebsd.org>; Mon, 27 Nov 1995 17:31:09 -0800
Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7/8.7) with SMTP id RAA23749 for <hackers@freebsd.org>; Mon, 27 Nov 1995 17:31:04 -0800 (PST)
Message-Id: <199511280131.RAA23749@multivac.orthanc.com>
X-Authentication-Warning: multivac.orthanc.com: Host lyndon@localhost didn't use HELO protocol
From: Lyndon Nerenberg VE7TCP <lyndon@orthanc.com>
To: hackers@freebsd.org
Subject: ibcs2(8)
X-Attribution: VE7TCP
Date: Mon, 27 Nov 1995 17:31:01 -0800
Sender: owner-hackers@freebsd.org
Precedence: bulk

What's wrong with something like this? It documents the fact that
iBCS2 support exists, and that it's not for the timid (yet).

.Dd November 27, 1995
.Dt IBCS2 8
.Os FreeBSD-Experimental
.Sh NAME
.Nm ibcs2
.Nd load iBCS2 runtime support for SCO and ISC binaries
.Sh SYNOPSIS
.Nm ibcs2
.Sh DESCRIPTION
The
.Nm
utility loads kernel runtime support for iBCS2 compliant programs.
This runtime support is limited to emulation of the iBCS2
system call interface, and is far from complete. COFF binaries
and shared libraries are supported, however no shared libraries
are provided with the FreeBSD distribution.
.Sh FILES
.Bl -tag -width /lkm/ibcs2_coff.o -compact
.It Pa /lkm/ibcs2_mod.o
.It Pa /lkm/ibcs2_coff.o
iBCS2 loadable kernel modules
.Sh "SEE ALSO"
.Pa /sys/i386/ibcs2/README.iBCS2 ,
.Xr modload 8 ,
.Xr lkm 4
.Sh BUGS
The emulation is very incomplete.
.Pp
Running dynamically linked binaries requires access to an existing
SCO system from which you can grab the shared libraries.
.Pp
You can't really use this without reading the source code.