From 6393ccd109d17c92e6427fba5730a05c7e4ac29c Mon Sep 17 00:00:00 2001 From: Ted Unangst Date: Tue, 29 Jun 2010 18:50:24 +0000 Subject: remove compat_ultrix docs --- share/man/man4/options.4 | 8 +-- share/man/man7/hier.7 | 7 ++- share/man/man8/Makefile | 4 +- share/man/man8/compat_ultrix.8 | 118 ----------------------------------------- 4 files changed, 6 insertions(+), 131 deletions(-) delete mode 100644 share/man/man8/compat_ultrix.8 (limited to 'share') diff --git a/share/man/man4/options.4 b/share/man/man4/options.4 index 05d30660196..09ae9211f26 100644 --- a/share/man/man4/options.4 +++ b/share/man/man4/options.4 @@ -1,4 +1,4 @@ -.\" $OpenBSD: options.4,v 1.196 2010/06/29 16:22:58 tedu Exp $ +.\" $OpenBSD: options.4,v 1.197 2010/06/29 18:50:23 tedu Exp $ .\" $NetBSD: options.4,v 1.21 1997/06/25 03:13:00 thorpej Exp $ .\" .\" Copyright (c) 1998 Theo de Raadt @@ -174,12 +174,6 @@ Possibly the most widely known operating system based on this binary architecture is Sun's Solaris 2.x. See .Xr compat_svr4 8 . -.It Cd option COMPAT_ULTRIX -On those architectures that support it, this enables binary -compatibility with Ultrix applications built for the same architecture. -This option is available on the vax architecture. -See -.Xr compat_ultrix 8 . .El .Sh DEBUGGING OPTIONS .Bl -ohang diff --git a/share/man/man7/hier.7 b/share/man/man7/hier.7 index 0f88e12ad9f..ca1ebb99206 100644 --- a/share/man/man7/hier.7 +++ b/share/man/man7/hier.7 @@ -1,4 +1,4 @@ -.\" $OpenBSD: hier.7,v 1.78 2010/06/20 08:32:03 jmc Exp $ +.\" $OpenBSD: hier.7,v 1.79 2010/06/29 18:50:23 tedu Exp $ .\" $NetBSD: hier.7,v 1.7 1994/11/30 19:07:10 jtc Exp $ .\" .\" Copyright (c) 1990, 1993 @@ -30,7 +30,7 @@ .\" .\" @(#)hier.7 8.1 (Berkeley) 6/5/93 .\" -.Dd $Mdocdate: June 20 2010 $ +.Dd $Mdocdate: June 29 2010 $ .Dt HIER 7 .Os .Sh NAME @@ -86,9 +86,8 @@ and the system compat pages: .Xr compat_linux 8 , .Xr compat_osf1 8 , .Xr compat_sunos 8 , -.Xr compat_svr4 8 , and -.Xr compat_ultrix 8 ) . +.Xr compat_svr4 8 ) . .It /etc/ System configuration files and scripts. .Pp diff --git a/share/man/man8/Makefile b/share/man/man8/Makefile index 76ce51a9c5f..a2c09d8aa25 100644 --- a/share/man/man8/Makefile +++ b/share/man/man8/Makefile @@ -1,11 +1,11 @@ -# $OpenBSD: Makefile,v 1.67 2010/01/24 15:38:49 matthieu Exp $ +# $OpenBSD: Makefile,v 1.68 2010/06/29 18:50:23 tedu Exp $ # $NetBSD: Makefile,v 1.13 1996/03/28 21:36:40 mark Exp $ # @(#)Makefile 8.1 (Berkeley) 6/5/93 MAN= afterboot.8 boot_config.8 compat_aout.8 compat_bsdos.8 \ compat_freebsd.8 compat_hpux.8 compat_ibcs2.8 \ compat_linux.8 compat_osf1.8 compat_sunos.8 \ - compat_svr4.8 compat_ultrix.8 crash.8 daily.8 dhcp.8 \ + compat_svr4.8 crash.8 daily.8 dhcp.8 \ diskless.8 genassym.sh.8 intro.8 netstart.8 rc.8 \ rc.conf.8 rc.shutdown.8 release.8 security.8 ssl.8 \ starttls.8 sticky.8 update.8 yp.8 diff --git a/share/man/man8/compat_ultrix.8 b/share/man/man8/compat_ultrix.8 deleted file mode 100644 index 0b251739572..00000000000 --- a/share/man/man8/compat_ultrix.8 +++ /dev/null @@ -1,118 +0,0 @@ -.\" $OpenBSD: compat_ultrix.8,v 1.17 2007/05/31 19:19:58 jmc 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 $Mdocdate: May 31 2007 $ -.Dt COMPAT_ULTRIX 8 -.Os -.Sh NAME -.Nm compat_ultrix -.Nd setup for running Ultrix binaries under emulation -.Sh DESCRIPTION -OpenBSD/mips and OpenBSD/vax architectures can run RISC ULTRIX and Vax -ULTRIX executables, respectively. -However, the user is responsible for -the legal issues of ensuring that they have a right to use any ULTRIX -binaries on their machine. -Emulation is controlled by the kern.emul.ultrix -.Xr sysctl 8 . -.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 compatibility. -However, Ultrix is based on a -.Bx 4.3 -alpha release. -Ultrix commands and libraries are often much older than their -.Ox -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: -.Bd -literal -offset indent -# mkdir -p /emul/ultrix/etc -# cd /emul/ultrix/etc -# egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf -# cp -p /usr/share/samples/emul/ultrix/etc/* ./ -.Ed -.Ss /etc/resolv.conf -The Ultrix resolver library only understands -.Sy domain -and -.Sy nameserver -lines in -.Xr resolv.conf 5 . -A copy of -.Pa /etc/resolv.conf -should be created containing only those commands and put in -.Pa /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. -.Ss /etc/svc.conf -Ultrix uses -.Pa /etc/svc.conf -to select an ordered search of YP, Hesiod, or local flat-file mappings. -Create an -.Pa /emul/ultrix/etc/svc.conf -file specifying either -local files or bind (DNS) lookups for all Ultrix name services. -.Sh SEE ALSO -.Xr resolv.conf 5 -.Sh BUGS -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 -.Ox -.Xr ypbind 8 -process. -The only workaround is to use -.Pa /etc/svc.conf -to disable YP(NIS). -.Pp -The ndbm hashed-password file used by Ultrix is incompatible with the -db hashed-password file used by -.Ox . -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. -- cgit v1.2.3