From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <599f06db1002170606l2178c152i2f92a36fbf405163@mail.gmail.com> References: <20100217133109.GA10816@nibiru.local> <599f06db1002170606l2178c152i2f92a36fbf405163@mail.gmail.com> Date: Wed, 17 Feb 2010 06:13:08 -0800 Message-ID: <3e1162e61002170613v1bcd8862j4c036a28378214b0@mail.gmail.com> From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd70d901ef4db047fcc7336 Subject: Re: [9fans] Binary format Topicbox-Message-UUID: d4b1fc26-ead5-11e9-9d60-3106f5b1d025 --000e0cd70d901ef4db047fcc7336 Content-Type: text/plain; charset=ISO-8859-1 And all of the below are some of the reasons I still love plan 9. Simplicity first is a really great way to work (I've learned over the years). Dave On Wed, Feb 17, 2010 at 6:06 AM, Gorka Guardiola wrote: > On Wed, Feb 17, 2010 at 2:31 PM, Enrico Weigelt 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 > > the dependency tree (the main program as root) > > no shared libraries. > > > * each module may have an entry point (main module w/o is allowed, > > even if it wouldn't make much sense ;-o), these are called after > > relocation, along the dependency tree, from leaf to root. > > no modules. > > > -- > - curiosity sKilled the cat > > --000e0cd70d901ef4db047fcc7336 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable And all of the below are some of the reasons I still love plan 9. =A0Simpli= city first is a really great way to work (I've learned over the years).=

Dave

On Wed, Feb 17, = 2010 at 6:06 AM, Gorka Guardiola <paurea@gmail.com> wrote:
On Wed, Feb 17, 2010 at 2= :31 PM, Enrico Weigelt <weigelt@metu= x.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 dependencie= s
> * 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 afte= r
> =A0relocation, along the dependency tree, from leaf to root.

no modules.


--
- curiosity sKilled the cat


--000e0cd70d901ef4db047fcc7336--