From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id ed55c0d9 for ; Sun, 13 Jan 2019 15:39:57 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 0454794674; Mon, 14 Jan 2019 01:39:56 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 4C70E94666; Mon, 14 Jan 2019 01:39:23 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=bsdimp-com.20150623.gappssmtp.com header.i=@bsdimp-com.20150623.gappssmtp.com header.b="Ego430uh"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 3FE1494666; Mon, 14 Jan 2019 01:39:19 +1000 (AEST) Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173]) by minnie.tuhs.org (Postfix) with ESMTPS id E4E2793D29 for ; Mon, 14 Jan 2019 01:39:17 +1000 (AEST) Received: by mail-qk1-f173.google.com with SMTP id y78so9222923qka.12 for ; Sun, 13 Jan 2019 07:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W3ZeqMJqxJpUvv0I39PE2fFNIpgB0TIfZqwmV+OJV2U=; b=Ego430uhLBcIex98eHvfYuLan7Fc8gOtVZbF6cRjELRLYN0Lo71zpFoLmQ63/Ze1EJ 98F8Y8tOi9BlBFyYhJUzS5M4Nu4RlsBJ4k+n65+hjErYAfT8drSuyR1mu0I0uy9NSN56 /OKmt2KqFb+8bX2jCSR37FOoy7iGwJR/D8bamgbqS8vocpVKWY+UolYZuYwov4LL49Yj TlvutGMClSeIGcKscCoBQKffKhOUHCWVNVan93USA5KHHNDIWMEOMMTayouV95cqoWqB HTYRAqokYPuNQCNmRkMCWO/iifBGnKbOUNUKo0pwR0ZBcaEzzjDV+rC8QSCFDo9FBKDn RsFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W3ZeqMJqxJpUvv0I39PE2fFNIpgB0TIfZqwmV+OJV2U=; b=JvziPA7elukAcjZ8tG6r3rVd59BY+FNSsy6ArK0m1UBGgwl1x7AhZSgAPYVNO0aj3T tG02K0CvsBVBImMYyZJDUXUBKIaj8CLnK7Z9A07I0w0IM1ZajTKmM3036E6Jl02+gt+F WGtdGTb0vOhUo5lE08hm5jjx0bvrxGCYFxey2dJBHjobhSTNjv2kpX1Q0VQswbBQP2b5 iO1C87DmWBSZ8MWexBnMomOXRTTj/c81cAJ8G2SZSE9soySBqu80b9wDnIqzV3svffeD jaHEQ9OdTFfBIkBolMoUldhtqhqn/bAASyPNaIcyKN0evJdKsu6hCEYkmCyhL/XOQ0Om B5LA== X-Gm-Message-State: AJcUukdeaTDQ/3Ai7sNnr9BZag8kDQy2QeuLIml2h2k8HLiPRhxykwCR xy8jz1n4PCShRcn6EMokxqRxzt9L5mBCz8kdwLAgZw== X-Google-Smtp-Source: ALg8bN6hGUoo7lRP8gwtlfZATI3mJUO6q4z7tYKs/1CDAePsVEMxu2opAV1XGgy6uE8RfT+qb4cBMNnBxbU9OS4RBVw= X-Received: by 2002:a37:6c05:: with SMTP id h5mr19754541qkc.175.1547393956876; Sun, 13 Jan 2019 07:39:16 -0800 (PST) MIME-Version: 1.0 References: <921E58F1-1631-4390-8CCD-52EE0238B241@planet.nl> In-Reply-To: <921E58F1-1631-4390-8CCD-52EE0238B241@planet.nl> From: Warner Losh Date: Sun, 13 Jan 2019 08:39:05 -0700 Message-ID: To: Paul Ruizendaal Content-Type: multipart/alternative; boundary="00000000000020b20f057f58bb35" Subject: Re: [TUHS] V6 networking & alarm syscall X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000020b20f057f58bb35 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jan 13, 2019 at 3:53 AM Paul Ruizendaal 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=3DBBN-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 =E2=80=98deprecated=E2=80=99 is where the code end= ed 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 --00000000000020b20f057f58bb35 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Jan 13, 2019 at 3:53 AM Paul Ruiz= endaal <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?fi= le=3DBBN-Vax-TCP

And was the BBN V6 ver= sion ever ported to V7?

Several tapes of it survived in the CSRG archives, currently held by the Ba= ncroft Library at Berkeley.

Are those o= nline? Or an index? Google is failing me (or my google skillz aren't ma= d this morning).
=C2=A0
A late version of the tcp/ip routines survived at the Sta= nford 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].
=C2=A0
A much evolved version is in the BSD SCCS history:
https://github.com/weiss/orig= inal-bsd/tree/master/sys/deprecated/bbnnet
Note that the location =E2=80=98deprecated=E2=80=99 is where the code ended= up. Back in 1985 it would have been in the normal build path, but SCCS doe= s not preserve that.

I wonder if anybod= y has gone to the trouble of trying to recreate the movement of these sys/d= eprecated 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 th= e tree buildable with these obscure things...

Warn= er
--00000000000020b20f057f58bb35--