The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] The Mark Williams Company and Coherent
Date: Fri, 15 Mar 2024 17:23:44 -0400	[thread overview]
Message-ID: <CAKH6PiWN+CNEBmU+f2BbPWWUyd3j0bDq2otJPJbDda-4iRSbBg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

> There was lawyerly concern about the code being stolen.

Not always misplaced. There was a guy in Boston who sold Unix look-alike
programs. A quick look at the binary revealed perfect correlation with our
C source. Coincidentally, DEC had hired this person as a consultant in
connection with cross-licensing negotiations with AT&T. Socializing at
the end of a day's negotiations,  our lawyer somehow managed to turn the
conversation to software piracy. He discussed  a case he was working on,
and happened to have some documents about it in his briefcase. He pulled
out a page disassembled binary and a page of source code and showed them to
the consultant.

After a little study, the consultant confidently opined that the binary was
obviously compiled from that source. "Would it surprise you," the lawyer
asked, "if I told you that this is yours and that is ours?" The consultant
did not attend the following day's meeting.

Doug

[-- Attachment #2: Type: text/html, Size: 1767 bytes --]

             reply	other threads:[~2024-03-15 21:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 21:23 Douglas McIlroy [this message]
2024-03-15 22:27 ` [TUHS] " Larry McVoy
2024-03-15 22:28 ` Dave Horsfall
2024-03-15 23:00   ` Marc Rochkind
2024-03-15 23:16     ` Rich Salz
2024-03-16  5:24       ` Dave Horsfall
2024-03-18 12:27 ` Dan Cross
2024-03-18 14:12   ` Douglas McIlroy
  -- strict thread matches above, loose matches on Subject: below --
2024-03-15  3:45 [TUHS] " Marc Rochkind

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=CAKH6PiWN+CNEBmU+f2BbPWWUyd3j0bDq2otJPJbDda-4iRSbBg@mail.gmail.com \
    --to=douglas.mcilroy@dartmouth.edu \
    --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).