more `` '' -> .Dq sillyness; remove redundant .Pp macros; other misc fixes

9 files changed, 136 insertions, 80 deletions

diff --git a/sbin/reboot/boot_atari.8 b/sbin/reboot/boot_atari.8
index f77b382e2d3..de0fbda58b1 100644
--- a/sbin/reboot/boot_atari.8
+++ b/sbin/reboot/boot_atari.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_atari.8,v 1.4 1998/09/17 04:15:00 aaron Exp $
+.\"	$OpenBSD: boot_atari.8,v 1.5 1998/11/11 22:19:59 aaron Exp $
 .\"	$NetBSD: boot_atari.8,v 1.1 1996/06/27 11:07:56 leo Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -48,7 +48,6 @@
 system bootstrapping procedures
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 When the
 .Tn OpenBSD
 kernel is booted normally (using one of the two methods discussed below),
@@ -69,7 +68,6 @@ during the next boot cycle).  After the dump completes (successful
 or not), the system will attempt a reboot.
 .Pp
 .Ss Booting OpenBSD using the bootloader
-.Pp
 When a bootable
 .Tn OpenBSD
 partition is created by means of
@@ -134,7 +132,6 @@ Enter the kernel debugger.
 .El
 .Pp
 .Ss Booting using the loadbsd program
-.Pp
 When you want (or have to) start OpenBSD from GEM, you have to use the
 .Xr loadbsd
 program that is supplied on the kernel-floppy. The loadbsd command line
diff --git a/sbin/reboot/boot_hp300.8 b/sbin/reboot/boot_hp300.8
index da91bed4e0b..1afaca88af3 100644
--- a/sbin/reboot/boot_hp300.8
+++ b/sbin/reboot/boot_hp300.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_hp300.8,v 1.4 1998/09/17 04:15:00 aaron Exp $
+.\"	$OpenBSD: boot_hp300.8,v 1.5 1998/11/11 22:19:59 aaron Exp $
 .\"	$NetBSD: boot_hp300.8,v 1.3 1995/04/23 10:33:34 cgd Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
@@ -47,13 +47,11 @@
 system bootstrapping procedures
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 On an HP300, the boot procedure uses the boot ROM to load a boot program
 from an
 .Tn LIF
@@ -63,7 +61,9 @@ The
 directory contains a disk boot program which should be placed in a
 new pack automatically by
 .Xr newfs 8
-when the ``a'' partition file system on the pack is created.
+when the
+.Dq a
+partition file system on the pack is created.
 .Pp
 This boot program
 finds the corresponding file on the given device 
@@ -72,7 +72,7 @@ by default),
 loads that file into memory,
 and starts the program at the entry address specified in the program header.
 .Pp
-The boot program can be interrupted by typing `^C' (ctrl-C).
+The boot program can be interrupted by typing ^C (ctrl-C).
 This will force the boot program to interactively prompt for a system to boot.
 If not interrupted, it will boot from the device from which the boot
 program itself was loaded.
@@ -90,14 +90,19 @@ and
 .Ar minor
 is the disk partition or tape file number.
 Normal line editing characters can be used when typing the file specification.
-Currently, ``rd'' and ``sd'' are the only valid
+Currently,
+.Dq rd
+and
+.Dq sd
+are the only valid
 .Ar device
 specifiers.
 .Pp
 For example,
-to boot from the ``a'' file system of unit 0 on HP-IB 2,
-type
-.Ql rd(16, 0)bsd
+to boot from the
+.Dq a
+file system of unit 0 on HP-IB 2, type
+.Dq rd(16, 0)bsd
 at the boot prompt.
 For tapes, the minor device number gives a file offset.
 .Pp
diff --git a/sbin/reboot/boot_i386.8 b/sbin/reboot/boot_i386.8
index 1e114a755bb..ff34c7344af 100644
--- a/sbin/reboot/boot_i386.8
+++ b/sbin/reboot/boot_i386.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_i386.8,v 1.8 1998/11/04 22:36:42 aaron Exp $
+.\"	$OpenBSD: boot_i386.8,v 1.9 1998/11/11 22:19:59 aaron Exp $
 .\"
 .\" Copyright (c) 1997 Tobias Weingartner
 .\"
@@ -40,13 +40,11 @@
 system bootstrapping procedures
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 The
 .Tn "PC AT"
 clones will perform a POST (Power On Self Test) upon being booted cold.
@@ -63,7 +61,6 @@ drive A (otherwise known as drive 0) first, and failing that, attempt to
 boot the hard disk C (otherwise known as hard disk controller 1, drive 0).
 .Pp
 .Ss Warm starts
-.Pp
 The BIOS loads the first block (at physical location: track 0, head 0,
 sector 1) off the boot device into memory, and if the last two bytes in the
 block match the signature 0x55AA, the BIOS considers the block a valid
@@ -74,7 +71,9 @@ to the boot block in register %dl.
 There are two different types of boot blocks on devices.  There is the
 MBR (master boot record) and the PBR (partition boot record).  A digression
 into a little piece of history will quickly give light as to why this is so.
-In the beginning, the PC ``architecture'' came with a single or dual floppy
+In the beginning, the PC
+.Dq architecture
+came with a single or dual floppy
 drives, and no hard drives.  The only type of bootable sectors on any device
 were the PBRs.  They were responsible for loading the rest of the operating
 system from the correct device.  When hard disks came out, it was felt that
@@ -94,8 +93,9 @@ partition is really an MBR, which will then load the corresponding MBR or PBR
 out of its extended partition's partition table.
 .Sh GEOMETRY TRANSLATION
 .Em WARNING:
-This portion of the ``PC BIOS Architecture'' is a mess, and a compatibility
-nightmare.
+This portion of the
+.Dq PC BIOS Architecture
+is a mess, and a compatibility nightmare.
 .Pp
 The PC BIOS has an API to manipulate any disk that the BIOS happens to
 support.  This interface uses 10 bits to address the cylinder, 8 bits to
@@ -107,7 +107,9 @@ the debut of hard disks on PC computers.
 .Pp
 Many (if not all) newer drives have many more cylinders than the BIOS API
 can support, and likely more sectors per track as well.  To allow the BIOS
-the ability of accessing these large drives, the BIOS would ``re-map'' the
+the ability of accessing these large drives, the BIOS would
+.Dq re-map
+the
 cylinder/head/sector of the real drive geometry into something that would
 allow the applications using the BIOS to access a larger portion of the
 drive, still using the restricted BIOS API.
@@ -142,7 +144,9 @@ system second stage bootstrap
 .Xr reboot 8 ,
 .Xr shutdown 8
 .Sh BUGS
-The ``PC BIOS Architecture'' makes this process very prone to weird and
+The
+.Dq PC BIOS Architecture
+makes this process very prone to weird and
 wonderful interactions between differing operating systems.  There is
 no published standard to the MBR and PBR, which makes coding these a
 nightmare.  Somebody *please* write me a decent BIOS, and make them (the
diff --git a/sbin/reboot/boot_mac68k.8 b/sbin/reboot/boot_mac68k.8
index fa708ca2705..4df0bb54eef 100644
--- a/sbin/reboot/boot_mac68k.8
+++ b/sbin/reboot/boot_mac68k.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_mac68k.8,v 1.7 1998/09/23 01:20:25 aaron Exp $
+.\"	$OpenBSD: boot_mac68k.8,v 1.8 1998/11/11 22:19:59 aaron Exp $
 .\"	$NetBSD: boot_mac68k.8,v 1.1 1995/07/02 02:09:52 briggs Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -48,7 +48,6 @@
 system bootstrapping procedures
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the
 .Ox
 kernel on the mac68k architecture is booted from the native operating
@@ -69,8 +68,12 @@ configured dump device (which will be automatically recovered with
 during the next boot cycle).  After the dump completes (successful
 or not), the system will attempt a reboot.
 .Pp
-On most mac68k machines with "soft-power" after the IIcx, the power
-switch can be physically rotated and locked in the ``on'' position.
+On most mac68k machines with
+.Dq soft-power
+after the IIcx, the power
+switch can be physically rotated and locked in the
+.Dq on
+position.
 The native OS can be configured to automatically start the
 .Ox
 boot program.  Additionally, the OpenBSD boot program can be configured
@@ -81,7 +84,6 @@ or lose power and reboot back to a fully multi-user state without
 any intervention.
 .Pp
 .Ss The boot application
-.Pp
 The boot application runs in the native OS on the system.  It has a
 dialog where booting preferences may be changed and an option whereby
 these options may be saved.  The preferences are stored in the program
@@ -93,12 +95,13 @@ One option that may be specified is a boot to single-user mode.  This
 stops the boot process very early on and allows system maintenence.
 If one wishes to provide some security at this phase of the boot, remove
 the
-.Ql secure
+.Dq secure
 option from ttye0 in the
 .Xr ttys 5
 file.
 .Pp
-Another useful option that may be specified is the "serial console"
+Another useful option that may be specified is the
+.Dq serial console
 option.  This will allow a serial device (terminal or computer) to
 act as a console for the system.  This device must be configured to
 use 9600 baud, eight bits, no parity, and one stop bit (9600-8N1).
diff --git a/sbin/reboot/boot_pmax.8 b/sbin/reboot/boot_pmax.8
index 18323300d7f..b2919f7657f 100644
--- a/sbin/reboot/boot_pmax.8
+++ b/sbin/reboot/boot_pmax.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_pmax.8,v 1.8 1998/09/24 07:08:38 pjanzen Exp $
+.\"	$OpenBSD: boot_pmax.8,v 1.9 1998/11/11 22:19:59 aaron Exp $
 .\"	$NetBSD: boot_pmax.8,v 1.1 1995/04/25 23:55:11 mellon Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -53,20 +53,22 @@ it is necessary to read it in from disk or tape
 each time it is to be bootstrapped.
 .Pp
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will boot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 At power up, all DECstation ROMs consult the
 .Nm haltaction
 environment
 variable in EEPROM to determine whether or not to attempt an automatic
 boot.  If this
-variable is set to ``h'', the ROM prints a prompt on the console and
-waits for user commands.  If set to ``b'', the ROM attempts to autoboot.
+variable is set to
+.Dq h ,
+the ROM prints a prompt on the console and
+waits for user commands.  If set to
+.Dq b ,
+the ROM attempts to autoboot.
 .Pp
 On the DECstation 2100 and 3100, the path used for automatic booting is
 stored in the
@@ -75,9 +77,15 @@ environment variable.  The path is made up of a
 device type specifier (e.g., rz, tz, mop or tftp), followed by
 a triplet in the form (x,y,z), followed by a filename to load.
 .Pp
-Within the triplet, ``x'' is the controller (always 0), ``y'' is the SCSI ID of
+Within the triplet,
+.Dq x
+is the controller (always 0),
+.Dq y
+is the SCSI ID of
 the drive to
-boot from or 0 for net boots, and ``z'' is the partition to boot from
+boot from or 0 for net boots, and
+.Dq z
+is the partition to boot from
 (usually 0 for SCSI devices, always zero for network booting).
 For network boots, () may be specified instead of (0,0,0).
 .Pp
@@ -164,8 +172,11 @@ TurboChannel option by typing
 followed by the slot number of that
 option.
 .Pp
-For SCSI devices, the option-specific device identifier is either ``rz#'' for
-disks or ``tz#'' for tapes, where # is the SCSI ID of the device.  For network
+For SCSI devices, the option-specific device identifier is either
+.Dq rz#
+for disks or
+.Dq tz#
+for tapes, where # is the SCSI ID of the device.  For network
 devices, the option-specific protocol identifier is either mop or tftp.
 Filename requirements are as for the DECstation 2100 and 3100.
 .Pp
diff --git a/sbin/reboot/boot_sparc.8 b/sbin/reboot/boot_sparc.8
index d92e7f01c1f..506c2f01774 100644
--- a/sbin/reboot/boot_sparc.8
+++ b/sbin/reboot/boot_sparc.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_sparc.8,v 1.6 1998/09/17 04:15:00 aaron Exp $
+.\"	$OpenBSD: boot_sparc.8,v 1.7 1998/11/11 22:20:00 aaron Exp $
 .\"	$NetBSD: boot_sparc.8,v 1.4 1995/04/25 11:37:25 pk Exp $
 .\"
 .\" Copyright (c) 1992, 1993
@@ -48,7 +48,6 @@ bootstrapping procedures
 .Op Fl q
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed
 (as described in
@@ -56,13 +55,16 @@ An automatic consistency check of the file systems will be performed
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 The SPARC system currently uses the SunOS bootstrap loaders.
 This will be changed in a future version of the system.
 The SunOS boot will attempt to load
 .Pa bsd
-from partition ``a'' of the boot device,
-which must currently be an ``sd'' disk.
+from partition
+.Dq a
+of the boot device,
+which must currently be an
+.Dq sd
+disk.
 .Pp
 The
 .Fl s
@@ -78,30 +80,52 @@ and the primary swap partition.
 .\".Xr kgdb 8 .
 Other flags are currently ignored.
 .Pp
-The SPARC boot ROM comes in two flavours: an ``old-style'' ROM is used in
-sun4 machines, while a ``new-style'' ROM can be found on sun4c and sun4m models.
-The ``new-style'' SPARC boot ROM is a full-featured Forth system with emacs
-key bindings. It can be put in ``old-style'' user-interface compatibility
-mode (in which case it shows a simple `>' prompt), but this is essentially
-useless. However, by default the ROM runs in old-mode; to enter new-mode type `n'.
-The ROM then shows a Forth-style `ok' prompt. It is recommended to have
-the ROM always start in its native ``new-style'' mode. Utter the following
+The SPARC boot ROM comes in two flavours: an
+.Dq old-style
+ROM is used in
+sun4 machines, while a
+.Dq new-style
+ROM can be found on sun4c and sun4m models.
+The
+.Dq new-style
+SPARC boot ROM is a full-featured Forth system with emacs
+key bindings. It can be put in
+.Dq old-style
+user-interface compatibility
+mode (in which case it shows a simple
+.Dq \&>
+prompt), but this is essentially
+useless. However, by default the ROM runs in old-mode; to enter new-mode type
+.Dq n .
+The ROM then shows a Forth-style
+.Dq ok
+prompt. It is recommended to have
+the ROM always start in its native
+.Dq new-style
+mode. Utter the following
 incantation in new-mode to force the ROM to always start in new-mode:
 .Pp
 .Em \	ok
 setenv sunmon-compat? false
 .Pp
-The ROM will normally load the kernel from "sd(0,0,0)bsd". To change the
+The ROM will normally load the kernel from
+.Dq sd(0,0,0)bsd .
+To change the
 default so that OpenBSD will be loaded, type the following:
 .Pp
 .Em \	ok
 setenv boot-from sd(0,0,0)bsd
 .Pp
-At any time you can break back to the ROM by pressing the `L1' and `a'
+At any time you can break back to the ROM by pressing the
+.Dq L1
+and
+.Dq a
 keys at the same time (if the console is a serial port the same is
-achieved by sending a `break').
+achieved by sending a
+.Dq break ) .
 If you do this accidentally you can continue whatever was in progress
-by typing `go'.
+by typing
+.Dq go .
 .Pp
 .Sh FILES
 .Bl -tag -width /bsdxx -compact
diff --git a/sbin/reboot/boot_sun3.8 b/sbin/reboot/boot_sun3.8
index 8f050a286cc..370d74589ec 100644
--- a/sbin/reboot/boot_sun3.8
+++ b/sbin/reboot/boot_sun3.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_sun3.8,v 1.5 1998/09/17 04:15:01 aaron Exp $
+.\"	$OpenBSD: boot_sun3.8,v 1.6 1998/11/11 22:20:00 aaron Exp $
 .\"	$NetBSD: boot_sun3.8,v 1.1 1995/08/08 20:46:20 gwr Exp $
 .\"
 .\" Copyright (c) 1992, 1993
@@ -48,7 +48,6 @@ bootstrapping procedures
 .Op Fl q
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed
 as described in
@@ -56,13 +55,16 @@ as described in
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 A disk-boot program
 .Pq Pa /usr/mdec/ufsboot
 will attempt to load
 .Pa bsd
-from partition ``a'' of the boot device,
-which must currently be an ``sd'' disk.
+from partition
+.Dq a
+of the boot device,
+which must currently be an
+.Dq sd
+disk.
 Alternatively, the network boot program
 .Pq Pa /usr/mdec/netboot
 will load
@@ -84,11 +86,17 @@ Here it waits for a kernel debugger connect; see
 .Xr ddb 8 .
 Other flags are currently ignored.
 .Pp
-At any time you can break back to the ROM by pressing the `L1' and `a'
+At any time you can break back to the ROM by pressing the
+.Dq L1
+and
+.Dq a
 keys at the same time (if the console is a serial port the same is
-achieved by sending a `break').
+achieved by sending a
+.Dq break ) .
 If you do this accidentally you can continue whatever was in progress
-by typing `c' followed by the return key.
+by typing
+.Dq c
+followed by the return key.
 .Pp
 .Sh FILES
 .Bl -tag -width /usr/mdec/installboot -compact
diff --git a/sbin/reboot/boot_vax.8 b/sbin/reboot/boot_vax.8
index a81c4d54ab3..2745fcf258b 100644
--- a/sbin/reboot/boot_vax.8
+++ b/sbin/reboot/boot_vax.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_vax.8,v 1.6 1998/09/24 07:08:38 pjanzen Exp $
+.\"	$OpenBSD: boot_vax.8,v 1.7 1998/11/11 22:20:00 aaron Exp $
 .\"	$NetBSD: boot_vax.8,v 1.3 1995/04/23 10:33:39 cgd Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
@@ -43,14 +43,12 @@
 system bootstrapping procedures
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 Provided the auto-restart is enabled on the machine's front panel,
 an automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 These are processor-type dependent.
 On an 11/780, there are two floppy files for each disk controller,
 both of which cause boots from unit 0 of the root file system
@@ -159,11 +157,17 @@ of 2 causes the boot program to come up single-user,
 and an
 .Ar n
 of 3 causes both of these actions to occur.
-The ``DM'' specifies RK07, the ``A'' represents the adaptor number
+The
+.Dq DM
+specifies RK07, the
+.Dq A
+represents the adaptor number
 .Pf ( Tn UNIBUS
 or
 .Tn MASSBUS ) ,
-and the ``0'' is the drive unit number.
+and the
+.Dq 0
+is the drive unit number.
 Other disk types which may be used are DB
 .Pq Tn MASSBUS ,
 DD (TU58),
@@ -264,34 +268,34 @@ to boot from a file system which starts at cylinder 0
 of unit 0 of a
 .Tn MASSBUS
 disk, type
-.Ql hp(0,0)bsd
+.Dq hp(0,0)bsd
 at the boot prompt;
-.Ql hp(2,0,1,0)bsd
+.Dq hp(2,0,1,0)bsd
 would specify drive 1 on
 .Tn MASSBUS
 adaptor 2;
-.Ql up(0,0)bsd
+.Dq up(0,0)bsd
 would specify a
 .Tn UNIBUS
 drive,
-.Ql hk(0,0)bsd
+.Dq hk(0,0)bsd
 would specify
 an RK07 disk drive,
-.Ql ra(1,0,0,0)bsd
+.Dq ra(1,0,0,0)bsd
 would specify a
 .Tn UDA50
 disk drive on a second
 .Tn UNIBUS ,
 and
-.Ql rb(0,0)bsd
+.Dq rb(0,0)bsd
 would specify a
 disk on a 730
 .Tn IDC .
 For tapes, the minor device number gives a file offset;
-.Ql mt(1,2,3,4)
+.Dq mt(1,2,3,4)
 would specify the fifth file on slave 3 of the formatter
 at
-.Ql drive
+.Dq drive
 2 on mba 1.
 .Pp
 On an 11/750 with patchable control store,
diff --git a/sbin/reboot/boot_x68k.8 b/sbin/reboot/boot_x68k.8
index 836f883e18e..1a7a69a2a6c 100644
--- a/sbin/reboot/boot_x68k.8
+++ b/sbin/reboot/boot_x68k.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_x68k.8,v 1.5 1998/09/17 04:15:01 aaron Exp $
+.\"	$OpenBSD: boot_x68k.8,v 1.6 1998/11/11 22:20:00 aaron Exp $
 .\"	$NetBSD: boot_x68k.8,v 1.1 1996/06/15 18:54:22 oki Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
@@ -43,20 +43,20 @@
 system bootstrapping procedures
 .Sh DESCRIPTION
 .Ss Power fail and crash recovery
-.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
 .Ss Cold starts
-.Pp
 The X68000/X68030 system boots from the device
 which is determined by the configuration of
 battery-backuped SRAM.
 By default, the boot ROM attempts to boot from a
 floppy disk drive (from 0 to 3) first,
 and then from a hard disk (SASI or SCSI).
-On the OpenBSD/X68k, booting from partition ``a'' of SCSI disks (sd?a) 
+On the OpenBSD/X68k, booting from partition
+.Dq a
+of SCSI disks (sd?a) 
 and 2HD floppy disks (fd?a, fd?c) is currently supported.
 .Pp
 First, the initial program loader of IOCS ROM or SCSI disk