[src/trunk]: src/distrib/notes clean up whitespace, formatting, copyrights

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

details:   https://anonhg.NetBSD.org/src/rev/492141179b9c
branches:  trunk
changeset: 533395:492141179b9c
user:      lukem <lukem%NetBSD.org@localhost>
date:      Sat Jun 29 09:33:10 2002 +0000

description:
clean up whitespace, formatting, copyrights

diffstat:

 distrib/notes/alpha/hardware |   26 ++++---
 distrib/notes/alpha/install  |  136 +++++++++++++++++++++++------------------
 distrib/notes/alpha/prep     |    5 +-
 distrib/notes/alpha/whatis   |    5 +-
 distrib/notes/amiga/hardware |   30 +++++----
 distrib/notes/amiga/install  |  137 ++++++++++++++++++++++++------------------
 distrib/notes/amiga/prep     |   64 ++++++++++---------
 distrib/notes/amiga/upgrade  |  113 ++++++++++++++++++++---------------
 8 files changed, 288 insertions(+), 228 deletions(-)

diffs (truncated from 1154 to 300 lines):

diff -r 03fec1dbd187 -r 492141179b9c distrib/notes/alpha/hardware
--- a/distrib/notes/alpha/hardware      Sat Jun 29 09:06:34 2002 +0000
+++ b/distrib/notes/alpha/hardware      Sat Jun 29 09:33:10 2002 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: hardware,v 1.12 2002/04/23 19:48:41 bouyer Exp $
+.\"    $NetBSD: hardware,v 1.13 2002/06/29 09:33:10 lukem Exp $
 .
 .Nx*M
 \*V runs on most of the
@@ -13,7 +13,8 @@
 boot
 .Tn "Windows NT" )
 by the fact that it has a command line interface,
-rather than a menu-driven interface. The SRM prompt is
+rather than a menu-driven interface.
+The SRM prompt is
 .Sq Li \*>\*>\*> .
 .Pp
 Some platforms have both the SRM console and
@@ -44,20 +45,22 @@
 .Nx
 has an extremely machine-independent device driver
 system, many device drivers are the same as used in other ports that
-use the same bus. For example, the
+use the same bus.
+For example, the
 .Em de
 network card driver is shared
-by the i386 and \*M ports. Some drivers on inspection appear as if
-they will work on the \*M but have not been tested because that
-hardware was not available to
+by the i386 and \*M ports.
+Some drivers on inspection appear as if they will work on the
+\*M but have not been tested because that hardware was not available to
 .Nx
 testers; these are marked as
 .Em UNTESTED
-below. If you have one of these devices, and it does work,
+below.
+If you have one of these devices, and it does work,
 please get in touch with
 .Mt port-\*M-maintainer%netbsd.org@localhost
-and let us know that it works. If it doesn't work, do the same thing and we
-can probably fix it pretty easily.
+and let us know that it works.
+If it doesn't work, do the same thing and we can probably fix it pretty easily.
 .
 .Ss2 Supported PCI bus devices
 .(bullet -offset indent
@@ -258,8 +261,9 @@
 SCSI and ATAPI CD-ROMs cd0, cd1, ...
         For each SCSI and IDE controller found, the SCSI or ATA(PI) devices
         present on the bus are probed in increasing ID order for SCSI and
-        master/slave order for ATA(PI). So the first SCSI drive found will
-        be called sd0, the second sd1, and so on ...
+        master/slave order for ATA(PI).
+       So the first SCSI drive found will be called sd0, the second sd1,
+       and so on ...
 
 3COM 3x59X or 3COM 3x90X PCI Ethernet boards
                 ep0     any     any     [you must assign an interrupt in your
diff -r 03fec1dbd187 -r 492141179b9c distrib/notes/alpha/install
--- a/distrib/notes/alpha/install       Sat Jun 29 09:06:34 2002 +0000
+++ b/distrib/notes/alpha/install       Sat Jun 29 09:33:10 2002 +0000
@@ -1,6 +1,6 @@
-.\"    $NetBSD: install,v 1.23 2002/02/16 18:17:04 he Exp $
+.\"    $NetBSD: install,v 1.24 2002/06/29 09:33:10 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
@@ -62,8 +62,8 @@
 disk set and then boot from the floppies, however, there
 are now six ways to boot the
 .Nx*M
-installation system! Each approach
-loads the exact same installation bits.
+installation system!
+Each approach loads the exact same installation bits.
 The six paths are:
 .Pp
 .
@@ -90,10 +90,12 @@
 Although booting from floppy is the usual path, the
 hard drive boot is useful if you have another operating system (and a spare
 drive) already installed, or if you don't mind swapping hard drives from
-box to box. CD and tape boots are nice and fast if you have a CD writer
+box to box.
+CD and tape boots are nice and fast if you have a CD writer
 or a tape format in common with another previously installed
 .Ul
-system. Finally, most versions of SRM can locate the
+system.
+Finally, most versions of SRM can locate the
 .Nx
 boot program
 .Ic netboot
@@ -148,7 +150,8 @@
 the
 .Ic rawrite.exe
 utility to transfer the image to a floppy
-disk. This utility is provided with the
+disk.
+This utility is provided with the
 .Nx Ns /i386
 install tools, under
 .Pa i386/installation/misc ;
@@ -180,7 +183,8 @@
 or
 .Tn DLT ,
 it is important
-to create the tape image with 512-byte records. Use a command like:
+to create the tape image with 512-byte records.
+Use a command like:
 .Pp
 .Dl # Ic "dd if=cdhdtape bs=512 of=/dev/rst0"
 .Pp
@@ -202,9 +206,9 @@
 contains
 .Pa netbsd.gz ;
 this is the same install kernel but without a bootable file system
-image wrapped around it. You can perform an complete reinstall
-by beginning it as an upgrade, and booting this kernel in the
-normal way off the root file system
+image wrapped around it.
+You can perform an complete reinstall by beginning it as an upgrade,
+and booting this kernel in the normal way off the root file system
 .Pq Pa /
 of a previous installation.
 .Pp
@@ -217,26 +221,28 @@
 Booting
 .Nx*M
 \*V over a network requires a BOOTP or
-DHCP server, a TFTP server and an NFS server. (These are usually
-all run on the same machine.) There are three basic stages to
-the boot:
+DHCP server, a TFTP server and an NFS server.
+(These are usually all run on the same machine.)
+There are three basic stages to the boot:
 .Pp
 .
 .
 .(bullet
 \*M console software sends a BOOTP request to get its
 own address, the address of the TFTP server and the file to
-download. It downloads this file, which is the second stage
-bootstrap, via TFTP and then executes it.
+download.
+It downloads this file, which is the second stage bootstrap,
+via TFTP and then executes it.
 .It
 The secondary boot program resends the BOOTP request, this
-time also locating the NFS server and root path. It mounts the
-root path via NFS and reads in and transfers to the kernel:
+time also locating the NFS server and root path.
+It mounts the root path via NFS and reads in and transfers to the kernel:
 .Pa /netbsd .
 .It
 The kernel probes and configures the devices, and then sends
 out another BOOTP request so it can find out its address, the NFS
-server, and path. It then mounts its root
+server, and path.
+It then mounts its root
 .Pq Pa /
 via NFS and continues.
 .bullet)
@@ -249,8 +255,8 @@
 .Nx
 snapshot or distribution
 into a directory on your server and NFS export that directory
-to the client. Make sure you put a kernel there as well, and
-create the device nodes in
+to the client.
+Make sure you put a kernel there as well, and create the device nodes in
 .Pa /dev
 with
 .Ic sh ./MAKEDEV all .
@@ -299,8 +305,8 @@
 .Ic netboot ,
 into an appropriately named file such as
 .Li boot.netbsd.\*M
-in the directory used by your TFTP server. If you extracted a full
-snapshot, you can get the netboot program from
+in the directory used by your TFTP server.
+If you extracted a full snapshot, you can get the netboot program from
 .Pa /usr/mdec/netboot ;
 if not, you can get this from the
 .Pa installation/netboot
@@ -356,14 +362,16 @@
 The only Ethernet device the console on most \*M systems
 knows how to boot from is the onboard Ethernet interface or a
 .Tn DEC
-Tulip (21040, 21041, 21140) PCI Ethernet card. Some
-older SMC 100 Mbps cards that use this chip have been known to
-work as well. Many older systems will not be able to use the
-newer 2.0 stepping of the 21140, however. If your system appears
-not to be receiving packets, this may be the problem. (You may
-or may not be able to update your firmware to fix this; see
+Tulip (21040, 21041, 21140) PCI Ethernet card.
+Some older SMC 100 Mbps cards that use this chip have been known to
+work as well.
+Many older systems will not be able to use the newer 2.0 stepping
+of the 21140, however.
+If your system appears not to be receiving packets, this may be the problem.
+(You may or may not be able to update your firmware to fix this; see
 the \*M port pages on www.netbsd.org for more information on
-this.) In general, 10 Mb cards from manufacturers other than
+this.)
+In general, 10 Mb cards from manufacturers other than
 .Tn DEC
 will work, and 100 Mb cards not from
 .Tn DEC
@@ -383,15 +391,17 @@
 .Em old SRM ,
 do not have a
 .Fl proto
-option and use different device names. They also tend to not netboot very
-well so you probably don't need to worry about this section. However, if you
-want to give it a try, note the following differences:
+option and use different device names.
+They also tend to not netboot very well so you probably don't
+need to worry about this section.
+However, if you want to give it a try, note the following differences:
 .(bullet -offset indent
 There is no
 .Fl proto
 argument, or
 .Ic ewa0_protocols
-variable. Old SRM uses bootp if the device name is given as
+variable.
+Old SRM uses bootp if the device name is given as
 .Sy ez0 .
 .It
 The use of the
@@ -434,7 +444,8 @@
 .Pp
 However, as stated above it is also possible to do the installation yourself
 from the shell, and in any case it is helpful to understand
-what the install script does. The procedure is:
+what the install script does.
+The procedure is:
 .Pp
 .
 .
@@ -490,8 +501,8 @@
 .Pp
 You may install
 on either a SCSI or an IDE disk; you will be prompted for
-the disk to install on. The disks in your system will be numbered
-starting at
+the disk to install on.
+The disks in your system will be numbered starting at
 .Em x Ns Li d0
 (where
 .Em x
@@ -504,7 +515,8 @@
 which ones are probed as which numbers.
 .Pp
 Once you've selected a disk to install on, you'll be prompted
-for the geometry. This is also displayed in the boot messages,
+for the geometry.
+This is also displayed in the boot messages,
 and you'll be given a chance to review the boot messages again
 to get the exact figures for the number of cylinders, heads
 and sectors.
@@ -515,7 +527,8 @@
 .Pp
 The swap partition is the second thing you specify, after the
 .Pa /
-(root) partition. Regardless of the size of your disk, you'll
+(root) partition.
+Regardless of the size of your disk, you'll
 want to specify a swap partition that's at least as large as
 the amount of RAM you have, and probably not less than 64 MB
 in any case.
@@ -531,22 +544,24 @@
 .Pa /
 (root) partition.
 .Pa /usr
-will need 150 MB or so if you're not installing X, 200 MB or so if you
-are. A typical organization is 50 MB for
+will need 150 MB or so if you're not installing X, 200 MB or so if you are.
+A typical organization is 50 MB for
 .Pa /
 (root), 150-250 MB for
 swap, and the remaining space for
 .Pa /usr .
 With enough swap space configured, you can make
 .Pa /tmp
-a nice, fast mfs. See
+a nice, fast mfs.
+See
 .Xr mount_mfs 8 ,
 and note that the mfs will require swap space for
 the largest planned amount of
 .Pa /tmp
-storage. It doesn't return