9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Raschke <rtrlists@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Binary format
Date: Wed, 17 Feb 2010 15:13:20 +0000	[thread overview]
Message-ID: <6a3ae47e1002170713g43f643b6l2a2e4a1ef2c56df9@mail.gmail.com> (raw)
In-Reply-To: <20100217143303.GC10816@nibiru.local>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

On Wed, Feb 17, 2010 at 2:33 PM, Enrico Weigelt <weigelt@metux.de> wrote:

> * Gorka Guardiola <paurea@gmail.com> wrote:
> > 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.
>
> 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

[-- Attachment #2: Type: text/html, Size: 2372 bytes --]

  parent reply	other threads:[~2010-02-17 15:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 13:31 Enrico Weigelt
2010-02-17  8:50 ` Jacob Todd
2010-02-17 13:58   ` Enrico Weigelt
2010-02-17 14:01     ` erik quanstrom
2010-02-17 14:06 ` Gorka Guardiola
2010-02-17 14:13   ` David Leimbach
2010-02-17 14:33   ` Enrico Weigelt
2010-02-17 14:55     ` Steve Simon
2010-02-17 15:04       ` Enrico Weigelt
2010-02-17 15:29         ` erik quanstrom
2010-02-17 15:48         ` blstuart
2010-02-17 17:54           ` lucio
2010-02-17 18:37         ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-17 19:00         ` Nick LaForge
2010-02-18 15:08         ` Patrick Kelly
2010-02-17 15:58       ` David Leimbach
2010-02-17 16:14       ` Stuart Morrow
2010-02-17 16:28         ` David Leimbach
2010-02-17 18:21           ` Enrico Weigelt
2010-02-17 18:34             ` David Leimbach
2010-02-17 19:02               ` Enrico Weigelt
2010-02-17 19:35                 ` Enrico Weigelt
2010-02-17 18:38             ` Corey Thomasson
2010-02-18 15:16             ` Patrick Kelly
2010-02-17 15:13     ` Robert Raschke [this message]
2010-02-17 21:32     ` Jacob Todd
2010-02-17 21:26   ` Nathaniel W Filardo
2010-02-17 23:16     ` EBo
2010-02-17 23:22       ` David Leimbach
2010-02-17 14:38 ` blstuart
2010-02-17 14:58   ` Enrico Weigelt
2010-02-17 15:25     ` blstuart

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=6a3ae47e1002170713g43f643b6l2a2e4a1ef2c56df9@mail.gmail.com \
    --to=rtrlists@googlemail.com \
    --cc=9fans@9fans.net \
    /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).