From: Warner Losh <imp@bsdimp.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] V6 networking & alarm syscall
Date: Sun, 13 Jan 2019 08:39:05 -0700 [thread overview]
Message-ID: <CANCZdfrvmuwQWg0PEZWE2NK9AVZcB9VZDJk_Okvp0mZxANTMfQ@mail.gmail.com> (raw)
In-Reply-To: <921E58F1-1631-4390-8CCD-52EE0238B241@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
On Sun, Jan 13, 2019 at 3:53 AM Paul Ruizendaal <pnr@planet.nl> wrote:
> > Where did you find the BBN TCP/IP stack?
>
> Easiest place to find it is the TUHS Unix Tree page:
> https://www.tuhs.org//cgi-bin/utree.pl?file=BBN-Vax-TCP
And was the BBN V6 version ever ported to V7?
Several tapes of it survived in the CSRG archives, currently held by the
> Bancroft Library at Berkeley.
>
Are those online? Or an index? Google is failing me (or my google skillz
aren't mad this morning).
> A late version of the tcp/ip routines survived at the Stanford SAIL
> archives, currently online here:
> https://www.saildart.org/[IP,SYS]/
> (mixed in with sources for WAITS).
>
Now that's quite interesting. There's even a C compiler in [C,SYS].
> A much evolved version is in the BSD SCCS history:
> https://github.com/weiss/original-bsd/tree/master/sys/deprecated/bbnnet
> Note that the location ‘deprecated’ is where the code ended up. Back in
> 1985 it would have been in the normal build path, but SCCS does not
> preserve that.
>
I wonder if anybody has gone to the trouble of trying to recreate the
movement of these sys/deprecated things into real moves to deprecated
coupled with the commit that removed them from the files files, or if any
work has been done to make the tree buildable with these obscure things...
Warner
[-- Attachment #2: Type: text/html, Size: 2534 bytes --]
next prev parent reply other threads:[~2019-01-13 15:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 10:52 Paul Ruizendaal
2019-01-13 15:39 ` Warner Losh [this message]
2019-01-16 23:13 ` [TUHS] Old Unix source code DVD [was: V6 networking & alarm syscall] Paul Ruizendaal
2019-01-17 13:19 ` reed
2019-01-17 14:38 ` Clem Cole
2019-01-17 19:33 ` Warren Toomey
2019-01-17 20:00 ` reed
[not found] <mailman.1.1547258402.6716.tuhs@minnie.tuhs.org>
2019-01-12 11:13 ` [TUHS] V6 networking & alarm syscall Paul Ruizendaal
-- strict thread matches above, loose matches on Subject: below --
2019-01-12 4:14 Noel Chiappa
2019-01-12 1:24 Noel Chiappa
2019-01-12 1:58 ` Dave Horsfall
2019-01-12 2:33 ` Warner Losh
2019-01-11 23:27 Paul Ruizendaal
2019-01-10 23:12 Paul Ruizendaal
2019-01-11 0:17 ` Clem cole
2019-01-11 15:33 ` ron
2019-01-11 18:45 ` Clem Cole
2019-01-11 19:06 ` David
2019-01-11 22:08 ` reed
2019-01-11 22:18 ` Larry McVoy
2019-01-12 12:04 ` reed
2019-01-12 17:20 ` Clem Cole
2019-01-12 18:16 ` Eric Allman
2019-01-13 1:16 ` Madeline Autumn-Rose
2019-01-11 22:47 ` Clem Cole
2019-01-11 22:55 ` Eric Allman
2019-01-11 23:32 ` Warner Losh
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=CANCZdfrvmuwQWg0PEZWE2NK9AVZcB9VZDJk_Okvp0mZxANTMfQ@mail.gmail.com \
--to=imp@bsdimp.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).