[src/trunk]: src/distrib/notes/sparc64 clean up whitespace and formatting

[lukem <lukem%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/881bc6c549bd
branches:  trunk
changeset: 533441:881bc6c549bd
user:      lukem <lukem%NetBSD.org@localhost>
date:      Sun Jun 30 12:48:46 2002 +0000

description:
clean up whitespace and formatting

diffstat:

 distrib/notes/sparc64/hardware |    4 +-
 distrib/notes/sparc64/install  |  206 ++++++++++++++++++++++++----------------
 distrib/notes/sparc64/prep     |   11 +-
 distrib/notes/sparc64/upgrade  |    7 +-
 4 files changed, 135 insertions(+), 93 deletions(-)

diffs (truncated from 530 to 300 lines):

diff -r 496f5d25b38a -r 881bc6c549bd distrib/notes/sparc64/hardware
--- a/distrib/notes/sparc64/hardware    Sun Jun 30 12:34:38 2002 +0000
+++ b/distrib/notes/sparc64/hardware    Sun Jun 30 12:48:46 2002 +0000
@@ -1,8 +1,8 @@
-.\"    $NetBSD: hardware,v 1.9 2002/06/18 01:41:26 eeh Exp $
+.\"    $NetBSD: hardware,v 1.10 2002/06/30 12:48:46 lukem Exp $
 .
 .Ss2 Supported machines
 .(bullet -offset indent
-Sbus-based UltraSPARC systems (the Ultra 1, Ultra 1 Creator/Ultra1 Creator3D, 
+Sbus-based UltraSPARC systems (the Ultra 1, Ultra 1 Creator/Ultra1 Creator3D,
 Ultra 2/Ultra 2 Creator/Ultra 2 Creator 3D)
 .It
 PCI-based UltraSPARC systems (known to work on the Ultra 5, Ultra 10, Ultra 30
diff -r 496f5d25b38a -r 881bc6c549bd distrib/notes/sparc64/install
--- a/distrib/notes/sparc64/install     Sun Jun 30 12:34:38 2002 +0000
+++ b/distrib/notes/sparc64/install     Sun Jun 30 12:48:46 2002 +0000
@@ -1,6 +1,6 @@
-.\"    $NetBSD: install,v 1.13 2002/06/18 01:42:10 eeh Exp $
+.\"    $NetBSD: install,v 1.14 2002/06/30 12:48:46 lukem Exp $
 .\"
-.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
+.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
@@ -39,15 +39,18 @@
 .Pp
 There are several ways to install
 .Nx
-onto a disk. The easiest way in terms of preliminary setup is to install
-from CDROM.  If you don't have access to a CDROM or CDROM burner, you
+onto a disk.
+The easiest way in terms of preliminary setup is to install from CDROM.
+If you don't have access to a CDROM or CDROM burner, you
 can use a miniroot image that can be booted off your local disk's swap
-partition. Alternatively, if your UltraSPARC is hooked up in a network 
-you can find a server and arrange for a diskless setup which is a convenient 
-way to install on a machine whose disk does not currently hold a usable 
-operating system (see the section `Installing
-.Nx
-by using a diskless setup' below).  If you have problems with these, it
+partition.
+Alternatively, if your UltraSPARC is hooked up in a network
+you can find a server and arrange for a diskless setup which is a convenient
+way to install on a machine whose disk does not currently hold a usable
+operating system (see the section
+.Sx Installing NetBSD by using a diskless setup
+below).
+If you have problems with these, it
 is possible to install NetBSD from Solaris (see the section `Installing
 .Nx
 using Solaris' below).
@@ -55,8 +58,10 @@
 .Ss2 Installing NetBSD from CDROM
 .
 Installing from CDROM, whether it has the full distribution or just
-a kernel and sysinst is the least pinful way to install
-.Nx
+a kernel and
+.Ic sysinst
+is the least painful way to install
+.Nx .
 Simply insert the CDROM in the drive, power up the computer, and
 when you get to the
 .Pp
@@ -70,13 +75,14 @@
 .Ic L1
 or
 .Ic Stop
-key and the 
+key and the
 .Ic A
 key on the keyboard or send a break if your console is serial port
 to terminate the boot process.
 .Pp
 .Nx
-should then boot and you will have the opportunity to use sysinst.
+should then boot and you will have the opportunity to use
+.Ic sysinst .
 .
 .Ss2 Installing NetBSD by using the NetBSD miniroot
 .
@@ -85,14 +91,17 @@
 file system holding all utilities
 necessary to install
 .Nx
-on a local disk. It is distributed as a plain
+on a local disk.
+It is distributed as a plain
 file designed to be transferred to a raw disk partition from which it can
-be booted using the appropriate OpenBoot PROM command. Usually, the miniroot
-will be loaded into the swap partition of a disk. If needed, you can use any
-other unused partition, but remember that the partition will then not
+be booted using the appropriate OpenBoot PROM command.
+Usually, the miniroot will be loaded into the swap partition of a disk.
+If needed, you can use any other unused partition,
+but remember that the partition will then not
 available during the installation process.
 .Pp
-Loading the miniroot onto your raw partition is simple. On
+Loading the miniroot onto your raw partition is simple.
+On
 .Nx
 as well as
 .Tn Solaris
@@ -102,12 +111,13 @@
 .Pp
 (Here,
 .Li /dev/rdsk/c0t0d0s1
-is assumed to be your swap partition.) There's a
-potential problem here if
+is assumed to be your swap partition.)
+There's a potential problem here if
 .Pa /dev/rdsk/c0t0d0s1
 is actually in use as a swap
-partition by your currently running system. If you don't have another
-disk or partition to spare, you can usually get away with running this
+partition by your currently running system.
+If you don't have another disk or partition to spare,
+you can usually get away with running this
 command anyway after first booting into single-user mode to ensure a
 quiet system.
 .Pp
@@ -129,21 +139,24 @@
 The monitor boot command will cause the
 .Nx
 kernel contained in the
-miniroot image to be booted. After the initial probe messages you'll be
-asked to start the install or upgrade procedure. Proceed to the section
+miniroot image to be booted.
+After the initial probe messages you'll be
+asked to start the install or upgrade procedure.
+Proceed to the section
 .Sx Running the installation scripts
 below.
 .
 .Ss2 Installing NetBSD by using a diskless setup
 .
-First, you must setup a diskless client configuration on a server. If
-you are using a
+First, you must setup a diskless client configuration on a server.
+If you are using a
 .Nx
 system as the boot-server, have a look at the
 .Xr diskless 8
 manual page for guidelines on how to proceed with this.
 If the server runs another operating system, you'll have to consult
-documentation that came with it. (On
+documentation that came with it.
+(On
 .Tn SunOS
 systems,
 .Xr add_client 8
@@ -154,7 +167,8 @@
 instructed to boot
 .Sq "over the net" .
 It will look for a filename composed of the machine's IP address in
-hexadecimal.  For example, a machine which has been assigned IP address
+hexadecimal.
+For example, a machine which has been assigned IP address
 130.115.144.11, will make an TFTP request for
 .Pa 8273900B .
 Normally, this file is a symbolic link to an appropriate second-stage
@@ -173,41 +187,45 @@
 .Pp
 After the boot program has been loaded into memory and given control by
 the OpenBoot PROM, it starts locating the machine's remote root directory
-through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast
-on the local net. The answer to this request (if it comes in) contains
-the client's name. This name is used in next step, a BOOTPARAM GETFILE
-request - sent to the server that responded to the WHOAMI request -
+through the BOOTPARAM protocol.
+First a BOOTPARAM WHOAMI request is broadcast on the local net.
+The answer to this request (if it comes in) contains
+the client's name.
+This name is used in next step, a BOOTPARAM GETFILE
+request \(em sent to the server that responded to the WHOAMI request \(em
 requesting the name and address of the machine that will serve the client's
 root directory, as well as the path of the client's root on that server.
 .Pp
 Finally, this information (if it comes in) is used to issue a REMOTE MOUNT
 request to the client's root file system server, asking for an NFS file
-handle corresponding to the root file system. If successful, the boot
-program starts reading from the remote root file system in search of the
-kernel which is then read into memory.
+handle corresponding to the root file system.
+If successful, the boot program starts reading from the remote root
+file system in search of the kernel which is then read into memory.
 .Pp
 As noted above in the section
 .Sx Preparing your System for NetBSD Installation
 you have several options when choosing a location to store the installation
-filesets. However, the easiest way is to put the
+filesets.
+However, the easiest way is to put the
 .Pa *.tgz
 files you want
 to install into the root directory for your client on the server.
 .Pp
-From here there are two methods of netboot install.  The first is much
-simpler and is intended for clients with local disk that will be used for
-installation.  The second is intended for clients that will use a network
-boot normally.
+From here there are two methods of netboot install.
+The first is much simpler and is intended for clients with local disk
+that will be used for installation.
+The second is intended for clients that will use a network boot normally.
 .Pp
 If you are going to be installing onto local disk, place the
 .Pa netbsd.INSTALL.gz
 file, located in the
 .Pa binary/kernel
-directory, into the root directory for your machine.  The
+directory, into the root directory for your machine.
+The
 .Pa netbsd.INSTALL.gz
-file contains a kernel with an embedded ramdisk that has the basic 
-installer filesystem that is part of the normal miniroot.  Now you 
-need to boot your workstation
+file contains a kernel with an embedded ramdisk that has the basic
+installer filesystem that is part of the normal miniroot.
+Now you need to boot your workstation
 from the server by entering the following command at the monitor prompt:
 .Pp
 .Dl "ok boot net netbsd.INSTALL.gz"
@@ -215,8 +233,8 @@
 And then follow the install instructions.
 .Pp
 If you are going to be installing to NFS, be sure to read the section
-about preparing your system for installation.  If you have access to
-another
+about preparing your system for installation.
+If you have access to another
 .Nx
 machine, the
 .Xr diskless 8
@@ -226,16 +244,17 @@
 and
 .Pa etc.tgz
 sets on the server in the root
-directory for your machine. If you elect to use a separately NFS-mounted
-file system for
+directory for your machine.
+If you elect to use a separately NFS-mounted file system for
 .Pa /usr
 with your diskless setup, make sure the
 .Pa ./usr
 base
 files in
 .Pa base.tgz
-end up in the correct location. One way to do this is
-to temporarily use a loopback mount on the server, re-routing
+end up in the correct location.
+One way to do this is to temporarily use a loopback mount on the server,
+re-routing
 .Ar root Ns Pa /usr
 to your server's exported
 .Nx
@@ -259,8 +278,8 @@
 .Pp
 Now you must populate the
 .Pa /dev
-directory for your client. If your server
-runs
+directory for your client.
+If your server runs
 .Tn SunOS
 4.x, you can simply change your working directory to
 .Ar root Ns Pa /dev
@@ -272,11 +291,12 @@
 systems,
 .Ic MAKEDEV
 can also be used, but there'll be error
-messages about unknown user and groups. These errors are inconsequential
-for the purpose of installing
+messages about unknown user and groups.
+These errors are inconsequential for the purpose of installing
 .Nx .
 However, you may want to correct them
-if you plan to use the diskless setup regularly. In that case, you may re-run
+if you plan to use the diskless setup regularly.
+In that case, you may re-run
 .Ic MAKEDEV
 on your
 .Nx
@@ -307,7 +327,8 @@
 When using
 .Xr disklabel 8
 to edit disklabels the -e switch will invoke the editor on the
-label.  The -i switch will run an interactive session.
+label.
+The -i switch will run an interactive session.
 .Pp
 At this point, it's worth checking the disk label and partition sizes on
 the disk you want to install
@@ -319,7 +340,8 @@
 disklabels, so if your disk was previously used by
 .Tn SunOS
 there will be