The current support for ufs2 in libsa (used by the boot code) causes
the boot code to explode its size limit.

The obvious solution is to build separate versions of the code for
the very size sensitive parts of the boot sequence.  These bits of
code are typically installed in the first few blocks of a filesystem
so only need to know about their own fs type.

The problems start with naming the fs!
The obvious thing would be to have:
	ufsv1	ufsv1 support only
	ufsv2	ufsv2 support only
	ufs	v1 and v2 support
(done in a similar way to the current lfsv1/2 build)

The only downside is that some of the low level boot code will
need changing to pick up ufsv1 instead of ufs.

I want to be able to build a single copy of libsa and libkern for
multiple fs types.  Most of it isn't used and compiling all of it
for every fs variant is a waste of disk space and cpu cycles.

Thoughts?

	David

-- 
David Laight: david@l8s.co.uk