Commit Graph

20 Commits

Author SHA1 Message Date
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
he 561186c423 Oops, need to descend into ramdisk-tiny now too. 2000-06-12 18:53:01 +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
he ceaccf4ae5 Add construction of three types of "rescue" images, based on the
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
2000-06-10 18:56:47 +00:00
hubertf baa1e576e4 Make it easier to comment out single targets/floppies. 2000-05-10 23:44:51 +00:00
mycroft 873c2fbd93 Build bootfloppy-small, as a 1.44MB floppy image. 2000-05-06 05:32:28 +00:00
mycroft 48b5b5f82c Build bootfloppy-tiny again. 2000-05-05 21:37:05 +00:00
mycroft 00975f989f Merge latest build system changes, and use the kernels built in ramdisk-kernel. 2000-05-05 20:13:29 +00:00
mycroft 64228ba734 Build in ramdisk-kernel. 2000-05-05 19:30:13 +00:00
sommerfeld 59c8861b20 Disable building of bootfloppy-tiny for now since we don't fit. 2000-04-23 15:05:02 +00:00
he eafd8f707f Provide some more automation in the "make release" process. Also build
and install:
 o INSTALL and INSTALL_TINY kernels (for boot floppy images)
 o GENERIC_TINY kernel
 o Boot floppy images
Ideas borrowed from etc/etc.sun3/ setup.
1999-11-09 00:22:39 +00:00
he 0c0355cfd9 bootfloppy-big/Makefile creates 2.88M diskette image suitable for CD-ROM boot.
(Depends on new disktab from etc/etc.i386/.)
Don't descend into bootfloppy and bootfloppy-small since these now overflow,
now do ramdisk, fdset, bootfloppy-big, and bootfloppy-tiny.
1999-02-01 21:55:31 +00:00
perry 274d4c2de2 Fixes to the install floppies
(from Havard.Eidnes@runit.sintef.no)
1998-10-12 16:32:16 +00:00
perry da801e20c2 Change default bootfloppy to 1.44M, and add a 1.2M "small" bootfloppy. 1997-11-05 03:39:51 +00:00
perry 3148c0e429 Initial commit of new single floppy install/upgrade system. 1997-06-14 18:56:00 +00:00
mikel d6af1b7d7c Merge separate kernel-copy floppies back into one. This is a stop-gap
measure; the next release will use something Different.
Update version number to 1.2C.
1997-02-18 07:38:15 +00:00
jtc 34d9f1513d merge in 1.2 branch 1996-10-09 00:13:36 +00:00
tls 9e67db5b49 This should now be OK for the 1.1 release. 1995-10-30 02:25:36 +00:00
cgd 20a68de085 only one kc now 1995-05-12 03:27:38 +00:00
cgd e9edc1803b i386 floppy build tools 1994-08-29 15:30:14 +00:00