From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <20100217133109.GA10816@nibiru.local>
References: <20100217133109.GA10816@nibiru.local>
Date: Wed, 17 Feb 2010 15:06:57 +0100
Message-ID: <599f06db1002170606l2178c152i2f92a36fbf405163@mail.gmail.com>
From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Binary format
Topicbox-Message-UUID: d4a6c05e-ead5-11e9-9d60-3106f5b1d025

On Wed, Feb 17, 2010 at 2:31 PM, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
> just curious: which binfmt does Plan9 use ?
> How are share libraries handled (if they exist at all) ?

a.out(6)
no shared libraries.

>
> Inspired by recent discussions @ gentoo-user, I'm thinking a bit
> how an simple and efficient binfmt could look like. Some key
> ideas are:
>
> * purely runtime information (no debug stuff, etc)

just strip it.

> * everthing's sharable/relocatable module, with strict dependencies
> * on exec() the process image will be constructed the modules along
> =A0the dependency tree (the main program as root)

no shared libraries.

> * each module may have an entry point (main module w/o is allowed,
> =A0even if it wouldn't make much sense ;-o), these are called after
> =A0relocation, along the dependency tree, from leaf to root.

no modules.


--=20
- curiosity sKilled the cat