On Sat, Apr 02, 2005 at 02:31:43PM -0500, jmk@plan9.bell-labs.com wrote:
> On Sat Apr  2 04:57:40 EST 2005, noselasd@asgaard.homelinux.org wrote:
> > ...
> > .. "See dynld(2)."
> > Well, there is no dynld :-) Beeing a curious person, what is/was
> > dynld ?
> 
>      DESCRIPTION
>           These functions allow a process to load further code and
>           data into the currently executing image.  A dynamically-
>           loadable file, called a module here, is a variant of the
>           a.out(6) executable format with some extra components.  The
>           loader for the architecture (see 2l(1)) creates a module
>           file from component object file(s) when given the -u option.
>           A module contains text and data sections, an import table,
>           an export table, and relocation data.  The import table
>           lists the symbols the module needs from the loading program;
>           the export table lists symbols the module provides when
>           loaded.  A program that loads a module provides a table of
>           its own symbols to match the symbols in the module's import
>           table.
> 
> Last summer I did a kernel module driver but a better management scheme
> was suggested and I ripped it out and started again. But never finished.
> 
> --jim

Need someone to finish this? I would really like it for the
filters I'm writing for nfil (/n/sources/dodell/nfil)

--Devon