c73933598a
When building a release, RELEASE_CRUNCH is defined for a `make' of the objects required by the crunch of each program. The object list is still obtained in the same way, so you must make sure that all objects are built (empty if necessary) by this make. ppp/Makefile provides an example. Reviewed by: jkh |
||
---|---|---|
.. | ||
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? :-).