The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] looking for 4.1a BSD full kernel source
Date: Thu, 1 Dec 2016 11:40:37 +0100	[thread overview]
Message-ID: <38CA85C9-C005-49C5-8BD5-3FC65FC170BF@planet.nl> (raw)
In-Reply-To: <0f3795f4-fb98-3370-510c-347a272dddae@aueb.gr>

Hi Diomidis,

Thanks for that link. This is exactly what I'm trying to ascertain, and I'm finding conflicting evidence.
- The socket API was in a state of flux between October '81 and March '82 (when 4.1a was supposedly cut). By March '82 it was mostly there, but not until later in the year did it fully stabilize.
- The BBN stack did not use the sockets API as late as January '82
- What I currently fathom from the SCCS files is that the socket API implementation was hard coded to use the nascent Berkeley stack.
- But the BBN code was likely in the 4.x BSD source tree, outside of SCCS (Berkeley started out with the BBN code, but it morphed quite quickly and drastically)
- In 1985 the BBN code finally enters SCCS (marked 'deprecated'); this code was integrated with the sockets API, and much developed from its 1982 form

Either the below link is correct (and I think I may have contributed to its view in a private mail to Kirk), or there were two different distributions (4.1a BSD with Berkeley network code and 4BSD with BBN network code). The two may have merged into one in peoples' memories: 35 years is a long time. Finding the actual kernel source for the 4.1a distribution could provide clarity on this point.

Perhaps Bill Joy could shed some light on the issue, but I don't have contact details. Having actual source removes all doubt.

Paul


On 1 Dec 2016, at 10:51 , Diomidis Spinellis wrote:

> The best description I could find is the following:
> 
> http://minnie.tuhs.org/pipermail/tuhs/2016-September/007417.html
> 
> > The 4.1a distribution had the initial socket interface with a
> > prerelease of the BBN TCP/IP under it. There was wide distribution
> > of 4.1a. The 4.1b distribution had the fast filesystem added and
> > a more mature socket interface (notably the listen/accept model
> > added by Sam Leffler).
> 
> Diomidis
> 
> On 01/12/2016 10:30, Paul Ruizendaal wrote:
>> 
>> Hi,
>> 
>> I'm trying to find out exactly what was in the 4.1a BSD distribution, as far as the kernel is concerned. The image in the CSRG archive comes from a tape that had a hard read error and does not include any kernel sources. Some of the kernel files were already covered by SCCS around that time, but not everything. My main focus is to understand tcp/ip networking in 4.1a and whether the kernel could be built with either the Berkeley or the BBN network stack.
>> 
>> Does anybody know where I could find a full set of kernel sources for the 4.1a BSD kernel?
>> 
>> Many thanks in advance!
>> 
>> Paul
>> 
> 



  parent reply	other threads:[~2016-12-01 10:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  8:30 Paul Ruizendaal
     [not found] ` <0f3795f4-fb98-3370-510c-347a272dddae@aueb.gr>
2016-12-01 10:40   ` Paul Ruizendaal [this message]
2016-12-01 14:27     ` Clem Cole
2016-12-01 15:30       ` [TUHS] Masscomp sources? was " Larry McVoy
2016-12-01 16:06         ` Clem Cole
2016-12-01 20:13       ` [TUHS] " Paul Ruizendaal
2016-12-01 21:28         ` Clem Cole
2016-12-03  4:16 Jason Stevens
2016-12-02  9:37 ` 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=38CA85C9-C005-49C5-8BD5-3FC65FC170BF@planet.nl \
    --to=pnr@planet.nl \
    /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).