From: Warner Losh <imp@bsdimp.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] My BSDcan talk
Date: Sun, 7 Jun 2020 14:03:46 -0600 [thread overview]
Message-ID: <CANCZdfr=v_fBbWQ1FHcE5QRkerz_uJAzyXY+pwL=9xP-mJszBQ@mail.gmail.com> (raw)
In-Reply-To: <465A2942-5740-4B74-AF7E-8E58B37DC499@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Sun, Jun 7, 2020 at 5:42 AM Paul Ruizendaal <pnr@planet.nl> wrote:
>
> > On 6 Jun 2020, at 18:01, Clem Cole <clemc@ccc.com> wrote:
> >
> > You mentioned that BBN Vax code did not use it. I've forgotten than how
> parameters like IP addresses were passed down? I had thought that Rob had
> it also in at least one version of the BBN code, as I remember talking to
> him about it at one point; but I have frankly forgotten.
>
> In the surviving source code, BBN VAX TCP re-purposed the ‘mode’ parameter
> of open() to be a pointer to a block with connection data (“struct con”).
> Details are here:
> https://www.tuhs.org/cgi-bin/utree.pl?file=BBN-Vax-TCP/doc/net.5.P
That's... clever? Gross? I don't even know how I'd want to react to
this... which likely means "too clever for its own good" :)
In any event, I've created a short, 2:00 correction to my talk. I'll have
the conference organizers tack onto the end before they upload it to
youtube.
https://www.youtube.com/watch?v=9uTjyfO6MM8
If people care :)
Thanks everybody for corrections...
Warner
[-- Attachment #2: Type: text/html, Size: 1808 bytes --]
next prev parent reply other threads:[~2020-06-07 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 14:55 Paul Ruizendaal
2020-06-06 16:01 ` Clem Cole
2020-06-07 11:41 ` Paul Ruizendaal
2020-06-07 20:03 ` Warner Losh [this message]
2020-06-07 5:15 ` Andrew Warkentin
-- strict thread matches above, loose matches on Subject: below --
2020-06-05 22:51 Warner Losh
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='CANCZdfr=v_fBbWQ1FHcE5QRkerz_uJAzyXY+pwL=9xP-mJszBQ@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.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).