aboutsummaryrefslogtreecommitdiff
path: root/release
diff options
context:
space:
mode:
authorDaniel C. Sobral <dcs@FreeBSD.org>2001-02-22 07:34:53 +0000
committerDaniel C. Sobral <dcs@FreeBSD.org>2001-02-22 07:34:53 +0000
commitc2bcc0a2086d3a5dfb6343ca1974768d78a5cc6c (patch)
treebdf7c095ed7dce4c1fa4212d12085985f526cd04 /release
parent18e73fc02ba9bf441b2d6ccdbf05c6dd45bde450 (diff)
Notes
Diffstat (limited to 'release')
-rw-r--r--release/texts/FLOPPIES.TXT8
1 files changed, 3 insertions, 5 deletions
diff --git a/release/texts/FLOPPIES.TXT b/release/texts/FLOPPIES.TXT
index 5cd6af413b4d..4a60e5cc2a4a 100644
--- a/release/texts/FLOPPIES.TXT
+++ b/release/texts/FLOPPIES.TXT
@@ -20,12 +20,10 @@ Assuming that you'd copied fdimage.exe and kern.flp into a directory
somewhere. You would do the same for mfsroot.flp, of course.
If you're creating the boot floppy from a UNIX machine, you may find
-that:
+that one of the following:
+ dd if=floppies/kern.flp of=/dev/fd0
dd if=floppies/kern.flp of=/dev/rfd0
-
-or
-
dd if=floppies/kern.flp of=/dev/floppy
work well, depending on your hardware and operating system environment
@@ -54,6 +52,6 @@ hardware arise. As long as the kernel is compiled with
and boot an mfsroot.flp image in memory when run (see how the
/boot/loader.rc file in kern.flp does its thing). The mfsroot.flp
image is also just a gzip'd filesystem image which is used as root,
-something which can be made rather easily using vnconfig(8).
+something which can be made rather easily using mdconfig(8).
If none of that makes any sense to you then don't worry about it -
just use the kern.flp and mfsroot.flp images as described above.