[src/trunk]: src/distrib/notes Rename mvme68k's ramdisk kernel from "netbsd-r...

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

details:   https://anonhg.NetBSD.org/src/rev/4ac184a4450f
branches:  trunk
changeset: 525393:4ac184a4450f
user:      scw <scw%NetBSD.org@localhost>
date:      Wed Apr 10 19:01:59 2002 +0000

description:
Rename mvme68k's ramdisk kernel from "netbsd-rd" to "netbsd.RAMDISK".

diffstat:

 distrib/notes/common/contents |   6 +++---
 distrib/notes/mvme68k/xfer    |  14 +++++++-------
 2 files changed, 10 insertions(+), 10 deletions(-)

diffs (82 lines):

diff -r b4ae9abd3c4a -r 4ac184a4450f distrib/notes/common/contents
--- a/distrib/notes/common/contents     Wed Apr 10 18:56:37 2002 +0000
+++ b/distrib/notes/common/contents     Wed Apr 10 19:01:59 2002 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: contents,v 1.45 2002/04/07 02:56:46 shin Exp $
+.\"    $NetBSD: contents,v 1.46 2002/04/10 19:01:59 scw Exp $
 .\"
 .\" Copyright (c) 1999-2001 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -1089,8 +1089,8 @@
 \*M
 ramdisk image from tape. This must be the second file written to the tape.
 .      tag)
-.      (tag netbsd-rd.gz
-.      It Pa netbsd-rd.gz
+.      (tag netbsd.RAMDISK.gz
+.      It Pa netbsd.RAMDISK.gz
 This is the
 .Nx
 \*M
diff -r b4ae9abd3c4a -r 4ac184a4450f distrib/notes/mvme68k/xfer
--- a/distrib/notes/mvme68k/xfer        Wed Apr 10 18:56:37 2002 +0000
+++ b/distrib/notes/mvme68k/xfer        Wed Apr 10 19:01:59 2002 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: xfer,v 1.11 2001/10/23 22:13:35 scw Exp $
+.\"    $NetBSD: xfer,v 1.12 2002/04/10 19:02:00 scw Exp $
 .
 Installation is supported from several media types, including:
 .(bullet
@@ -43,7 +43,7 @@
 .Dl # Ic "mt -f $T rewind"
 .Dl # Ic "dd if=tapeimage/stboot of=$T"
 .Dl # Ic "dd if=tapeimage/bootst of=$T obs=8k conv=osync"
-.Dl # Ic "gzip -dc tapeimage/netbsd-rd.gz | dd of=$T obs=8k conv=osync"
+.Dl # Ic "gzip -dc tapeimage/netbsd.RAMDISK.gz | dd of=$T obs=8k conv=osync"
 .Dl # Ic "gzip -dc miniroot/miniroot.fs.gz  | dd of=$T obs=8k conv=osync"
 .Dl # Ic "mt -f $T rewind"
 .Pp
@@ -124,14 +124,14 @@
 .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
-that location. The server should have a copy of the netbsd-rd kernel in
+that location. The server should have a copy of the netbsd.RAMDISK kernel in
 the root area for your client (no other files are needed in the client
 root, although it might be a convenient place to put the uncompressed
 miniroot image) and
 .Pa /etc/bootparams
 on the server should have an entry for your client and its root directory.
 Note that you should rename the
-.Pa netbsd-rd
+.Pa netbsd.RAMDISK
 kernel to just
 .Pa netbsd
 in the client's root directory before trying to netboot the client.
@@ -145,7 +145,7 @@
 .Nx
 on several clients, it may be useful
 to know that you can use a single NFS root for all the clients as long
-as they only use the netbsd-rd kernel. There will be no conflict
+as they only use the netbsd.RAMDISK kernel. There will be no conflict
 between clients because the RAM-disk kernel will not use the NFS root.
 No swap file is needed; the RAM-disk kernel does not use that either.
 .
@@ -154,7 +154,7 @@
 This method requires that you boot from another device (i.e. tape
 or network, as described above). You may need to make a boot tape
 on another machine using the files provided on the CD-ROM. Once
-you have booted netbsd-rd (the RAMDISK kernel) and loaded the
+you have booted netbsd.RAMDISK (the RAMDISK kernel) and loaded the
 miniroot, you can load any of the distribution sets directly from
 the CD-ROM. The
 .Ic install
@@ -166,7 +166,7 @@
 This method requires that you boot from another device (i.e. tape
 or network, as described above). You may need to make a boot tape
 on another machine using the files in .../install (which you get
-via FTP). Once you have booted netbsd-rd (the RAM-disk kernel)
+via FTP). Once you have booted netbsd.RAMDISK (the RAM-disk kernel)
 and loaded the miniroot, you can load any of the distribution sets
 over the net using FTP. The
 .Ic install