On Sunday, 11 September 2016 at 23:24:47 -0600, Warner Losh wrote:
On Sun, Sep 11, 2016 at 10:44 PM, Greg
'groggy' Lehey <grog(a)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,
Right, the discussion was about 4.1c. I just wanted to confirm that
it was, in fact, the first version with TCP/IP.
but rather Research Unix Edition 8 having these
things.
Yes, that's what Norman said:
>> if it did, they were excised.
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 think the perceived "failings" were with sockets, not with TCP/IP.
That was what led to the misimplementation of STREAMS. My real
confusion was what they really wanted from 4.1c, but I suppose it was
the VM implementation. Can anybody comment?
Greg
--
Sent from my desktop computer.
Finger grog(a)FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read
http://lemis.com/broken-MUA