> Since a.out files don't contain the address to load things at, the
> bootloader has to have wired-in knowledge of where the kernel goes.  ELF,
> of course, doesn't suffer from this.
> 
ELF would solve many problems but it's not exactly trivial to change too. 
> It's also worth noting that libkvm currently has the value of
> VM_MAXUSER_ADDRESS compiled into it, so changing it may cause
> compatibility issues there.
> 
Yes but the m68k code has to deal with this being variable so maybe it is 
possible to do the same on arm32 to get people over the compatibility problems 
without causing too much pain. If this can be done it removes at least one 
obstacle to the relocation.

Mike

Mike