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 14:52:33 -0500	[thread overview]
Message-ID: <CAEoi9W6jy129hkK1-1p+CUvwPQox+K_VsYea5gfnVdJCk+Uy2Q@mail.gmail.com> (raw)
In-Reply-To: <2BE827F7-5498-4D7A-90B9-1228BBBEB950@cs.uwlax.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

On Tue, Jan 6, 2015 at 2:38 PM, Milo Velimirović <milov at cs.uwlax.edu> wrote:

> On Jan 6, 2015, at 12:41 PM, random832 at fastmail.us wrote:
> > In the "distrib" directory there are four files exactly 1440 kb in size
> > - maybe someone could try loading those into a VM/Emulator?
>
> I had exactly that thought after I downloaded the tar ball this morning.
> Any suggestions for a VM config that would facilitate this would be
> welcome. Otherwise I’m going to stumble through virtual box and see what
> happens.
>

Those look an awful lot like the distribution disks for COHERENT 4.2.10.
There's a writeup of how to get that installed and running under qemu here:
http://thebeezspeaks.blogspot.in/2012/05/my-life-with-coherent-part-2.html

However, there have been some reports of stability issues with the emulated
disk under qemu; VirtualBox seems to be the most consistently reliable (and
fast!) alternative, but you have to run it under a 32-bit host OS.  I ended
up installing a 32-bit Linux under VMWare to run virtual box to run
COHERENT (yes, it's awful).  I haven't tried qemu lately to see if the
stability problems have been addressed, though.

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


  parent reply	other threads:[~2015-01-06 19:52 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
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 [this message]
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=CAEoi9W6jy129hkK1-1p+CUvwPQox+K_VsYea5gfnVdJCk+Uy2Q@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).