> 
> Having the linker as in-kernel process would also make it possible (besides
> other neat things) to allow modload on higher securelevel. Since
> modload would always upload only "raw" mod.o file, it's possible
> to register "safe" lkms and allow to load only those later on.
> 
Yep, that is one of the goals for step two. Or actually, the linker
itself keeps track of which modules are eferenced and loads and unloads
them when needed. This is something that will be described in the 
software design specification for this that is planned.

> I'll gladly help with this, if you would need one more coder :)
> 
I'll keep that in mind :-)

-- Ragge