The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] 8th Edition Research Unix on SIMH
Date: Tue, 25 Apr 2017 20:50:11 -0700	[thread overview]
Message-ID: <1493178611.2693377.956432024.3DC45D21@webmail.messagingengine.com> (raw)
In-Reply-To: <CAGSRWbj9BHLg6ou8czcYRfuDQtPLJaUHmcwA_0k9C74EmSw5Kg@mail.gmail.com>

I've invited you to the TUHS github group so you can toss it there, too.

On Mon, Apr 24, 2017, at 20:16, Tim Newsham wrote:
> I put together some scripts to install V8 from tape:
> https://github.com/timnewsham/myv8
> 
> My goals are (roughly in order):
>   - easy to use
>   - documentary
>   - reproducible
> 
> I also moved my earlier v6 installer to github for convenience:
> https://github.com/timnewsham/myv6
> 
> 
> On Tue, Mar 28, 2017 at 1:50 PM, Tim Newsham
> <tim.newsham at gmail.com> wrote:>> Would be great if someone scripted it up to make it dog-simple.
>> Here's how I did it for v6:
>> http://www.thenewsh.com/~newsham/myv6/README>> (I should do this, but I'm not sure I'll have time in the near
>> future).>> 
>> On Tue, Mar 28, 2017 at 8:58 AM, David du Colombier
>> <0intro at gmail.com> wrote:>>> Here are my notes to run 8th Edition Research Unix on SIMH.
>>> 
>>> http://9legacy.org/9legacy/doc/simh/v8
>>> 
>>>  These notes are quite raw and unpolished, but should be
>>>  sufficient to get Unix running on SIMH.
>>> 
>>>  Fell free to use, improve and share.
>>> 
>>>  --
>>>  David du Colombier
>> 
>> 
>> 
>> -- 
>> Tim Newsham | www.thenewsh.com/~newsham | @newshtwit |
>> thenewsh.blogspot.com>> 
> 
> 
> 
> -- 
> Tim Newsham | www.thenewsh.com/~newsham | @newshtwit |
> thenewsh.blogspot.com
--
  Cory Smelosky
  b4 at gewt.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170425/1aef9acf/attachment.html>


  parent reply	other threads:[~2017-04-26  3:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 18:58 David du Colombier
2017-03-28 19:32 ` Cory Smelosky
2017-03-28 23:50 ` Tim Newsham
2017-04-25  3:16   ` Tim Newsham
2017-04-25 20:34     ` David du Colombier
2017-04-26  3:50     ` Cory Smelosky [this message]
2017-03-29  1:06 ` Henry Bent
2017-03-29  1:19   ` Cory Smelosky
2017-03-29  1:35     ` Henry Bent
2017-03-30 14:16 ` David du Colombier
2017-03-30 18:30   ` David du Colombier
2017-03-31  5:05     ` Michael Kerpan
2017-03-31  5:36       ` Kurt H Maier
2017-03-31 14:41         ` Michael Kerpan
2017-03-31 16:34           ` [TUHS] 8th Edition Research Unix on SIMHtuhs Cory Smelosky
2017-04-26  3:05       ` [TUHS] 8th Edition Research Unix on SIMH Tim Newsham
2017-04-26  5:53         ` Noel Hunt
2017-04-26  6:10           ` Tim Newsham
2017-04-26 23:49         ` Tim Newsham
2017-04-26 22:45     ` Tim Newsham
2017-04-26 23:02       ` Arthur Krewat
2017-04-26 23:21         ` Dave Horsfall
2017-04-26 23:07       ` Kurt H Maier
2017-03-29  0:49 Noel Chiappa
2017-03-29  1:02 ` Grant Taylor
2017-03-29 10:41   ` Steffen Nurpmeso
2017-03-29  2:44 ` Tim Newsham
2017-03-29  1:45 Noel Chiappa
2017-03-29  1:57 ` Steve Nickolas
2017-03-29  4:11 ` Grant Taylor
2017-03-30 11:47 Jason Stevens
2017-03-31 22:31 Nelson H. F. Beebe
2017-04-27  1:04 Norman Wilson
2017-04-27  1:26 ` Kurt H Maier

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=1493178611.2693377.956432024.3DC45D21@webmail.messagingengine.com \
    --to=b4@gewt.net \
    /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).