The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] COHERENT sources released under 3-clause BSD license.
Date: Mon, 5 Jan 2015 21:23:58 -0500	[thread overview]
Message-ID: <CAEoi9W7c+-4kJcwatWi75gjLVK_yaccBMdNZCukz_uie9mMO+w@mail.gmail.com> (raw)

Bob Swartz, founder of Mark Williams Co, has allowed the sources for
COHERENT to be published under a three-clause BSD license.  Steve Ness is
hosting them.  They are available here:

    http://nesssoftware.com/home/mwc/source.php

For reference, for folks who don't know what COHERENT is, it started as a
clone of 7th Edition, but grew more modern features over time.  Dennis
Ritchie's recollections of his interaction with it:
https://groups.google.com/forum/#!msg/alt.folklore.computers/_ZaYeY46eb4/5B41Uym6d4QJ

And of course the requisite Wikipedia link:
http://en.wikipedia.org/wiki/Coherent_(operating_system)

        - Dan C.

PS: I hold a soft spot for COHERENT in my heart.  I became interested in
Unix in high school, but this was before Linux was really a thing and
access to other systems was still hard to come by.  I spotted an ad for
COHERENT in the back of one of the PC-oriented publications at the time,
"Computer Shopper" or some such, and realized that it was *almost* within
my reach financially and that I could install it on the computer I already
owned.  Over the next month or so, I scraped up enough money to buy a copy,
did so, and put it on my PC.  It was quirky compared to actual Unix
distributions, but it was enough to give one a flavor for things.  The
manual, in particular, did not follow the traditional Unix format, but
rather was an alphabetical "lexicon" of commands, system calls and
functions and was (I've always thought) particularly well done.  Links to
the COHERENT lexicon and various other documents:
http://www.nesssoftware.com/home/mwc/.

I graduated onto other systems rather quickly, but COHERENT served as my
introduction to Unix and Unix-like systems.

PPS: Bob Swartz is the father of the late Aaron Swartz.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150105/883d3003/attachment.html>


             reply	other threads:[~2015-01-06  2:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  2:23 Dan Cross [this message]
2015-01-06  2:40 ` Larry McVoy
2015-01-06  2:49   ` Larry McVoy
2015-01-06  3:01     ` Warner Losh
2015-01-06  8:07 ` Warren Toomey
2015-01-06 18:02   ` Warner Losh
2015-01-06 13:41 Doug McIlroy
2015-01-06 14:25 ` Rico Pajarola
     [not found]   ` <CAHfSdrUT3VWQnezocJmM02v3-Syx4N7i+8mjwbggYW4ejwvc7A@mail.gmail.com>
2015-01-06 16:48     ` Rico Pajarola
2015-01-06 17:04       ` Dan Cross
2015-01-06 18:09         ` Warner Losh
2015-01-07 19:47           ` Andrzej Popielewicz
2015-01-07 19:02             ` Michael Kerpan
2015-01-07 21:19               ` Warner Losh
2015-01-07 19:40         ` Andrzej Popielewicz
2015-01-08  3:22           ` Dan Cross
2015-01-06 18:41       ` random832
2015-01-06 19:38         ` Milo Velimirović
2015-01-06 19:50           ` Jacob Goense
2015-01-07 20:17             ` Andrzej Popielewicz
2015-01-07 22:19               ` Jacob Goense
2015-01-09  9:50               ` Jose R. Valverde
2015-01-06 19:52           ` Dan Cross
2015-01-07 19:36       ` Andrzej Popielewicz
2015-01-07 20:03       ` Andrzej Popielewicz

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=CAEoi9W7c+-4kJcwatWi75gjLVK_yaccBMdNZCukz_uie9mMO+w@mail.gmail.com \
    --to=crossd@gmail.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).