The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: heinz@osta.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: The Mark Williams Company and Coherent
Date: Fri, 15 Mar 2024 18:00:12 +1100	[thread overview]
Message-ID: <CAKzdPgz4iq1UYT+x=wNqDBBo1i3Nezm8Wv+YZhLN2SY4Mi4CSA@mail.gmail.com> (raw)
In-Reply-To: <4999eb0b-e0e5-4a79-b14f-77d17995f454@osta.com>

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

Another detail. There was lawyerly concern about the code being stolen, and
we (127) were asked to find ways to test, absent their source, whether they
had just stolen our source and built the binaries. It was soon concluded
that there were enough details different to definitively say that at least
most of the work was done in a clean room, as advertised, but the piece I
liked best is that their PPT(1) program (ASCII art showing a paper tape
rendering the argument text) did not include the original, and just
discovered, bug that mispunched, if I remember right, the letter 'R'.

-rob


On Fri, Mar 15, 2024 at 4:16 PM Heinz Lycklama <heinz@osta.com> wrote:

> Interesting little history about Coherent. They were
> one of a few companies building UNIX-like systems
> from scratch without using UNIX source code in the
> early 1980's. Robert Schwartz represented the Mark
> Williams Company on the /usr/group standards
> effort resulting in the /usr/group Standard in 1984.
> Robert was very insistent that members of the
> /usr/group standards group did not have to be
> UNIX source licensees.
>
> Heinz
>
> On 3/14/2024 8:45 PM, Marc Rochkind wrote:
> > In another thread there's been some discussion of Coherent. I just
> > came across this very detailed history, just posted last month.
> > There's much more to it than I knew.
> >
> > https://www.abortretry.fail/p/the-mark-williams-company
> >
> > Marc
> >
>
>

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

  reply	other threads:[~2024-03-15  7:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  3:45 [TUHS] " Marc Rochkind
2024-03-15  5:16 ` [TUHS] " Heinz Lycklama
2024-03-15  7:00   ` Rob Pike [this message]
2024-03-15 13:03     ` Dan Cross
2024-03-15 13:43       ` Dan Cross
2024-03-15 14:10         ` Marc Rochkind
2024-03-15 15:42           ` Theodore Ts'o
2024-03-15 14:40     ` Paul Winalski
2024-03-15 21:23 [TUHS] " Douglas McIlroy
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

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='CAKzdPgz4iq1UYT+x=wNqDBBo1i3Nezm8Wv+YZhLN2SY4Mi4CSA@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=heinz@osta.com \
    --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).