Reinstate INSTALL kernel for embedded ramdisk installs.

Reasons being:
- INSTALL is GENERIC with an embedded ramdisk, and as such, can benefit from
features included within.
- INSTALL_FLOPPY has its own config(5) file, and is tailored for "small"
floppy images; it misses features/drivers that could be needed to boot
in a decent environment for recent x86 machines (like ACPI)
- makes it closer to floppies distrib available for amd64

While here, comment out INSTALL_FLOPPY and bootfloppy-big image build. NetBSD
does not use the 3.6MiB image for El Torito cdroms anymore.

Remove the FLOPPYMAX limit; i386 needs 4 floppies now. Modify boot.cfg and
release/contents to reflect reality.

See http://mail-index.netbsd.org/port-i386/2011/02/08/msg002307.html

No comments, no objections.

branches: 1.37.14;
remove duplicate entry for bootfloppy-big

branches: 1.36.8; 1.36.12;
Remove GENERIC_LAPTOP and INSTALL_LAPTOP. To compensate, switch
bootfloppy-big to actually use INSTALL_LARGE (with ACPI) and 5 floppies.

branches: 1.35.8;
As has been pointed out recently, the list of i386 release kernels needs
updating. Probably to an ACPI kernel that need not fit into an 'emulated floppy'
and a 'legacy' kernel that will fit.
In any case the small/tiny kernels which are really for i386 systems with
< 16MB of memory (some are sized for a 5.25" floppy) don't need to be built.
Remove bootfloppy-small, bootfloppy-tiny, rescue-tiny and bootfloppy-ps2
and associated ramdisks.

Prepare creation of boot CDs:

* Move files in distrib/i386:

floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk-big/Makefile -> ramdisks/ramdisk-big/Makefile
floppies/ramdisk-big/disktab.preinstall -> ramdisks/ramdisk-big/disktab.preinstall
floppies/ramdisk-big/list -> ramdisks/ramdisk-big/list
floppies/ramdisk-big/list.inet6 -> ramdisks/ramdisk-big/list.inet6
floppies/ramdisk-rescuetiny/Makefile -> ramdisks/ramdisk-rescuetiny/Makefile
floppies/ramdisk-rescuetiny/list -> ramdisks/ramdisk-rescuetiny/list
floppies/ramdisk-small/Makefile -> ramdisks/ramdisk-small/Makefile
floppies/ramdisk-small/list -> ramdisks/ramdisk-small/list
floppies/ramdisk-tiny/Makefile -> ramdisks/ramdisk-tiny/Makefile
floppies/ramdisk-tiny/list -> ramdisks/ramdisk-tiny/list
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini

* Adjust paths

Restructure this Makefile to make it easier to comment out subdirectories.

Add bootfloppy-laptop-big, which creates bootlap-big.fs, which is a 2.88MB
version of bootlap[12].fs.
This is suitable for using as a boot file for an El Torito CD-ROM image
to be used to boot laptops, as it has the INSTALL_LAPTOP kernel
(instead of the INSTALL kernel that bootbig.fs has).

As both boot-small and rescue-small have expanded onto a second 1.2MB
floppy (and there's not the same RAM contraints that *-tiny has),
fold rescue-small into boot-small and deprecate the former.
The "all in one" boot-small is only 100KB larger on the second floppy.

Merge kernel-ramdisk & kernel-rescue into instkernel, now that
../../common/Makefile.mdset supports building multiple copies of the
same kernel (as long as they're to separate filenames).
Now there's no need to set FLOPPYKERNDIR, as it now defaults to instkernel.

- Convert to using distrib/common/buildfloppies.sh, which can build both
single and multi-volume floppies in better fashion that the crufty
shell commands in the various Makefiles.
- Move fdset* -> bootfloppy*, as that's more consistent

Yet Another Cleanup:
- factor more stuff into common/Makefile.*
- use NDWO makefile layout
- don't always rebuild bootfloppy-* and fdset-* stuff. (mmm, dependencies)
- add .WAIT sync in top level Makefile

Turn back on all floppies. They all build once again with both new and old
toolchains

1. delete all instances of /dev/{r,}vnd0d. Use vnconfig vnd0 and disklabel
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.

GCC 2.95 generates significantly larger code with -O2 than our old compiler did; thus we overflow the floppies. I thought we used to explicitly set -Os in here; anyway, with this change, we do now!

Add PS/2 bootfloppy, to be used for installation on IBM PS/2 machines.

Re-enable all floppies. All of them now build.

rescue-small is currently borked, too.

Who'd've guessed? The -tiny floppies don't build any more.

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.

branches: 1.19.2;
Oops, need to descend into ramdisk-tiny now too.

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.

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

Make it easier to comment out single targets/floppies.

Build bootfloppy-small, as a 1.44MB floppy image.

Build bootfloppy-tiny again.

Merge latest build system changes, and use the kernels built in ramdisk-kernel.

Build in ramdisk-kernel.

Disable building of bootfloppy-tiny for now since we don't fit.

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.

branches: 1.9.2; 1.9.6;
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.

Fixes to the install floppies
(from Havard.Eidnes@runit.sintef.no)

Change default bootfloppy to 1.44M, and add a 1.2M "small" bootfloppy.

branches: 1.6.2;
Initial commit of new single floppy install/upgrade system.

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.

merge in 1.2 branch

branches: 1.3.2; 1.3.6;
This should now be OK for the 1.1 release.

only one kc now

branches: 1.1.1;
Initial revision