add; jonathan

2 files changed, 109 insertions, 2 deletions

diff --git a/share/man/man8/Makefile b/share/man/man8/Makefile
index 262f57d6357..dae86c643cd 100644
--- a/share/man/man8/Makefile
+++ b/share/man/man8/Makefile
@@ -1,9 +1,9 @@
-#	$OpenBSD: Makefile,v 1.10 1997/03/05 09:13:17 niklas Exp $
+#	$OpenBSD: Makefile,v 1.11 1997/06/11 01:14:13 deraadt Exp $
 #	$NetBSD: Makefile,v 1.13 1996/03/28 21:36:40 mark Exp $
 #	@(#)Makefile	8.1 (Berkeley) 6/5/93
 
 MAN=	compat_freebsd.8 compat_linux.8 compat_sunos.8 \
-	compat_svr4.8 diskless.8 intro.8 rc.8 \
+	compat_svr4.8 compat_ultrix.8 diskless.8 intro.8 rc.8 \
 	sticky.8 update.8 yp.8 boot_config.8
 SUBDIR=	man8.amiga man8.arm32 man8.atari man8.hp300 man8.i386 man8.mac68k \
 	man8.sparc man8.sun3 man8.vax
diff --git a/share/man/man8/compat_ultrix.8 b/share/man/man8/compat_ultrix.8
new file mode 100644
index 00000000000..1b32815808f
--- /dev/null
+++ b/share/man/man8/compat_ultrix.8
@@ -0,0 +1,107 @@
+.\"	$OpenBSD: compat_ultrix.8,v 1.1 1997/06/11 01:14:13 deraadt Exp $
+.\"
+.\" Copyright (c) 1997 Jonathan Stone
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by Jonathan Stone.
+.\" 4. Neither the name of the author nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.Dd June 7, 1997
+.Dt COMPAT_ULTRIX 8
+.Os OpenBSD 1.3
+.Sh NAME
+.Nm compat_ultrix
+.Nd setup procedure for Ultrix compatibility on mips and vax architectures
+.Sh DESCRIPTION
+
+OpenBSD/mips and OpenBSD/vax architectures can run Risc ULTRIX and Vax
+ULTRIX executables, respectively.  However, you have to worry about
+the legal issues of ensuring that you have a right to use any ULTRIX
+binaries on your machine.
+.Pp
+Most executables will work.  The exceptions include programs that use
+proprietary, Ultrix-specific features (LAT, CI support, DECnet
+support) and various system calls, ioctl()'s, or Ultrix kernel
+semantics that are difficult to emulate (e.g., Ultrix packetfilter) or
+buggy (e.g., Ultrix YP). 
+.Pp
+All Ultrix executables are static, so no shared libraries are required
+for Ultrix compatiblity. However, Ultrix is based on a 4.3BSD alpha
+release.  Ultrix commands and libraries are often much older than
+their OpenBSD or even SunOS 4.x equivalents, and may require incompatible
+configuration files.
+.Sh SYSTEM CONFIGURATION FILES
+Set up resolv.conf and svc.conf as below:
+.Pp
+.Bl -tag -width 123 -compact -offset indent
+.It # mkdir -p /emul/ultrix/etc
+.br
+.It # cd /emul/ultrix/etc
+.br
+.It # egrep 'domain|nameserver' /etc/resolv.conf  > ./resolv.conf
+.br
+.It # cp -p /usr/share/samples/emul/ultrix/etc/*	./
+.El
+.Pp
+.Ss /etc/resolv.conf
+The Ultrix resolver library only understands
+.Sy domain
+and
+.Sy nameserver
+lines in
+.Xr  /etc/resolv.conf 5 .
+You should create a copy of /etc/resolv.conf containing only those
+commands and put it in /emul/ultrix/etc/resolv.conf.  Note that the
+domain search order used by Ultrix executables may not be the same as
+native binaries; there is no good way around this.
+.Pp
+.Ss /etc/svc.conf
+Ultrix uses /etc/svc.conf to select an ordered search of YP, Hesiod,
+or local flat-file mappings.  You should create an
+/emul/ultrix/etc/svc.conf specifying either local files or bind (DNS)
+lookups for all Ultrix name services.
+.Sh BUGS
+.Pp
+RISC Ultrix YP(NIS) is known to not work.  The Ultrix YP libraries have
+a consistent endian-ness bug. Ultrix YP client will not inter-operate
+with the OpenBSD 
+.Xr ypbind 8
+process.  The only workaround is to use
+/etc/svc.conf to disable YP(NIS).
+.Pp
+The ndbm hashed-password file used by Ultrix are incompatible with the
+db hashed-password file used by OpenBSD. There is no good solution for
+this. (YP would be a good one, if Ultrix YP worked.)
+.Pp 
+The API used by Xservers to talk to the kernel is currently compatible
+with Ultrix 4.1.  An implementation of the Ultrix 4.2 Xws interface
+(used by X11R6) is in progress.
+.Pp
+A complete list of things which fail to work in Ultrix compatibility
+mode should be added here.
+.Sh SEE ALSO
+.Xr resolv.conf 5 .