23 files changed, 354 insertions, 289 deletions
diff --git a/share/man/man8/afterboot.8 b/share/man/man8/afterboot.8
index de85cbf825d..5829150c004 100644
--- a/share/man/man8/afterboot.8
+++ b/share/man/man8/afterboot.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: afterboot.8,v 1.63 2001/10/04 16:56:52 mpech Exp $
+.\"	$OpenBSD: afterboot.8,v 1.64 2001/10/05 14:45:54 mpech Exp $
 .Dd October 20, 1997
 .Dt AFTERBOOT 8
 \!\" Originally created by Marshall M. Midden -- 1997-10-20, m4@umn.edu
@@ -389,9 +389,9 @@ Note that the
 .Pa /etc/motd
 file is modified by
 .Pa /etc/rc
-whenever the system is booted. To keep any custom message intact, ensure
-that you leave two blank lines at the top, or your message will be
-overwritten.
+whenever the system is booted.
+To keep any custom message intact, ensure that you leave two blank lines
+at the top, or your message will be overwritten.
 .Ss Add new users
 Add users.
 There is an
@@ -510,11 +510,12 @@ To cause sendmail to accept network connections, modify the
 variable in
 .Pa /etc/rc.conf
 in accordance with the comments therein.
-Note that sendmail now also listens on port 587 by default.  This
-is to implement the RFC2476 message submission protocol.  You may
-disable this via the
+Note that sendmail now also listens on port 587 by default.
+This is to implement the RFC2476 message submission protocol.
+You may disable this via the
 .Dq no_default_msa
-option in your sendmail .mc file.  See
+option in your sendmail .mc file.
+See
 .Pa /usr/share/sendmail/README
 for more information.
 .Ss DHCP server
@@ -582,8 +583,8 @@ filling up disk space from normal running processes and database updates.
 (You probably do not need to understand them.)
 .Pp
 The /altroot filesystem can optionally be used to provide a backup of the
-root filesystem on a daily basis.  To take advantage of this, you must
-have an entry in
+root filesystem on a daily basis.
+To take advantage of this, you must have an entry in
 .Pa /etc/fstab
 with
 .Dq xx
diff --git a/share/man/man8/boot_config.8 b/share/man/man8/boot_config.8
index 28f9efba581..80c11d91576 100644
--- a/share/man/man8/boot_config.8
+++ b/share/man/man8/boot_config.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_config.8,v 1.16 2001/08/17 11:13:58 mpech Exp $
+.\"	$OpenBSD: boot_config.8,v 1.17 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1996 Mats O Jansson
 .\" All rights reserved.
@@ -121,10 +121,11 @@ driver.
 UKC>
 .Ed
 .Pp
-ne1 seems to match the configuration except it uses IRQ 5 instead of IRQ 10. So
-the irq on ne1 should be changed via the
+ne1 seems to match the configuration except it uses IRQ 5 instead of IRQ 10.
+So the irq on ne1 should be changed via the
 .Fa change
-command. The device can be specified by either name or number.
+command.
+The device can be specified by either name or number.
 .Pp
 .Bd -literal
 .No UKC> Ic change ne1
@@ -146,8 +147,8 @@ UKC>
 Another case is a mistakenly detected non-existing device instead of another
 device at the probed location.
 One known case is the Mitsumi
-CD-ROM in OpenBSD/i386. The simplest thing to solve that problem is to
-disable mcd0.
+CD-ROM in OpenBSD/i386.
+The simplest thing to solve that problem is to disable mcd0.
 .Pp
 .Bd -literal
 .No UKC> Ic find mcd0
@@ -178,7 +179,8 @@ UKC>
 .Ed
 .Pp
 It is possible to add new devices, but only devices that were linked into the
-kernel. If a new device is added, following devices will be renumbered.
+kernel.
+If a new device is added, following devices will be renumbered.
 .Pp
 .Bd -literal
 .No UKC> Ic find ep
diff --git a/share/man/man8/compat_bsdos.8 b/share/man/man8/compat_bsdos.8
index 62503c8a049..1e19b26357a 100644
--- a/share/man/man8/compat_bsdos.8
+++ b/share/man/man8/compat_bsdos.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_bsdos.8,v 1.4 2001/08/17 11:13:58 mpech Exp $
+.\"	$OpenBSD: compat_bsdos.8,v 1.5 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1997, Jason Downs.  All rights reserved.
 .\"
@@ -53,7 +53,8 @@ follows the standard
 .Dq emul
 filesystem scheme, using
 .Pa /emul/bsdos
-as the prefix.  This means that all BSDI executables first look in
+as the prefix.
+This means that all BSDI executables first look in
 .Pa /emul/bsdos
 whenever opening a file; configuration information, shared library images,
 etc., for BSDI binaries should all be installed under the emulation
@@ -65,13 +66,14 @@ Although many commercial BSDI binaries are
 compiled/linked with the BSDI
 .\" no .Xr here because we don't have junk like shlicc.
 .Nm shlicc
-program require the appropriate shared library images.  These may be
-found in the
+program require the appropriate shared library images.
+These may be found in the
 .Pa /shlib
 directory on a BSDI system, and must be copied to
 .Pa /emul/bsdos/shlib
-in order for such binaries to work.  The user is responsible for having
-the appropriate BSDI licenses in order to use the shared library images.
+in order for such binaries to work.
+The user is responsible for having the appropriate BSDI licenses in order
+to use the shared library images.
 .Sh BUGS
 If BSDI ever manages to port their system to more architectures or switch
 to real dynamically linked libraries these instructions may have to change.
diff --git a/share/man/man8/compat_freebsd.8 b/share/man/man8/compat_freebsd.8
index 3dd260d8d29..4e308cc49e0 100644
--- a/share/man/man8/compat_freebsd.8
+++ b/share/man/man8/compat_freebsd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_freebsd.8,v 1.8 2001/08/17 11:13:58 mpech Exp $
+.\"	$OpenBSD: compat_freebsd.8,v 1.9 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: compat_linux.8,v 1.1 1995/03/05 23:30:36 fvdl Exp $
 .\"
 .\" Copyright (c) 1995 Frank van der Linden
@@ -55,8 +55,8 @@ with the
 .Nm 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 "shadow root" directory for
@@ -115,7 +115,8 @@ Install the port named
 .Nm freebsd_lib
 in the
 .Nm emulators
-category.  The
+category.
+The
 .Nm freebsd_lib
 port contains the shared libraries, binaries, and other related files
 necessary to run
@@ -151,8 +152,8 @@ system you have access to, and check which shared libraries it needs by running
 .El
 .Pp
 You would need go get all the files from the last column, and
-put them under /emul/freebsd. This means you eventually have
-these files on your
+put them under /emul/freebsd.
+This means you eventually have these files on your
 .Ox
 system:
 .Pp
@@ -171,7 +172,8 @@ column of the 'ldd' output, you won't need to copy the file named in the
 last column to your system, the one you already have should work.
 It is advisable to copy the shared library anyway if it is a newer version,
 though.
-You can remove the old one. So, if you have these libraries on your system:
+You can remove the old one.
+So, if you have these libraries on your system:
 .Pp
 .nf
 /emul/freebsd/usr/lib/libc.so.2.0
@@ -298,7 +300,8 @@ of shared libraries that the program depends on, in the
 form -l<majorname> => <fullname>.
 .Pp
 If it prints "not found" instead of <fullname> it means that
-you need an extra library. Which library this is, is shown
+you need an extra library.
+Which library this is, is shown
 in <majorname>, which will be of the form XXXX.<N>
 You will need to find a libXXXX.so.<N>.<mm> on a
 .Fx
@@ -320,8 +323,8 @@ 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
-with gzipped tar files in them. The primary ftp sites for the
-distributions are:
+with gzipped tar files in them.
+The primary ftp sites for the distributions are:
 .Pp
 .nf
 ftp.freebsd.org:/pub/FreeBSD
@@ -335,9 +338,11 @@ ftp.freebsd.org:/pub/FreeBSD/MIRROR.SITES
 .Pp
 This distribution consists of a number of tar-ed and gzipped files,
 Normally, they're controlled by an install program, but you can
-retrieve files "by hand" too. The way to look something up is to retrieve all
+retrieve files "by hand" 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.
+you need.
+Here is an example of a list of files that you might need.
 .Pp
 .Bd -unfilled -offset indent
 Needed                 Files
diff --git a/share/man/man8/compat_ibcs2.8 b/share/man/man8/compat_ibcs2.8
index 29af1686ff8..519b9ce28ad 100644
--- a/share/man/man8/compat_ibcs2.8
+++ b/share/man/man8/compat_ibcs2.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_ibcs2.8,v 1.7 2001/08/17 11:13:58 mpech Exp $
+.\"	$OpenBSD: compat_ibcs2.8,v 1.8 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1998 Scott Bartram
 .\" Copyright (c) 1995 Frank van der Linden
@@ -41,18 +41,20 @@
 .Sh DESCRIPTION
 .Ox
 supports running Intel Binary Compatibility Standard 2 (iBCS2)
-binaries.  This only applies to i386 systems for now.  Binaries
-are supported from SCO UNIX and other systems derived from UNIX
-System V Release 3. iBCS2 support is only well tested using SCO
-binaries. XENIX binaries are also supported although not as well
-tested.  SVR4 binaries are supported by the
+binaries.
+This only applies to i386 systems for now.
+Binaries are supported from SCO UNIX and other systems derived from UNIX
+System V Release 3.
+iBCS2 support is only well tested using SCO binaries.
+XENIX binaries are also supported although not as well tested.
+SVR4 binaries are supported by the
 .Dv COMPAT_SVR4
 option.
 .Pp
-iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries
-from SCO OpenServer (version 5.x) are the only ELF binaries that have
-been tested.  Most programs should work, but not ones that use or
-depend on:
+iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats.
+Binaries from SCO OpenServer (version 5.x) are the only ELF binaries
+that have been tested.
+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
@@ -67,24 +69,27 @@ depend on:
 The iBCS2 compatibility feature is active for kernels compiled with
 the
 .Dv COMPAT_IBCS2
-option enabled.  If support for iBCS2 ELF executables is desired,
+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 "shadow root"
-directory for iBCS2 binaries on your
+linked.
+This means that you will also need the shared libraries that the program
+depends on.
+Also, you will need to create a "shadow root" directory for iBCS2 binaries
+on your
 .Ox
 system.
 This directory is named /emul/ibcs2.
 Any file operations done by iBCS2 programs run
 under
 .Ox
-will look in this directory first. So, if an iBCS2
-program opens, for example, /etc/passwd,
+will look in this directory first.
+So, if an iBCS2 program opens, for example, /etc/passwd,
 .Ox
 will first try to open /emul/ibcs2/etc/passwd, and if that does not
 exist open the 'real' /etc/passwd file.
@@ -106,17 +111,19 @@ any extra work.
 
 .Ss Setting up shared libraries
 How to get to know which shared libraries iBCS2 binaries need, and
-where to get them? Depending on the file type of the executable, there
-are different possibilities (when following these instructions: you
-will need to be root on your
+where to get them?
+Depending on the file type of the executable, there are different
+possibilities (when following these instructions: you will need to be
+root on your
 .Ox
 system to do the necessary installation steps).
-
+.Pp
 .Bl -tag -width 123 -compact
 .It 1. 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
-found in /shlib and can be obtained from the following sources:
+are fairly small in size.
+The COFF shared libraries are typically found in /shlib and can be
+obtained from the following sources:
 .sp
 .nf
 SCO UNIX version 3.x (aka ODT)
@@ -151,11 +158,12 @@ 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
-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
-mounted and used to copy the necessary files.
+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 mounted
+and used to copy the necessary files.
 .Sh BUGS
 The information about SCO distributions may become outdated.
 .Pp
diff --git a/share/man/man8/compat_linux.8 b/share/man/man8/compat_linux.8
index a68d1e9cef6..5b8158d694c 100644
--- a/share/man/man8/compat_linux.8
+++ b/share/man/man8/compat_linux.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_linux.8,v 1.19 2001/10/04 16:56:52 mpech Exp $
+.\"	$OpenBSD: compat_linux.8,v 1.20 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: compat_linux.8,v 1.2 1995/10/16 20:17:59 fvdl Exp $
 .\"
 .\" Copyright (c) 1995 Frank van der Linden
@@ -38,12 +38,14 @@
 .Nd setup procedure for running Linux binaries under emulation
 .Sh DESCRIPTION
 .Ox
-supports running Linux binaries. This only applies to i386 systems
-for now. Both the a.out and ELF binary formats are supported. Most programs
-should work, including the ones that use the Linux SVGAlib. Additionally,
-OSS audio is emulated, so Linux bins can access the native audio
-transparently. Programs that will not work include those that use the Linux
-/proc filesystem (which is different from the optional 
+supports running Linux binaries.
+This only applies to i386 systems for now.
+Both the a.out and ELF binary formats are supported.
+Most programs should work, including the ones that use the Linux SVGAlib.
+Additionally, OSS audio is emulated, so Linux bins can access the native audio
+transparently.
+Programs that will not work include those that use the Linux /proc filesystem
+(which is different from the optional 
 .Ox
 /proc
 filesystem), and i386-specific calls, such as enabling virtual 8086 mode.
@@ -53,22 +55,23 @@ for kernels compiled with the
 .Nm COMPAT_LINUX
 option enabled.
 .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"
-directory for Linux binaries on your
+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" directory for Linux binaries
+on your
 .Ox
-system. This directory
-is named /emul/linux. Any file operations done by Linux programs
-run under
+system.
+This directory is named /emul/linux.
+Any file operations done by Linux programs run under
 .Ox
-will look in this directory first. So, if a Linux
-program opens, for example, /etc/passwd,
+will look in this directory first.
+So, if a Linux program opens, for example, /etc/passwd,
 .Ox
 will first try to open /emul/linux/etc/passwd, and if that does not exist
-open the 'real' /etc/passwd file. It is recommended that you install
-Linux packages that include configuration files, etc under /emul/linux,
-to avoid naming conflicts with possible
+open the 'real' /etc/passwd file.
+It is recommended that you install Linux packages that include configuration
+files, etc under /emul/linux, to avoid naming conflicts with possible
 .Ox
 counterparts.
 Shared libraries should also be installed in the shadow tree.
@@ -83,28 +86,31 @@ on your system to be able to run newly imported Linux binaries without
 any extra work.
 .Ss Setting up shared libraries
 How to get to know which shared libraries Linux binaries need, and where
-to get them? Basically, there are 3 possibilities (when following
-these instructions: you will need to be root on your OpenBSD system to
-do the necessary installation steps).
-
+to get them?
+Basically, there are 3 possibilities (when following these instructions:
+you will need to be root on your OpenBSD system to do the necessary
+installation steps).
+.Pp
 .Bl -tag -width 123 -compact
 .It 1.
 You have access to the OpenBSD
 .Xr ports 7
-system.  Install the port named
+system.
+Install the port named
 .Nm redhat_base
 in the
 .Nm emulators
-category.  The
+category.
+The
 .Nm redhat_base
 port contains the shared libraries, binaries, and other related files
-necessary to run Linux applications.  Access to a Linux system is not
-needed.
+necessary to run Linux applications.
+Access to a Linux system is not needed.
 .Pp
 .It 2.
-You have access to a Linux system. In this case you can
-temporarily install the binary there, see what shared libraries
-it needs, and copy them to your
+You have access to a Linux system.
+In this case you can temporarily install the binary there, see what
+shared libraries it needs, and copy them to your
 .Ox
 system.
 Example: you have just ftp-ed the Linux binary of Doom.
@@ -122,8 +128,8 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29
 .Pp
 You would need go get all the files from the last column, and
 put them under /emul/linux, with the names in the first column
-as symbolic links pointing to them. This means you eventually have
-these files on your
+as symbolic links pointing to them.
+This means you eventually have these files on your
 .Ox
 system:
 .Pp
@@ -139,11 +145,12 @@ system:
 Note that if you already have a Linux shared library with a
 matching major revision number to the first column of the 'ldd'
 output, you won't need to copy the file named in the last column
-to your system, the one you already have should work. It is
-advisable to copy the shared library anyway if it is a newer version,
-though. You can remove the old one, as long as you make the symbolic
-link point to the new one. So, if you have these libraries
-on your system:
+to your system, the one you already have should work.
+It is advisable to copy the shared library anyway if it is a newer version,
+though.
+You can remove the old one, as long as you make the symbolic
+link point to the new one.
+So, if you have these libraries on your system:
 .Pp
 .nf
 /emul/linux/lib/libc.so.4.6.27
@@ -175,9 +182,9 @@ runtime linker takes care of looking for matching major revision numbers
 itself, you don't need to worry about that.
 .Pp
 Finally, you must make sure that you have the Linux runtime linker
-and its config files on your system. You should copy these
-files from the Linux system to their appropriate place on your
-OpenBSD system (in the /emul/linux tree):
+and its config files on your system.
+You should copy these files from the Linux system to their appropriate
+place on your OpenBSD system (in the /emul/linux tree):
 .Pp
 .nf
 /lib/ld.so
@@ -186,10 +193,12 @@ OpenBSD system (in the /emul/linux tree):
 .fi
 .Pp
 .It 3.
-You don't have access to a Linux system. In that case, you
-should get the extra files you need from various ftp sites.
+You don't have access to a Linux 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 /emul/linux
@@ -203,8 +212,8 @@ any version mismatches), and install them under /emul/linux
 .fi
 .Pp
 ldconfig and ldd don't necessarily need to be under /emul/linux,
-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
 .Ox
 counterparts.
 A good idea would be to install them in /usr/local/bin as ldconfig-linux
@@ -212,9 +221,10 @@ and ldd-linux.
 .Pp
 Create the file /emul/linux/etc/ld.so.conf, containing the
 directories in which the Linux runtime linker should look
-for shared libs. It is a plain text file, containing a directory
-name on each line. /lib and /usr/lib are standard, you could
-add the following:
+for shared libs.
+It is a plain text file, containing a directory
+name on each line.
+/lib and /usr/lib are standard, you could add the following:
 .Pp
 .nf
 /usr/X11/lib
@@ -223,17 +233,19 @@ add the following:
 .Pp
 Note that these are mapped to /emul/linux/XXXX by OpenBSD's compat
 code, and should exist as such on your system.
-
-Run the Linux ldconfig program. It should be statically
-linked, so it doesn't need any shared libraries by itself.
+.Pp
+Run the Linux ldconfig program.
+It should be statically linked, so it doesn't need any shared libraries
+by itself.
 It will create the file /emul/linux/etc/ld.so.cache
 You should rerun the Linux version of the ldconfig program
 each time you add a new shared library.
 .Pp
 You should now be set up for Linux binaries which only need
-a shared libc. You can test this by running the Linux ldd
-on itself. Suppose that you have it installed as ldd-linux, it
-should produce something like:
+a shared libc.
+You can test this by running the Linux ldd on itself.
+Suppose that you have it installed as ldd-linux, it should produce
+something like:
 .Pp
 .Bl -tag -width 123 -compact -offset indent
 .It % ldd-linux `which ldd-linux`
@@ -243,8 +255,9 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29
 This been done, you are ready to install new Linux binaries.
 Whenever you install a new Linux program, you should check
 if it needs shared libraries, and if so, whether you have
-them installed in the /emul/linux tree. To do this, you run
-the Linux version ldd on the new program, and watch its output.
+them installed in the /emul/linux tree.
+To do this, you run the Linux version ldd on the new program, and
+watch its output.
 ldd (see also the manual page for ldd(1)) will print a list
 of shared libraries that the program depends on, in the
 form  <majorname> (<jumpversion>) => <fullname>.
@@ -253,30 +266,30 @@ If it prints "not found" instead of <fullname> it means that
 you need an extra library. Which library this is, is shown
 in <majorname>, which will be of the form libXXXX.so.<N>
 You will need to find a libXXXX.so.<N>.<mm> on a Linux ftp site,
-and install it on your system. The XXXX (name) and <N> (major
-revision number) should match; the minor number(s) <mm> are
-less important, though it is advised to take the most
-recent version.
+and install it on your system.
+The XXXX (name) and <N> (major revision number) should match;
+the minor number(s) <mm> are less important, though it is
+advised to take the most recent version.
 .El
 .Ss Finding the necessary files.
 .Nm 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.  You can also
-save yourself a lot of headaches by using the
+may have changed by the time you read this.
+You can also save yourself a lot of headaches by using the
 .Ox
 .Xr ports 7
 system (possibility 3, above).
 .Pp
 Linux is distributed by several groups that make their own set
-of binaries that they distribute. Each distribution has its own
-name, like "Slackware" or "Yggdrasil". The distributions are
-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
-with gzipped tar files in them. The primary ftp sites for the
-distributions are:
+of binaries that they distribute.
+Each distribution has its own name, like "Slackware" or "Yggdrasil".
+The distributions are 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 with gzipped tar files in them.
+The primary ftp sites for the distributions are:
 .Pp
 .nf
 sunsite.unc.edu:/pub/Linux/distributions
@@ -291,17 +304,20 @@ ftp.demon.co.uk:/pub/linux/distributions
 src.doc.ic.ac.uk:/packages/linux/distributions
 .fi
 .Pp
-For simplicity, let's concentrate on Slackware here. This distribution
-consists of a number of subdirectories, containing separate packages.
+For simplicity, let's concentrate on Slackware here.
+This distribution consists of a number of subdirectories, containing
+separate packages.
 Normally, they're controlled by an install program, but you can
-retrieve files "by hand" too. First of all, you will need to look
-in the "contents" subdir of the distribution. You will find
-a lot of small textfiles here describing the contents of the separate
-packages. The fastest way to look something up is to retrieve all
+retrieve files "by hand" too.
+First of all, you will need to look in the "contents" subdir of
+the distribution.
+You will find a lot of small textfiles here describing the contents of
+the separate packages.
+The fastest way to look something up is to retrieve all
 the files in the contents subdirectory, and grep through them for the file
-you need. Here is an example of a list of files that you might need, and
+you need.
+Here is an example of a list of files that you might need, and
 in which contents-file you will find it by grepping through them:
-.Pp
 .Bd -unfilled -offset indent
 Needed                  Package
 
@@ -320,7 +336,6 @@ In each of the contents-files for these packages, look for a line saying
 "PACKAGE LOCATION", it will tell you on which 'disk' the package is,
 in our case it will tell us in which subdirectory we need to look.
 For our example, we would find the following locations:
-.Pp
 .Bd -unfilled -offset indent
 Package                 Location
 
@@ -347,9 +362,10 @@ Extract the files from these gzipped tarfiles in your /emul/linux directory
 (possibly omitting or afterwards removing files you don't need), and you
 are done.
 .Ss Programs using SVGAlib
-SVGAlib binaries require some extra care. The pcvt virtual console driver
-has to be in the kernel for them to work, and you will also have to create
-some symbolic links in the /emul/linux/dev directory, namely:
+SVGAlib binaries require some extra care.
+The pcvt virtual console driver has to be in the kernel for them to work,
+and you will also have to create some symbolic links in the /emul/linux/dev
+directory, namely:
 .Pp
 .nf
 /emul/linux/dev/console -> /dev/tty
diff --git a/share/man/man8/compat_sunos.8 b/share/man/man8/compat_sunos.8
index d5069e7fc04..c91bb938a12 100644
--- a/share/man/man8/compat_sunos.8
+++ b/share/man/man8/compat_sunos.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_sunos.8,v 1.10 2001/08/17 11:13:58 mpech Exp $
+.\"	$OpenBSD: compat_sunos.8,v 1.11 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: compat_sunos.8,v 1.6 1995/06/11 23:05:17 pk Exp $
 .\"
 .\" Copyright (c) 1994 Theo de Raadt
@@ -39,7 +39,8 @@
 .Nd setup procedure for running SunOS binaries under emulation
 .Sh DESCRIPTION
 OpenBSD/sparc and some of the OpenBSD/m68k architectures can run
-SunOS executables.  Most executables will work.
+SunOS executables.
+Most executables will work.
 .Pp
 The SunOS compatibility feature is active
 for kernels compiled with the
diff --git a/share/man/man8/compat_svr4.8 b/share/man/man8/compat_svr4.8
index 18817f3a48a..0bb6665c588 100644
--- a/share/man/man8/compat_svr4.8
+++ b/share/man/man8/compat_svr4.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_svr4.8,v 1.9 2000/12/22 16:54:38 avsm Exp $
+.\"	$OpenBSD: compat_svr4.8,v 1.10 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: compat_svr4.8,v 1.1 1996/07/06 17:14:50 christos Exp $
 .\"
 .\" Copyright (c) 1996 Christos Zoulas
@@ -40,9 +40,9 @@
 .Nd setup procedure 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:
+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
@@ -63,26 +63,27 @@ for kernels compiled with the
 .Nm COMPAT_SVR4
 option enabled.
 .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
+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
 .Ox
-system. This directory
-is named /emul/svr4. Any file operations done by SVR4 programs
-run under
+system.
+This directory is named /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, /etc/passwd,
+will look in this directory first.
+So, if a SVR4 program opens, for example, /etc/passwd,
 .Ox
 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
+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
 .Ox
-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 setup your system for SVR4 binaries is:
 .Bl -tag -width 123 -compact
@@ -147,17 +148,18 @@ 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).
+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
-the
+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 the
 .Fl 2
 option to
 .Xr mount_nfs 8 .
diff --git a/share/man/man8/compat_ultrix.8 b/share/man/man8/compat_ultrix.8
index 7df6a0e0231..7fa3759d8ba 100644
--- a/share/man/man8/compat_ultrix.8
+++ b/share/man/man8/compat_ultrix.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: compat_ultrix.8,v 1.9 2001/10/04 16:56:52 mpech Exp $
+.\"	$OpenBSD: compat_ultrix.8,v 1.10 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1997 Jonathan Stone
 .\" All rights reserved.
@@ -38,22 +38,24 @@
 .Nd setup procedure for running Ultrix binaries under emulation
 .Sh DESCRIPTION
 OpenBSD/mips and OpenBSD/vax architectures can run Risc ULTRIX and Vax
-ULTRIX executables, respectively.  However, you have to worry about
+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, ioctl()'s, or Ultrix kernel
 semantics that are difficult to emulate (e.g., Ultrix packetfilter) or
 buggy (e.g., Ultrix YP).
 .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
 .Ox
 or even SunOS 4.x equivalents, and may require incompatible
 configuration files.
@@ -77,22 +79,22 @@ and
 lines in
 .Xr  /etc/resolv.conf 5 .
 You should create a copy of /etc/resolv.conf containing only those
-commands and put it in /emul/ultrix/etc/resolv.conf.  Note that the
-domain search order used by Ultrix executables may not be the same as
-native binaries; there is no good way around this.
+commands and put it in /emul/ultrix/etc/resolv.conf.
+Note that the domain search order used by Ultrix executables may
+not be the same as native binaries; there is no good way around this.
 .Ss /etc/svc.conf
 Ultrix uses /etc/svc.conf to select an ordered search of YP, Hesiod,
-or local flat-file mappings.  You should create an
-/emul/ultrix/etc/svc.conf specifying either local files or bind (DNS)
-lookups for all Ultrix name services.
+or local flat-file mappings.
+You should create an /emul/ultrix/etc/svc.conf specifying either
+local files or bind (DNS) lookups for all Ultrix name services.
 .Sh BUGS
-RISC Ultrix YP(NIS) is known to not work.  The Ultrix YP libraries have
-a consistent endian-ness bug. Ultrix YP client will not inter-operate
-with the
+RISC Ultrix YP(NIS) is known to not work.
+The Ultrix YP libraries have a consistent endian-ness bug.
+Ultrix YP client will not inter-operate with the
 .Ox
 .Xr ypbind 8
-process.  The only workaround is to use
-/etc/svc.conf to disable YP(NIS).
+process.
+The only workaround is to use /etc/svc.conf to disable YP(NIS).
 .Pp
 The ndbm hashed-password file used by Ultrix are incompatible with the
 db hashed-password file used by
@@ -101,8 +103,9 @@ There is no good solution for this.
 (YP would be a good one, if Ultrix YP 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
-(used by X11R6) is in progress.
+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
 mode should be added here.
diff --git a/share/man/man8/crash.8 b/share/man/man8/crash.8
index 4948fd39a20..6126b08a231 100644
--- a/share/man/man8/crash.8
+++ b/share/man/man8/crash.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: crash.8,v 1.13 2001/08/22 08:16:50 niklas Exp $
+.\"	$OpenBSD: crash.8,v 1.14 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1980, 1991 The Regents of the University of California.
 .\" All rights reserved.
@@ -162,7 +162,8 @@ Copyright 1996 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you are
 welcome to change it and/or distribute copies of it under certain conditions.
 Type "show copying" to see the conditions.
-There is absolutely no warranty for GDB.  Type "show warranty" for details.
+There is absolutely no warranty for GDB.
+Type "show warranty" for details.
 This GDB was configured as "i386-unknown-openbsd2.8".
 (gdb) file /var/crash/bsd.0
 Reading symbols from /var/crash/bsd.0...(no debugging symbols found)...done.
@@ -301,9 +302,9 @@ The first number is the offset.
 Find the offset that you got in the ddb trace
 (in this case it's 4711).
 .Pp
-When reporting data collected in this way, include ~20 lines before and ~10 lines
-after the offset from the objdump output in the crash report, as well as the output
-of
+When reporting data collected in this way, include ~20 lines before and ~10
+lines after the offset from the objdump output in the crash report, as well
+as the output of
 .Xr ddb 4 Ns 's
 "show registers" command.
 It's important that the output from objdump includes at least two or
diff --git a/share/man/man8/dhcp.8 b/share/man/man8/dhcp.8
index e491cbe49bd..85f7577128a 100644
--- a/share/man/man8/dhcp.8
+++ b/share/man/man8/dhcp.8
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: dhcp.8,v 1.8 2001/10/04 10:28:20 wilfried Exp $
+.\"     $OpenBSD: dhcp.8,v 1.9 2001/10/05 14:45:54 mpech Exp $
 .\"
 .Dd July 8, 1999
 .Dt DHCP 8
@@ -11,9 +11,9 @@ for DHCP
 .Sh DESCRIPTION
 The Dynamic Host Configuration Protocol (DHCP) allows hosts on a TCP/IP network
 to configure one or more network interfaces based on information collected from
-a DHCP server in response to a DHCP request. This mechanism is often used, for
-example, by cable modem and DSL network providers to simplify network
-configurations for their clients/customers.
+a DHCP server in response to a DHCP request.
+This mechanism is often used, for example, by cable modem and DSL network
+providers to simplify network configurations for their clients/customers.
 .Pp
 Information typically contained within a DHCP response includes an IP
 address for the interface, subnet mask, broadcast address, router (gateway)
@@ -29,7 +29,8 @@ For each interface that is to be configured via DHCP, create a
 file (where XXX is the interface's identifier, e.g., ep1) that starts with
 the word
 .Dq dhcp ,
-optionally followed by additional interface options. See
+optionally followed by additional interface options.
+See
 .Xr hostname.if 5
 for more information on the format of these files.
 .Pp
@@ -57,7 +58,8 @@ as a DHCP server:
 .It
 Edit
 .Pa /etc/dhcpd.conf .
-This file is shipped with the system. See
+This file is shipped with the system.
+See
 .Xr dhcpd.conf 5
 and
 .Xr dhcpd 8
@@ -68,8 +70,8 @@ Edit
 This file should contain a list of interfaces you wish to serve by
 .Xr dhcpd 8 .
 If you have only one broadcast network interface or you wish to serve all
-interfaces, this step is not required. Be sure to leave this file empty (or
-even delete it) if this is the case.
+interfaces, this step is not required.
+Be sure to leave this file empty (or even delete it) if this is the case.
 .It
 Edit
 .Pa /etc/rc.conf
@@ -79,8 +81,8 @@ This will cause
 .Ox
 to start the
 .Xr dhcpd 8
-daemon at boot-time and listen for DHCP requests on the local network. To
-start it manually, execute the following commands:
+daemon at boot-time and listen for DHCP requests on the local network.
+To start it manually, execute the following commands:
 .Pp
 .Dl # touch /var/db/dhcpd.leases
 .Dl # /usr/sbin/dhcpd -q [netif1 netif2 ...]
diff --git a/share/man/man8/diskless.8 b/share/man/man8/diskless.8
index 6b8290b1a6d..e3569c81394 100644
--- a/share/man/man8/diskless.8
+++ b/share/man/man8/diskless.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: diskless.8,v 1.15 2001/09/20 15:39:57 miod Exp $
+.\"	$OpenBSD: diskless.8,v 1.16 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: diskless.8,v 1.7.4.1 1996/05/30 18:58:10 cgd Exp $
 .\"
 .\"
@@ -78,8 +78,8 @@ Other machines may load a
 network boot program either from diskette or
 using a special PROM on the network card.
 .Pp
-In phase 2, the boot program loads a kernel.  Operation in
-this phase depends on the design of the boot program.
+In phase 2, the boot program loads a kernel.
+Operation in this phase depends on the design of the boot program.
 The boot program:
 .Pp
 .Bl -tag -width 2.2 -compact
@@ -207,7 +207,8 @@ For example:
 .Ed
 .Pp
 Some architectures, such as the Sun3 and Ultrasparc machines, do not append the
-architecture name. It this case, the name would be just C0C5600C.
+architecture name.
+It this case, the name would be just C0C5600C.
 The name used is architecture dependent, it simply has to match what the
 booting client's PROM wishes to it to be.
 If the client's PROM fails to fetch the expected file,
@@ -230,10 +231,10 @@ Add myclient to the bootparams database
 myclient  root=server:/export/myclient/root \\
           swap=server:/export/myclient/swap
 .Ed
-Note that some bootparam servers are somewhat sensitive.  Some require
-fully qualified hostnames or partially qualified hostnames (which can
-be solved by having both fully and partially qualified entries). Other
-servers are case sensitive.
+Note that some bootparam servers are somewhat sensitive.
+Some require fully qualified hostnames or partially qualified hostnames
+(which can be solved by having both fully and partially qualified entries).
+Other servers are case sensitive.
 .Pp
 .It 6.
 Build the swap file for myclient:
@@ -247,8 +248,8 @@ This creates a 16 Megabyte swap file.
 .It 7.
 Populate myclient's
 .Pa /
-filesystem on the server.  How this is done depends on the
-client architecture and the version of the 
+filesystem on the server.
+How this is done depends on the client architecture and the version of the 
 .Ox
 distribution.
 It can be as simple as copying and modifying the server's root
diff --git a/share/man/man8/makedev.8 b/share/man/man8/makedev.8
index 139f43dbe9d..0083709acb5 100644
--- a/share/man/man8/makedev.8
+++ b/share/man/man8/makedev.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: makedev.8,v 1.5 2000/12/22 16:54:38 avsm Exp $
+.\"	$OpenBSD: makedev.8,v 1.6 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: makedev.8,v 1.3 1994/11/30 19:36:25 jtc Exp $
 .\"
 .\" Copyright (c) 1983, 1991, 1993
@@ -46,7 +46,8 @@
 .Sh DESCRIPTION
 .Nm MAKEDEV
 is a shell script normally used to install
-special files.  It resides in the
+special files.
+It resides in the
 .Pa /dev
 directory, as this is the normal location of special files.
 Arguments to
@@ -58,8 +59,8 @@ where
 is one of the supported devices listed in section 4 of the
 manual and
 .Dq Sy \&?
-is a logical unit number (0-9).  A few
-special arguments create assorted collections of devices and are
+is a logical unit number (0-9).
+A few special arguments create assorted collections of devices and are
 listed below.
 .Bl -tag -width Ds
 .It Sy std
@@ -83,11 +84,11 @@ console cassette device(s),
 .Pa /dev/tu?
 devices would be made for the appropriate system.
 .It Sy local
-Create those devices specific to the local site.  This
-request causes the shell file
+Create those devices specific to the local site.
+This request causes the shell file
 .Pa /dev/MAKEDEV.local
-to be executed.  Site specific commands, such as those
-used to setup dialup lines as
+to be executed.
+Site specific commands, such as those used to setup dialup lines as
 .Pa ttyd?
 should be included
 in this file.
@@ -98,7 +99,8 @@ Since all devices are created using
 this shell script is useful only to the superuser.
 .Sh DIAGNOSTICS
 Either self-explanatory, or generated by one of the programs
-called from the script.  Use
+called from the script.
+Use
 .Ql sh -x MAKEDEV
 in case of
 trouble.
diff --git a/share/man/man8/man8.alpha/boot_alpha.8 b/share/man/man8/man8.alpha/boot_alpha.8
index 5ca7b691721..f5c9d903f37 100644
--- a/share/man/man8/man8.alpha/boot_alpha.8
+++ b/share/man/man8/man8.alpha/boot_alpha.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: boot_alpha.8,v 1.2 2001/01/29 02:11:14 niklas Exp $
+.\" $OpenBSD: boot_alpha.8,v 1.3 2001/10/05 14:45:54 mpech Exp $
 .\" $NetBSD: boot.8,v 1.3 2000/06/14 17:25:48 cgd Exp $
 .\"
 .\" Copyright (c) 1999 Christopher G. Demetriou
@@ -82,10 +82,10 @@ When the
 .Ox
 .Ns Tn /alpha
 kernel is booted normally
-it initializes itself and proceeds to start the system.  An automatic
-consistency check of the file systems takes place, and unless this
-fails, the system comes up to multi-user operation.  The proper way
-to shut the system down is with the
+it initializes itself and proceeds to start the system.
+An automatic consistency check of the file systems takes place, and unless
+this fails, the system comes up to multi-user operation.
+The proper way to shut the system down is with the
 .Xr shutdown 8
 command.
 .Pp
diff --git a/share/man/man8/man8.vax/drtest.8 b/share/man/man8/man8.vax/drtest.8
index 16ddd835bd6..f409657d1a7 100644
--- a/share/man/man8/man8.vax/drtest.8
+++ b/share/man/man8/man8.vax/drtest.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: drtest.8,v 1.8 2001/04/18 11:14:23 bjc Exp $
+.\"	$OpenBSD: drtest.8,v 1.9 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1983, 1991 Regents of the University of California.
 .\" All rights reserved.
@@ -47,8 +47,8 @@ It was primarily intended as a test program
 for new standalone drivers, but has shown
 useful in other contexts as well, such as
 verifying disks and running speed
-tests. For example, when a disk has been formatted
-(by
+tests.
+For example, when a disk has been formatted (by
 .Xr format 8 ) ,
 you can check that
 hard errors has been taken care of by running
@@ -71,7 +71,8 @@ In this example (using a 750),
 is loaded from the root file system;
 usually it
 will be loaded from the machine's
-console storage device.  Boldface means user input.
+console storage device.
+Boldface means user input.
 As usual, ``#'' and ``@'' may be used to edit input.
 .Pp
 .Bd -unfilled -offset indent -compact
@@ -95,9 +96,9 @@ As usual, ``#'' and ``@'' may be used to edit input.
 .Em (...to abort halt machine with \&^P)
 .Ed
 .Sh DIAGNOSTICS
-The diagnostics are intended to be self explanatory. Note, however, that
-the device number
-in the diagnostic messages is identified as
+The diagnostics are intended to be self explanatory.
+Note, however, that the device number in the diagnostic messages
+is identified as
 .Em typeX
 instead of
 .Em type(a,u)
diff --git a/share/man/man8/man8.vax/format.8 b/share/man/man8/man8.vax/format.8
index ed21ce86639..04b24143d19 100644
--- a/share/man/man8/man8.vax/format.8
+++ b/share/man/man8/man8.vax/format.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: format.8,v 1.9 2001/10/04 16:56:52 mpech Exp $
+.\"	$OpenBSD: format.8,v 1.10 2001/10/05 14:45:54 mpech Exp $
 .\" Copyright (c) 1980, 1983 The Regents of the University of California.
 .\" All rights reserved.
 .\"
@@ -39,10 +39,11 @@
 .Nm format
 .Nd how to format disk packs
 .Sh DESCRIPTION
-There are two ways to format disk packs.  The simplest is to
-use the
+There are two ways to format disk packs.
+The simplest is to use the
 .Nm
-program.  The alternative is to use the DEC standard formatting
+program.
+The alternative is to use the DEC standard formatting
 software which operates under the DEC diagnostic supervisor.
 This manual page describes the operation of
 .Nm format ,
@@ -129,8 +130,8 @@ amiss.)
 .Pp
 .Nm
 uses the standard notation of the standalone I/O library
-in identifying a drive to be formatted.  A drive is
-specified as
+in identifying a drive to be formatted.
+A drive is specified as
 .Do 
 .Ar zz Ns (x,y),
 .Dc
@@ -161,15 +162,15 @@ should be formatted.
 Before each formatting attempt,
 .Nm
 prompts the user in case debugging should be enabled
-in the appropriate device driver.  A carriage return
-disables debugging information.
+in the appropriate device driver.
+A carriage return disables debugging information.
 .Pp
 .Nm
 should be used prior to building file systems (with
 .Xr newfs 8
 to ensure that all sectors with uncorrectable media errors
-are remapped.  If a drive develops uncorrectable
-defects after formatting, either
+are remapped.
+If a drive develops uncorrectable defects after formatting, either
 .Xr bad144 8
 or
 .Xr badsect 8
@@ -242,13 +243,13 @@ The diagnostics are intended to be self explanatory.
 The steps needed for 11/750 or 11/730 CPUs are similar, but not
 covered in detail here.
 .Pp
-The formatting procedures are different for each type of disk.  Listed
-here are the formatting procedures for RK07's, RP0X, and RM0X
-disks.
+The formatting procedures are different for each type of disk.
+Listed here are the formatting procedures for RK07's, RP0X, and RM0X disks.
 .Pp
 You should shut down UNIX and halt the machine to do any disk formatting.
-Make certain you put in the pack you want formatted.  It is also a good idea
-to spin down or write protect the disks you don't want to format, just in case.
+Make certain you put in the pack you want formatted.
+It is also a good idea to spin down or write protect the disks you don't
+want to format, just in case.
 .Ss Formatting an RK07
 Load the console floppy labeled, "RX11 VAX DSK LD DEV #1" in
 the console disk drive, and type the following commands:
diff --git a/share/man/man8/rc.8 b/share/man/man8/rc.8
index a8cd87f5290..ff60b0b987a 100644
--- a/share/man/man8/rc.8
+++ b/share/man/man8/rc.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: rc.8,v 1.16 2001/08/03 15:21:17 mpech Exp $
+.\"	$OpenBSD: rc.8,v 1.17 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
@@ -152,8 +152,9 @@ of course) by
 .Pa /etc/rc .
 Various comments in
 .Nm rc.conf
-make it clear what each variable does.  Refer to the specific man pages
-for each daemon to determine what that subsystem does.
+make it clear what each variable does.
+Refer to the specific man pages for each daemon to determine what that
+subsystem does.
 .Pp
 For example, the
 .Xr sendmail 8
@@ -164,7 +165,8 @@ daemon is controlled by the line
 .Pp
 This does not start
 .Xr sendmail 8
-at system startup.  But
+at system startup.
+But
 .Xr sendmail 8
 is started with the specified flags if the specification is modified to be
 .Bd -literal
diff --git a/share/man/man8/rc.shutdown.8 b/share/man/man8/rc.shutdown.8
index 7fd4711ba55..231274e32a3 100644
--- a/share/man/man8/rc.shutdown.8
+++ b/share/man/man8/rc.shutdown.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: rc.shutdown.8,v 1.2 1999/09/03 22:14:08 deraadt Exp $
+.\"	$OpenBSD: rc.shutdown.8,v 1.3 2001/10/05 14:45:54 mpech Exp $
 .Dd July 20, 1999
 .Dt RC.SHUTDOWN 8
 .Os
@@ -12,7 +12,8 @@ or
 .Xr halt 8
 command, either of these programs checks for the existence of a
 .Pa /etc/rc.shutdown
-script to run before halting the system. It will also be executed by
+script to run before halting the system.
+It will also be executed by
 .Xr init 8
 if a keyboard-requested halt is issued (for architectures that support this).
 .Pp
diff --git a/share/man/man8/release.8 b/share/man/man8/release.8
index 4d693b5e611..69023431aad 100644
--- a/share/man/man8/release.8
+++ b/share/man/man8/release.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: release.8,v 1.18 2001/10/04 16:56:52 mpech Exp $
+.\"	$OpenBSD: release.8,v 1.19 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\"	Copyright (c) 2000 Marco S. Hyman
 .\"
@@ -319,7 +319,9 @@ the build process is:
 .Pa XF86Setup ,
 built and installed above, requires version 8.3 of the
 .Pa tcl/tk
-libraries.   They must be installed to do a proper build. Version 8.3 of
+libraries.
+They must be installed to do a proper build.
+Version 8.3 of
 .Pa tcl/tk
 can be found in the ports tree at
 .Pa /usr/ports/lang/tcl/8.3/
@@ -340,7 +342,8 @@ However, the install phase of the build does
 .Em not
 overwrite
 .Pa /etc/X11/xdm .
-That directory must be installed by hand.   Or you can
+That directory must be installed by hand.
+Or you can
 .Ic "cd /etc/X11 && mv xdm xdm-"
 before the build and copy any local configuration from
 .Pa xdm-
@@ -357,7 +360,8 @@ mechanism noted in the section on building a system release, above.
 They may be the same values used above, but be warned that the
 contents of
 .Va DESTDIR
-will be removed if you follow this procedure.   However,
+will be removed if you follow this procedure.
+However,
 .Va DESTDIR
 should not be the same directory used to build the system release.  
 It may be the same if you don't care to keep the contents of the
diff --git a/share/man/man8/ssl.8 b/share/man/man8/ssl.8
index 2dea2892415..fd61ef864f5 100644
--- a/share/man/man8/ssl.8
+++ b/share/man/man8/ssl.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ssl.8,v 1.35 2001/09/19 19:42:00 millert Exp $
+.\"	$OpenBSD: ssl.8,v 1.36 2001/10/05 14:45:54 mpech Exp $
 .\"
 .Dd September 19, 2001
 .Dt SSL 8
@@ -174,9 +174,9 @@ transactions with your machine on port 443.
 You will most likely want to generate a self-signed certificate in the
 manner above along with your certificate signing request to test your
 server's functionality even if you are going to have the certificate
-signed by another Certifying Authority.  Once your Certifying
-Authority returns the signed certificate to you, you can switch to
-using the new certificate by replacing the self-signed
+signed by another Certifying Authority.
+Once your Certifying Authority returns the signed certificate to you,
+you can switch to using the new certificate by replacing the self-signed
 .Pa /etc/ssl/server.crt
 with the certificate signed by your Certifying Authority, and then
 restarting 
diff --git a/share/man/man8/update.8 b/share/man/man8/update.8
index 8d55a63fd5c..6b1b47fdfa2 100644
--- a/share/man/man8/update.8
+++ b/share/man/man8/update.8
@@ -27,7 +27,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.\"	$OpenBSD: update.8,v 1.6 1998/09/01 16:38:22 deraadt Exp $
+.\"	$OpenBSD: update.8,v 1.7 2001/10/05 14:45:54 mpech Exp $
 .\"
 .Dd June 8, 1996
 .Dt UPDATE 8
@@ -58,7 +58,8 @@ process will do this in a staggered manner.
 It is possible on some systems, that a
 .Xr sync
 occurring simultaneously with a crash may cause
-file system damage. See
+file system damage.
+See
 .Xr fsck 8 .
 .Sh HISTORY
 An
diff --git a/share/man/man8/vpn.8 b/share/man/man8/vpn.8
index c4901cd6cb1..dad740624bb 100644
--- a/share/man/man8/vpn.8
+++ b/share/man/man8/vpn.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: vpn.8,v 1.55 2001/10/04 16:56:52 mpech Exp $
+.\" $OpenBSD: vpn.8,v 1.56 2001/10/05 14:45:54 mpech Exp $
 .\"
 .\" Copyright 1998 Niels Provos <provos@physnet.uni-hamburg.de>
 .\" All rights reserved.
@@ -38,7 +38,8 @@
 .Nd configuring the system for virtual private networks
 .Sh DESCRIPTION
 A virtual private network is used to securely connect two or more subnets
-over the internet. For each subnet there is a security gateway which is
+over the internet.
+For each subnet there is a security gateway which is
 linked via a cryptographically secured tunnel to the security gateway of
 the other subnet.
 .Xr ipsec 4
@@ -107,12 +108,14 @@ For more permanent operation, these options should be enabled in your
 .Ss Generating Manual Keys [manual keying]
 The shared secret symmetric keys used to create a VPN can
 be any hexadecimal value, so long as both sides of the connection use
-the same values. Since the security of the VPN is based on these keys
+the same values.
+Since the security of the VPN is based on these keys
 being unguessable, it is very important that the keys be chosen using a
-strong random source. One practical method of generating them
-is by using the
+strong random source.
+One practical method of generating them is by using the
 .Xr random 4
-device. To produce 160 bits (20 bytes) of randomness, for example, do:
+device.
+To produce 160 bits (20 bytes) of randomness, for example, do:
 .Bd -literal
 	# openssl rand 20 | hexdump -e '20/1 "%02x"'
 .Ed
@@ -139,8 +142,9 @@ Furthermore, recent attacks on SKIPJACK have shown severe weaknesses
 in its structure.
 .Pp
 Note that DES requires 8 bytes to form a 56-bit key and 3DES requires 24 bytes
-to form its 168-bit key. This is because the most significant bit of each byte
-is ignored by both algorithms.
+to form its 168-bit key.
+This is because the most significant bit of each byte is ignored by both
+algorithms.
 .Ss Creating Security Associations [manual keying]
 Before the IPsec flows can be defined, two Security Associations (SAs)
 must be defined on each end of the VPN, e.g.:
@@ -161,7 +165,8 @@ and
 .Fl authkey
 options may be used to specify the keys directly in the
 .Xr ipsecadm 8
-command line.  However, another user could view the keys by using the
+command line.
+However, another user could view the keys by using the
 .Xr ps 1
 command at the appropriate time (or use a program for doing so).
 .Ss Creating IPsec Flows [manual keying]
@@ -250,7 +255,8 @@ either the
 .Xr isakmpd 8
 or
 .Xr photurisd 8
-key management daemon. To make sure the daemon is properly configured
+key management daemon.
+To make sure the daemon is properly configured
 to provide the required security services (typically, encryption and
 authentication) start the daemon with debugging or verbose output.
 .Pp
@@ -591,10 +597,11 @@ Suites=			QM-ESP-3DES-SHA-SUITE
 .Ed
 .Pp
 .It
-Read through the configuration one more time. The only real
-differences between the two files in this example is
+Read through the configuration one more time.
+The only real differences between the two files in this example is
 the IP-addresses, and ordering of Local- and Remote-ID for the VPN
-itself. Note that the shared secret (the
+itself.
+Note that the shared secret (the
 .Em Authentication
 tag) must match between machineA and machineB.
 .Pp
diff --git a/share/man/man8/yp.8 b/share/man/man8/yp.8
index 2461013a5ad..3ea012df2ae 100644
--- a/share/man/man8/yp.8
+++ b/share/man/man8/yp.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: yp.8,v 1.12 2000/04/17 02:32:48 aaron Exp $
+.\"	$OpenBSD: yp.8,v 1.13 2001/10/05 14:45:54 mpech Exp $
 .\"	$NetBSD: yp.8,v 1.9 1995/08/11 01:16:52 thorpej Exp $
 .\"
 .\" Copyright (c) 1992, 1993, 1996 Theo de Raadt <deraadt@theos.com>
@@ -127,16 +127,18 @@ of their maps through
 .Nm ypinit
 is used to initialize
 .Nm YP
-as a server or master.  This creates
-various files in
+as a server or master.
+This creates various files in
 .Pa /var/yp .
 By default the
 .Nm YP
-server will be setup in backwards compatible mode.  To enable
+server will be setup in backwards compatible mode.
+To enable
 .Dq secure
 mode, the file
 .Pa /var/yp/Makefile.yp
-must be edited.  This
+must be edited.
+This
 .Dq secure
 mode is compatible with
 .Ox
@@ -202,8 +204,8 @@ YP maps Makefile
 .Sh HISTORY
 This free
 .Nm YP
-subsystem is thought to be compatible with Sun's implementation.  It is,
-of course, not compatible with
+subsystem is thought to be compatible with Sun's implementation.
+It is, of course, not compatible with
 .Nm NIS+
 or any other
 .Dq secure