The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Rico Pajarola <rp@servium.ch>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] History of symbol preemption
Date: Mon, 13 Jan 2020 14:20:21 -0800	[thread overview]
Message-ID: <20200113222021.GG8511@mcvoy.com> (raw)
In-Reply-To: <CACwAiQ=+J2A0GyAKh9ywuHCPbqT0h05HDmttOu5-raLXWJ8ZNw@mail.gmail.com>

On Mon, Jan 13, 2020 at 01:45:48PM -0800, Rico Pajarola wrote:
> On Mon, Jan 13, 2020 at 1:44 PM Paul Winalski <paul.winalski@gmail.com>
> wrote:
> 
> > On 1/13/20, Rico Pajarola <rp@servium.ch> wrote:
> > >
> > > yes, but unless my memory is playing tricks, SunOS a.out had this
> > feature.
> >
> > Do you mean support for shared libraries, or symbol preemption?
> >
> symbol preemption

My memory of this is it was dns lookups that wanted something like this.
SunOS really wanted the world to love YP but the world wanted Sun to
support DNS.  You could, and people did, make a shared lib that overloaded
the default gethostbyname(3) that wanted to do YP, the lib would provide
a DNS based one instead.

That's where I first learned of this stuff.  Gingell would know if you
want to know for sure.

  reply	other threads:[~2020-01-13 22:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 19:58 Paul Winalski
2020-01-13 20:46 ` Rico Pajarola
2020-01-13 21:04   ` Clem Cole
2020-01-13 21:40     ` Rico Pajarola
2020-01-13 21:44       ` Paul Winalski
2020-01-13 21:45         ` Rico Pajarola
2020-01-13 22:20           ` Larry McVoy [this message]
2020-01-13 21:42     ` Paul Winalski
2020-01-13 22:53       ` Henry Bent
2020-01-14  0:31         ` Clem Cole
2020-01-14  2:53 ` Rob Gingell
2020-01-14 19:21 ` [TUHS] two AIX items [was " Charles H Sauer
2020-01-14 20:31   ` Clem Cole
2020-01-14 23:22   ` Kevin Bowling
2020-01-15 16:41   ` Paul Winalski

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=20200113222021.GG8511@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=rp@servium.ch \
    --cc=tuhs@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).