The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] BerkNet
Date: Wed, 26 Nov 2014 15:03:27 -0500	[thread overview]
Message-ID: <CAC20D2NWog=nAMVrcmyNS2qg+yx9B1oK2ikkgVf2xGYzVgtJ=g@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W6h6kY5+m72+pL9WJb3+z5N6x2EaD-+HcQiZ68Rk6gNpg@mail.gmail.com>

BBN did a second release that used the sockets.    At Stellar we used that
stack, not the UCB stack, since we were taking System V and adding BSD to
it.  Since the author of the BBN stack (Rob Gurwitz) was with us, it was
felt that the BBN stack was actually better in many ways.  In particular,
we had a parallel machine and it was felt that the BBN stack would be
easier/cleaner to multi-thread.

I can ask around, I lost track of the code base after Stellar.   tjt might
still know.

On Wed, Nov 26, 2014 at 1:35 PM, Dan Cross <crossd at gmail.com> wrote:

> On Wed, Nov 26, 2014 at 1:24 PM, Clem Cole <clemc at ccc.com> wrote:
>
>> [snip]  The MIT guys did ARP for ChaosNet which quickly migrated down the
>> street to BBN for the 4.1 IP stack.  Remember that BBN had the contract to
>> do IP for UNIX and that was the stack a number of us ran on our Vaxen for
>> long time [IIRC - Sam actually did the routed and rcp stuff which the BBN
>> stack, before Joy had rewritten it - created the sockets interface etc].
>>
>
> This brings up something I've been meaning to ask about for a while now.
> Whatever happened to the BBN stack after the BSD stack became dominant?  Is
> any of the code still available anywhere?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141126/b2561a33/attachment.html>


  reply	other threads:[~2014-11-26 20:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  1:32 [TUHS] 2.10 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
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 [this message]
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-26 18:49 [TUHS] BerkNet Noel Chiappa
2014-11-26 20:16 ` Clem Cole
2014-11-27 20:40   ` Dave Horsfall
2014-11-29 16:39     ` Clem Cole
2014-11-26 23:33 ` Jesus Cea
2014-11-27 14:38 Noel Chiappa
2014-11-29 16:34 ` Clem Cole

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='CAC20D2NWog=nAMVrcmyNS2qg+yx9B1oK2ikkgVf2xGYzVgtJ=g@mail.gmail.com' \
    --to=clemc@ccc.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).