From: "Devon H. O'Dell " <dodell@offmyserver.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: programming style under Plan9??
Date: Sat, 2 Apr 2005 22:57:05 +0200 [thread overview]
Message-ID: <20050402205705.GL92880@smp500.sitetronics.com> (raw)
In-Reply-To: <067bdf1802892bc4ecab67c558aed529@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2005-04-02 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 1:34 I RATTAN
2005-04-02 2:40 ` Ronald G. Minnich
2005-04-02 3:34 ` Brantley Coile
2005-04-02 4:06 ` Russ Cox
2005-04-04 9:56 ` Gorka Guardiola
2005-04-04 13:24 ` jmk
2005-04-04 14:20 ` Charles Forsyth
2005-04-02 9:31 ` Charles Forsyth
2005-04-02 9:56 ` noselasd
2005-04-02 19:31 ` jmk
2005-04-02 20:57 ` Devon H. O'Dell [this message]
2005-04-02 22:08 ` jmk
2005-04-02 12:36 ` Brantley Coile
2005-04-02 3:54 ` Russ Cox
2005-04-02 13:11 ` I RATTAN
2005-04-02 15:50 ` Ronald G. Minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050402205705.GL92880@smp500.sitetronics.com \
--to=dodell@offmyserver.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).