From: milov@uwlax.edu (Milo Velimirovic)
Subject: [TUHS] MIT Releases the Source of MULTICS, Father of UNIX
Date: Wed, 14 Nov 2007 11:36:49 -0600 [thread overview]
Message-ID: <EBCCE98F-B8F4-4190-BA81-490A4F5BC3D5@uwlax.edu> (raw)
In-Reply-To: <473B31EA.8070302@fairhaven.za.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Time for someone to step up to the task for writing a GE635 645 module
for simh?
I know I'm not up to it. :(
- Milo
On Nov 14, 2007, at 11:35 AM, Angus Robinson wrote:
> Not to sure if anybody on the list has seen this ? Or if anybody has
> the
> hardware to run it.
>
> http://web.mit.edu/multics-history/source/Multics_Internet_Server/Multics_sources.html
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
--
Milo Velimirović, Unix Computer Network Administrator
608.785.6618 Office - 608.386.2817 Cell
University of Wisconsin - La Crosse
La Crosse, Wisconsin 54601 USA 43 48 48 N 91 13 53 W
next prev parent reply other threads:[~2007-11-14 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 17:35 Angus Robinson
2007-11-14 17:36 ` Milo Velimirovic [this message]
2007-11-14 17:55 ` Al Kossow
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=EBCCE98F-B8F4-4190-BA81-490A4F5BC3D5@uwlax.edu \
--to=milov@uwlax.edu \
/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).