From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20100217143303.GC10816@nibiru.local> References: <20100217133109.GA10816@nibiru.local> <599f06db1002170606l2178c152i2f92a36fbf405163@mail.gmail.com> <20100217143303.GC10816@nibiru.local> Date: Wed, 17 Feb 2010 15:13:20 +0000 Message-ID: <6a3ae47e1002170713g43f643b6l2a2e4a1ef2c56df9@mail.gmail.com> From: Robert Raschke To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0015175cd87e6ec263047fcd4a56 Subject: Re: [9fans] Binary format Topicbox-Message-UUID: d4e1ad0e-ead5-11e9-9d60-3106f5b1d025 --0015175cd87e6ec263047fcd4a56 Content-Type: text/plain; charset=UTF-8 On Wed, Feb 17, 2010 at 2:33 PM, Enrico Weigelt wrote: > * 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. > > ah, already suspected that ;-o > > I know that plan9's standard libraries are so small, that they > dont really need to be shared. But when more and more applications > von *nix world get ported, the problem might arise again. > Well, I know that it is very tempting to "just" port across lots of programs. But if you are looking to solve an actual problem (in a business or "just do it" sense) and there is nothing on Plan 9 to help you with that, then use Linux or Windows or OSX or ... On the other hand, if you are really interested in providing functionality to be used within Plan 9 that I'd strongly suggest investigating more than a port. Re-implementing using the appropriate Plan 9 approach would be way more beneficial. > And another important feature of shared libraries is, that when > some lib is updated, importing programs dont have to be recompiled. > What's the Plan9 solution here ? > :-) Recompile. (The usual argument to counter this approach is that security updates to underlying libs are easier to get out across to everyone, while at the same time completely ignoring the depths of DLL Hell and the myriads of wonderfull new ways to break perfectly fine software all over the place. Me, cynical, noooo! :-) Robby --0015175cd87e6ec263047fcd4a56 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Wed, Feb 17, 2010 at 2:33 PM, Enrico Weig= elt <weigelt@metux= .de> wrote:
* Gorka Guardiola <paurea@gmail.com> wrote:
> On Wed, Feb 17, 2010 at 2:31 PM, Enrico Weigel= t <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.

ah, already suspected that ;-o

I know that plan9's standard libraries are so small, that they
dont really need to be shared. But when more and more applications
von *nix world get ported, the problem might arise again.
<= div>
Well, I know that it is very tempting to "just" port acro= ss lots of programs. But if you are looking to solve an actual problem (in = a business or "just do it" sense) and there is nothing on Plan 9 = to help you with that, then use Linux or Windows or OSX or ...

On the other hand, if you are really interested in providing functional= ity to be used within Plan 9 that I'd strongly suggest investigating mo= re than a port. Re-implementing using the appropriate Plan 9 approach would= be way more beneficial.
=C2=A0
And another important feature of shared libraries is, that when
some lib is updated, importing programs dont have to be recompiled.
What's the Plan9 solution here ?

:-) Re= compile.

(The usual argument to counter this approach is that securi= ty updates to underlying libs are easier to get out across to everyone, whi= le at the same time completely ignoring the depths of DLL Hell and the myri= ads of wonderfull new ways to break perfectly fine software all over the pl= ace. Me, cynical, noooo! :-)


Robby
=C2=A0

--0015175cd87e6ec263047fcd4a56--