Subject: Re: What's a "real" elf loader like ?
To: None <tech-kern@netbsd.org>
From: Christos Zoulas <christos@astron.com>
List: tech-kern
Date: 06/16/2006 17:48:48
In article <20060616165153.GH12175@gallia.cubidou.net>,
Quentin Garnier  <cube@cubidou.net> wrote:
>-=-=-=-=-=-
>
>On Fri, Jun 16, 2006 at 03:07:13PM +0000, Christos Zoulas wrote:
>> In article <67a22f44bed1715672baa92e866f1538@zyx.in>,
>> Cherry G. Mathew  <cherry@zyx.in> wrote:
>> >Hi,
>> >
>> >I was wondering if someone could put down briefly and to the point, 
>> >what the NetBSD "elf" related shortcomings are.
>> >
>> >Here's my shallow understanding of the situation.
>> >
>> >- libsa has no standalone support for kernel modules, does not 
>> >understand all elf header types.
>> >- There are shortcomings related to kernel module linking, which uses 
>> >userspace ld ( for what ? How ? )
>> >
>> >It would be could to have a concise elf related feature "wishlist" for 
>> >NetBSD. It would probably make a well deserved
>> >"projects" entry at http://www.netbsd.org/contrib/projects.html
>> 
>> We really need to have an ELF linker inside the kernel, instead of pre-linking
>> the object file in userland. The current model makes symbol resolution in
>> lkms that depend on each other annoying.
>
>The last part is not true since ksyms.

Still you have to do the ugly symbol renames to avoid symbol collisions
to make lkms work standalone, without depending on others.

christos