The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Charles H Sauer <sauer@technologists.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Early shared library implementations
Date: Thu, 30 Sep 2021 09:12:00 -0500	[thread overview]
Message-ID: <3b9abb98-6265-fa2d-8956-3ce6a70a0979@technologists.com> (raw)
In-Reply-To: <202109301039.18UAdT0F026748@freefriends.org>

On 9/30/2021 5:39 AM, arnold@skeeve.com wrote:
> Paul Ruizendaal via TUHS <tuhs@minnie.tuhs.org> wrote:
> 
>> So far, I have not come across any shared library implementations or
>> precursors in early Unix prior to SunOS 4.
> 
> In more or less the same time frame, the AT&T UnixPC / 3B1, which was
> OEM'ed from Convergent, had shared libraries.  This was ~ 1986.
> 
> I don't know the details of how it worked and how one built the shared
> libraries; I am sure that it was an independent implementation from Sun's.
> 
> This was done on top of a System V Release 2 kernel.  Later versions
> of the OS had some bits of the SVR3 user land, but the kernel remained
> SVR2 based.
> 
> There is a 3B1 emulator and disk images for it available for anyone
> who really wants to go back to a system with short filenames and no
> job control. :-)

I'm very hazy on the details, because I wasn't directly involved, but we 
had shared libraries in AIX for the RT starting with the initial release 
in 1986 (based on SVR1). Larry Loucks did most of the design, with help 
from ISC folks and maybe Rick Simpson. Larry mentions this work in our 
AIX 2 paper 
(https://technologists.com/sauer/Advanced%20Interactive%20Executive%20(AIX)%20Operating%20System%20Overview.pdf) 
but I don't see any useful description, nor do I see anything useful 
skimming http://www.bitsavers.org/pdf/ibm/pc/rt/ docs. A more 
sophisticated shared library design was one of the additions in AIX 3.

Charlie

P.S. That paper and 
https://technologists.com/sauer/SA23-1057_IBM_RT_Personal_Computer_Technology_1986.pdf 
do include a bit more discussion of our memory mapped files since 
support for those was a primary goal of the 801 virtual memory design 
(summarized in the "Rosetta" paragraph of 
https://notes.technologists.com/notes/2017/03/08/lets-start-at-the-very-beginning-801-romp-rtpc-aix-versions/). 


-- 
voice: +1.512.784.7526       e-mail: sauer@technologists.com
fax: +1.512.346.5240         Web: https://technologists.com/sauer/
Facebook/Google/Twitter: CharlesHSauer

  reply	other threads:[~2021-09-30 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  9:01 [TUHS] mmap origin (was Systematic approach to command-line interfaces) Paul Ruizendaal via TUHS
2021-09-30 10:39 ` [TUHS] Early shared library implementations arnold
2021-09-30 14:12   ` Charles H Sauer [this message]
2021-10-11  6:43   ` Rob Gingell via TUHS
2021-10-11  7:08     ` George Michaelson
2021-10-11 14:22       ` Clem Cole
2021-10-17 22:19     ` Chris Hanson
2021-10-17 22:15   ` Chris Hanson
2021-09-30 12:56 ` [TUHS] mmap origin (was Systematic approach to command-line interfaces) Dan Halbert

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=3b9abb98-6265-fa2d-8956-3ce6a70a0979@technologists.com \
    --to=sauer@technologists.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).