requirement to build as root on a system with vnconfig.
Use ${KERNSRCDIR} and ${_SRC_TOP_} where appropriate
Remove now-obsolete:
list2sh.awk runlist.sh bootfloppy-common/list
Bootfloppy-*/Makefile: don't need to set DISKTYPE or BLOCK8K any more
Rename bootfloppy-common/Makefile.inc to common/Makefile.bootfloppy
and fdset-common/Makefile.inc to common/Makefile.fdset
This uses makefs instead of vnconfig and disklabel, thus removing the
need for root privileges to build these floppies..
Add common/Makefile.ramdisk, to simplify ramdisk-*/Makefile.
Uses shared ${_SRC_TOP_}/distrib/common/Makefile.crunch and
${_SRC_TOP_}/distrib/common/Makefile.image to even further simply things.
Migrate ramdisk-*/dot.profile to a shared common/dot.profile, which
detects whether it's an install or rescue profile based on the existance
of /sysinst. Remove /dev generation code as init(8) now does that for us.
Migrate common parts of */list to a shared common/list.ramdisk.
Convert ramdisk-*/list to new format used by distrib/common/parselist.awk
Don't bother running pwd_mkdb now that libhack's getpwent parses
/etc/master.passwd instead of /etc/passwd.
Migrate ramdisk-*/mtree.conf to a shared common/mtree.conf, which is now a
new full-path-style specfile.
Remove ramdisk-*/ramdiskbin.conf as it's now automatically generated
from ramdisk-*/list by parselist.awk.
Migrate ramdisk-*/termcap.mini to a shared common/termcap.mini.
Remove unused ramdisk-{small,tiny}/disktab.preinstall.
Use .for loops in kernel-*/Makefile to simply defining mostly-duplicated
targets.
ramdisk-*/Makefile: convert to using common/Makefile.ramdisk
Remove unused ramdisk-*/dot.hdprofile.
from ../bootfloppy-common/Makefile.inc like the other boot floppies.
it wasn't ustarfs that was broken, it was the broken PAD=yes code in the
latter trashing the last 8k of the kernel...
vnd0 and let opendisk(3) DTRT.
2. resize some of the images since we've gotten an average of 5K more
with the new toolchain.
3. comment out the rescue disks, since they don't fit anymore.
Now the whole directory compiles and works with the in-tree toolchain,
but does not work still with USETOOLS.
Also adjust the clean rule to first run the clean rule from ramdiskbin.mk
if it exists (cleans up the object subdirs then from the new crunchgen setup)
Since impatient users might think the machine locked up, print a message
'Creating real /dev (this may take a while) ...' so that they know what's
happening.
not padded to disk-size boundaries (except for boot-big, for somewhat
unnecessary reasons), and the included kernel is already gzipped. Adding
another round of gzip saves only tens of K, but creates a duplicate image,
wasting space on release media including these files.
Then once booted mount mfs onto /dev and make a full device tree. This gets
around the silliness of running out of either space/inodes all the time when
building the floppy images. Tested this on all combinations of floppies.
Then once booted mount mfs onto /dev and make a full device tree. This gets
around the silliness of running out of either space/inodes all the time when
building the floppy images. Tested this on all combinations of floppies.
+ build the passwd file before copying in ramdiskbin
+ don't copy MAKEDEV, run it, then delete it - run it in-place from
${.CURDIR}/...../etc.i386/MAKEDEV
Also, use LINK instead of SYMLINK for files under /usr - it's not a
separate filesystem.
Fixes PR misc/11473 and port-i386/11504 (until something else grows
again).
floppies as long as they fit, but they are the first to be sacrificed
if space is short, and get moved to a seperate rescue floppy.
This means that the default fdset and the 2.88M image have them,
but others (the "small" and "tiny" floppies) do not.
Sysinst is also back on the "tiny" image, and tested to be working
within 4M.
XXX1: clearly /bin/test and /bin/[ should be replaced by #!/bin/sh\ntest "$@"\n
XXX2: ramdisk-tiny/list should be generated from ramdisk/list to avoid skew;
XXX3: there is no point in including dump in ramdisk-tiny/list
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
lukem