The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Unix V8 Chaosnet, any takers?
Date: Thu, 14 Jul 2022 21:50:53 +0000	[thread overview]
Message-ID: <VtxDj_Co-tRgUGmB9ntbtLTSy6wn4zO0gHTjaXmmXNdVsubFsMbMCMjBGGzAEbS7x2hX9l88Wy-vi4aeu_PJX7BZyYtcy43M3bt6TAyCc5E=@protonmail.com> (raw)
In-Reply-To: <7w1qunxz8p.fsf@junk.nocrew.org>

This looks like it might be exactly what you're looking for:

http://9legacy.org/9legacy/doc/simh/v8

Steps to start with a 4.1BSD base in simh and use that to ultimately produce a V8 system. I haven't audited these instructions myself, so YMMV, but I suspect someone wouldn't go through the hard work if this didn't do anything.

That said, your original posting mentions the PDP-11, but also "Berkeley Unix Nodes". For the latter, do you mean VAX? These instructions are for VAX too, I don't know whether V8 ran on PDP-11 or not, but if that's your intent, you may want to start with a 2.xBSD or V7 as a base instead.

- Matt G.

------- Original Message -------
On Thursday, July 14th, 2022 at 12:36 PM, Lars Brinkhoff <lars@nocrew.org> wrote:


> segaloco wrote:
>
> > What sort of help are you looking for? I've got idle fingers in the
> > evenings lately, if you just need some code junkies to work on things
> > I'm happy to throw my hat in the ring.
>
>
> I'm mainly curious if the V8 code works. I haven't examined it at all,
> so I have no idea.
>
> For reference, I have a disk image with 4.1BSD patched and ready to
> run with SIMH here:
> http://lars.nocrew.org/tmp/Chaotic-4.1BSD.tar.bz2
>
> I collected all the bits and pieces here and intended to make
> an expect script to install, patch, and build everything. I didn't
> the script but all the stuff should be here:
> https://github.com/Chaosnet/Chaosnet-for-4.1BSD

  reply	other threads:[~2022-07-14 21:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 11:08 [TUHS] " Lars Brinkhoff
2022-07-14 16:37 ` [TUHS] " John Floren
2022-07-14 17:00   ` Lars Brinkhoff
2022-07-14 17:51     ` segaloco via TUHS
2022-07-14 18:19       ` Ron Natalie
2022-07-14 20:32         ` Tom Teixeira
2022-07-14 20:39           ` Ron Natalie
2022-07-15  0:33             ` Grant Taylor via TUHS
2022-07-15  4:29               ` Erik E. Fair
2022-07-14 19:36       ` Lars Brinkhoff
2022-07-14 21:50         ` segaloco via TUHS [this message]
2022-07-16  6:38           ` Lars Brinkhoff
2022-07-16 14:05             ` Warner Losh
2022-07-15  8:51 Paul Ruizendaal via TUHS
2022-07-15 10:25 Noel Chiappa
2022-07-15 11:53 ` Theodore Ts'o
2022-07-16  6:59 ` Lars Brinkhoff
2022-07-16 15:51 Noel Chiappa
2022-07-16 17:02 ` Warner Losh
2022-07-16 20:02 Paul Ruizendaal
2022-07-17 23:39 Noel Chiappa
2022-07-18  1:01 ` Ron Natalie
2022-07-18 17:07 Noel Chiappa

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='VtxDj_Co-tRgUGmB9ntbtLTSy6wn4zO0gHTjaXmmXNdVsubFsMbMCMjBGGzAEbS7x2hX9l88Wy-vi4aeu_PJX7BZyYtcy43M3bt6TAyCc5E=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=lars@nocrew.org \
    --cc=segaloco@protonmail.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).