The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jacob Ritorto <jacob.ritorto@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs@minnie.tuhs.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Tue, 11 Dec 2018 20:20:51 -0500	[thread overview]
Message-ID: <CAHYQbfAcYJDiMPxQ5xn7enk8jEPzcpspoiBp9BMwEb9zCEV-zA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2N8MMzMR+tBfu4MMh+wPY4CMbqG4NEys6xdvnxPEzC=Tg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

Man, this thread is really going!  Excellent to see; thank you, all!

I'm going to of course begin with what Clem and others suggested and do it
on a simh 11/45 initially to try to get the needed tcp stuff compiled in.
In looking at
https://minnie.tuhs.org//cgi-bin/utree.pl?file=2.9BSD/usr/net/sys/net/NOTES
, it's mentioned that

>>> The 4K bytes of in address malloc space for dynamic structures is ok
for an
>>> I/D machine, but may be tight on a /34 or /23.  Not sure yet whether
this
>>> will squeeze in.

, so it feels like there's hope that it can be done.  Lots of rereading and
research for me to get to the point of completely understanding that NOTES
file.

Anyway, I'm going to try and get a simh instance up somewhere publicly
accessible (will provide creds to those curious / interested) and see where
I get stuck.  Will be back with more questions!  Thanks again for the
initial engagement on this!


jake


P.S.  I do have a Xylogics Annex "terminal server" that'd be a great front
end to the real 11/45's serial lines as Clem suggested, but for me, the
romance of having the machine truly speaking tcp as intended is one of the
goals.  I'll keep the Annex handy for when it's running SysV and other
things that definitively can't speak tcp.

[-- Attachment #2: Type: text/html, Size: 1737 bytes --]

  reply	other threads:[~2018-12-12  1:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 18:43 Noel Chiappa
2018-12-11 18:51 ` Clem Cole
2018-12-12  1:20   ` Jacob Ritorto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-15  1:54 Paul Ruizendaal
2018-12-12 17:55 Paul Ruizendaal
2018-12-12 14:38 Noel Chiappa
2018-12-12 14:14 Noel Chiappa
2018-12-12 10:29 Paul Ruizendaal
2018-12-11 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole
2018-12-11 16:16 Noel Chiappa
2018-12-11 16:26 ` Clem Cole
2018-12-11  4:42 Noel Chiappa
2018-12-11  2:11 Noel Chiappa
2018-12-11  2:36 ` Grant Taylor via TUHS
2018-12-11  3:28   ` Warner Losh
2018-12-10 22:05 Jacob Ritorto
2018-12-11  1:21 ` Clem cole
2018-12-11  1:55   ` Grant Taylor via TUHS
2018-12-11  7:22     ` Lars Brinkhoff
2018-12-11 15:28       ` Clem Cole
2018-12-11 17:21         ` Lars Brinkhoff

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=CAHYQbfAcYJDiMPxQ5xn7enk8jEPzcpspoiBp9BMwEb9zCEV-zA@mail.gmail.com \
    --to=jacob.ritorto@gmail.com \
    --cc=clemc@ccc.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@minnie.tuhs.org \
    /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).