From: henry.r.bent@gmail.com (Henry Bent)
Subject: [TUHS] 8th Edition Research Unix on SIMH
Date: Tue, 28 Mar 2017 21:35:44 -0400 [thread overview]
Message-ID: <CAEdTPBc78fU=KTnLAZVMkm-AJ9n-wVG1rqepJWBc=0ugO4Q_nA@mail.gmail.com> (raw)
In-Reply-To: <31189C6E-570A-4954-BD4F-B4BE214A52C7@gewt.net>
After looking at some open SIMH bugs, doing "set noasync" seems to fix the
problem.
-Henry
On 28 March 2017 at 21:19, Cory Smelosky <b4 at gewt.net> wrote:
> Yes - there is a SIMH bug
>
> One I think I reported, actually maybe...
>
> Use SIMH 3.8-1
>
> Sent from my iPhone
>
> On Mar 28, 2017, at 18:06, Henry Bent via TUHS <tuhs at minnie.tuhs.org>
> wrote:
>
> I can install 4.1BSD just fine, but I seem to be having trouble writing
> anything to a second RP06:
>
> # mkfs /dev/hp1a 7942
> isize = 5072
> m/n = 3 500
> # mkfs /dev/hp1g 145673
> isize = 65488
> m/n = 3 500
> # mount /dev/hp1a /v8
> # mkdir /v8/usr
> # mount /dev/hp1g /v8/usr
> # cd /v8
> # mt rew
> # mt fsf 2
> # tar xvpb 20
> hp0a: hard error sn10 mbsr=82000<PGE,DTCMP> er1=0 er2=0
> hp1a: hard error sn16 er1=5<RMR,ILF> er2=0
> mkdir: cannot make directory adm
> ...
>
> Am I missing something, or did I run into a SIMH bug? My /dev entries all
> look fine.
>
> -Henry
>
> On 28 March 2017 at 14:58, 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170328/d0e4df8a/attachment.html>
next prev parent reply other threads:[~2017-03-29 1:35 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
2017-03-29 1:06 ` Henry Bent
2017-03-29 1:19 ` Cory Smelosky
2017-03-29 1:35 ` Henry Bent [this message]
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='CAEdTPBc78fU=KTnLAZVMkm-AJ9n-wVG1rqepJWBc=0ugO4Q_nA@mail.gmail.com' \
--to=henry.r.bent@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).