lowercase manpage names (.Nm); fixes PR 3218.

also cleaned up some .Nm usage and other problems.
This commit is contained in:
mikel 1997-02-27 08:05:36 +00:00
parent 275506db58
commit 1009df021a
4 changed files with 34 additions and 34 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_freebsd.8,v 1.1 1996/08/09 18:03:23 explorer Exp $
.\" $NetBSD: compat_freebsd.8,v 1.2 1997/02/27 08:05:36 mikel Exp $
.\" from: compat_linux.8,v 1.1 1995/03/05 23:30:36 fvdl Exp
.\"
.\" Copyright (c) 1995 Frank van der Linden
@ -34,7 +34,7 @@
.Dt COMPAT_FREEBSD 8
.Os BSD 4
.Sh NAME
.Nm COMPAT_FREEBSD
.Nm compat_freebsd
.Nd setup procedure for running FreeBSD binaries
.Sh DESCRIPTION
NetBSD supports running FreeBSD binaries. Most binaries should work,
@ -42,9 +42,9 @@ except programs that use FreeBSD-specific features. These include
i386-specific calls, such as syscons utilities, and audio devices.
The FreeBSD compatibility feature is active for kernels compiled
with the
.Nm COMPAT_FREEBSD
.Dv COMPAT_FREEBSD
option enabled.
.Pp
A lot of programs are dynamically linked. This means, that you will
also need the FreeBSD shared libraries that the program depends on, and
the runtime linker. Also, you will need to create a "shadow root"
@ -219,13 +219,13 @@ recent version.
.El
.Ss Finding the necessary files.
.Nm Note:
the information below is valid as of the \time this
document was written (Jun, 1995), but certain details
.Em Note:
the information below is valid as of the time this
document was written (June, 1995), but certain details
such as names of ftp sites, directories and distribution names
may have changed by the time you read this.
.Pp
FreeBSD distribution is
The FreeBSD distribution is
available on a lot of ftp sites. Sometimes the files are unpacked,
and you can get the individual files you need, but mostly they
are stored in distribution sets, usually consisting of subdirectories

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_linux.8,v 1.4 1996/10/15 11:41:09 fvdl Exp $
.\" $NetBSD: compat_linux.8,v 1.5 1997/02/27 08:05:38 mikel Exp $
.\"
.\" Copyright (c) 1995 Frank van der Linden
.\" All rights reserved.
@ -33,7 +33,7 @@
.Dt COMPAT_LINUX 8
.Os BSD 4
.Sh NAME
.Nm COMPAT_LINUX
.Nm compat_linux
.Nd setup procedure for running Linux binaries
.Sh DESCRIPTION
NetBSD supports running Linux binaries. This only applies to i386 systems
@ -46,20 +46,20 @@ binaries (they will probably run, but not produce any sound).
The Linux compatibility feature is active
for kernels compiled with the
.Nm COMPAT_LINUX
.Dv COMPAT_LINUX
option enabled.
If support for Linux a.out executables is desired, the
.Nm EXEC_AOUT
.Dv EXEC_AOUT
option should be enabled in addition to
.Nm COMPAT_LINUX .
.Dv COMPAT_LINUX .
Similarly, if support for Linux 32-bit and/or 64-bit ELF executables
is desired, the
.Nm EXEC_ELF32
.Dv EXEC_ELF32
and/or
.Nm EXEC_ELF64
.Dv EXEC_ELF64
options (respectively) should be enabled in addition to
.Nm COMPAT_LINUX .
.Dv COMPAT_LINUX .
.Pp
A lot of programs are dynamically linked. This means, that you will
also need the Linux shared libraries that the program depends on, and
the runtime linker. Also, you will need to create a "shadow root"
@ -149,7 +149,7 @@ you with:
.fi
.Pp
Please note that the symbolic link mechanism is
.Nm only
.Em only
needed for Linux binaries, the NetBSD runtime linker takes care of
looking for matching major revision numbers itself, you
don't need to worry about that.
@ -243,8 +243,8 @@ such as YP and DNS. You must create or get a valid copy of this file
and put it in /emul/linux/etc.
.Ss Finding the necessary files.
.Nm Note:
the information below is valid as of the \time this
.Em Note:
the information below is valid as of the time this
document was written (March, 1995), but certain details
such as names of ftp sites, directories and distribution names
may have changed by the time you read this.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_sunos.8,v 1.6 1995/06/11 23:05:17 pk Exp $
.\" $NetBSD: compat_sunos.8,v 1.7 1997/02/27 08:05:39 mikel Exp $
.\"
.\" Copyright (c) 1984 Theo de Raadt
.\" All rights reserved.
@ -34,7 +34,7 @@
.Dt COMPAT_SUNOS 8
.Os BSD 4
.Sh NAME
.Nm COMPAT_SUNOS
.Nm compat_sunos
.Nd setup procedure for m68k and sparc architectures
.Sh DESCRIPTION
NetBSD/sparc and some of the NetBSD/m68k architectures can run

View File

@ -1,4 +1,4 @@
.\" $NetBSD: compat_svr4.8,v 1.3 1996/10/02 05:23:03 cgd Exp $
.\" $NetBSD: compat_svr4.8,v 1.4 1997/02/27 08:05:40 mikel Exp $
.\"
.\" Copyright (c) 1996 Christos Zoulas
.\" All rights reserved.
@ -35,7 +35,7 @@
.Dt COMPAT_SVR4 8
.Os BSD 4
.Sh NAME
.Nm COMPAT_SVR4
.Nm compat_svr4
.Nd setup procedure for running SVR4/iBCS2 binaries
.Sh DESCRIPTION
NetBSD supports running SVR4/iBCS2 binaries. This code has been tested on
@ -60,22 +60,22 @@ or depend on:
.sp
The SVR4 compatibility feature is active
for kernels compiled with the
.Nm COMPAT_SVR4
.Dv COMPAT_SVR4
option enabled.
Since support for ELF executables is included
only if the kernel is compiled with the
.Nm EXEC_ELF32
.Dv EXEC_ELF32
or
.Nm EXEC_ELF64
.Dv EXEC_ELF64
options enabled, kernels which include
.Nm COMPAT_SVR4
.Dv COMPAT_SVR4
should also typically include
.Nm EXEC_ELF32
.Dv EXEC_ELF32
(for 32-bit ELF support)
and/or
.Nm EXEC_ELF64
.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"
@ -89,7 +89,7 @@ SVR4 packages that include configuration files, etc under /emul/svr4,
to avoid naming conflicts with possible NetBSD counterparts. Shared
libraries should also be installed in the shadow tree.
.Pp
The simplest way to setup your system for SVR4 biraries is:
The simplest way to setup your system for SVR4 binaries is:
.Bl -tag -width 123 -compact
.It 1.
@ -140,8 +140,8 @@ Setup the configuration files and devices:
.El
.El
.Pp
An alternative method is to mount a whole svr4 partition in /emul/svr4
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.)
incomplete (socketpair does not work yet).