[src/netbsd-1-5]: src/distrib/notes/macppc Pull up revision 1.13 (requested b...

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

details:   https://anonhg.NetBSD.org/src/rev/803bf822dcd5
branches:  netbsd-1-5
changeset: 491810:803bf822dcd5
user:      he <he%NetBSD.org@localhost>
date:      Sat May 26 17:34:39 2001 +0000

description:
Pull up revision 1.13 (requested by mbw):
  Minor cleanups.

diffstat:

 distrib/notes/macppc/hardware |  19 ++++++++++---------
 distrib/notes/macppc/install  |  24 ++++++++++++------------
 2 files changed, 22 insertions(+), 21 deletions(-)

diffs (153 lines):

diff -r d210051ccf35 -r 803bf822dcd5 distrib/notes/macppc/hardware
--- a/distrib/notes/macppc/hardware     Sat May 26 17:13:55 2001 +0000
+++ b/distrib/notes/macppc/hardware     Sat May 26 17:34:39 2001 +0000
@@ -1,4 +1,4 @@
-.\"$NetBSD: hardware,v 1.3.4.5 2001/05/26 16:39:39 he Exp $
+.\"$NetBSD: hardware,v 1.3.4.6 2001/05/26 17:34:39 he Exp $
 .
 Currently,
 .Nx*M
@@ -39,12 +39,12 @@
 .Nx
 will run on this system.
 .Pp
-The minimal configuration requires 8 MB of RAM and ~80 MB of disk space.
+The minimal configuration requires 16 MB of RAM and ~80 MB of disk space.
 To install the entire system requires much more disk space, and to run
 X or compile the system, more RAM is recommended, as
 .Nx
-with 8 MB of RAM is very slow. Note that until you have
-around 16 MB of RAM, getting more RAM is more important than getting a
+with 16 MB of RAM is very slow. Note that until you have
+around 32 MB of RAM, getting more RAM is more important than getting a
 faster CPU.
 .
 .Ss2 Supported models
@@ -298,8 +298,9 @@
 Several models have been reported to not work with
 .Nx
 if the on-board video is in use, such as the Performa 54xx, 6360, 6400,
-PowerMacintosh 9500/150, 9500/180, 9500/200, PowerComputing PowerTower, and
-UMAX C600 and Apus 3000
+PowerComputing PowerTower, and UMAX C600 and Apus 3000.  Also, the video
+card that shipped with the PowerMacintosh 9500/150, 9500/180, and 9500/200
+systems is reported to have the same problem.
 .Note)
 .Pp
 .It
@@ -423,14 +424,14 @@
 .
 Each version of Open Firmware supports different devices and media that you
 may boot from.  We define the terms
-.Dq bootable media
+.Dq "bootable media"
 as the media (hard drive, CD-R, ethernet) that will be used to bootstrap
 your \*M system into
 .Nx No Ns ,
 and
-.Dq distribution sets
+.Dq "distribution sets"
 or
-.Dq distribution media
+.Dq "distribution media"
 as the media (hard drive, CD-R, ethernet) that contains the files that
 will be installed to generate a working 
 .Nx
diff -r d210051ccf35 -r 803bf822dcd5 distrib/notes/macppc/install
--- a/distrib/notes/macppc/install      Sat May 26 17:13:55 2001 +0000
+++ b/distrib/notes/macppc/install      Sat May 26 17:34:39 2001 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: install,v 1.2.10.6 2001/05/26 16:39:20 he Exp $
+.\"    $NetBSD: install,v 1.2.10.7 2001/05/26 17:34:56 he Exp $
 .
 .Ss2 Booting the installer
 .
@@ -23,7 +23,7 @@
 .Li kernel_location
 is either a filename if the kernel is on the same partition as the
 bootloader, or another complete
-.Sq Li device:partition,filename .
+.Sq Li "device:partition,filename" .
 And, there's no reason (other than Open Firmware bugginess) that you can't
 specify an entirely different device for the kernel.
 For instance, you could have a
@@ -86,13 +86,13 @@
 .
 Here are some examples of the commands you might use to boot your system:
 .(bullet
-.Em Floppy disk
+.Em "Floppy disk"
 .br
 (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open 
 Firmware 2.4)
 .Pp
 The floppy disk has a
-.Sq partition zero
+.Sq "partition zero"
 bootloader. 
 .(Note
 This is not a normal
@@ -119,7 +119,7 @@
 Or you may be more specific,
 specifying the bootloader filename and the kernel name:
 .Pp
-.Dl 0 > Ic boot "enet:,ofwboot.xcf enet:,netbsd.ram.gz"
+.Dl 0 > Ic "boot enet:,ofwboot.xcf enet:,netbsd.ram.gz"
 .(Note
 Some Open Firmware 1.0.5 machines do not retrieve the BOOTP information
 correctly. These machines cannot netboot.
@@ -136,7 +136,7 @@
 Or you may be more specific,
 specifying the bootloader filename and the kernel name:
 .Pp
-.Dl 0 > Ic boot "enet:0,ofwboot.xcf enet:0,netbsd.ram.gz"
+.Dl 0 > Ic "boot enet:0,ofwboot.xcf enet:0,netbsd.ram.gz"
 .It
 .Em CD-ROM
 .br
@@ -189,15 +189,15 @@
 .Dl 0 > Ic "boot ide1/disk@0:0,OFWBOOT.XCF NETBSD.RAM"
 .Dl 0 > Ic "boot cd:0,OFWBOOT.XCF NETBSD.RAM"
 .It
-.Em IDE or SCSI drive with a
-.Sq partition zero
+.Em "IDE or SCSI drive with a"
+.Sq "partition zero"
 bootloader
 .br
 (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
 Firmware 2.4)
 .Pp
 You do not specify a file to load, since the
-.Sq partition zero
+.Sq "partition zero"
 booloader knows what to do. You would boot such a system if you have dumped
 the boot floppy image to your drive, or if you have an already-installed
 .Nx*M
@@ -216,7 +216,7 @@
 .Dl 0 > Ic "boot ide0/disk@0:0"
 .Dl 0 > Ic "boot zip:0"
 .It
-.Em IDE or SCSI drive from an HFS or HFS+ partition
+.Em "IDE or SCSI drive from an HFS or HFS+ partition"
 .br
 (Open Firmware 2.4, Open Firmware 3)
 .Pp
@@ -478,7 +478,7 @@
 .Nx
 from the media of your choice.  First, make sure you know what command you
 need to boot (see above).  If you are using a 
-.Sq partition zero
+.Sq "partition zero"
 style boot scheme, you would type something like the following:
 .Pp
 .Dl 0 > Ic "setenv auto-boot? true"
@@ -496,7 +496,7 @@
 .Dl 0 > Ic "setenv boot-command begin ['] boot catch 1000 ms cr again"
 .Pp
 If you are not using a
-.Sq partition zero
+.Sq "partition zero"
 style boot scheme, then you can still plug in all the information you
 need:
 .Pp