Module Name: src
Committed By: wiz
Date: Mon Nov 21 15:11:45 UTC 2011
Modified Files:
src/share/man/man8: compat_freebsd.8 compat_ibcs2.8 compat_sunos.8
compat_svr4.8 compat_ultrix.8
Log Message:
New sentence, new line.
To generate a diff of this commit:
cvs rdiff -u -r1.14 -r1.15 src/share/man/man8/compat_freebsd.8
cvs rdiff -u -r1.6 -r1.7 src/share/man/man8/compat_ibcs2.8
cvs rdiff -u -r1.19 -r1.20 src/share/man/man8/compat_sunos.8 \
src/share/man/man8/compat_ultrix.8
cvs rdiff -u -r1.25 -r1.26 src/share/man/man8/compat_svr4.8
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/share/man/man8/compat_freebsd.8
diff -u src/share/man/man8/compat_freebsd.8:1.14 src/share/man/man8/compat_freebsd.8:1.15
--- src/share/man/man8/compat_freebsd.8:1.14 Mon Nov 21 14:27:41 2011
+++ src/share/man/man8/compat_freebsd.8 Mon Nov 21 15:11:45 2011
@@ -1,4 +1,4 @@
-.\" $NetBSD: compat_freebsd.8,v 1.14 2011/11/21 14:27:41 njoly Exp $
+.\" $NetBSD: compat_freebsd.8,v 1.15 2011/11/21 15:11:45 wiz Exp $
.\" from: compat_linux.8,v 1.1 1995/03/05 23:30:36 fvdl Exp
.\"
.\" Copyright (c) 1995 Frank van der Linden
@@ -52,18 +52,19 @@ with the
.Dv COMPAT_FREEBSD
option enabled.
.Pp
-A lot of programs are dynamically linked. This means, that you will
-also need the
+A lot of programs are dynamically linked.
+This means, that you will also need the
.Fx
shared libraries that the program depends on, and the runtime
-linker. Also, you will need to create a
+linker.
+Also, you will need to create a
.Dq shadow root
directory for
.Fx
binaries on your
.Nx
-system. This directory
-is named
+system.
+This directory is named
.Pa /emul/freebsd .
Any file operations done by
.Fx
@@ -88,8 +89,8 @@ packages that include configuration file
.Pa /emul/freebsd ,
to avoid naming conflicts with possible
.Nx
-counterparts. Shared
-libraries should also be installed in the shadow tree.
+counterparts.
+Shared libraries should also be installed in the shadow tree.
.Pp
Generally, you will need to look for the shared libraries that
.Fx
@@ -97,7 +98,8 @@ binaries depend on only the first few ti
.Fx
program on your
.Nx
-system. After a while, you will have a sufficient set of
+system.
+After a while, you will have a sufficient set of
.Fx
shared libraries on your system to be able to run newly imported
.Fx
@@ -209,10 +211,11 @@ tree):
.It
You don't have access to a
.Fx
-system. In that case, you
-should get the extra files you need from various ftp sites.
+system.
+In that case, you should get the extra files you need from various ftp sites.
Information on where to look for the various files is appended
-below. For now, let's assume you know where to get the files.
+below.
+For now, let's assume you know where to get the files.
.Pp
Retrieve the following files (from _one_ ftp site to avoid
any version mismatches), and install them under
@@ -237,8 +240,8 @@ and
.Ic ldd
don't necessarily need to be under
.Pa /emul/freebsd ,
-you can install them elsewhere in the system too. Just make sure
-they don't conflict with their
+you can install them elsewhere in the system too.
+Just make sure they don't conflict with their
.Nx
counterparts.
A good idea would be to install them in
@@ -290,7 +293,8 @@ binaries which only need a shared libc.
You can test this by running the
.Fx
.Ic ldd
-on itself. Suppose that you have it installed as
+on itself.
+Suppose that you have it installed as
.Ic ldd-freebsd ,
it should produce something like:
.Bd -literal -offset indent
@@ -342,7 +346,8 @@ For example,
X server software needs
.Fx
.Pa /dev/ttyv0
-for ioctls. In this case, create a symbolic link from
+for ioctls.
+In this case, create a symbolic link from
.Pa /emul/freebsd/dev/ttyv0
to a
.Xr wscons 4
@@ -386,7 +391,8 @@ This distribution consists of a number o
Normally, they're controlled by an install program, but you can
retrieve files
.Dq by hand
-too. The way to look something up is to retrieve all the files in the
+too.
+The way to look something up is to retrieve all the files in the
distribution, and ``tar ztvf'' through them for the file you need.
Here is an example of a list of files that you might need.
.Bd -literal -offset indent
Index: src/share/man/man8/compat_ibcs2.8
diff -u src/share/man/man8/compat_ibcs2.8:1.6 src/share/man/man8/compat_ibcs2.8:1.7
--- src/share/man/man8/compat_ibcs2.8:1.6 Mon Nov 21 14:27:41 2011
+++ src/share/man/man8/compat_ibcs2.8 Mon Nov 21 15:11:45 2011
@@ -1,4 +1,4 @@
-.\" $NetBSD: compat_ibcs2.8,v 1.6 2011/11/21 14:27:41 njoly Exp $
+.\" $NetBSD: compat_ibcs2.8,v 1.7 2011/11/21 15:11:45 wiz Exp $
.\"
.\" Copyright (c) 1998 Scott Bartram
.\" Copyright (c) 1995 Frank van der Linden
@@ -71,15 +71,17 @@ virtual 8086 mode
The iBCS2 compatibility feature is active for kernels compiled with
the
.Dv COMPAT_IBCS2
-option enabled. If support for iBCS2 ELF executables is desired,
-the
+option enabled.
+If support for iBCS2 ELF executables is desired, the
.Dv EXEC_ELF32
option should be enabled in addition to
.Dv COMPAT_IBCS2 .
.Pp
Many COFF-format programs and most ELF-format programs are dynamically
-linked. This means that you will also need the shared libraries that
-the program depends on. Also, you will need to create a
+linked.
+This means that you will also need the shared libraries that
+the program depends on.
+Also, you will need to create a
.Dq shadow root
directory for iBCS2 binaries on your
.Nx
@@ -98,7 +100,8 @@ will first try to open
and if that does not exist open the
.Sq real
.Pa /etc/passwd
-file. It is recommended that you install iBCS2 packages
+file.
+It is recommended that you install iBCS2 packages
that include configuration files, etc. under
.Pa /emul/ibcs2 ,
to avoid naming conflicts with possible
@@ -125,7 +128,8 @@ installation steps).
.Bl -tag -width "COFF binaries"
.It COFF binaries
You can simply copy all of the available shared libraries since they
-are fairly small in size. The COFF shared libraries are typically
+are fairly small in size.
+The COFF shared libraries are typically
found in /shlib and can be obtained from the following sources:
.Bd -literal
SCO UNIX version 3.x (aka ODT)
@@ -158,7 +162,8 @@ following files on your system:
.Pp
.El
If you don't have access to a SCO system, you will need to get the
-extra files you need from a SCO distribution. As of January 1998, SCO
+extra files you need from a SCO distribution.
+As of January 1998, SCO
sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for
personal/non-commercial use for only the cost of shipping (about $20US).
The distribution comes on an ISO9660-format CDROM which can be
Index: src/share/man/man8/compat_sunos.8
diff -u src/share/man/man8/compat_sunos.8:1.19 src/share/man/man8/compat_sunos.8:1.20
--- src/share/man/man8/compat_sunos.8:1.19 Wed Oct 14 23:49:50 2009
+++ src/share/man/man8/compat_sunos.8 Mon Nov 21 15:11:45 2011
@@ -1,4 +1,4 @@
-.\" $NetBSD: compat_sunos.8,v 1.19 2009/10/14 23:49:50 joerg Exp $
+.\" $NetBSD: compat_sunos.8,v 1.20 2011/11/21 15:11:45 wiz Exp $
.\"
.\" Copyright (c) 1984 Theo de Raadt
.\" All rights reserved.
@@ -37,7 +37,8 @@ and some of the
.Nx Ns Tn /m68k
architectures can run
.Tn SunOS
-executables. Most executables will work.
+executables.
+Most executables will work.
.Pp
The exceptions include programs that use the
.Tn SunOS
@@ -115,9 +116,10 @@ Should such an offset occur, you will se
.Dq sunos_getdents: dir offset too large for emulated program .
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
+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 .
Index: src/share/man/man8/compat_ultrix.8
diff -u src/share/man/man8/compat_ultrix.8:1.19 src/share/man/man8/compat_ultrix.8:1.20
--- src/share/man/man8/compat_ultrix.8:1.19 Sun Mar 30 21:34:51 2003
+++ src/share/man/man8/compat_ultrix.8 Mon Nov 21 15:11:45 2011
@@ -1,4 +1,4 @@
-.\" $NetBSD: compat_ultrix.8,v 1.19 2003/03/30 21:34:51 wiz Exp $
+.\" $NetBSD: compat_ultrix.8,v 1.20 2011/11/21 15:11:45 wiz Exp $
.\"
.\" Copyright (c) 1997 Jonathan Stone
.\" All rights reserved.
@@ -41,11 +41,12 @@
and
.Nx Ns Tn /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.
+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
+Most executables will work.
+The exceptions include programs that use
proprietary, ULTRIX-specific features (LAT, CI support, DECnet
support) and various system calls,
.Fn ioctl Ns 's ,
@@ -55,10 +56,11 @@ buggy (e.g. ULTRIX
.Tn NIS ) .
.Pp
All ULTRIX executables are static, so no shared libraries are required
-for ULTRIX compatibility. However, ULTRIX is based on a
+for ULTRIX compatibility.
+However, ULTRIX is based on a
.Bx 4.3
-alpha release. ULTRIX commands and libraries are often much older
-than their
+alpha release.
+ULTRIX commands and libraries are often much older than their
.Nx
or even
.Tn SunOS 4.x
@@ -100,7 +102,8 @@ ULTRIX uses
to select an ordered search of
.Tn NIS ,
Hesiod,
-or local flat-file mappings. You should create an
+or local flat-file mappings.
+You should create an
.Pa /emul/ultrix/etc/svc.conf
specifying either local files or bind (DNS)
lookups for all ULTRIX name services.
@@ -109,14 +112,17 @@ lookups for all ULTRIX name services.
.Sh BUGS
RISC ULTRIX
.Tn NIS
-(YP) is known to not work. The ULTRIX
+(YP) is known to not work.
+The ULTRIX
.Tn NIS
-libraries have a consistent endian-ness bug. ULTRIX
+libraries have a consistent endian-ness bug.
+ULTRIX
.Tn NIS
client will not inter-operate with the
.Nx
.Xr ypbind 8
-process. The only workaround is to use
+process.
+The only workaround is to use
.Pa /etc/svc.conf
to disable
.Tn NIS
@@ -133,7 +139,8 @@ would be a good one, if ULTRIX
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
+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
Index: src/share/man/man8/compat_svr4.8
diff -u src/share/man/man8/compat_svr4.8:1.25 src/share/man/man8/compat_svr4.8:1.26
--- src/share/man/man8/compat_svr4.8:1.25 Wed Oct 21 01:07:46 2009
+++ src/share/man/man8/compat_svr4.8 Mon Nov 21 15:11:45 2011
@@ -1,4 +1,4 @@
-.\" $NetBSD: compat_svr4.8,v 1.25 2009/10/21 01:07:46 snj Exp $
+.\" $NetBSD: compat_svr4.8,v 1.26 2011/11/21 15:11:45 wiz Exp $
.\"
.\" Copyright (c) 1996 Christos Zoulas
.\" All rights reserved.
@@ -35,11 +35,12 @@
.Nd setup procedure for running 32-bit SVR4/iBCS2 binaries
.Sh DESCRIPTION
.Nx
-supports running SVR4/iBCS2 binaries. This code has been tested on
+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:
+and sparc (with binaries from Solaris) systems.
+Most programs should work, but not ones that use or depend on:
.sp
.Bl -item -compact -offset indent
.It
@@ -79,7 +80,8 @@ and/or
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
+with a 64-bit kernel.
+This requires
.Dv EXEC_ELF32
and
.Dv COMPAT_NETBSD32
@@ -104,19 +106,20 @@ Execution of 32-bit SVR4 binaries on a m
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
+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
.Dq shadow root
directory for SVR4 binaries on your
.Nx
-system. This directory
-is named
+system.
+This directory is named
.Pa /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,
+will look in this directory first.
+So, if a SVR4 program opens, for example,
.Pa /etc/passwd ,
.Nx
will
@@ -125,13 +128,14 @@ first try to open
and if that does not exist open the
.Sq real
.Pa /etc/passwd
-file. It is recommended that you install
+file.
+It is recommended that you install
SVR4 packages that include configuration files, etc under
.Pa /emul/svr4 ,
to avoid naming conflicts with possible
.Nx
-counterparts. Shared
-libraries should also be installed in the shadow tree.
+counterparts.
+Shared libraries should also be installed in the shadow tree.
.Pp
The simplest way to set up your system for SVR4 binaries is:
.Bl -enum -compact
@@ -235,18 +239,21 @@ and then override with other mounts
and
.Pa /emul/svr4/dev .
.Sh BUGS
-Many system calls are still not emulated. The streams emulation is
+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 \*[Gt] 32
-bits. More recent ones, compiled for large file support (Solaris 2.6
-and up) can. With older programs, you will see the message
-.Dq 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
+bits.
+More recent ones, compiled for large file support (Solaris 2.6 and up) can.
+With older programs, you will see the message
+.Dq 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 .
