The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem cole <clemc@ccc.com>
To: Jacob Ritorto <jacob.ritorto@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Mon, 10 Dec 2018 20:21:06 -0500	[thread overview]
Message-ID: <940B149F-923C-4D12-B5D7-698DEA2E4F1F@ccc.com> (raw)
In-Reply-To: <CAHYQbfBnUoX9Eefe6xO_taa8Lg=5x2=c+FRZakod1sY_cffQfg@mail.gmail.com>

It is going to be very difficult.  If this is real HW you might try practicing configuration using simh.     It will be faster and easy to play with until you have the config that meets your needs.         That said for telnet and ftp you are going to need tcp. 

Btw.  I might suggest setting up and Arduino, an RPi or the like and connect via serial ports to the 11.  That way you might not need networking.    

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

> On Dec 10, 2018, at 5:05 PM, Jacob Ritorto <jacob.ritorto@gmail.com> wrote:
> 
> Hi,
>   I have an 11/45 I'm hoping will be running soon.  
> 
> I'd like to run 2.9BSD on it because it's the most highly functional system I know of that has "official hopes" to fit on such a restrictive machine.
> 
>  I've heard that it's really unlikely / tough to get a kernel built that'll run tcp (I care mostly about ftp and telnet) on such a small-memory-footprint machine.  Is this true?  
> 
> Would anyone be willing to do a quick mentoring / working session with me to get me up to speed with the constraints I'm facing here and possibly give me a jump on making adjustments to build such a kernel if possible?
> 
> thx
> jake
> 
> P.S. There's kind of an implied challenge in the 2.11bsd setup docs, mentioning that "2.11BSD would probably only require a moderate amount of squeezing to fit on machines with less memory, but it would also be very unhappy about the prospect."  
> 
> I'm sure it's been attempted before, but would anyone be up to the challenge of trying to get that going with networking on an 18-bit-address-space pdp11?
> 

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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 22:05 Jacob Ritorto
2018-12-11  1:21 ` Clem cole [this message]
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
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-11  4:42 Noel Chiappa
2018-12-11 16:16 Noel Chiappa
2018-12-11 16:26 ` Clem Cole
2018-12-11 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole
2018-12-11 18:43 Noel Chiappa
2018-12-11 18:51 ` Clem Cole
2018-12-12  1:20   ` Jacob Ritorto
2018-12-12 10:29 Paul Ruizendaal
2018-12-12 14:14 Noel Chiappa
2018-12-12 14:38 Noel Chiappa
2018-12-12 17:55 Paul Ruizendaal
2018-12-15  1:54 Paul Ruizendaal

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=940B149F-923C-4D12-B5D7-698DEA2E4F1F@ccc.com \
    --to=clemc@ccc.com \
    --cc=jacob.ritorto@gmail.com \
    --cc=tuhs@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).