On Wed, Jan 7, 2015 at 2:40 PM, Andrzej Popielewicz <andrzejpopielewicz@gmail.com> wrote:
> > > On Tue, Jan 6, 2015 at 10:42 AM, Michael Kerpan <mjkerpan@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.
>
> Hi Dan,
> What to You mean by building distribution. The archive contains original distribution
> of Coherent 4.2.10. Or You mean one could build quite new distribution ?
> I mean, which would work on modern hardware ?
To a first order approximation, I meant regenerating the installation media from source.
You would certainly know more than I would about it; if you say it can be done, I believe you. :-) I don't know how to go about it, though (I assume it involves typing more than one command, but I could well be wrong).
- Dan C.