Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.lang.c
Subject: Re: Appending to executables.
Message-ID: <5398@brl-tgr.ARPA>
Date: Fri, 19-Oct-84 16:03:46 EDT
Article-I.D.: brl-tgr.5398
Posted: Fri Oct 19 16:03:46 1984
Date-Received: Sat, 20-Oct-84 07:19:08 EDT
References: <>, <404@ncoast.UUCP> <261@lzmi.UUCP>
Organization: Ballistic Research Lab
Lines: 13

> It is not true that one cannot write a Unix executable to which
> additional functions can be appended at runtime. One of the uses of
> shared memory, available in System V and V(2), is linking executables at
> runtime. All you need to do is define the shared memory, then fork and
> exec a process that copies some of its own functions into shared memory
> and then goes to sleep.

Can we absolutely count on being able to read instruction space and
write another chunk of instruction space from a user process?

The above idea seems pretty kludgy.  Will the new memory management
system for future UNIX System V (or whatever) support a reasonable
solution to shared libraries, dynamic linking, etc.?