From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <067bdf1802892bc4ecab67c558aed529@plan9.bell-labs.com>
Date: Sat,  2 Apr 2005 14:31:43 -0500
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OT: programming style under Plan9??
In-Reply-To: <b57e680b81a035a8a27e762bf4fe81f4@smtp.songnetworks.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 31a5b2ca-ead0-11e9-9d60-3106f5b1d025

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