The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick+tuhs@gmail.com (Nick Downing)
Subject: [TUHS] SVR4 x86 -- Sources
Date: Tue, 12 Jul 2011 21:54:08 +1000	[thread overview]
Message-ID: <CAH1jEzayh9XWAGy7nVpPCuRQCfDNnzLJ1j6Aw8jNPb3ya0h54Q@mail.gmail.com> (raw)
In-Reply-To: <ED332722-0FCC-4FC7-9CF0-A49DE67FA597@tfeb.org>

Yes, but I think the SunOS 4 shared library stuff was based on a.out,
I remember looking at the ld.so source code and thinking how simple
and elegant it all was, until those SysV people got their hands on it
and created ELF ;)  What SysV release introduced ELF though?
cheers, Nick

On Tue, Jul 12, 2011 at 9:22 PM, Tim Bradshaw <tfb at tfeb.org> wrote:
> On 12 Jul 2011, at 10:57, Nick Downing wrote:
>
>> Also as I understand it, SunOS was a BSD which had heaps of
>> development and original ideas put into it (shared libraries I think
>> is one example), but was discarded as a political decision because
>> AT&T had managed to convince most corporate customers that BSD was
>> merely a hack and SysV was the "real unix", so Sun decided to create
>> Solaris instead by licensing SysV as a starting point, I may have
>> things slightly backward so I would appreciate if anyone can confirm
>> this?
>
> I think that's basically correct, although in some technical sense "SunOS" is still the name for the OS component of Solaris (or was until recently - Oracle have probably renamed it), so you probably mean "SunOS n" where n<=4.
>
> I think (though I am not sure) that a lot of the virtual memory and shared library stuff which originated in SunOS 4 moved wholesale into SunOS 5, as well.



  reply	other threads:[~2011-07-12 11:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 10:29 Michele Ghisolfo
2011-07-11 12:42 ` Michael Kerpan
2011-07-11 12:53   ` Jim Capp
2011-07-14 17:42     ` Al Kossow
2011-07-14 17:46       ` Jason Stevens
2011-07-15  4:10         ` Random832
2011-07-15  4:22           ` John Cowan
2011-07-12  7:54   ` Wesley Parish
2011-07-12  9:53     ` Nick Downing
2011-07-19 23:17       ` Doug McIntyre
2011-07-20  0:42         ` Larry McVoy
2011-07-20  3:16         ` John Cowan
2011-07-20  4:04           ` Warner Losh
2011-07-12  9:57     ` Nick Downing
2011-07-12 11:22       ` Tim Bradshaw
2011-07-12 11:54         ` Nick Downing [this message]
2011-07-11 12:50 ` Sergio Aguayo
     [not found] ` <4E1B6A45.40607@laposte.net>
2011-07-11 19:50   ` Michele Ghisolfo
2011-07-11 21:56     ` Jason Stevens
2011-07-11 20:08       ` Michele Ghisolfo
2011-07-11 22:56         ` Warren Toomey
2011-07-12 13:04       ` Milo Velimirović
2011-07-12 13:07         ` Jason Stevens
     [not found] <1310385759.2145.18.camel@localhost.localdomain>
2011-07-11 14:09 ` Sergio Aguayo
2011-07-12 13:24 Norman Wilson
2011-07-12 15:11 Michele Ghisolfo
2011-07-12 23:26 ` Larry McVoy
2011-07-13  0:23   ` Jason Stevens
2011-07-13 13:25     ` Arno Griffioen
2011-07-13  2:48   ` John Cowan
2011-07-13  3:07     ` Larry McVoy
2011-07-14 17:37   ` Al Kossow
2011-07-15  4:30 ` Warren Toomey

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=CAH1jEzayh9XWAGy7nVpPCuRQCfDNnzLJ1j6Aw8jNPb3ya0h54Q@mail.gmail.com \
    --to=downing.nick+tuhs@gmail.com \
    /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).