From: Marc Rochkind <mrochkind@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: The Mark Williams Company and Coherent
Date: Fri, 15 Mar 2024 08:10:31 -0600 [thread overview]
Message-ID: <CAOkr1zVjv2qfRkAjz7c_A6a-2rB=mDgMQU_xuNxNvnQG+V4PvA@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W732FGzUObLfP7_-1pPvaqoeMhUxgUsytEssA+Knq1LRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
I have already posted this in another thread (on non-BTL C compilers), but
it's more relevant here. My 1985 review of Coherent for BYTE Magazine:
https://www.mrochkind.com/mrochkind/docs/Byte-Pick-Coherent-Theos.pdf
I see that I went into some detail. For example:
"Of the 77 requests in the Version 7 nroff. only 31 are present in Coherent
(the most useful 31. however)."
And this, although I'm sure there were incompatibilities I didn't uncover:
"Coherent has all the Version 7 system calls except nice (which sets a
process's priority). and they seem to be used in the same way. It should be
easy to port C programs between Coherent and UNIX Version 7."
On the whole my review was very positive.
Marc
On Fri, Mar 15, 2024 at 7:43 AM Dan Cross <crossd@gmail.com> wrote:
> On Fri, Mar 15, 2024 at 9:03 AM Dan Cross <crossd@gmail.com> wrote:
> >
> > On Fri, Mar 15, 2024 at 3:00 AM Rob Pike <robpike@gmail.com> wrote:
> > > 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'.
> >
> > Along those lines, Dennis Ritchie wrote up a summary of the event on
> > USENET; apparently in 1998 (I had no idea it was this late):
> >
> https://groups.google.com/g/alt.folklore.computers/c/_ZaYeY46eb4/m/5B41Uym6d4QJ
>
> Sorry, just to clarify: I meant I had no idea Dennis's posting about
> the event happened so late; by 1998 USENET was basically overrun by
> spam. Obviously, the inspection trip had happened much earlier.
>
> - Dan C.
>
--
*My new email address is mrochkind@gmail.com <mrochkind@gmail.com>*
[-- Attachment #2: Type: text/html, Size: 3154 bytes --]
next prev parent reply other threads:[~2024-03-15 14:10 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
2024-03-15 13:03 ` Dan Cross
2024-03-15 13:43 ` Dan Cross
2024-03-15 14:10 ` Marc Rochkind [this message]
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='CAOkr1zVjv2qfRkAjz7c_A6a-2rB=mDgMQU_xuNxNvnQG+V4PvA@mail.gmail.com' \
--to=mrochkind@gmail.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).