From: Larry McVoy <lm@mcvoy.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Open sourcing SunOS?
Date: Wed, 22 Feb 2023 12:54:40 -0800 [thread overview]
Message-ID: <20230222205440.GB7194@mcvoy.com> (raw)
In-Reply-To: <CANCZdfoFiQ3oTorQcdPr8eqaXeQumdqsjkTqMD6i0HVDDVhWQA@mail.gmail.com>
On Wed, Feb 22, 2023 at 01:46:53PM -0700, Warner Losh wrote:
> On Wed, Feb 22, 2023 at 1:12 PM Larry McVoy <lm@mcvoy.com> wrote:
> > The networking stack in SunOS 4.x was BSD derived. You might be thinking
> > of Solaris, that took the Lachman STREAMS stack but that was 5.x, not
> > 4.x.
> >
>
> I was thinking of the streams stuff that's in 4.x BSD. There's AT&T
> copyrights
> on it. There's also, strangely, rfs sources included with some of the stuff
> one
> can find online. But it looks to be imported nearly verbatim from System V
> of some flavor with very few edits, judging by the 1.1 versions in many of
> the
> files.
I ripped out the STREAMS stuff (it was STREAMS, not dmr's streams).
And I ripped out RFS. There was more than 1.1 versions in some version
of SunOS, my former office mate, Howard Chartok, did a pile of work on
RFS.
> > As the only guy, that I'm aware of, who took all the encumbered stuff
> > out of the kernel, put back the BSD tty drivers and a few other small
> > things that resulted in a kernel that we could freely open source,
> > I beg to differ with:
> >
> > > Bits of the
> > > network stack as well. It was hopeless to try to open source. There was a
> > > lot of bits
> > > and pieces that Sun had done with contracts that were, at best, ambiguous
> > > for
> > > what to do should they want to open source it.
>
> I'm just reporting what my VP told me... Grepping through the source I can
> find online, the evidence is closer to what you say than what Glen told me.
> Either he or I must have confused Solaris 2 with SunOS 4.
Like I said, in 1992 or 1993, I had a BSD licensed SunOS 4.1.something,
I think 4.1.3, kernel. No STREAMS, no RFS, no STREAMS based tty drivers,
it was what lots of people called SunOS: "A bugfixed and improved BSD".
I shopped it around inside Sun and there were plenty of people who wanted
a reason to say it wasn't open source ready and they couldn't find one.
--
---
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2023-02-22 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 15:49 [TUHS] " Dan Cross
2023-02-22 16:23 ` [TUHS] " Robert Clausecker
2023-02-22 16:30 ` Dan Cross
2023-02-22 19:52 ` Dave Horsfall
2023-02-22 20:04 ` Warner Losh
2023-02-22 20:12 ` Larry McVoy
2023-02-22 20:44 ` Brad Spencer
2023-02-22 20:46 ` Warner Losh
2023-02-22 20:54 ` Larry McVoy [this message]
2023-02-23 0:12 ` Rob Gingell
2023-02-23 2:14 ` Warner Losh
2023-02-23 7:22 ` Rob Gingell
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=20230222205440.GB7194@mcvoy.com \
--to=lm@mcvoy.com \
--cc=imp@bsdimp.com \
--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).