I've implemented a crude work-around for the boot program load address
clash. It has been back-ported to the 1.4.2 branch.

In /usr/mdec, several versions of `boot' are installed, each linked
to run at a different virtual address. Boot image filesystem builders
can pick one which seems most suited to the image in question.
For instance, the `memory disk' image (bootfs) now picks `boot.700000'
to allow for the large INSTALL kernel + memory filesystem.

The default boot program is stil run at 0x300000.

(This is all rather sad..)

-pk