The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] BSD/v8 TCP/IP (was Shell control through external commands)
Date: Mon, 12 Sep 2016 11:41:09 -0400	[thread overview]
Message-ID: <1473694872.12045.for-standards-violators@oclsc.org> (raw)

  Because of the design bug I mentioned, I searched for UNIX sources from AT&T
  that include streams support, but could never find any.

=====

None of the Research systems after 32/V was ever distributed except
to a handful of sites under site-specific letter agreements that
forbade redistribution.

This is a bug, not a feature, but there it is.  It was easy to get
approval to write a paper, much harder to get permission to distribute
code, especially when the code in some way overlapped the Official
Product.

Warren and I (and Dennis, when he was still alive) hoped to do
something about some years back, but it's a lot harder than it used
to be because it is harder to find a corporate entity that is
confident enough to give permission, even for stuff that is so old
that it is unlikely to have a trumppenceworth of commercial value.
Then IBM vs SCO intervened, and now things are even more fragmented.

There may be other efforts under way now and then to negotiate the
legal minefield.  I wish them all well, and will help them where I
can.

Norman Wilson
Toronto ON


             reply	other threads:[~2016-09-12 15:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 15:41 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-12 12:56 Norman Wilson
2016-09-12 15:27 ` Joerg Schilling
2016-09-12  1:31 [TUHS] Shell control through external commands Norman Wilson
2016-09-12  4:44 ` [TUHS] BSD/v8 TCP/IP (was Shell control through external commands) Greg 'groggy' Lehey
2016-09-12  5:24   ` Warner Losh
2016-09-12  5:38     ` Cory Smelosky
2016-09-12  5:48     ` Erik E. Fair
2016-09-12  9:22       ` Joerg Schilling
2016-09-12 10:25         ` Brantley Coile
2016-09-12 11:00           ` Joerg Schilling
2016-09-12 11:16             ` Brantley Coile
2016-09-12 11:42               ` Brantley Coile
2016-09-12 11:42               ` Joerg Schilling
2016-09-12  7:20     ` Greg 'groggy' Lehey
2016-09-12 18:32       ` Clem Cole
2016-09-13 10:52         ` Tony Finch
2016-09-13 12:54           ` Clem Cole

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=1473694872.12045.for-standards-violators@oclsc.org \
    --to=norman@oclsc.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).