When building a release, RELEASE_CRUNCH is defined for a `make' of
the objects required by the crunch of each program. The object list
is still obtained in the same way, so you must make sure that all
objects are built (empty if necessary) by this make. ppp/Makefile
provides an example.
Reviewed by: jkh
moment - the compile-time options are useless since the object
files are being used from ppp to build the crunched image, and
the ppp objects include DES at this stage since they were last
built that way to make the secure distribution. Hmmmm!
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
. 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. :-(
`make release':
. the `doc' distribution was missing, so the FAQ and handbook files
couldn't be installed (Q: why did the psd etc. files install, only
that the dirs had the wrong ownership?)
. the crunched binaries do need now -lipx
floppy (for slip install).
2. Try to work around a bodge in the ftp extraction loop where FtpEOF() was
being called more than once. Also fix a problem where the URL was getting
smashed in the environment by copying it to a temporary area before we
jump up and down on it.
