191 lines
6.1 KiB
Groff
191 lines
6.1 KiB
Groff
.\" $NetBSD: compat_svr4.8,v 1.16 2000/09/05 00:57:04 hubertf 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 April 19, 1999
|
|
.Dt COMPAT_SVR4 8
|
|
.Os
|
|
.Sh NAME
|
|
.Nm compat_svr4
|
|
.Nd setup procedure for running SVR4/iBCS2 binaries
|
|
.Sh DESCRIPTION
|
|
.Nx
|
|
supports running SVR4/iBCS2 binaries. This code has been tested on
|
|
i386 (with binaries from SCO OpenServer and XENIX), m68k (with binaries from
|
|
.Tn AMIX )
|
|
and sparc (with binaries from Solaris) systems. Most programs should work,
|
|
but not ones that use or depend on:
|
|
.sp
|
|
.Bl -tag -width 123 -compact -offset indent
|
|
.It kernel internal data structures
|
|
.br
|
|
.It the /proc filesystem
|
|
.br
|
|
.It the ticotsord loopback rpc mechanism (nis uses this)
|
|
.br
|
|
.It sound and video interfaces
|
|
.br
|
|
.It threads (ttsession uses threads)
|
|
.br
|
|
.It the streams administrative driver
|
|
.El
|
|
.sp
|
|
The SVR4 compatibility feature is active
|
|
for kernels compiled with the
|
|
.Dv COMPAT_SVR4
|
|
option enabled.
|
|
Since support for ELF executables is included
|
|
only if the kernel is compiled with the
|
|
.Dv EXEC_ELF32
|
|
or
|
|
.Dv EXEC_ELF64
|
|
options enabled, kernels which include
|
|
.Dv COMPAT_SVR4
|
|
should also typically include
|
|
.Dv EXEC_ELF32
|
|
(for 32-bit ELF support)
|
|
and/or
|
|
.Dv EXEC_ELF64
|
|
(for 64-bit ELF support).
|
|
.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"
|
|
directory for SVR4 binaries on your
|
|
.Nx
|
|
system. This directory
|
|
is named /emul/svr4. Any file operations done by SVR4 programs
|
|
run under
|
|
.Nx
|
|
will look in this directory first. So, if a SVR4
|
|
program opens, for example, /etc/passwd,
|
|
.Nx
|
|
will
|
|
first try to open /emul/svr4/etc/passwd, and if that does not exist
|
|
open the 'real' /etc/passwd file. It is recommended that you install
|
|
SVR4 packages that include configuration files, etc under /emul/svr4,
|
|
to avoid naming conflicts with possible
|
|
.Nx
|
|
counterparts. Shared
|
|
libraries should also be installed in the shadow tree.
|
|
.Pp
|
|
The simplest way to setup your system for SVR4 binaries is:
|
|
|
|
.Bl -tag -width 123 -compact
|
|
.It 1.
|
|
Make the necessary directories:
|
|
.Pp
|
|
.Bl -tag -width 123 -compact -offset indent
|
|
.It (me@netbsd) mkdir -p /emul/svr4/{dev,etc}
|
|
.br
|
|
.It (me@netbsd) mkdir -p /emul/svr4/usr/{bin,lib}
|
|
.br
|
|
.It (me@netbsd) mkdir -p /emul/svr4/usr/openwin/{bin,lib}
|
|
.br
|
|
.It (me@netbsd) mkdir -p /emul/svr4/usr/dt/{bin,lib}
|
|
.El
|
|
.Pp
|
|
.It 2.
|
|
Copy files from an svr4 system:
|
|
.Pp
|
|
.Bl -tag -width 123 -compact -offset indent
|
|
.It (me@svr4) cd /usr/lib
|
|
.br
|
|
.It (me@svr4) tar -cf -\ . | \e
|
|
.in +5
|
|
.It rsh netbsd 'cd /emul/svr4/usr/lib; tar -xpf -'
|
|
.in -5
|
|
.El
|
|
.Pp
|
|
If you are running openwindows:
|
|
.Pp
|
|
.Bl -tag -width 123 -compact -offset indent
|
|
.It (me@svr4) cd /usr/openwin/lib
|
|
.br
|
|
.It (me@svr4) tar -cf -\ . | \e
|
|
.in +5
|
|
.It rsh netbsd 'cd /emul/svr4/usr/openwin/lib; tar -xpf -'
|
|
.in -5
|
|
.It (me@svr4) cd /usr/dt/lib
|
|
.br
|
|
.It (me@svr4) tar -cf -\ . | \e
|
|
.in +5
|
|
.It rsh netbsd 'cd /emul/svr4/usr/dt/lib; tar -xpf -'
|
|
.in -5
|
|
.El
|
|
.Pp
|
|
.It 3.
|
|
Setup the configuration files and devices:
|
|
.Pp
|
|
.Bl -tag -width 123 -compact -offset indent
|
|
.It (me@netbsd) cd /usr/share/examples/emul/svr4/etc
|
|
.br
|
|
.It (me@netbsd) cp netconfig nsswitch.conf /emul/svr4/etc
|
|
.br
|
|
.It (me@netbsd) cp SVR4_MAKEDEV /emul/svr4/dev
|
|
.br
|
|
.It (me@netbsd) cd /emul/svr4/dev; sh SVR4_MAKEDEV all
|
|
.El
|
|
.Pp
|
|
As the major number allocated for emulation of SVR4 devices may vary between
|
|
.Nx
|
|
platforms, the SVR4_MAKEDEV script utilizes the
|
|
.Xr uname 1
|
|
command to determine the architecture the devices nodes are being created for;
|
|
this can be overridden by setting the
|
|
.Ev MACHINE
|
|
environment variable accordingly.
|
|
.El
|
|
.Pp
|
|
An alternative method is to mount a whole SVR4 partition in /emul/svr4
|
|
and then override with other mounts /emul/svr4/etc and /emul/svr4/dev.
|
|
.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, you will see the message "svr4_getdents:
|
|
dir offset too large for emulated program" 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
|
|
offset translation enabled. See the
|
|
.Fl X
|
|
option to
|
|
.Xr mount_nfs 8 .
|
|
The
|
|
.Fl 2
|
|
option to
|
|
.Xr mount_nfs 8
|
|
will also have the desired effect, but is less preferable.
|