86ff624834
so you don't need to re-enter it for each and every filesystem. Heads up! This change is incompatible with the previous scripting format, so those folks (all 2 of you) using config files should take a look at the changes to the sample install.cfg file for the diskLabelEditor's new calling syntax. Finally write a man page for this thing, documenting all of the above and more. I can't drive a stake through this thing's heart without properly documenting it first, so please consider this step #1 in that process (to be honest, sysinstall will also live on for some time in the 2.2. branch since it's unlikely that the new install tools will ever make it over there - they're strictly 3.0 material). |
||
---|---|---|
.. | ||
alpha | ||
amd64 | ||
floppies | ||
i386 | ||
pc98 | ||
picobsd/build | ||
scripts | ||
sysinstall | ||
ABOUT.TXT | ||
boot_crunch.conf | ||
doFS.sh | ||
dumpnlist.c | ||
fixit_crunch.conf | ||
fixit.profile | ||
fixit.services | ||
info.sh | ||
Makefile | ||
README.TXT | ||
tar.sh | ||
write_mfs_in_kernel.c |
For a normal CDROM or network installation, all you need to copy onto an actual floppy from this directory is the boot.flp image (for 1.44MB floppies). NOTE: These images are NOT DOS files! You cannot simply copy them to a DOS floppy as regular files, you need to *image* copy them to the floppy with fdimage.exe under DOS or `dd' under UNIX. For example: To create the boot floppy image from DOS, you'd do something like this: C> fdimage boot.flp a: Assuming that you'd copied fdimage.exe and boot.flp into a directory somewhere. If you were doing this from the base of a CD distribution, then the *exact* command would be: E> tools\fdimage floppies\boot.flp a: If you're creating the boot floppy from a UNIX machine, you may find that: dd if=floppies/boot.flp of=/dev/rfd0 or dd if=floppies/boot.flp of=/dev/floppy work well, depending on your hardware and operating system environment (different versions of UNIX have totally different names for the floppy drive - neat, huh? :-).