From: Clem Cole <clemc@ccc.com>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: BSD Talk History -- Credit Where Credit is Due
Date: Sat, 14 Dec 2024 11:35:39 -0500 [thread overview]
Message-ID: <CAC20D2NA6Go-CZbPMH_MH6okv9uUjVhZ1i7jr8c5N9EFi0fNrg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4doFQSvDDjTfJv9-JpD_1A0jYcwe0Dch8yyQs3hs5QQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2550 bytes --]
I don't remember how Kipp did it. It would have been very V7 oriented and
using the FS and signals I suspect. I remember is was not very sexy and
one of things sockets allowed was completely rethink. That was the bull
session I was referring too. As for the security issue, sure - we would not
have considered that. Again we were grad students and basically friendly
so actions like that would have been considered uncool.
As I have pointed out elsewhere when a connection to the ARPAnet cost
250K/yr per host and a host cost $1-4M, the concepts of security and us all
being in it together—a friendly community, as it were—had different
behaviors when a host is is $10-30 micro and wireless Interconnect can
slimed at Starbucks for free.
ᐧ
On Sat, Dec 14, 2024 at 11:01 AM Dan Cross <crossd@gmail.com> wrote:
> On Sat, Dec 14, 2024 at 10:41 AM Clem Cole <clemc@ccc.com> wrote:
> > I was thinking about this some more.
> >
> > IIRC: Peter and I sketched out the protocol for the sockets version on a
> whiteboard in our office one night after a beer and pizza run. Rick
> Spicklemeir, Tom Quarles, and Jim Kleckner also participated in those bull
> sessions. I started writing the program soon after that and had it working
> to a point in a couple of hours. I don't remember the issues, but a couple
> of them were when I left for the USENIX conference later that week. When I
> got back Peter had finished it and put it into RCS. The key is that the
> coding was primarily Peter and myself, but Rick, TQ, and Jim all had
> contributed in some manner, too,
> >
> > Although the famous bug of using a vax integer, you can squarely blame
> me — and as I said, having worked on networking for several years before my
> time at UCB, I should have known better. But did not even think about it.
> I failed Henry's ten programming commandments and concluded that the world
> was a Vax. Mei culpa.
> > ᐧ
>
> Thanks, Clem, these are very interesting notes.
>
> The protocol had some interesting aspects to it; since the ctl address
> was embedded in the message sent to the distant end, a trick of some
> locals when I was younger was to put fake data in the request. The
> effect would be that one would get a request to talk from user1@host1,
> but actually be talking to user2@host2. This could either be very
> funny or very uncool.
>
> I'm curious how the original worked, which I sort of gather was before
> sockets? How did the two users rendezvous?
>
> - Dan C.
>
[-- Attachment #2: Type: text/html, Size: 3484 bytes --]
prev parent reply other threads:[~2024-12-14 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 15:40 [TUHS] " Clem Cole
2024-12-14 16:00 ` [TUHS] " Dan Cross
2024-12-14 16:35 ` Clem Cole [this message]
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=CAC20D2NA6Go-CZbPMH_MH6okv9uUjVhZ1i7jr8c5N9EFi0fNrg@mail.gmail.com \
--to=clemc@ccc.com \
--cc=crossd@gmail.com \
--cc=tuhs@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).