Correct for mfsroot.flp now.

1 files changed, 4 insertions, 7 deletions

diff --git a/release/texts/FLOPPIES.TXT b/release/texts/FLOPPIES.TXT
index 2d3e9a4..c817d8c 100644
--- a/release/texts/FLOPPIES.TXT
+++ b/release/texts/FLOPPIES.TXT
@@ -10,15 +10,15 @@ This release still uses only one installation floppy, the boot.flp
 image. For convenience (and for the DEC ALPHA architecture, on which
 binaries are quite a bit larger), however, we also provide the
 functionality of boot.flp now "decoupled" into a kern.flp image,
-which contains just the boot kernel, and mfsroot.gz, which contains
+which contains just the boot kernel, and mfsroot.flp, which contains
 the compressed MFS root image that is normally stored as part of
 the kernel itself on the boot.flp image.  This allows you to boot
 from kern.flp, which will fit on a 1.44MB floppy even on the alpha,
-and then load mfsroot.gz from a 2nd floppy.  This also allows you
+and then use mfsroot.flp from a 2nd floppy.  This also allows you
 to easily make your own boot or MFS floppies should you need to customize
 some aspect of the installation process.  As long as the kernel is compiled
-with ``options MFS'' and ``options MFS_ROOT'', it will properly
-boot an mfsroot.gz image when run.  The mfsroot.gz image is simply
+with ``options MFS'' and ``options MFS_ROOT'', it will properly look for
+and boot an mfsroot.flp image when run.  The mfsroot.flp image is simply
 a gzip'd filesystem image, something which can be made rather
 easily using vnconfig(8).  If none of this makes any sense to you,
 don't worry about it - just use the boot.flp image as always; nothing
@@ -55,6 +55,3 @@ or
 work well, depending on your hardware and operating system environment
 (different versions of UNIX have totally different names for the
 floppy drive - neat, huh? :-).
-
-The only image which is copied onto a floppy as an ordinary file is
-mfsroot.gz, should you actually be using that image for something.