another update...

1 files changed, 5 insertions, 5 deletions

diff --git a/distrib/notes/sun3/xfer b/distrib/notes/sun3/xfer
index a7e58bbe86c..41348254995 100644
--- a/distrib/notes/sun3/xfer
+++ b/distrib/notes/sun3/xfer
@@ -14,8 +14,8 @@ for each type of media are given below.
 
 In order to create installation media, you will need all the 
 files in these two directories:
-	.../OpenBSD-1.1/sun3/install
-	.../OpenBSD-1-1/sun3/binary
+	.../2.0/sun3/install
+	.../2.0/sun3/binary
 
 * Creating boot/install tapes:
 
@@ -25,7 +25,7 @@ tape, and another called the "install" tape.
 
 The boot tape is created as follows:
 
-	cd .../OpenBSD-1.1/sun3/install
+	cd .../2.0/sun3/install
 	set T = /dev/nrst0
 	mt -f $T rewind
 	dd if=tapeboot of=$T bs=8k conv=sync
@@ -35,7 +35,7 @@ The boot tape is created as follows:
 
 The install tape is created as follows:
 
-	cd .../OpenBSD-1.1/sun3/install
+	cd .../2.0/sun3/install
 	set T = /dev/nrst0
 	mt -f $T rewind
 	foreach f (base etc comp games man misc text)
@@ -69,7 +69,7 @@ Your Sun3 expects to be able to download a second stage bootstrap
 program via TFTP after having acquired its IP address through RARP
 when instructed to boot "over the net".  It will look for a filename
 derived from the machine's IP address expressed in hexadecimal.  For
-example, a sun3 which has been assigned IP address 130.115.144.11
+example, a sun3 which has been assigned IP address 130.115.144.20
 will make an TFTP request for `8273900B'.  Normally, this file is a
 symbolic link to the OpenBSD/sun3 "netboot" program, which should be
 located in a place where the TFTP daemon can find it (remember, many