hardenedbsd/HardenedBSD
1
0
Fork 0
mirror of https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git synced 2024-11-28 12:07:10 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Since we don't have rfd0 anymore, put in a line that will actually work

Browse Source 
for generating floppies.

Mention mdconfig(8) instead of vnconfig(8).
This commit is contained in:
Daniel C. Sobral 2001-02-22 07:34:53 +00:00
parent 18e73fc02b
commit c2bcc0a208
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=72855
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
release/texts/FLOPPIES.TXT
View File

@ -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.