Use this in bootfloppy-big. mkisofs likes to have images fullsize nowadays.
Also, insert a file called "USTAR.volsize.<blocksize_in_octal>" if the
size of the ustar image is not the 1.44M default. This stops bootfloppy-big
from asking for a second diskette.
move it to ${IMAGE} when done, to ensure that an interrupted
build does not leave a broken non-functional target. (This can occur,
for instance, if one types 'make' as a non-root user and the vnconfig
fails, and then a subsequent 'make' will not rebuild the filesystem
image, using the all-zeroes image created by dd.)
files have copyright held by people in addition to myself. (I did the
original work, they copied it, enhanced it, and added their copyright
to the derivative work.) Their approval has been given re: the license
change.
o Wave goodbye to INSTALL_SMALL-based boot image (it was originally
built for 5.25" media, but isn't anymore).
o Make a separate ramdisk image for the INSTALL_TINY image,
using the old script-based installer (not fixed/checked at the moment).
However, at least tweak the profile scripts to start it instead of sysinst.
Also remove ping6 and rtsol from ramdisk compared to original; the
INSTALL_TINY image doesn't have INET6.
o Add dump/restore back into both ramdisk images.
o Add scsictl and chio to the normal ramdisk image (INSTALL-based fdset)
o With dump/restore reinstated, remove the rescue-* and ramdisk-rescue
directories.
So, we're now back to having the recovery tools on the same image as
the boot media images.
boot images.
The difference compared to the boot images is that these do not contain
sysinst, but do on the other hand contain dump/rdump, restore/rrestore,
scsictl and chio in addition to the other stuff already on the install
floppies.
The images built are
rescue1.fs
rescue2.fs Based on the full INSTALL kernel, on two floppies
rescue-sm.fs Based on INSTALL_SMALL
rescue-ti.fs Based on INSTALL_TINY
