another update...

11 files changed, 43 insertions, 43 deletions

diff --git a/distrib/notes/amiga/install b/distrib/notes/amiga/install
index 03f727bee23..d8de5ecac5a 100644
--- a/distrib/notes/amiga/install
+++ b/distrib/notes/amiga/install
@@ -129,11 +129,11 @@ begin again from scratch.
 		to extract.  For example, to extract the base
 		distribution, use the command:
 
-			Extract base11
+			Extract base20
 
 		and to extract the games distribution:
 
-			Extract game11
+			Extract game20
 
 		If the distribution sets are in different directories,
 		you will need to cd to each directory in turn, runing
@@ -176,11 +176,11 @@ begin again from scratch.
 		wish to extract.  For example, to extract the base
 		distribution, use the command:
 
-			Extract base11
+			Extract base20
 
 		and to extract the games distribution:
 
-			Extract game11
+			Extract game20
 
 		After the extraction is complete, go to the location
 		of the next set you want to extract, "Set_tmp_dir"
@@ -199,7 +199,7 @@ begin again from scratch.
 		files for the game09 set, after the "Extract game09"
 		command has completed, issue the command:
 
-			rm game11.??
+			rm game20.??
 
 		Once you have extracted all sets and are at the "#" prompt
 		again, proceed to the section "Configuring Your System,"
diff --git a/distrib/notes/amiga/prep b/distrib/notes/amiga/prep
index 7a1292950ba..101ef5bb08a 100644
--- a/distrib/notes/amiga/prep
+++ b/distrib/notes/amiga/prep
@@ -90,7 +90,7 @@ Transferring the miniroot filesystem:
 	disk.
 
 	Once the hard disk has been prepared for OpenBSD, the appropriate
-	miniroot filesystem (inst-11.fs for a new install or upgr-11.fs
+	miniroot filesystem (inst-20.fs for a new install or upgr-20.fs
 	for an upgrade) is transferred to the swap partition configured
 	during the hard disk prep (or the existing swap parition in
 	the case of an upgrade).  The xstreamtodev utility provided in
@@ -103,9 +103,9 @@ Transferring the miniroot filesystem:
 	single-user state processes are not using the swap partition.
 
 	On AmigaDOS, the command:
-		xstreamtodev --input=inst-11.fs --rdb-name=<swap partition>
+		xstreamtodev --input=inst-20.fs --rdb-name=<swap partition>
 	where <swap partition> is the name you gave to the OpenBSD
-	partition to be used for swapping.  Use upgr-11.fs if you
+	partition to be used for swapping.  Use upgr-20.fs if you
 	are going to do an upgrade of an existing OpenBSD system.  If
 	xstreamtodev is unable to determine the SCSI driver device
 	name or the unit number of the specified partition, you may
@@ -116,7 +116,7 @@ Transferring the miniroot filesystem:
 	in single user state on the current OpenBSD system, or use the
 	"shutdown now" command to shutdown to single-uyser state.  Then
 	copy the miniroot using dd:
-		dd if=upgr-11.fs of=/dev/rsd0b
+		dd if=upgr-20.fs of=/dev/rsd0b
 	where /dev/rsd0b should be the device path of the swap partition
 	your system is configured to use.  Once the file is copied,
 	reboot back to AmigaDOS to boot the upgrade kernel.  NOTE:  the
diff --git a/distrib/notes/atari/install b/distrib/notes/atari/install
index 6169d7db186..eb1c8089e65 100644
--- a/distrib/notes/atari/install
+++ b/distrib/notes/atari/install
@@ -121,11 +121,11 @@ begin again from scratch.
 		to extract.  For example, to extract the base
 		distribution, use the command:
 
-			Extract base11
+			Extract base20
 
 		and to extract the games distribution:
 
-			Extract game11
+			Extract game20
 
 		If the distribution sets are in different directories,
 		you will need to cd to each directory in turn, runing
@@ -168,11 +168,11 @@ begin again from scratch.
 		wish to extract.  For example, to extract the base
 		distribution, use the command:
 
-			Extract base11
+			Extract base20
 
 		and to extract the games distribution:
 
-			Extract game11
+			Extract game20
 
 		After the extraction is complete, go to the location
 		of the next set you want to extract, "Set_tmp_dir"
@@ -191,7 +191,7 @@ begin again from scratch.
 		files for the game09 set, after the "Extract game09"
 		command has completed, issue the command:
 
-			rm game11.??
+			rm game20.??
 
 		Once you have extracted all sets and are at the "#" prompt
 		again, proceed to the section "Configuring Your System,"
diff --git a/distrib/notes/hp300/prep b/distrib/notes/hp300/prep
index 2159aa1f501..5922c99ff1e 100644
--- a/distrib/notes/hp300/prep
+++ b/distrib/notes/hp300/prep
@@ -49,7 +49,7 @@ In order to complete this process, you will need the following from the
 	SYS_INST	The standalone disklabel and miniroot
 			installation tool
 
-	inst-11.fs.gz	A gzipped miniroot filesystem image.  This image
+	inst-20.fs.gz	A gzipped miniroot filesystem image.  This image
 			must be un-gzipped before copying to disk.
 
 To boot SYS_INST via the network, you will need a system capable of handling
diff --git a/distrib/notes/hp300/upgrade b/distrib/notes/hp300/upgrade
index 87555a76ee4..180dedd2c0c 100644
--- a/distrib/notes/hp300/upgrade
+++ b/distrib/notes/hp300/upgrade
@@ -36,7 +36,7 @@ manually.  To do this, follow the following procedure:
 	  between the OpenBSD 2.0 kernel and older route(8)
 	  binaries.
 
-	* Back up your pre-existing kernel and copy the 1.1
+	* Back up your pre-existing kernel and copy the 2.0
 	  kernel into your root partition.
 
 	* Reboot with the 2.0 kernel into single-user mode.
@@ -56,7 +56,7 @@ manually.  To do this, follow the following procedure:
 		sh /etc/netstart
 
 	  NOTE: the route(8) commands may fail due to potential
-	  incompatibilities between route(8) and the OpenBSD 1.1
+	  incompatibilities between route(8) and the OpenBSD 2.0
 	  kernel.  Once you have enabled the network, mount the
 	  NFS filesystems.  If you use amd(8), you may or may not
 	  have to mount these filesystems manually.  Your mileage
@@ -66,7 +66,7 @@ manually.  To do this, follow the following procedure:
 	  the `base' binary set:
 
 		cd /
-		tar -xzvpf /path/to/base11.tar.gz
+		tar -xzvpf /path/to/base20.tar.gz
 
 	  NOTE: the `--unlink' option is _very_ important!
 
diff --git a/distrib/notes/hp300/xfer b/distrib/notes/hp300/xfer
index 0f5ef6642e1..9113cb4d65b 100644
--- a/distrib/notes/hp300/xfer
+++ b/distrib/notes/hp300/xfer
@@ -27,7 +27,7 @@ To prepare for installing via a tape:
 	way to do this is with the dd(1) command.  Make sure you
 	use a `no-rewind-on-close' tape device.  For example:
 
-		for file in base11.tar.gz etc11.tar.gz; do
+		for file in base20.tar.gz etc20.tar.gz; do
 			dd if=${file} of=/dev/nrst0 bs=20b
 		done
 
@@ -77,4 +77,4 @@ To prepare for installing via FTP:
 		IP Address: 205.149.163.23
 		Login: anonymous
 		Password: <your e-mail address>
-		Server path: /pub/OpenBSD/OpenBSD-1.1/hp300/binary
+		Server path: /pub/OpenBSD/2.0/hp300/binary
diff --git a/distrib/notes/mac68k/install b/distrib/notes/mac68k/install
index e6fcd960448..f38743ad336 100644
--- a/distrib/notes/mac68k/install
+++ b/distrib/notes/mac68k/install
@@ -69,7 +69,7 @@ If you are installing onto a single root partition, proceed to the
 Installation of base files:
 
 	Select the "Install" menu item from the "File" menu and install
-	base11, bsd, and any other packages you wish to install at
+	base20, bsd, and any other packages you wish to install at
 	this time (see the contents section for information about what's
 	in each package).  The installer will print out the filename of
 	each file as it is installed, and will take quite some time to
@@ -105,7 +105,7 @@ If the system does not come up:
 	  you saw.
 
 If the system does come up, congratulations, you have successfully
-installed OpenBSD 1.1.  When you reboot into OpenBSD, you should log
+installed OpenBSD 2.0.  When you reboot into OpenBSD, you should log
 in as "root" at the login prompt.  There is no initial password, but
 if you're using the machine in a networked environment, you should
 create yourself an account and protect it and the "root" account with
diff --git a/distrib/notes/mac68k/xfer b/distrib/notes/mac68k/xfer
index bf1a6b61a89..ef575bafd38 100644
--- a/distrib/notes/mac68k/xfer
+++ b/distrib/notes/mac68k/xfer
@@ -9,10 +9,10 @@ If the install is being done from an AppleShare-mounted volume,
 the install utility must be in the same folder as the data files.
 
 There will be two images of each file.  One in "raw" Unix format
-and one in a binhex format.  Therefore, base20 and base11.hqx both
-contain the same information, but base11.hqx has been encoded in
+and one in a binhex format.  Therefore, base20 and base20.hqx both
+contain the same information, but base20.hqx has been encoded in
 binhex format.  Download the files; if necessary, decode them so
-you have all of the files as base11, etc11, etc.  This can be
+you have all of the files as base20, etc20, etc.  This can be
 accomplished from the .hqx files by using _Stuffit Expander_ or
 any one of a number of freeware and shareware Macintosh tools.
 
diff --git a/distrib/notes/pc532/install b/distrib/notes/pc532/install
index 4ebe7fae92f..5c1a984654d 100644
--- a/distrib/notes/pc532/install
+++ b/distrib/notes/pc532/install
@@ -2,7 +2,7 @@
 your system, see the next section.)
 
 To install OpenBSD/pc532, there are several things you need to know.
-First, OpenBSD "autoconfigs" the scsi devices. inst-11.fs has only
+First, OpenBSD "autoconfigs" the scsi devices. inst-20.fs has only
 support for disks configured into the kernel. Starting the search at
 SCSI address 0, lun 0 and increasing, the first disk found will be sd0
 regardless of the address, the second will be sd1. KLONDIKE for example
@@ -15,7 +15,7 @@ has the following devices installed:
 	cd0 -> ID 3 LUN 0: Toshiba XM-4101TA CD-ROM drive
 	st0 -> ID 4 LUN 0: Tandberg TDC3600 QIC tape drive
 
-Only sd0-sd3 are supported by the inst-11.fs kernel.
+Only sd0-sd3 are supported by the inst-20.fs kernel.
 
 Next you need to know what the install script wants to do.  This install
 is script on the ram disk root that can do most of the work of configuring
@@ -41,15 +41,15 @@ your disk.
 The Install Procedure:
 
   a) Adjust your console device settings.
-	The inst-11.fs kernel will come up with 9600 baud, 7 bits,
+	The inst-20.fs kernel will come up with 9600 baud, 7 bits,
 	even parity and one stop bit. Adjust your terminal to match
 	these settings. The monitor's baud rate can be changed with
 	"baud d'9600".
 
-  b) Get inst-11.fs and boot the kernel.
+  b) Get inst-20.fs and boot the kernel.
 
 	From Floppy: (and using the autoboot monitor)
-	If you have a 1.44 meg SCSI floppy drive, you can put inst-11.fs
+	If you have a 1.44 meg SCSI floppy drive, you can put inst-20.fs
 	onto a 3.5" floppy disk. Insert the disk into your floppy
 	drive and use the monitor's boot command to boot the default
 	image from the floppy. The image booted will ask you for a
@@ -58,8 +58,8 @@ The Install Procedure:
 	Replace X with your drive number. For KLONDIKE X would be "2".
 
 	Tape:
-	You will need to load a copy of inst-11.fs into RAM.
-		- load the inst-11.fs at 0x288000
+	You will need to load a copy of inst-20.fs into RAM.
+		- load the inst-20.fs at 0x288000
 		- run at 0x3E8820
 	The boot program will ask you now for a kernel to load. Answer
 		rd0a:/bsd
@@ -71,7 +71,7 @@ The Install Procedure:
 	output to standard output a byte sequence used by the pc532
 	ROM monitor to download a binary file into RAM.  Using this
 	program on a computer connected to the pc532, one can
-	load a copy of inst-11.fs into RAM at 0x288000.  The boot
+	load a copy of inst-20.fs into RAM at 0x288000.  The boot
 	sequence is now the same as with tape.
 
   c) Choose a disk geometry.  For me, the reported geometry left
@@ -81,7 +81,7 @@ The Install Procedure:
 	2053880 sectors.
 
 	To help in this process, there is a program "factor" that is
-	on the inst-11.fs.  The usage is "factor number" and it lists
+	on the inst-20.fs.  The usage is "factor number" and it lists
 	the prime factors of number.
 	For example, with the 2053880 sector disk I got:
 
@@ -116,7 +116,7 @@ The Install Procedure:
 	partitions, it will ask for a mount point.  The mount point will
 	be "relative to /" and should not include the leading "/".  Also,
 	IF you do not want the partition to have newfs run on it (that is
-	it might be the last one and have a copy of inst-11.fs) enter "NO"
+	it might be the last one and have a copy of inst-20.fs) enter "NO"
 	to the mount point and it will not run newfs on the partition.
 	It will enter the partition into the disklabel.
 
diff --git a/distrib/notes/sun3/upgrade b/distrib/notes/sun3/upgrade
index 4116b2da030..b2c1c28a928 100644
--- a/distrib/notes/sun3/upgrade
+++ b/distrib/notes/sun3/upgrade
@@ -11,7 +11,7 @@ Manual upgrade procedure:
 	  between the OpenBSD 2.0 kernel and older route(8)
 	  binaries.
 
-	* Back up your pre-existing kernel and copy the 1.1
+	* Back up your pre-existing kernel and copy the 2.0
 	  kernel into your root partition.
 
 	* Reboot with the 2.0 kernel into single-user mode.
@@ -31,7 +31,7 @@ Manual upgrade procedure:
 		sh /etc/netstart
 
 	  NOTE: the route(8) commands may fail due to potential
-	  incompatibilities between route(8) and the OpenBSD 1.1
+	  incompatibilities between route(8) and the OpenBSD 2.0
 	  kernel.  Once you have enabled the network, mount the
 	  NFS filesystems.  If you use amd(8), you may or may not
 	  have to mount these filesystems manually.  Your mileage
@@ -41,7 +41,7 @@ Manual upgrade procedure:
 	  the `base' binary set:
 
 		cd /
-		tar -xzvpf /path/to/base11.tar.gz
+		tar -xzvpf /path/to/base20.tar.gz
 
 	* Install a new boot block:
 
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