Add documentation for COMPAT_SVR4_32.

This commit is contained in:
eeh 2001-06-27 16:41:00 +00:00
parent 46a9744df4
commit 5d3b545fcc
2 changed files with 26 additions and 2 deletions

View File

@ -1,4 +1,4 @@
# $NetBSD: Makefile,v 1.47 2001/06/13 15:05:38 simonb Exp $
# $NetBSD: Makefile,v 1.48 2001/06/27 16:41:00 eeh Exp $
# @(#)Makefile 8.1 (Berkeley) 6/5/93
MAN= compat_freebsd.8 compat_ibcs2.8 compat_linux.8 compat_netbsd32.8 \
@ -6,6 +6,7 @@ MAN= compat_freebsd.8 compat_ibcs2.8 compat_linux.8 compat_netbsd32.8 \
compat_ultrix.8 diskless.8 genassym.sh.8 intro.8 rc.8 sticky.8 yp.8
MLINKS+=compat_svr4.8 compat_sco.8
MLINKS+=compat_svr4.8 compat_solaris.8
MLINKS+=compat_svr4.8 compat_svr4_32.8
MLINKS+=compat_svr4.8 compat_xenix.8
MLINKS+=compat_pecoff.8 compat_win32.8
MLINKS+=compat_pecoff.8 peace.8

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_svr4.8,v 1.17 2001/05/16 14:27:58 christos Exp $
.\" $NetBSD: compat_svr4.8,v 1.18 2001/06/27 16:41:00 eeh Exp $
.\"
.\" Copyright (c) 1996 Christos Zoulas
.\" All rights reserved.
@ -37,6 +37,8 @@
.Sh NAME
.Nm compat_svr4
.Nd setup procedure for running SVR4/iBCS2 binaries
.Nm compat_svr4_32
.Nd setup procedure for running 32-bit SVR4/iBCS2 binaries
.Sh DESCRIPTION
.Nx
supports running SVR4/iBCS2 binaries. This code has been tested on
@ -77,6 +79,27 @@ and/or
.Dv EXEC_ELF64
(for 64-bit ELF support).
.Pp
Another compatibility feature is
.Dv COMPAT_SVR4_32,
which allows the execution of 32-bit SVR4 binaries on a machine
with a 64-bit kernel. This requires
.Dv EXEC_ELF32
and
.Dv COMPAT_NETBSD32
options as well as
.Dv COMPAT_SVR4.
It is configured the same way as
.Dv COMPAT_SVR4
but uses the /emul/svr4_32 directory instead of /emul/svr4. But
typically, /emul/svr4_32 can be made to point to /emul/svr4 if the
operating system donating the libraries has support for both 32-bit
and 64-bit binaries.
.Pp
Execution of 32-bit SVR4 binaries on a machine with a 32-bit kernel uses
.Dv COMPAT_SVR4,
not
.Dv COMPAT_SVR4_32.
.Pp
Most SVR4 programs are dynamically linked. This means that you will
also need the shared libraries that the program depends on and the
runtime linker. Also, you will need to create a "shadow root"