[src/netbsd-1-5]: src/distrib/notes/mvme68k Pullup 1.8 [scw]:

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

details:   https://anonhg.NetBSD.org/src/rev/fa59b3306c4a
branches:  netbsd-1-5
changeset: 490092:fa59b3306c4a
user:      tv <tv%NetBSD.org@localhost>
date:      Thu Nov 02 23:30:18 2000 +0000

description:
Pullup 1.8 [scw]:
These bring the mvme68k installation notes up to date WRT supported
hardware and diskspace requirements. Plus a few minor tweaks/corrections.

diffstat:

 distrib/notes/mvme68k/xfer |  13 +++++++++----
 1 files changed, 9 insertions(+), 4 deletions(-)

diffs (36 lines):

diff -r 05afb0804cc0 -r fa59b3306c4a distrib/notes/mvme68k/xfer
--- a/distrib/notes/mvme68k/xfer        Thu Nov 02 23:30:07 2000 +0000
+++ b/distrib/notes/mvme68k/xfer        Thu Nov 02 23:30:18 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: xfer,v 1.5.10.1 2000/11/01 03:48:22 tv Exp $
+.\"    $NetBSD: xfer,v 1.5.10.2 2000/11/02 23:30:18 tv Exp $
 .
 Installation is supported from several media types, including:
 .(bullet
@@ -107,10 +107,15 @@
 a chroot'ed environment). The netboot program may be found in the
 install directory of this distribution.
 .Pp
-The MVME167 boot ROM has code builtin to boot over ethernet from a
+The
+.Tn MVME162-LX
+and
+.Tn MVME167
+boot ROMs have code builtin to boot over ethernet from a
 TFTP server. You should configure it to download the same
 .Pa netboot
-program as is used for MVME147.
+program as is used for
+.Tn MVME147 .
 .Pp
 The netboot program will query a bootparamd server to find the NFS
 server address and path name for its root, and then load a kernel from
@@ -129,7 +134,7 @@
 The client will need access to the miniroot image, which can be
 provided using NFS or remote shell. If using NFS, miniroot.gz should be
 expanded on the server, because doing so from the RAMDISK shell is not
-so easy. The unzipped miniroot takes about 6 MB of space.
+so easy. The unzipped miniroot takes about 7.5 MB of space.
 .Pp
 If you will be installing
 .Nx