From: segaloco via TUHS <email@example.com>
To: The Eunuchs Hysterical Society <firstname.lastname@example.org>
Subject: [TUHS] Re: when did v8 or later get networking?
Date: Thu, 10 Aug 2023 03:17:25 +0000 [thread overview]
Message-ID: <SeUP9fhGy63CKDEJgvZU1o2O_-ILWoInPSYrezt2wGE5ZUg1vQfidwcBNr843YqYGAZg7NAqkgx1b3f9ClNTDt0X7Jz7KhbpeyyNxjbp4n0email@example.com> (raw)
> > > TCP/IP, not datakit.
> > The V8 manual contains internet(3), tcp(3), and udp(3). In the copy I have these are dated 8/7/85. Down in the kernel in /usr/sys/inet the earliest files appear to be dated 3/22/85. I'm going to do a comparison with the 4.1cBSD TCP/IP stuff because a casual glance reveals some overlap.
> > - Matt G.
> Yea, I thought it was 4.1bsd + later tcp code but with a STREAMS instead of Socket interface...
This comment at the top of /usr/sys/netinet/socket.c is illuminating:
> * socket emulation routines
> * pretty much 4.2 sys/uipc_socket2.c
All of the files that have timestamps at the top list 83/07/29, except ip_input.c which has 83/08/16 instead. The V8 version has _device (device driver) and _ld (line discipline) components that the 4.1cBSD code does not have. Many other files have analogs between the two. The byte ordering subroutines have been copied into a file, goo.s, from their home in 4.1cBSD in the C library (/usr/src/lib/libc/net/misc). When this work originated someone else would need to answer, but looks like it was as Warner described, modified 4.xBSD TCP/IP.
- Matt G.
next prev parent reply other threads:[~2023-08-10 3:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 1:09 [TUHS] " Larry McVoy
2023-08-10 2:38 ` [TUHS] " segaloco via TUHS
2023-08-10 2:45 ` Warner Losh
2023-08-10 3:17 ` segaloco via TUHS [this message]
2023-08-10 3:18 ` Rob Pike
2023-08-10 5:44 ` John Cowan
2023-08-10 12:41 ` Douglas McIlroy
2023-08-10 14:00 ` Jonathan Gray
2023-08-11 9:05 Paul Ruizendaal
2023-08-12 5:08 ` Warner Losh
2023-08-12 5:41 ` George Michaelson
2023-08-12 9:06 ` Paul Ruizendaal
2023-08-12 10:29 ` Paul Ruizendaal
2023-08-12 15:20 ` Warner Losh
2023-08-12 15:24 ` Dan Cross
2023-08-12 16:12 ` Paul Ruizendaal
2023-08-12 15:05 Noel Chiappa
2023-08-12 18:00 ` Paul Ruizendaal
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).