>
>6) The crunched binaries are not built by a normal build.sh, so
>   many developers tracking current won't build them.

They are part of the builds of distrib which only gets done on release
builds. Anyone using build.sh to build releases would get this, so how are
you thinking they're not built by build.sh? (I consider build, distribution
and release to all be valid "normal" builds via build.sh).

>
>7) The ramdisk image size has to match the size of the gap in the
>   kernel.  These are set in two different places, but have to match.

Yes, tracking them in 2 places sucks. In general the size is made in the
kernel of "should be big enough" and then the image is shoved into there
which usually means slop.

James