From: b4@gewt.net (Cory Smelosky)
Subject: [TUHS] BSD/v8 TCP/IP (was Shell control through external commands)
Date: Sun, 11 Sep 2016 22:38:27 -0700 [thread overview]
Message-ID: <9E04568D-9E90-4A3F-B584-C5A16871DAE0@gewt.net> (raw)
In-Reply-To: <CANCZdfpUicqxu-x-3AFo-h+0X-Grfje-74Kd0Ht0J60Q-zBxhw@mail.gmail.com>
Do any copies of 8th Edition exist anywhere? ;)
That's one way to check!
Sent from my iPhone
> On Sep 11, 2016, at 22:24, Warner Losh <imp at bsdimp.com> wrote:
>
>> On Sun, Sep 11, 2016 at 10:44 PM, Greg 'groggy' Lehey <grog at lemis.com> wrote:
>>> On Sunday, 11 September 2016 at 21:31:10 -0400, Norman Wilson wrote:
>>>
>>> -- Adopt 4.1c BSD kernel
>>> ...
>>>
>>> I don't think the BSD kernel when adopted had much, if any,
>>> of sockets, Berkeley's TCP/IP, McKusick's FFS; if it did,
>>> they were excised.
>>>
>>> ...
>>>
>>> TCP/IP support didn't show up until later, I think summer 1985,
>>> though it might have been a year later.
>>
>> I'm confused. 4.1c has gone down in history as the first version with
>> Internet code, and looking at the sources (from mckusick's CD set), I
>> see the network files in /sys/netinet with names very reminiscent of
>> current FreeBSD file names. The files have timestamps between
>> November 1982 and May 1983. Why should they have been removed? I
>> would have thought that exactly this functionality would have been the
>> reason why you adopted 4.1c.
>>
>> Similarly, it also included FFS and (not surprisingly sockets.
>>
>> I checked further back, but unfortunately the previous version on the
>> CDs is 4.1a, and it has no kernel code.
>
> I don't think they are talking about BSD4.1a having these things, but
> rather Research Unix Edition 8 having these things. Bell labs didn't
> integrate them until later. I recall reading articles at the time (1983
> or 1984) that they had their own notion of what networking to use
> that wasn't TCP/IP due to some perceived failings of TCP/IP that
> they fixed with their stuff. I recall that I read it in the library in
> high school. Wish I'd forgotten that and recalled what the network
> protocol was they implemented instead...
>
> Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160911/02a63b7a/attachment.html>
next prev parent reply other threads:[~2016-09-12 5:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 1:31 [TUHS] Shell control through external commands Norman Wilson
2016-09-12 4:44 ` [TUHS] BSD/v8 TCP/IP (was Shell control through external commands) Greg 'groggy' Lehey
2016-09-12 5:24 ` Warner Losh
2016-09-12 5:38 ` Cory Smelosky [this message]
2016-09-12 5:48 ` Erik E. Fair
2016-09-12 9:22 ` Joerg Schilling
2016-09-12 10:25 ` Brantley Coile
2016-09-12 11:00 ` Joerg Schilling
2016-09-12 11:16 ` Brantley Coile
2016-09-12 11:42 ` Brantley Coile
2016-09-12 11:42 ` Joerg Schilling
2016-09-12 7:20 ` Greg 'groggy' Lehey
2016-09-12 18:32 ` Clem Cole
2016-09-13 10:52 ` Tony Finch
2016-09-13 12:54 ` Clem Cole
2016-09-12 9:33 ` [TUHS] Shell control through external commands Joerg Schilling
2016-09-12 12:56 [TUHS] BSD/v8 TCP/IP (was Shell control through external commands) Norman Wilson
2016-09-12 15:27 ` Joerg Schilling
2016-09-12 15:41 Norman Wilson
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=9E04568D-9E90-4A3F-B584-C5A16871DAE0@gewt.net \
--to=b4@gewt.net \
/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).