The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] 2.10
Date: Thu, 20 Nov 2014 23:55:58 -0500 (EST)	[thread overview]
Message-ID: <alpine.GSO.2.03.1411202351250.646@gewt.net> (raw)
In-Reply-To: <CAC20D2OsAL=mduWBiorqDSbm6f=dHQwVqww9Kwgk7dXTPeLUeg@mail.gmail.com>

On Thu, 20 Nov 2014, Clem Cole wrote:

> I don't think the BSD networking code in 2.10 worked on systems with only
> 256K bytes of memory.  The kernel is too big even without networking and a
> lot of work was done to push things out of the kernel. [The 17th bit (split
> I/D) really only mattered for user space, the kernel mapped things around -
> but with only 18 bits of address map there is not much space]. Adding
> networking and in particular the space for the mbuf's becomes a real issue.
>

It's unsupported; see my email where I pasted the "HCL" from 2.10's 
GENERIC config.

>
> Here are some thoughts..
>
> 1.) Easiest/Cheapest solution might be to front end the system with an RPi,
> Intel Edison or the like and run the IP stack on it and then use one or
> more serial ports from the micro to 11.
>

Well, 2.10 has SLIP, but it'd certainly be easier to implement a simple 
userland tool to talk to a frontend!

> 2.) See if you can dig up an old copy of the 3 COM's first product - UNET -
> which was the original TCP/IP for V7.  It's old and not very sexy, but the
> kernel requirements are minimal and if all you want it telnet & FTP that
> will work.
>

That I am pretty sure I DO NOT have source for.

> 3.) If you have real hardware, see if you can find an old Able "Enable"
> board which will allow you to put 4Megs of memory in an 40 class processor
> (you get a cache plus a new memory MAP with 22 bits of address like the 45
> class processors).   I had 2.X working on that years ago (and wrote a
> USENIX paper on it).  The Enable board support was in the BSD 2*
> distributions (I put there) but I doubt its been tried in many years.
>

That sounds like a neat board.  Betting it's a bit hard to find, though. 
;)

> 4.) Ultrix-11 should boot on a 40 class system, but I do not remember if on
> the 18 bit machines you could configure networking.   Armando might
> remember if Fred ever made that work.  If any one could have or would have,
> it would have been Fred.  As I said, there just is not a lot of space and
> frankly there is not going to be a lot of space left for user programs.
>

I'd check but I'm pretty sure I don't have Ultrix-11 sources. :(

> Clem
>
> PS I remember running V6 on 11/34 with 48K bytes of memory for a few months
> as our memory for that system was back ordered.  It was slow, but it worked
> and we were happy.  It was our machine!!
>

What were you using for paging/swapping on that?

-- 
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects



  reply	other threads:[~2014-11-21  4:55 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
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 [this message]
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=alpine.GSO.2.03.1411202351250.646@gewt.net \
    --to=b4@gewt.net \
    /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).