From: Dave Lukes <davel@anvil.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] python
Date: Fri, 5 Jan 2007 18:03:39 +1100 [thread overview]
Message-ID: <459DF84B.3010405@anvil.com> (raw)
In-Reply-To: <d00a9f70ecec5450b3aad09a38058d28@coraid.com>
There may be the germ of an insane but possibly usable idea here ...
What we need is a facility by which a program can glue together a bunch
of object files
when it's run ...
Now ?l can already do the gluing,
so why not replace any program that requires dynamic libraries with an
rc script
that links together all the required object files together on the fly
into a temporary file,
then executes the resultant file then removes it.
Yes, it's psychotic, but so are shared libs.
Of course, if you want to link at run-time rather than execute-time,
you're out of luck, but, pedantically, it will do most of what linux
does with .so files
with no changes lower down.
DaveL
(who's on holiday in Sydney and thinks that the next plan9 conference
definitely ought to be here).
erik quanstrom wrote:
> perhaps my assembly-language addled brain is just rebelling, but my snarky reaction
> to this python thread is this:
>
> eh, while you're at it, why not just run the whole dynamicly-bound
> bit in a 386-emulator. that way, when movietunes3000 really wants some
> bit of linux, you can just run it in the emulator.
>
> or, Just Run Linux™.
>
> my slightly more thoughtful reaction is, why does the operating system need to control
> the late-linking process? (python doesn't really need .so shared libraries per se, does it?)
> to me this seems more like a linker problem than anything else. why not write your own?
> you could write an rc script to gather the bits and waah laa. ... ooh, ron. i just invented
> linker scripts. ;-)
>
> - erik
>
next prev parent reply other threads:[~2007-01-05 7:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 22:31 ron minnich
2007-01-05 4:14 ` John Barham
2007-01-05 6:18 ` erik quanstrom
2007-01-05 7:03 ` Dave Lukes [this message]
2007-01-05 7:09 ` Bruce Ellis
2007-01-05 7:26 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2010-10-10 14:06 [9fans] Python Michaelian Ennis
2010-10-10 14:21 ` Federico G. Benavento
2010-10-11 1:30 ` Michaelian Ennis
2010-10-11 1:55 ` Steve Simon
2010-10-11 23:59 ` Michaelian Ennis
2006-12-23 21:50 [9fans] python Bad-Santa
2006-12-23 23:54 ` ron minnich
2006-12-24 1:00 ` Russ Cox
2006-12-25 0:28 ` LiteStar numnums
2006-12-30 5:06 ` John Floren
2006-12-23 5:10 ron minnich
2006-12-23 5:27 ` Russ Cox
2006-12-23 5:31 ` ron minnich
2006-12-23 6:19 ` Russ Cox
2006-12-23 7:13 ` arisawa
2006-12-23 13:29 ` LiteStar numnums
2006-12-23 14:23 ` arisawa
2006-12-23 20:20 ` Russ Cox
2006-12-23 11:57 ` Matt
2003-11-03 16:11 matt
2003-11-03 15:20 ` Russ Cox
2002-03-11 18:51 Russ Cox
2002-03-18 13:21 ` Boyd Roberts
2002-02-08 13:51 Boyd Roberts
2001-12-06 7:29 Russ Cox
2001-12-06 7:17 ` Lucio De Re
2001-12-02 9:39 Russ Cox
2001-12-02 12:08 ` Boyd Roberts
[not found] ` <rsc@plan9.bell-labs.com>
2001-12-02 16:05 ` Jonathan Sergent
2001-12-03 22:24 ` Laura Creighton
2000-11-06 8:26 [9fans] Python Jonathan Sergent
1999-01-16 5:53 arisawa
1998-12-30 0:17 arisawa
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=459DF84B.3010405@anvil.com \
--to=davel@anvil.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).