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: Tue, 6 Jan 2015 12:04:52 -0500	[thread overview]
Message-ID: <CAEoi9W4DxADcQst87WOEVecY-V+GGievnL7Vp-Jbf1GFJoz4kA@mail.gmail.com> (raw)
In-Reply-To: <CACwAiQkePc2ueFNMMMj=gxxRd7uk-MmYg9VKxE18Xc0RLPZhLA@mail.gmail.com>

On Tue, Jan 6, 2015 at 11:48 AM, Rico Pajarola <rp at servium.ch> wrote:

> adding the list back
>
> On Tue, Jan 6, 2015 at 10:42 AM, Michael Kerpan <mjkerpan at kerpan.com>
> wrote:
>
>> This is a cool development. Does this code build into a working version
>> of Coherent or is this mainly useful to study? Either way, it should be
>> interesting to look at the code for a clone specifically aimed at low-end
>> hardware.
>>
> Unknown (to me, anyway).  Steve said he had intended to organize and
catalog the code at some point, but that he hasn't gotten around to it (and
not to hold one's breath).  I gathered that the tar ball he provided is a
snapshot of (a subset of?) the MWC development disks at the time he was
asked to create the archive.  To that end, I suspect that if one were
sufficiently motivated one *could* use it to build a distribution of
COHERENT, but I suspect you'd have to know quite a bit about their internal
development practices and release processes to do so successfully;
knowledge that may very well have been lost over time.  Perhaps some
motivated person will be able to reverse engineer it, though I suspect it's
more useful as a case study than as working code.

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150106/a70691a5/attachment.html>


  reply	other threads:[~2015-01-06 17:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2015-01-06  2:23 Dan Cross
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

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=CAEoi9W4DxADcQst87WOEVecY-V+GGievnL7Vp-Jbf1GFJoz4kA@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).