The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick@gmail.com (Nick Downing)
Subject: [TUHS] SVR4 x86 -- Sources
Date: Tue, 12 Jul 2011 19:53:46 +1000	[thread overview]
Message-ID: <CAH1jEzYnncpNZfOHT_J0UKZ=nWFZ6rqrhBW2AA44iAvVT80rmQ@mail.gmail.com> (raw)
In-Reply-To: <1310457285.4e1bfdc575d76@www.paradise.net.nz>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3308 bytes --]

On Tue, Jul 12, 2011 at 5:54 PM, Wesley Parish
<wes.parish at paradise.net.nz> wrote:
> For what it's worth, if I remember correctly, 4.3BSD was one of the major
> contributions to SVR4. I suspect that if it hadn't been, nobody would've bought it.

My understanding had been that BSD and SysV were quite distinct and
that BSD forked off around the early research editions (V6 or V7?), if
indeed 4.3BSD was a major contributor to SVR4 then it would have been
in a few specific areas, e.g. the sockets code, because SysV had its
own competing idea called STREAMS that I believe was later discarded
(or not used much) when the BSD sockets API became the de facto
standard.  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?

cheers, Nick

> From what I've read, people bought SVRx for the source code license, and then
> bought the 4.xBSD for the reliability and usability.
>
> And yes, it would be nice if the entire SysVRx source trees were released under
> a suitable FOSS license; but I think the usefulness of such a gesture would be
> in stymieing any future "The SCO Group" shenanigans, and I don't know that such
> acts of self-preservation are quite the flavour of the month with modern
> software companies.
>
> Wesley Parish
>
> Quoting Michael Kerpan <madcrow.maxwell at gmail.com>:
>
>> On Mon, Jul 11, 2011 at 6:29 AM, Michele Ghisolfo <ghisolfo.m at gmail.com>
>> wrote:
>> >  Hi,
>> >
>> >  I'm currently reading J. Lion's commentary of Unix Code Level Six.
>>  It
>> > is the most useful commentary to operating system kernel I have ever
>> > read.
>> >
>> >  It would be really useful to also have the source code of SVR4
>> kernel
>> > for Intel x86.  Does anyone have that?
>> >
>> > _______________________________________________
>> > TUHS mailing list
>> > TUHS at minnie.tuhs.org
>> > https://minnie.tuhs.org/mailman/listinfo/tuhs
>> OpenSolaris is derived from SVR4 and much of the userland stuff is
>> still quite similar to the original release. Sadly, System V as a
>> whole is still regarded as a commercial product and no source is
>> available. If you want the source code for a decent early-90s Unix
>> implementation, I'd take a look at 4.4BSD. It's not SVR4, but it's
>> from the same era and has many of the same abilities.
>>
>> Mike
>> _______________________________________________
>> TUH S mailing list
>> TUHS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuh s
>>
>
>
>
> "Sharpened hands are happy hands.
> "Brim the tinfall with mirthful bands"
> - A Deepness in the Sky, Vernor Vinge
>
> "I me.  Shape middled me.  I would come out into hot!"
> I from the spicy that day was overcasked mockingly - it's a symbol of the
> other horizon. - emacs : meta x dissociated-press
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>



  reply	other threads:[~2011-07-12  9:53 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 [this message]
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
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='CAH1jEzYnncpNZfOHT_J0UKZ=nWFZ6rqrhBW2AA44iAvVT80rmQ@mail.gmail.com' \
    --to=downing.nick@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).