The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] System Economics
Date: Thu, 16 Mar 2017 18:04:45 -0700	[thread overview]
Message-ID: <2f004b6cd59d100c4853aa1c15c06cf0c0db93ec@webmail.yaccman.com> (raw)
In-Reply-To: <201703161933.v2GJXAdo144602@tahoe.cs.Dartmouth.EDU>

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

Yes, Doug is spot on.  Being told by the govt. that we had to patent
everything we could and license it fairly got rather strange when
software was involved -- there was a lot of question whether software
could be patented at all, and the Labs had to patent software if it
could be patented (e.g., the setuid bit).

The biggest issue, which still hasn't gone away, is that software
moves so much faster than the law.  The lawyers seemed to take the
standpoint that if something was questionable, just wait for five
years until there are better legal precedents. 

At one point I made a major push to get the PCC grammar for C released
in the public domain.  I still think this would have brought
standardization about much sooner, and my managers were in favor of
it.  But the lawyers delayed and delayed.  The next thing you know,
we had "far pointers" and all sorts of other gook in the language that
took the standards committee additional years to wring out.  Sigh...

Steve

----- Original Message -----
From: "Doug McIlroy" <doug@cs.dartmouth.edu>
To:<tuhs at tuhs.org>
Cc:
Sent:Thu, 16 Mar 2017 15:33:10 -0400
Subject:Re: [TUHS] System Economics

 "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.

 Out in the field, the trade secret was treated in many
 different ways. Perhaps the most extreme was MIT, whose
 lawyers believed it could not be adequately protected in
 academia and forbade its use there. I don't know what eventually
broke the logjam.

 Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170316/e174f549/attachment-0001.html>


  parent reply	other threads:[~2017-03-17  1:04 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
2017-03-16 23:46   ` Wesley Parish
2017-03-17  1:04 ` Steve Johnson [this message]
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=2f004b6cd59d100c4853aa1c15c06cf0c0db93ec@webmail.yaccman.com \
    --to=scj@yaccman.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).