remove compat_svr4

4 files changed, 7 insertions, 178 deletions

diff --git a/share/man/man4/options.4 b/share/man/man4/options.4
index 23b2176ba38..6cd647287f5 100644
--- a/share/man/man4/options.4
+++ b/share/man/man4/options.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: options.4,v 1.217 2011/07/03 22:40:06 tedu Exp $
+.\"	$OpenBSD: options.4,v 1.218 2011/07/04 22:59:43 tedu Exp $
 .\"	$NetBSD: options.4,v 1.21 1997/06/25 03:13:00 thorpej Exp $
 .\"
 .\" Copyright (c) 1998 Theo de Raadt
@@ -34,7 +34,7 @@
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\"
-.Dd $Mdocdate: July 3 2011 $
+.Dd $Mdocdate: July 4 2011 $
 .Dt OPTIONS 4
 .Os
 .Sh NAME
@@ -99,16 +99,6 @@ applications built for the same architecture.
 This option is supported on the i386 architecture.
 See
 .Xr compat_linux 8 .
-.It Cd option COMPAT_SVR4
-On those architectures that support it, this enables binary
-compatibility with
-.At V.4
-binaries built for the same architecture.
-This currently includes the sparc and i386.
-Possibly the most widely known operating system
-based on this binary architecture is Sun's Solaris 2.x.
-See
-.Xr compat_svr4 8 .
 .El
 .Sh DEBUGGING OPTIONS
 .Bl -ohang
diff --git a/share/man/man7/hier.7 b/share/man/man7/hier.7
index 4457625c41d..f2eb7d508dd 100644
--- a/share/man/man7/hier.7
+++ b/share/man/man7/hier.7
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: hier.7,v 1.94 2011/04/26 13:29:23 jmc Exp $
+.\"	$OpenBSD: hier.7,v 1.95 2011/07/04 22:59:43 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: April 26 2011 $
+.Dd $Mdocdate: July 4 2011 $
 .Dt HIER 7
 .Os
 .Sh NAME
@@ -82,9 +82,8 @@ emulation is in effect (see
 .Xr sysctl 8
 and the system compat pages:
 .Xr compat_aout 8 ,
-.Xr compat_linux 8 ,
 and
-.Xr compat_svr4 8 ) .
+.Xr compat_linux 8 .
 .It /etc/
 System configuration files and scripts.
 .Pp
diff --git a/share/man/man8/Makefile b/share/man/man8/Makefile
index 39e02d87611..e15b62fa46a 100644
--- a/share/man/man8/Makefile
+++ b/share/man/man8/Makefile
@@ -1,10 +1,9 @@
-#	$OpenBSD: Makefile,v 1.78 2011/04/29 07:08:27 jmc Exp $
+#	$OpenBSD: Makefile,v 1.79 2011/07/04 22:59:43 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_linux.8 \
-	compat_svr4.8 crash.8 daily.8 dhcp.8 \
+	compat_linux.8 crash.8 daily.8 dhcp.8 \
 	diskless.8 genassym.sh.8 intro.8 netstart.8 rc.8 \
 	rc.conf.8 rc.d.8 rc.shutdown.8 rc.subr.8 release.8 \
 	security.8 ssl.8 starttls.8 sticky.8 yp.8
diff --git a/share/man/man8/compat_svr4.8 b/share/man/man8/compat_svr4.8
deleted file mode 100644
index baf55186bc2..00000000000
--- a/share/man/man8/compat_svr4.8
+++ /dev/null
@@ -1,159 +0,0 @@
-.\"	$OpenBSD: compat_svr4.8,v 1.18 2009/11/19 07:23:53 jmc Exp $
-.\"	$NetBSD: compat_svr4.8,v 1.1 1996/07/06 17:14:50 christos Exp $
-.\"
-.\" Copyright (c) 1996 Christos Zoulas
-.\" 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 acknowledgment:
-.\"      This product includes software developed for the NetBSD Project
-.\"      by Christos Zoulas
-.\" 4. The name of the author may not 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.
-.\"
-.\"	Stolen from compat_linux.8,v 1.2 1995/10/16 20:17:59 fvdl
-.\"
-.Dd $Mdocdate: November 19 2009 $
-.Dt COMPAT_SVR4 8
-.Os
-.Sh NAME
-.Nm compat_svr4
-.Nd setup for running SVR4/iBCS2 binaries under emulation
-.Sh DESCRIPTION
-.Ox
-supports running SVR4/iBCS2 binaries.
-This code has been tested on i386 and sparc systems.
-Most programs should work, but not ones that use or depend on:
-.Pp
-.Bl -tag -width 123 -compact -offset indent
-.It kernel internal data structures
-.It the /proc filesystem
-.It the ticotsord loopback rpc mechanism (NIS uses this)
-.It sound and video interfaces
-.It threads (ttsession uses threads)
-.It the streams administrative driver
-.It "mapping of page zero to the executable for Dell SVR4 binaries"
-.El
-.Pp
-The SVR4 compatibility feature is active
-for kernels compiled with the
-.Nm COMPAT_SVR4
-option and kern.emul.svr4
-.Xr sysctl 8
-enabled.
-.Pp
-Most SVR4 programs are dynamically linked.
-This means that the shared libraries that the programs depend on
-and the runtime linker are also needed.
-Additionally, a "shadow root" directory for SVR4 binaries
-on the
-.Ox
-system will have to be created.
-This directory is named
-.Pa /emul/svr4 .
-Any file operations done by SVR4 programs run under
-.Ox
-will look in this directory first.
-So, if a SVR4 program opens, for example,
-.Pa /etc/passwd ,
-.Ox
-will
-first try to open
-.Pa /emul/svr4/etc/passwd ,
-and if that does not exist open the `real'
-.Pa /etc/passwd file .
-It is recommended that SVR4 packages that include configuration
-files, etc., be installed under
-.Pa /emul/svr4 ,
-to avoid naming conflicts with possible
-.Ox
-counterparts.
-Shared libraries should also be installed in the shadow tree.
-.Pp
-The simplest way to set up the system for SVR4 binaries is:
-.Bl -tag -width 123 -compact
-.It 1.
-Make the necessary directories:
-.Bd -literal -offset indent
-(me@openbsd) mkdir -p /emul/svr4/{dev,etc}
-(me@openbsd) mkdir -p /emul/svr4/usr/{bin,lib}
-(me@openbsd) mkdir -p /emul/svr4/usr/openwin/{bin,lib}
-.Ed
-.Pp
-.It 2.
-Copy files from an SVR4 system:
-.Bd -literal -offset indent
-(me@svr4) cd /usr/lib
-(me@svr4) tar -cf -\ . | \e
-     rsh openbsd 'cd /emul/svr4/usr/lib; tar -xpf -'
-.Ed
-.Pp
-If OpenWindows is going to be run:
-.Bd -literal -offset indent
-(me@svr4) cd /usr/openwin/lib
-(me@svr4) tar -cf -\ . | \e
-     rsh openbsd 'cd /emul/svr4/usr/openwin/lib; tar -xpf -'
-.Ed
-.Pp
-.It 3.
-Set up the configuration files and devices:
-.Bd -literal -offset indent
-(me@openbsd) cd /usr/src/etc/etc.svr4
-(me@openbsd) cp netconfig nsswitch.conf /emul/svr4/etc
-(me@openbsd) cp SVR4_MAKEDEV /emul/svr4/dev
-(me@openbsd) cd /emul/svr4/dev; sh SVR4_MAKEDEV all
-.Ed
-.El
-.Pp
-An alternative method is to mount a whole SVR4 partition in
-.Pa /emul/svr4
-and then override with other mounts
-.Pa /emul/svr4/etc
-and
-.Pa /emul/svr4/dev .
-.Pp
-Clearly, a complete SVR4
-.Pa /dev
-directory cannot be used as
-.Pa /emul/svr4/dev ,
-because other device nodes, such as
-.Pa /dev/null ,
-need to be
-.Ox
-device nodes.
-.Sh BUGS
-Many system calls are still not emulated.
-The streams emulation is incomplete (socketpair does not work yet).
-.Pp
-Most SVR4 executables can not handle directory offset cookies > 32
-bits.
-More recent ones, compiled for large file support (Solaris 2.6 and up) can.
-With older programs, the message
-"svr4_getdents: dir offset too large for emulated program"
-will appear when this happens.
-Currently, this can only happen on NFS mounted filesystems, mounted from
-servers that return offsets with information in the upper 32 bits.
-These errors should rarely happen, but can be avoided by mounting this
-filesystem with the
-.Fl 2
-option to
-.Xr mount_nfs 8 .