The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jacob.ritorto@gmail.com (Jacob Ritorto)
Subject: [TUHS] 2.10
Date: Thu, 20 Nov 2014 22:25:43 -0500	[thread overview]
Message-ID: <CAHYQbfDGnf1tfSpZJx1K80x4MRfPH4_aHs8fq=vxkekeTc8Hqg@mail.gmail.com> (raw)
In-Reply-To: <CA+oaVqwGKiOPKm8Bz62Z0s9dEYiAbTXR9=WrQyjqGFX-uaYmjQ@mail.gmail.com>

Jim / Nick,  That's kinda my problem: can't find enough documentation on
2.10 to ascertain if I can / should run it. I know 2.9 is OK for the 11/34,
but 2.9 doesn't have telnet or ftp and I want this machine to be easily
reachable on the net.

  From what I've read, 2.11 is right out except for the little glimmer of
hope in the docs that it "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," which I think roughly translates to, "don't
try it on a puny thing like an 11/34."

  I wonder if porting telnet and ftp to 2.9 on the 11/34 would be my best
hope?  But with a much more antique tcp stack, it sounds daunting.


On Thu, Nov 20, 2014 at 9:05 PM, Jim Carpenter <jim at deitygraveyard.com>
wrote:
>
>
> 2.10 and 2.11 require split I/D, right? I'm positive 2.9 was the
> latest I could run on my 11/34.
>
> Jim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141120/7e451367/attachment.html>


  parent reply	other threads:[~2014-11-21  3:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  1:32 Jacob Ritorto
2014-11-21  1:56 ` Nick Downing
     [not found] ` <CA+oaVqwGKiOPKm8Bz62Z0s9dEYiAbTXR9=WrQyjqGFX-uaYmjQ@mail.gmail.com>
2014-11-21  3:25   ` Jacob Ritorto [this message]
2014-11-21  3:36     ` Cory Smelosky
2014-11-21  4:02       ` Cory Smelosky
2014-11-21  4:43 ` Clem Cole
2014-11-21  4:55   ` Cory Smelosky
2014-11-21  5:46     ` Clem Cole
2014-11-21  6:07       ` Cory Smelosky
2014-11-26  6:28         ` [TUHS] BerkNet Erik E. Fair
2014-11-26  6:48           ` Cory Smelosky
2014-11-27 16:42             ` Mary Ann Horton
2014-11-29 16:38               ` Clem Cole
2014-11-26 18:24           ` Clem Cole
2014-11-26 18:35             ` Dan Cross
2014-11-26 20:03               ` Clem Cole
2014-11-26 18:26           ` Dave Horsfall
2014-11-21  6:13       ` [TUHS] 2.10 Jacob Ritorto
2014-11-21 13:06         ` Clem Cole
2014-11-21 15:37 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='CAHYQbfDGnf1tfSpZJx1K80x4MRfPH4_aHs8fq=vxkekeTc8Hqg@mail.gmail.com' \
    --to=jacob.ritorto@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).