added to install_notes instructions for loading distribtuion

files from a MS-DOS partition.
Minor cleanup:
fixed spelling error in inst1.install
capitalized sentences in kc.profile
reworded initial load_fd options

4 files changed, 177 insertions, 111 deletions

diff --git a/etc/etc.i386/inst1.install b/etc/etc.i386/inst1.install
index 15a86e2..46fbf63 100755
--- a/etc/etc.i386/inst1.install
+++ b/etc/etc.i386/inst1.install
@@ -981,11 +981,11 @@ echo "esac"
 echo "echo"
 echo "echo	\"OK.  All of the base files are installed.\""
 echo "echo"
-echo "echo	\"The next step: reboot from the hard disk, and follow\""
-echo "echo	\"more instrutctions.\""
+echo "echo	\"The next step: reboot from the hard disk.  Further\""
+echo "echo	\"instructions are presented upon rebooting.\""
 echo "echo"
-echo "echo	\"To do this, enter 'halt' at the prompt to halt the machine.\""
-echo "echo	\"Once the machine has halted, remove the floppy from the disk\""
+echo "echo	\"Enter 'halt' now at the prompt to halt the machine.\""
+echo "echo	\"After the machine has halted, remove the floppy from the disk\""
 echo "echo	\"drive, and hit any key to reboot from the hard disk.\""
 ) >.profile
 
@@ -995,7 +995,7 @@ echo
 echo	"The next step:  reboot from the kernel-copy disk, copy a kernel"
 echo	"to the hard disk, and finally reboot from the hard disk."
 echo
-echo	"To do this, enter 'halt' now to halt the machine.  After it"
+echo	"To do this, enter \`halt' now to halt the machine.  After it"
 echo	"announces that it has halted, remove the floppy from the drive"
 echo	"and insert the kernel-copy disk that was booted before."
 echo	"Press any key to reboot.  When prompted to insert the filesystem"
diff --git a/etc/etc.i386/inst2.profile b/etc/etc.i386/inst2.profile
index 35c4372..87193eb 100644
--- a/etc/etc.i386/inst2.profile
+++ b/etc/etc.i386/inst2.profile
@@ -121,7 +121,7 @@ load_fd()
 	altdrive=
 	subdir=
 	while [ -z "$drive" ]; do
-		echo -n "Read from which drive (a, b, c or ? for help)? [c] "
+		echo -n "Read from which drive (or ? for help)? [c] "
 		read answer junk
 		case "${answer:-c}" in
 		a*b|A*B)	
diff --git a/etc/etc.i386/install_notes b/etc/etc.i386/install_notes
index bc04851..61aea3d 100644
--- a/etc/etc.i386/install_notes
+++ b/etc/etc.i386/install_notes
@@ -37,46 +37,49 @@ Bootable Kernel-copy floppies
 
 Installation floppies
 
-	In addition to a bootble floppy, currently two additional
+	In addition to a bootable floppy, currently two additional
 	disks are required to prepare your hard drive for FreeBSD
 	and to install the FreeBSD distribution.  Like the boot
 	floppies, these are distributed as binary images.  They are
-	are named "filesystem-floppy" and "cpio-floppy".
+	are referred to below as the  "filesystem-floppy" and the
+	"cpio-floppy".
 
 	There is also an optional fourth installation disk referred
-	to as the "dos-floppy".  This can include any programs
-	from the tools directory.  For instance, add kermit if
-	this is needed for downloading files.  Unlike the binary
-	images which are written to a floppy via dd(1) or rawrite.exe,
-	these programs should be copied to a DOS formatted floppy
-	using 386BSD's `mcopy' command (or the `copy' command if
-	working from DOS).
+	to as the "dos-floppy".  Unlike the other install disks,
+	there is no binary image for the dos floppy.  Instead this
+	is a regular MS-DOS-formatted floppy disk containing any
+	FreeBSD programs you choose to copy to it using mtools or
+	even the DOS copy command.  The most commonly requested
+	programs have been put in a tools directory at FreeBSD
+	archives sites.
 
 Upgrade floppies
 
 	These facilitate upgrading to FreeBSD from any previous
-	patch-kit level of 386BSD 0.1.  Since they are currently
-	in BETA testing, they are not further mentioned in this
-	document.  However, they are currently available upon
-	request to FreeBSD-questions@freebsd.cdrom.com.
+	patch-kit level of 386BSD 0.1.  They are still in testing,
+	but should be available by the time you read this from
+	the tools/upgrade directory at FreeBSD archive sites.
+	[the current version is: 
+	tools/upgrade/386BSD-to-FreeBSD-update-LATE-BETA.tar.gz]
 
 FreeBSD distribution sets
 
 	These collections contain the complete FreeBSD system and
-	utilities.  There are three separate sets: the FreeBSD
-	binaries, the FreeBSD sources, and the DES sources+binaries.
-	The DES set contains only crypt(3) code and is subject to
-	U.S.A.  export restrictions.
+	utilities in source and binary form.  There are three
+	separate sets: the FreeBSD binaries, the FreeBSD sources,
+	and the DES sources+binaries.  The DES set contains only
+	crypt(3) code and is subject to U.S.A. export restrictions.
 
 	The binary distribution set can be found in the "binarydist"
-	subdirectory of the distribution. It is a single gzip'ed
-	tar archive split into files named bin_tgz.aa to bin_tgz.db
-	(i.e., 80 files all told), plus file CKSUMS.
+	subdirectory of the FreeBSD archive sites.  It consists
+	of files named bin_tgz.aa to bin_tgz.db (i.e., 80 files
+	all told).  A CKSUMS file (* see note below) is included
+	for verifying the integrity of these.
 
 	The source distribution sets can be found in under
-	"sourcedist" subdirectory of the distribution. It is
-	consists of files named src_tgz.aa to src_tgz.cp (i.e.,
-	68 files all told), plus file CKSUMS.
+	"sourcedist" subdirectory of archive sites. It is consists
+	of files named src_tgz.aa to src_tgz.cp (i.e., 68 files
+	all told), plus file CKSUMS*.
 
 	Finally, the security distribution set contains
 	usr/src/libcrypt/*, the source files for the DES encryption
@@ -91,8 +94,8 @@ FreeBSD distribution sets
 
 	Each collection is a split, gzip'ed tar archive.  They
 	are reassembled and extracted by the install procedure.
-	However, to view them without installing, you can use, e.g.,
-	the command line:
+	However, to view them without installing FreeBSD, you can
+	use, e.g., the command line:
 
 		cat bin* | gunzip | tar tvf - | more
 
@@ -100,10 +103,10 @@ FreeBSD distribution sets
 
 		cat bin* | gunzip | tar xvfp -
 
-	Using this method, the files are extracted, "below" the
-	current directory.  That is, if you want to extract the
-	binaries "into" your system, i.e. replace the system
-	binaries with them, you have to run the "tar xvfp" from /.
+	Using this method, the files are extracted in the current
+	directory.  So to install the binary distribution, for
+	instance, you have to run the "tar xvfp" from the root
+	directory (/).
 
 	In each of the distribution directories, there is a file
 	named "CKSUMS" which contains the checksums of the files
@@ -112,10 +115,10 @@ FreeBSD distribution sets
 	if you suspect one of the files is corrupted.
 
 	N.B.: The CKSUMS files are produced using the 4.4BSD 
-	version of cksum which is POSIX compliant.  The values in
-	this file will probably not match with cksums from other
-	systems.  FreeBSD uses the new 4.4BSD cksum routine.  A
-	copy of the new cksum binary that will run on
+	version of cksum which is POSIX-compliant.  The values in
+	these file do not match the cksums generated by the 386BSD 0.1
+	version  of cksum (which is based on an earlier "standard").
+	A copy of the new cksum binary that will run on
 	386bsd/Netbsd/FreeBSD can be found in the "tools" subdirectory
 	of the distribution.
 
@@ -126,7 +129,7 @@ System Requirements and Supported Devices:
 FreeBSD 1.0 runs on ISA (AT-Bus) and EISA systems, with 386 and 486
 processors, with or without math coprocessors.  It does NOT support
 Micro-channel systems, such as some IBM PS/2 systems.  The minimal
-configuration includes 4Meg of RAM, and a 70Meg hard disk, but to
+configuration includes 4Meg of RAM, and an 80Meg hard disk, but to
 install the entire system you'll need much more disk space, and to run
 X or compile the system more RAM is recommended.  (4Meg will actually
 allow you to run X and/or compile, but it's extremely slow.)
@@ -151,6 +154,8 @@ Supported devices include:
 		8250
 		16450
 		16550A
+		[4-port multi-serial cards - require kernel built
+		with MULTI_PORT option]
 	Ethernet controllers
 		SMC/WD 8003, 8013, and equivalents
 			(including the SMC "Elite" series)
@@ -159,11 +164,13 @@ Supported devices include:
 		ISOLAN ISOLink
 	Tape drives:
 		QIC-02 format tape drives
-		most SCSI tape drives should work
-		_NO_ QIC-40 or QIC-80 tape drives will work
+		most SCSI tape/DAT drives
+		[an early QIC-40 or QIC-80 tape driver exists,
+		but is not yet incorporated into FreeBSD]
 	CD-ROM drives:
-		most SCSI CD-ROM drives should work
-		_NO_ non-SCSI CD-ROM drives will work
+		most SCSI CD-ROM drives
+		[an early MITSUMI non-SCSI CD-ROM driver exists,
+		but is not yet incorporated into FreeBSD]
 
 To be detected by the distributed kernels, the devices must
 be configured as follows: (Note: IRQ 9 is the same as IRQ 2
@@ -178,7 +185,7 @@ Std. Hard Disk Cntlr.
 
 AHA-154x SCSI Cntlr.	0x330	11	5	 [kcopy-ah-floppy]
 
-AHA-174x SCSI Cntlr.	automagically configured [kcopy-ah-floppy]
+AHA-174x SCSI Cntlr.	automatically configured [kcopy-ah-floppy]
 
 BT742 SCSI Cntlr.	0x330	12		 [kcopy-bt-floppy]
 
@@ -186,11 +193,11 @@ UHA-14f	SCSI Cntlr. or
 UHA-34f SCSI Cntlr.	0x330	14	5        [kcopy-bt-floppy]
 (In FreeBSD GAMMA and before, UHA was on IRQ 11)
 
-SCSI Disks	sd[0-2]	automagically configured
+SCSI Disks	sd[0-2]	automatically configured
 
-SCSI Tapes	st[01]	automagically configured
+SCSI Tapes	st[01]	automatically configured
 
-SCSI CD-ROMs	cd0	automagically configured
+SCSI CD-ROMs	cd0	automatically configured
 
 Serial Ports	com0	0x3f8	4
 		com1	0x2f8	3
@@ -235,8 +242,9 @@ To recompile the sources requires an additional 55 MB.
 To recompile the kernel requires an additional 2 MB.
 
 Since additional room is required for extracting the distributions,
-a full binary installation requires a minimum of about 70 MB (46
-MB extracted + 16 MB archived + 8 MB minimum swap).
+a full binary installation requires a minimum of about 80 MB (46
+MB extracted + 16 MB archived + 8 MB minimum swap + room for
+extracting).
 
 A complete source + binary distribution requires a minimum of
 about 210 MB (assuming a minimum 8 MB swap).
@@ -248,6 +256,7 @@ Getting the System on to Useful Media:
 Installation is supported from several media types, including:
 
 	MS-DOS floppies
+	MS-DOS hard disk (Primary partition)
 	Tape
 	NFS partitions
 	FTP
@@ -282,13 +291,13 @@ or for a 3.5" 1.44 Mb floppy:
 
 If you are using DOS to make the floppies, use the rawrite.exe
 utility.  This can be found in the "tools" subdirectory of the
-distribution.  Copy or download  rawrite.exe and the binary images
-to a DOS disk, type "rawrite" under MS-DOS and follow the
-instructions.  Rawrite can write binary images to either 1.2MB or
-1.44MB floppies (which must be DOS formatted).
+archive site.  Copy rawrite.exe and the binary images to a DOS
+disk, type "rawrite" under MS-DOS and follow the instructions.
+Rawrite can write binary images to either 1.2MB or 1.44MB
+MS-DOS-formatted floppies.
 
 Any other programs from the tools directory that might be needed
-for installing FreeBSD, such as kermit, should be copied to a DOS
+for installing FreeBSD, such as kermit, should be copied to a DOS-
 formatted floppy (1.2MB or 1.44MB).  Under 386BSD, they can be
 copied to floppy using the mcopy command.  Under DOS, use the DOS
 copy command.
@@ -297,6 +306,27 @@ The steps necessary to prepare the distribution sets for installation
 depend on which method of installation you choose.  The various methods
 are explained below.
 
+To prepare for installing via MS-DOS hard disk:
+
+	To prepare FreeBSD for installaton from the MS-DOS C: drive
+	of the hard disk, you need to do the following:
+
+		If FreeBSD is installed on a hard disk containing
+		a Primary MS-DOS partition (as opposed to an
+		Extended DOS partition), then the FreeBSD distribution
+		files can be read directly from DOS.  Preparation
+		is just a matter of copying the FreeBSD distribution
+		files onto DOS C: drive of the hard disk.
+
+		If FreeBSD is installed on a separate hard disk than
+		MS-DOS, it is not currently possible to read the FreeBSD
+		distribution files directly from DOS.  In this case,
+		a different medium should be used.
+
+	Once you have the files on the C: drive, you can proceed to the
+	next step in the installation process, viz preparing your hard
+	disk.
+
 To prepare for installing via MS-DOS floppies:
 
 	To prepare FreeBSD for installaton from MS-DOS floppies, you
@@ -313,9 +343,9 @@ To prepare for installing via MS-DOS floppies:
 
 		Format all of the floppies, with MS-DOS.
 		Don't make any of them MS-DOS bootable
-		floppies.  (i.e. don't use "format /s"!)
-		(If you use "format /u" then the format
-		will run a tad faster).
+		floppies  (i.e., don't use "format /s"!)
+		If you use "format /u" then the format
+		will run a tad faster.
 
 		Copy all of the "<set>_tgz.xx" files on
 		the DOS disks.  Under DOS use the DOS copy
@@ -329,8 +359,8 @@ To prepare for installing via MS-DOS floppies:
 			for dist in bin_tgz.*; do
 				if [ $x -ge $N_PER_DISK ]; then
 					x=0
-					echo "Insert next disk"
-					echo "And press ENTER..."
+					echo -n "Insert next disk, "
+					echo -n "and press ENTER... "
 					read reply
 					mdel a:/\*
 				fi
@@ -338,7 +368,7 @@ To prepare for installing via MS-DOS floppies:
 				x=`expr $x + 1`
 			done
 
-	(Or you might use tar instead).
+		(Or you might use tar instead).
 
 	Once you have the files on DOS disks, you can proceed to the
 	next step in the installation process, viz preparing your hard
@@ -363,6 +393,12 @@ To prepare for installing via a tape:
 	"<files>" are the names of the "<set>.tar.gz.xx" files
 	which you want to be placed on the tape.
 
+	If your tape drive is not a type recognzed by the
+	kernel, then it may be necessary to set the tape density
+	using either the st(1) command  (for SCSI tape) or the
+	mt(1) command.   Both these programs are available from
+	the tools directory of the FreeBSD archive site.
+
 To prepare for installing via an NFS partition:
 
 	NOTE: this method of installation is recommended
@@ -442,7 +478,7 @@ FOR DOS!  If you do not, FreeBSD will not be able to properly coexist
 with DOS.
 
 Secondly, make sure your disk has at least 16 Mbytes free space (or 
-70 Mbytes for the complete binary distribition).
+80 Mbytes for the complete binary distribition).
 
 You are now set to install FreeBSD on your hard drive.
 
@@ -498,7 +534,7 @@ may hit Control-C at any prompt and then type `halt'.
 
 	You will then be asked for a label name for your disk.
 	This should be a short, one-word name for your disk,
-	e.g. "cp3100-mine" for a Conner Peripherals "3100" disk.
+	e.g., "cp3100-mine" for a Conner Peripherals "3100" disk.
 	You needn't remember this name.
 
 	Next, you will be prompted for the geometry information.
@@ -528,7 +564,7 @@ may hit Control-C at any prompt and then type `halt'.
 	Next, you will be asked for the size of your swap partition
 	- again, you must calculate this in cylinders.  You should
 	probably allocate around twice as much swap space as you
-	have real memory.  If you wish the system to save crash dumps
+	have RAM memory.  If you wish the system to save crash dumps
 	when it panics, you will need at least as much swap as you
 	have RAM.
 
@@ -540,19 +576,36 @@ may hit Control-C at any prompt and then type `halt'.
 	in the FreeBSD portion of the disk. When it asks you for the
 	mount point for this partition, say "/usr".
 
+	After the FreeBSD partition have been assigned, install checks
+	the disk for an MS-DOS partition.  If one exists, you are prompted
+	whether to make this accessible from FreeBSD (i.e., for reading
+	and writing).  And if you choose to make the DOS partition
+	accessible, you are prompted for what directory it should
+	be mounted on.  "/dos" is used by default.  With this
+	choice, you could copy the contents of the DOS root
+	directory (i.e., C:\), for instance, with the Unix command:
+
+		# cp /dos/* .
+
+	If have you a DOS partition and you don't want it visible
+	from FreeBSD, just respond with "n" when asked whether to
+	make it accessible.
+
 	YOU ARE NOW AT THE POINT OF NO RETURN.
 
 	If you confirm that you want to install FreeBSD, your hard
 	drive will be modified, and perhaps it contents scrambled at
 	the whim of the install program.  This is especially likely
 	if you gave the install program incorrect information.
+	Enter "no" at the prompt to get the option of redoing the
+	configuration, using your previous choices as defaults.
 
 	If you are sure you want to proceed, enter "yes" at the prompt.
 
-	The install program will now make the filesystems you
-	specified.  There should be no errors in this section of the
-	installation.  If there are, restart from the the beginning
-	of the installation process.
+	The install program now makes the filesystems you specified.
+	If all goes well, there should be no errors in this section
+	of the installation.  If there are, restart from the the
+	beginning of the installation process.
 
 	After the installation program prompts you to see if you'd
 	like to be told about all of the files it's going to copy
@@ -597,7 +650,10 @@ may hit Control-C at any prompt and then type `halt'.
 	You are given the option to load the dos-floppy disk.
 	In particular, if you want to use kermit for downloading
 	the distribution, the dos-floppy should have the kermit
-	binary.  If loading it, remove the cpio-floppy from the
+	binary.  Or if you are using SCSI tape, the dos-floppy should
+	contain the st command.  
+
+	To load the dos-floppy, remove the cpio-floppy from the
 	drive,  insert the dos-floppy and enter a "yes" response
 	at the prompt.  Otherwise, enter "no" at the prompt.
 
@@ -620,7 +676,7 @@ may hit Control-C at any prompt and then type `halt'.
 	using to install FreeBSD.  Follow the appropriate
 	instructions, given below.
 
-	To install from tape or floppy:
+	To install from MS-DOS hard disk partition, floppy or tape:
 
 		The first thing you should do is to choose a temporary
 		directory where the distribution files can be stored.
@@ -630,28 +686,35 @@ may hit Control-C at any prompt and then type `halt'.
 		After you have chosen a temporary directory,
 		you should issue the appropriate load command:
 
-			load_fd if you're loading from floppies
-			(NOTE: as of time of writing these notes,
-			this does not work).
+			load_fd - for loading from a MS-DOS hard disk 
+				partition, or from floppies,
 			
-			load_qic_tape if loading from QIC-02 tape
+			load_qic_tape - for loading from QIC-02 tape, or
+
+			load_scsi_tape - for you're loading from the first
+			       SCSI tape drive in the system.
 
-			load_scsi_tape if you're loading from the first
-				       SCSI tape drive in the system.
+		If loading from tape, it may be necessary to first
+		set the default density using the mt or st command.
+		The low-density device (/dev/rst0 or /dev/rmt0)
+		is used by the load_xx_tape command, so to prepare
+		a SCSI device for reading QIC-150 tape, you might use:
 
-		You will then be prompted for information as to which
-		floppy drive to load from, if you choose that
-		method of installation.
+			# st -f /dev/nrst0 rewind
+			# st -f /dev/nrst0 low_dnsty 16
+			# load_scsi_tape
 
-		Next, you will be told to insert the media into
-		the appropriate drive, and hit return.  Continue
-		to follow instructions until you are returned to
-		the "#" prompt.
+		If loading from floppy or hard disk, the load_fd
+		command prompts for information, such as to which
+		floppy drive or hard disk directory to load from.
+		Additional options are available, e.g., for listing
+		and, if loading from hard disk, changing source
+		directories.
 
 		Go to the directory which contains the first
 		distribution set you wish to install.  This is
-		either the directory you specified above, if loading
-		from floppy, or possibly a subdirectory of that
+		either the directory you specified above, if using
+		load_fd, or possibly a subdirectory of that
 		directory, if you loaded from tape.
 
 		When there, run "set_tmp_dir" again, and choose
@@ -786,6 +849,7 @@ may hit Control-C at any prompt and then type `halt'.
 		A typical session might be:
 		# stty -f /dev/sio01 clocal
 		# kermit
+		C-Kermit> set file type binary
 		C-Kermit> set line /dev/sio01
 		C-Kermit> set baud 9600
 		C-Kermit> set receive packet 740
@@ -799,14 +863,12 @@ may hit Control-C at any prompt and then type `halt'.
 		atdt 1234567		<-- dial the remote
 		Connect 9600 
 		login: mylogin		<-- login to the remote
-		remote$ kermit -x	<-- invoke remote kermit as server
-		C-Kermit server starting.  Return to your local machine by typing
-		its escape sequence for closing the connection, and issue further
-		commands from there.  To shut down the C-Kermit server, issue the
-		BYE command to logout, or the FINISH command and then reconnect.
+		[...]
+		remote$ kermit -ix	<-- remote kermit as binary server
+		[...]
 		^\C			<-- return to local kermit
 		C-Kermit> get bin_tgz*	<-- request files from remote
-		...			(wait long for transfer to complete)
+		[...]			(wait long for transfer to complete)
 		C-Kermit> finish	<-- terminate remote server
 		C-Kermit> connect
 		C-Kermit> exit		<-- exit remote kermit
@@ -875,20 +937,24 @@ Further Tips on Installing FreeBSD
 	the install profile will be active (i.e., you will find the
 	commands load_fd, extract etc available to you again).
 
-	If your disk has several operating systems, you may want to
-	install the Thomas Wolfram's os-bs boot manager for selecting
-	which system to boot.  os-bs135.exe if available from the
-	tools directory of the FreeBSD FTP site.  This works well
-	with DOS, OS/2, FreeBSD and other systems.  To install
-	it, boot the system with MS-DOS and insert the dos-floppy
-	containing os-bs135.exe in floppy drive A:.  Then enter the 
-	DOS commands:
+	If your disk has several operating systems, you may want
+	to install a boot manager such as Thomas Wolfram's os-bs
+	for selecting which system to boot.  os-bs135.exe and other
+	boot managers are available from the tools directory of
+	the FreeBSD FTP site.  os-bs works well with DOS, OS/2,
+	FreeBSD and other systems, however, it cannot currently
+	be used to boot FreeBSD from a second hard disk.  Another
+	boot manager, such as boot-easy should be used.
+
+	To install, for instance,  os-bs, boot the system with
+	MS-DOS and insert the dos-floppy containing os-bs135.exe
+	in floppy drive A:.  Then enter the DOS commands:
 	> A:
 	> os-bs135
 	> cd os-bs
 	> os-bs
 	A menu should now appear on the screen. Use the cursor keys
-	to highlight the install option and hit ENTER.    And follow the
+	to highlight the install option, hit ENTER, and follow the
 	instructions from there.
 
 	For more information about the ob-bs program, including its
@@ -966,4 +1032,4 @@ THANKS FOR USING THIS; that's what makes it all worthwhile.
  as they will end up in our personal mail spools.  We will be
  happy to make other arrangements]
 
-This is $Id: install_notes,v 1.4 1993/09/14 02:36:09 alm Exp $
+This is $Id: install_notes,v 1.5 1993/09/14 21:26:32 alm Exp $
diff --git a/etc/etc.i386/kc.profile b/etc/etc.i386/kc.profile
index 298ec56..3502893 100644
--- a/etc/etc.i386/kc.profile
+++ b/etc/etc.i386/kc.profile
@@ -25,7 +25,7 @@ bail_out() {
 	reboot_it
 }
 
-echo    enter '"copy"' at the prompt to copy the kernel on this
+echo    Enter '"copy"' at the prompt to copy the kernel on this
 echo    floppy to your hard disk.  enter anything else to reboot,
 echo	but wait for the machine to restart to remove the floppy.
 echo    ""
@@ -35,23 +35,23 @@ read todo
 
 if [ X"$todo" = Xcopy ]; then
 	echo    ""
-	echo    "what disk partition should the kernel be installed on?"
-	echo    "(e.g. "wd0a", "sd0a", etc.)"
+	echo    "What disk partition should the kernel be installed on?"
+	echo    "(e.g., "wd0a", "sd0a", etc.)"
 	echo    ""
 	echo -n "copy kernel to> "
 	while :; do
 		read diskpart junk
 		[ -c /dev/r$diskpart ] && break
-		echo "$diskpart: invalid partition"
+		echo "${diskpart}: invalid partition"
 		echo
 		echo -n "copy kernel to> "
 	done
 	echo    ""
-	echo    "checking the filesystem on $diskpart..."
+	echo    "Checking the filesystem on $diskpart..."
 	fsck -y /dev/r$diskpart
 	if [ $? -ne 0 ]; then
 		echo ""
-		echo "fsck failed...  sorry, can't copy kernel..."
+		echo "fsck failed...  Sorry, can't copy kernel..."
 		bail_out
 	fi
 	echo    ""
@@ -59,15 +59,15 @@ if [ X"$todo" = Xcopy ]; then
 	mount /dev/$diskpart /mnt
 	if [ $? -ne 0 ]; then
 		echo ""
-		echo "mount failed...  sorry, can't copy kernel..."
+		echo "mount failed...  Sorry, can't copy kernel..."
 		bail_out
 	fi
 	echo    ""
-	echo    "copying kernel..."
+	echo    "Please wait.  Copying kernel..."
 	cp /386bsd /mnt/386bsd
 	if [ $? -ne 0 ]; then
 		echo ""
-		echo "copy failed...  (?!?!?!)"
+		echo "Copy failed...  (?!?!?!)"
 		bail_out
 	fi
 	echo    ""
@@ -75,7 +75,7 @@ if [ X"$todo" = Xcopy ]; then
 	umount /mnt > /dev/null 2>&1
 	if [ $? -ne 0 ]; then
 		echo ""
-		echo "unmount failed...  shouldn't be a problem..."
+		echo "unmount failed...  Shouldn't be a problem..."
 	fi
 	bail_out
 fi