The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: paul.winalski@gmail.com (Paul Winalski)
Subject: [TUHS] System Economics
Date: Thu, 16 Mar 2017 17:28:08 -0400	[thread overview]
Message-ID: <CABH=_VTE0+Sc-_ez=iho6jBOW8Jhfot6xMkt2LLTNqyC9R2aKA@mail.gmail.com> (raw)
In-Reply-To: <201703161933.v2GJXAdo144602@tahoe.cs.Dartmouth.EDU>

On 3/16/17, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> "Open" was certainly not a work heard in the Unix lab,
> where our lawyers made sure we knew it was a "trade secret".
> John Lions was brought into the lab both because we admired
> his work and because the lawyers wanted to reel that work
> back in-house.

That matches my recollection:  AT&T treated the UNIX sources as a
trade secret.  When I worked on DEC's port of the VAX/VMS linker to
Ultrix, our team was very careful to work from the a.out specification
only, and to avoid any contact with the sources to ld.  We wanted to
avoid any chance of AT&T claiming that our VMS linker port in any way
used their proprietary technology.

AT&T made the sources available pretty widely in academia, for use as
a teaching tool, and some of the universities involved seemed to play
pretty fast and loose with the NDA.  A lot of CS students I talked to
were under the impression that the UNIX sources were freely open and
hackable at their college.  Because of this I always wondered whether,
if push came to shove, AT&T would be able to legally enforce its trade
secret claims.  I don't think the issue was ever actually litigated.

-Paul W.


  parent reply	other threads:[~2017-03-16 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 19:33 Doug McIlroy
2017-03-16 20:05 ` Clem Cole
2017-03-16 21:28 ` Paul Winalski [this message]
2017-03-16 23:46   ` Wesley Parish
2017-03-17  1:04 ` Steve Johnson
2017-03-16 20:21 Noel Chiappa

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='CABH=_VTE0+Sc-_ez=iho6jBOW8Jhfot6xMkt2LLTNqyC9R2aKA@mail.gmail.com' \
    --to=paul.winalski@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).