Commit Graph

17 Commits

Author SHA1 Message Date
jmc af957ccb50 Make sure crunchgen remakes the makefile everytime and it doesn't use it's
cache since other Makefiles could change source files too easily.
2001-02-25 03:54:24 +00:00
jmc 26563cce4d Trim down /dev entries to only things that are configured in INSTALL_TINY
kernels (which doesn't include sd, ld, etc). Tested on a 4M constrained
machine.
2001-01-24 18:16:43 +00:00
jmc 6e076acf2e Add var/spool/lock so tip works 2000-12-24 23:50:48 +00:00
jmc 55d6fd3a35 Force crunchgen to remake the makefile each time. This way dependency checking can occur 2000-12-17 09:57:48 +00:00
jmc 00bf71bd90 Replace less (1) with more(1) so the smaller images build. 2000-12-14 22:28:31 +00:00
simonb 9bb5785535 Adjust a couple of things to use less temporary space:
+ 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).
2000-11-16 13:21:05 +00:00
garbled 83f61a5891 Change all ocurrences of "crunchgen" to ${CRUNCHGEN} 2000-11-01 07:57:55 +00:00
fvdl 350aa78fde Re-add another merge victim: generation of the obsolete file lists. 2000-09-27 17:43:49 +00:00
fvdl 37f785d55d Rearrange bootfloppies. The idea is that "rescue" tools go on the
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.
2000-09-27 16:04:13 +00:00
fvdl 7864d584a1 Remove old files in preparation of rearrangement. 2000-09-27 15:45:40 +00:00
jlam aa8883f44d Make the `clean' target match the one in ../ramdisk/Makefile. 2000-09-10 18:55:15 +00:00
jhawk a022cf9d37 Use
${MAKE}
instead of
  make
2000-08-30 23:51:46 +00:00
jhawk 5b7f59e5d1 For all filesytem image building targets, build ${IMAGE}.tmp and
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.)
2000-07-06 18:16:35 +00:00
cgd c85d2eb42b sweep of my licenses for consistency. (no functional changes) These
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.
2000-06-14 22:52:37 +00:00
cgd db755e7c76 sweep of my licenses (userland files w/o only my copyright) for
consistency.  (no functional changes)
2000-06-14 17:24:02 +00:00
cgd d220ca5ba3 fix up NetBSD RCS Ids to match the standard, and the leading comment as
to match as well.  No functional changes.
2000-06-14 06:48:47 +00:00
he 5ebb61c202 Fix the previous in another way:
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.
2000-06-12 18:51:14 +00:00