From: Clem Cole <clemc@ccc.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SDB debugger
Date: Sat, 2 May 2020 12:04:09 -0400 [thread overview]
Message-ID: <CAC20D2N8RkBK=D3qJuW4Sv=sgeXbc8YYUvCu3GbsWUBpiJHkXA@mail.gmail.com> (raw)
In-Reply-To: <8CBDD12A-563F-458D-938B-3AF84D936F39@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Paul - you are correct that its got a lot of it there and in particular the
kernel (which is good). But the /usr directory (and thus /usr/src) is
missing. It's not a completely distribution, it's the BBN 4.1 TCP
distribution which was a subset.
As I said, 4.0 and 4.1 were similar, but different.
The trick is find a complete 4.1 distribution tape.
On Sat, May 2, 2020 at 5:10 AM Paul Ruizendaal <pnr@planet.nl> wrote:
>
> On May 1, 2020, at 11:57 PM, Clem Cole <clemc@ccc.com> wrote:
>
>
> [Note to Warren, we should put 4.1 in the browsing tree. The kernel is
> different enough from 4.0 and does have new utilities, although it was not
> nearly as different as 4.1c. The reality is until 4.2BSD came out with the
> networking support, most Vaxen running BSD were 4.1 not 4.0 based.
>
>
> It is already there! The entry named "BBN's TCP/IP Code for the VAX” is
> 4.1BSD with the BBN TCP stack added. The changes to the kernel are just one
> or two dozen lines (all in sys2.c and main.c) bracketed in #ifdef BBNNET
> blocks. The actual network stack is in a separate build directory.
>
> Maybe the entry should be renamed “4.1BSD with TCP/IP” to make this more
> clear.
>
>
>
[-- Attachment #2: Type: text/html, Size: 2266 bytes --]
next prev parent reply other threads:[~2020-05-02 16:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:48 Paul Ruizendaal
2020-05-01 21:57 ` Clem Cole
2020-05-02 9:10 ` Paul Ruizendaal
2020-05-02 16:04 ` Clem Cole [this message]
2020-05-01 23:05 ` Jeremy C. Reed
2020-05-02 0:49 ` Noel Hunt
2020-05-02 1:22 ` Rob Pike
2020-05-02 3:49 ` Noel Hunt
2020-05-02 20:16 ` Paul Ruizendaal
2020-05-03 6:58 ` arnold
2020-05-03 16:13 ` Clem Cole
2020-05-03 16:53 ` Henry Bent
2020-05-03 17:06 ` Henry Bent
2020-05-03 17:13 ` Henry Bent
2020-05-03 20:26 ` Clem Cole
2020-05-05 0:22 ` [TUHS] DEC Compilers (was: " Win Treese
2020-05-05 17:36 ` Paul Winalski
2020-05-05 18:53 ` Dr Iain Maoileoin
2020-05-05 21:59 ` Dan Cross
2020-05-05 21:49 ` Henry Bent
2020-05-03 17:35 ` [TUHS] " Paul Winalski
2020-05-03 21:27 ` Paul Ruizendaal
2020-05-12 4:15 ` Dave Horsfall
2020-05-02 2:52 Doug McIlroy
2020-05-02 17:45 ` Larry McVoy
2020-05-03 16:16 ` Rich Morin
2020-05-12 4:36 ` Dave Horsfall
2020-05-03 2:21 Norman Wilson
2020-05-03 2:41 ` Larry McVoy
2020-05-03 7:14 ` arnold
2020-05-03 3:05 ` Rob Pike
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='CAC20D2N8RkBK=D3qJuW4Sv=sgeXbc8YYUvCu3GbsWUBpiJHkXA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.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).