tar(1), but actually uses cpio(1). Many people are getting confused
about the lack of a tar on the fixit floppy, and simply don't know
that cpio can basically handle tar format fine (or they simply don't
know how to invoke cpio).
BLOAT! BLOAT! BLOAT! BLOAT!
Yes, but where else to put these stinking compat distributions. I, for one,
am bone tired of creating them by hand and then having everyone tell me I left
something out/in. Now any commiter can adjust the list as necessary, and I
forsee this as being so seldom necessary that I've simply committed the
uuencoded tarballs - these are from the last SNAP, and nobody complained
(for once) about that set.
. Don't gzip the crunched binary by now; it just fits, and execution is
a lot faster this way (it's truly demand-paged again).
. Add more(1), ft(8), protocols(5), a stripped down services(5).
. Improve the .profile, and make sysinstall actually use it again.
Still no go for a 4 MB configuration though. :-(
First, change sysinstall and the Makefile rules to not build the kernel
nlist directly into sysinstall now. Instead, spit it out as an ascii
file in /stand and parse it from sysinstall later. This solves the chicken-n-
egg problem of building sysinstall into the fsimage before BOOTMFS is built
and can have its symbols extracted. Now we generate the symbol file in
release.8.
Second, add Poul-Henning's USERCONFIG_BOOT changes. These have two
effects:
1. Userconfig is always entered, rather than only after a -c
(don't scream yet, it's not as bad as it sounds).
2. Userconfig reads a message string which can optionally be
written just past the boot blocks. This string "preloads"
the userconfig input buffer and is parsed as user input.
If the first command is not "USERCONFIG", userconfig will
treat this as an implied "quit" (which is why you don't need
to scream - you never even know you went through userconfig
and back out again if you don't specifically ask for it),
otherwise it will read and execute the following commands
until a "quit" is seen or the end is reached, in which case
the normal userconfig command prompt will then be presented.
How to create your own startup sequences, using any boot.flp image
from the next snap forward (not yet, but soon):
% dd of=/dev/rfd0 seek=1 bs=512 count=1 conv=sync <<WAKKA_WAKKA_DOO
USERCONFIG
irq ed0 10
iomem ed0 0xcc000
disable ed1
quit
WAKKA_WAKKA_DOO
Third, add an intro screen to UserConfig so that users aren't just thrown
into this strange screen if userconfig is auto-launched. The default
boot.flp startup sequence is now, in fact, this:
USERCONFIG
intro
visual
(Since visual never returns, we don't need a following "quit").
Submitted-By: phk & jkh
pick up the old CVSROOT if we don't have the environment variable set.
If /usr/src/release/install.cfg is present, put it out onto
the root filesystem of the boot floppy. It may optionally be
used to pre-configure sysinstall with custom values. (See next
batch of commits).
