The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] SunOS vs Linux
Date: Fri, 6 Jan 2017 19:13:28 -0800	[thread overview]
Message-ID: <20170107031328.GJ16253@mcvoy.com> (raw)
In-Reply-To: <CANCZdfo-phrnKyuz=nfH7KAZ_gGdn8DYpkU2yc+UN4ar=07F2w@mail.gmail.com>

On Fri, Jan 06, 2017 at 08:09:18PM -0700, Warner Losh wrote:
> On Fri, Jan 6, 2017 at 7:58 PM, Greg 'groggy' Lehey <grog at lemis.com> wrote:
> > On Friday,  6 January 2017 at  9:27:36 -0500, Clem Cole wrote:
> >> On Thu, Jan 5, 2017 at 10:56 PM, Dan Cross <crossd at gmail.com> wrote:
> >>
> >>> Perhaps an interesting area of speculation is, "what would the world have
> >>> looked like if USL v BSDi hadn't happened *and* SunOS was opened to the
> >>> world?" I think in that parallel universe, Linux wouldn't have made it
> >>> particularly far: absent the legal angle, what would the incentive had been
> >>> to work on something that was striving to basically be Unix, when really
> >>> good Unix was already available?
> >>
> >>> I agree.
> >
> > I think that if SunOS 4 had been released to the world at the right
> > time, the free BSDs wouldn't have happened in the way they did either;
> > they would have evolved intimately coupled with SunOS.
> 
> With the right license (BSD), I'd go so far as to saying there'd be no
> BSD 4.4, or if there was, it would have been rebased from the SunOS
> base... There were discussions between CSRG and Sun about Sun donating
> it's reworked VM and VFS to Berkeley to replace the Mach VM that was
> in there... Don't know the scope of these talks, or if they included
> any of the dozens of other areas that Sun improved from its BSD 4.3
> base... The talks fell apart over the value of the code, if the rumors
> I've heard are correct.

So as much as I know, I was not privy to these talks.  I didn't even know
they were happening.


  reply	other threads:[~2017-01-07  3:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 17:08 Clem Cole
2017-01-06  2:32 ` ron minnich
2017-01-06  3:56 ` Dan Cross
2017-01-06  3:58   ` Larry McVoy
2017-01-06 14:27   ` Clem Cole
2017-01-07  2:58     ` Greg 'groggy' Lehey
2017-01-07  3:09       ` Warner Losh
2017-01-07  3:13         ` Larry McVoy [this message]
2017-01-07  3:12       ` Larry McVoy
2017-01-08 16:28   ` Angus Robinson
2017-01-08 18:02     ` Kay Parker   
2017-01-08 20:51       ` Clem cole
2017-01-09  3:00         ` Greg 'groggy' Lehey
2017-01-09  6:32           ` Arno Griffioen
2017-01-09  8:27             ` Wesley Parish
2017-01-09 13:07             ` Joerg Schilling
2017-01-09 15:57             ` Clem Cole
2017-01-09 16:08               ` ron minnich
2017-01-09 17:40                 ` Dan Cross
2017-01-09 17:32               ` Rico Pajarola
2017-01-10 11:02                 ` Joerg Schilling
2017-01-08 22:52     ` Wesley Parish
2017-01-09 19:45   ` Jacob Goense
2017-01-08  6:10 Kirk McKusick
2017-01-08 14:52 ` Ron Natalie

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=20170107031328.GJ16253@mcvoy.com \
    --to=lm@mcvoy.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).