Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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



details:   https://anonhg.NetBSD.org/src/rev/db4f07409322
branches:  trunk
changeset: 533443:db4f07409322
user:      lukem <lukem%NetBSD.org@localhost>
date:      Sun Jun 30 12:57:29 2002 +0000

description:
clean up whitespace and formatting

diffstat:

 distrib/notes/sun2/hardware   |  20 ++++++----
 distrib/notes/sun2/install    |  76 ++++++++++++++++++++++++-----------------
 distrib/notes/sun2/upgrade    |  28 ++++++++-------
 distrib/notes/sun2/xfer       |  74 +++++++++++++++++++++-------------------
 distrib/notes/sun3/hardware   |  16 ++++---
 distrib/notes/sun3/install    |  78 ++++++++++++++++++++++++------------------
 distrib/notes/sun3/prep       |  16 ++++---
 distrib/notes/sun3/upgrade    |  25 +++++++------
 distrib/notes/sun3/xfer       |  76 ++++++++++++++++++++++-------------------
 distrib/notes/vax/install     |  22 +++++++----
 distrib/notes/vax/upgrade     |  20 ++++++----
 distrib/notes/vax/xfer        |  48 +++++++++++++++-----------
 distrib/notes/walnut/hardware |  26 +++++++------
 distrib/notes/walnut/legal    |   4 +-
 distrib/notes/walnut/prep     |   6 +-
 distrib/notes/walnut/whatis   |   4 +-
 16 files changed, 300 insertions(+), 239 deletions(-)

diffs (truncated from 1312 to 300 lines):

diff -r 970e7c249ae0 -r db4f07409322 distrib/notes/sun2/hardware
--- a/distrib/notes/sun2/hardware       Sun Jun 30 12:49:29 2002 +0000
+++ b/distrib/notes/sun2/hardware       Sun Jun 30 12:57:29 2002 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: hardware,v 1.2 2002/05/08 16:32:55 fredette Exp $
+.\"    $NetBSD: hardware,v 1.3 2002/06/30 12:57:29 lukem Exp $
 .
 .Nx*M
 \*V runs on Multibus Sun2 machines, including:
@@ -7,14 +7,15 @@
 .El
 .Pp
 The minimal configuration requires 4 MB of RAM and about 130 MB of disk
-space.  To install the entire system requires much more disk space
+space.
+To install the entire system requires much more disk space
 (approx. 100 MB additional space is necessary for full sources).
-To compile the system, more RAM is recommended.  Good
-performance requires 7 MB of RAM.
+To compile the system, more RAM is recommended.
+Good performance requires 7 MB of RAM.
 .Pp
 Here is a table of recommended HD partition sizes for a full install:
-.Bl -column -offset indent Partition Suggested Needed 
-.It Partition Ta Suggested Ta Needed 
+.Bl -column -offset indent Partition Suggested Needed
+.It Partition Ta Suggested Ta Needed
 .It /\ (root) Ta "20 MB"   Ta "15 MB"
 .It /usr      Ta "210 MB"  Ta "110 MB"
 .It /var      Ta "20 MB"   Ta "5 MB"
@@ -27,7 +28,8 @@
 As you may note, the recommended size of
 .Pa /usr
 is 100 MB greater than
-needed. This is to leave room for a kernel source and compile tree as
+needed.
+This is to leave room for a kernel source and compile tree as
 you will probably want to compile your own kernel.
 .Li ( GENERIC
 is large and bulky to accommodate all people).
@@ -35,8 +37,8 @@
 Note that the \*M installation procedure uses a
 .Em miniroot
 image
-which is placed into the swap area of the disk.  The swap partition
-must be at least as large as the miniroot image (12 MB).
+which is placed into the swap area of the disk.
+The swap partition must be at least as large as the miniroot image (12 MB).
 .
 .Ss2 Supported hardware
 .(bullet -offset indent
diff -r 970e7c249ae0 -r db4f07409322 distrib/notes/sun2/install
--- a/distrib/notes/sun2/install        Sun Jun 30 12:49:29 2002 +0000
+++ b/distrib/notes/sun2/install        Sun Jun 30 12:57:29 2002 +0000
@@ -1,6 +1,6 @@
-.\"    $NetBSD: install,v 1.3 2002/05/08 16:32:55 fredette Exp $
+.\"    $NetBSD: install,v 1.4 2002/06/30 12:57:29 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,11 +39,11 @@
 .Pp
 There are several ways to install
 .Nx
-onto your disk. If your
-machine has a tape drive the easiest way is
+onto your disk.
+If your machine has a tape drive the easiest way is
 .Sx "Installing from tape"
-(details below). If your machine is on a network with a suitable
-NFS server, then
+(details below).
+If your machine is on a network with a suitable NFS server, then
 .Sx "Installing from NFS"
 is the next best method.
 Otherwise, if you have another
@@ -62,14 +62,15 @@
 \*V boot tape as described in the section
 entitled
 .Sx "Creating boot/install tapes"
-and boot the tape. At the PROM
-monitor prompt, use one of the commands:
+and boot the tape.
+At the PROM monitor prompt, use one of the commands:
 .Pp
 .Dl \*> Ns Ic "b st()"
 .Dl \*> Ns Ic "b st(0,8,0)"
 .Pp
 The first example will use the tape on SCSI target 4, where the
-second will use SCSI target 5. The
+second will use SCSI target 5.
+The
 .Li \*>
 is the monitor prompt.
 .Pp
@@ -107,8 +108,8 @@
 .disp)
 .Pp
 Copy the miniroot as described in the welcome message, and
-reboot from that just installed miniroot. See the section
-entitled
+reboot from that just installed miniroot.
+See the section entitled
 .Sx Booting the miniroot
 for details.
 .
@@ -124,8 +125,8 @@
 First, at the
 .Tn Sun
 PROM monitor prompt, enter a boot command
-using the network interface as the boot device.  If your machine
-has Intel Ethernet, this is
+using the network interface as the boot device.
+If your machine has Intel Ethernet, this is
 .Em ie ,
 and if it has 3Com Ethernet, this is
 .Em ec .
@@ -137,15 +138,18 @@
 After the boot program loads the RAMDISK kernel, you should
 see the welcome screen as shown in the
 .Sx Installing from tape
-section above. You must configure the network interface before you
-can use any network resources. For example the command:
+section above.
+You must configure the network interface before you
+can use any network resources.
+For example the command:
 .Pp
 .Dl ssh\*> Ic "ifconfig ie0 inet 192.233.20.198 up"
 .Pp
-will bring up the network interface with that address. The next
-step is to copy the miniroot from your server. This can be done
-using either NFS or remote shell. (In the examples that follow,
-the server has IP address 192.233.20.195.) You may then need to
+will bring up the network interface with that address.
+The next step is to copy the miniroot from your server.
+This can be done using either NFS or remote shell.
+(In the examples that follow, the server has IP address 192.233.20.195.)
+You may then need to
 add a default route if the server is on a different subnet:
 .Pp
 .Dl ssh\*> Ic "route add default 192.233.20.255 1"
@@ -159,18 +163,21 @@
 .Dl ssh\*> Ic "mount -o rdonly,-r=1024 192.233.20.195:/server/path /mnt"
 .Pp
 The procedure is simpler and much faster if you have space for an expanded
-(not compressed) copy of the miniroot image. In that case:
+(not compressed) copy of the miniroot image.
+In that case:
 .Pp
 .Dl ssh\*> Ic "dd if=/mnt/miniroot.fs of=/dev/rsd0b bs=8k"
 .Pp
 Otherwise, you will need to use
 .Ic zcat
-to expand the miniroot image while copying. This is tricky because the
+to expand the miniroot image while copying.
+This is tricky because the
 .Ic ssh
 program
 (small shell) does not handle
 .Xr sh 1
-pipeline syntax. Instead,
+pipeline syntax.
+Instead,
 you first run the reader in the background with its input set
 to
 .Pa /dev/pipe
@@ -182,19 +189,21 @@
 .Dl ssh\*> Ic "run -o /dev/pipe zcat /mnt/install/miniroot.fs.gz"
 .Pp
 To load the miniroot using rsh to the server, you would use a
-pair of commands similar to the above. Here is another example:
+pair of commands similar to the above.
+Here is another example:
 .Pp
 .Dl ssh\*> Ic "run -b dd if=/dev/pipe of=/dev/rsd0b obs=8k"
 .Dl ssh\*> Ic "run -o /dev/pipe rsh 192.233.20.195 zcat miniroot.fs.gz"
 .Pp
 Note that decompression on a sun2 is
 .Em extremely
-slow, be prepared to wait.  For this reason, expanding the miniroot
+slow, be prepared to wait.
+For this reason, expanding the miniroot
 image on the NFS server is highly recommended.
 .Pp
 Once the miniroot has been copied using one of the above methods,
-you reboot from that just installed miniroot. See the section
-entitled
+you reboot from that just installed miniroot.
+See the section entitled
 .Sx Booting the miniroot
 for details.
 .
@@ -221,7 +230,8 @@
 Next, bring
 .Tn SunOS
 down to single user mode to insure that nothing
-will be using the swap space on your drive. To be extra safe, reboot
+will be using the swap space on your drive.
+To be extra safe, reboot
 the machine into single-user mode rather than using the
 .Ic shutdown
 command.
@@ -267,9 +277,9 @@
 .
 .Ss2 Miniroot install program
 .
-The miniroot's install program is very simple to use. It will guide
-you through the entire process, and is well automated. Additional
-improvements are planned for future releases.
+The miniroot's install program is very simple to use.
+It will guide you through the entire process, and is well automated.
+Additional improvements are planned for future releases.
 .Pp
 The miniroot's install program will:
 .(bullet -offset indent
@@ -281,7 +291,8 @@
 .It
 Allow you to set up your system's network configuration.
 Remember to specify host names without the domain name
-appended to the end. For example use
+appended to the end.
+For example use
 .Li foo
 instead of
 .Li foo.bar.org .
@@ -290,7 +301,8 @@
 be able to re-configure that interface by simply selecting
 it for configuration again.
 .It
-Mount target file systems. You will be given the opportunity
+Mount target file systems.
+You will be given the opportunity
 to manually edit the resulting
 .Pa /etc/fstab .
 .It
diff -r 970e7c249ae0 -r db4f07409322 distrib/notes/sun2/upgrade
--- a/distrib/notes/sun2/upgrade        Sun Jun 30 12:49:29 2002 +0000
+++ b/distrib/notes/sun2/upgrade        Sun Jun 30 12:57:29 2002 +0000
@@ -1,6 +1,6 @@
-.\"    $NetBSD: upgrade,v 1.2 2002/05/08 04:13:15 lukem Exp $
+.\"    $NetBSD: upgrade,v 1.3 2002/06/30 12:57:29 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
@@ -36,12 +36,13 @@
 It is possible to easily upgrade your existing
 .Nx*M
 system
-using the upgrade program in the miniroot. If you wish to upgrade
-your system by this method, simply select the
+using the upgrade program in the miniroot.
+If you wish to upgrade your system by this method, simply select the
 .Ic upgrade
 option once
-the miniroot has booted. The upgrade program with then guide you
-through the procedure. The upgrade program will:
+the miniroot has booted.
+The upgrade program with then guide you through the procedure.
+The upgrade program will:
 .(bullet -offset indent
 Enable the network based on your system's current network configuration.
 .It
@@ -73,16 +74,16 @@
 of upgrading your system.
 .\}
 .Pp
-However, it is possible to upgrade your system
-manually. To do this, follow the following procedure:
+However, it is possible to upgrade your system manually.
+To do this, follow the following procedure:
 .(bullet -offset indent
 Place
 .Em at least
 the
 .Sy base
 binary set in a file system
-accessible to the target machine. A local file system
-is preferred, since the NFS subsystem in the
+accessible to the target machine.
+A local file system is preferred, since the NFS subsystem in the
 .Nx \*V
 kernel may be incompatible with your old binaries.
 .It
@@ -106,8 +107,8 @@
 or
 .Pa /usr/share
 on an NFS server, you
-will want to mount those file systems as well. To do
-this, you will need to enable the network:
+will want to mount those file systems as well.
+To do this, you will need to enable the network:
 .Pp
 .Dl # Ic "sh /etc/rc.d/network start"



Home | Main Index | Thread Index | Old Index