The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 17:11:54 -0500	[thread overview]
Message-ID: <CAC20D2Ok_WyZV2K1gL9vaqOG7ndhtOJn2X-wNiyBv=BDsc1RAw@mail.gmail.com> (raw)
In-Reply-To: <201702222018.v1MKIUKO030787@freefriends.org>

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

On Wed, Feb 22, 2017 at 3:18 PM, <arnold at skeeve.com> wrote:

> I mostly watched the whole AT&T/BSD lawsuit stuff from the side. At
> one USENIX I remember talking to Keith Bostic about it, and understanding
> that it was trade secret, but I asked him "Given the book by Maurice
> Bach on how UNIX works, how can they still think it's trade secret?"
> He just sorta nodded and said "yep" or something equivalent.
>

​Not a  lawyer... but for patents, I am under the impression that the date
is defined as "first public discloser."  So I think the official date would
be the UNIX talk given in *"paper presented at the Fourth ACM Symposium on
Operating Systems Principles, IBM Thomas J. Watson Research Center,
Yorktown Heights, New York, October 15-17, 1973."   [*
https://www.bell-labs.com/usr/dmr/www/cacm.html]

I believe that said paper predates all of the books.   Fact is before Bach,
UNIX shows up in a number of OS texts, so the point is that the IP is being
taught by Universities and studies by students.   Which is of course what
the judge points out when the case was decided.

And clearly, the legal battle was stupid.  But pride is an amazing thing
and corporate pride seems the worst in my experience.

all quite sad.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170222/fdb46268/attachment.html>


  reply	other threads:[~2017-02-22 22:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  3:38 Clem Cole
2017-02-22  4:28 ` Dan Cross
2017-02-22 15:36   ` Clem Cole
2017-02-22 16:11     ` Larry McVoy
2017-02-22 17:00       ` Clem Cole
2017-02-22 17:06         ` Chet Ramey
2017-02-22 18:24         ` Larry McVoy
2017-02-22 19:35           ` Clem Cole
2017-02-22 20:18             ` arnold
2017-02-22 22:11               ` Clem Cole [this message]
2017-02-22 21:34             ` Larry McVoy
2017-02-22 22:56               ` Clem Cole
2017-02-22 23:13                 ` Larry McVoy
2017-02-22 23:51                   ` Clem Cole
2017-02-22 23:51           ` Paul Ruizendaal
2017-02-23 19:15             ` Clem Cole
2017-02-23 20:31               ` Random832
2017-02-23 22:48                 ` Joerg Schilling
2017-02-24  2:07                   ` Jason Stevens
2017-02-23 23:06                 ` Wesley Parish
2017-02-22 17:41       ` Arthur Krewat
2017-02-22 21:00     ` Michael Kerpan
2017-02-22 22:03       ` Arno Griffioen
2017-02-22 22:51         ` Larry McVoy
2017-02-22 23:29         ` Clem Cole
2017-02-23  4:53           ` Gregg Levine
2017-02-22 22:18       ` Clem Cole
2017-02-24  3:53     ` Dan Cross
2017-02-22  5:56 ` Steve Nickolas
2017-02-24  5:31   ` John Labovitz

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='CAC20D2Ok_WyZV2K1gL9vaqOG7ndhtOJn2X-wNiyBv=BDsc1RAw@mail.gmail.com' \
    --to=clemc@ccc.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).