The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] My BSDcan talk
Date: Sat, 6 Jun 2020 12:01:08 -0400	[thread overview]
Message-ID: <CAC20D2M_VOM58EuCPnTzMdpshqUW6nQH+fKbj3F6gnZLHTqqdA@mail.gmail.com> (raw)
In-Reply-To: <9E4F4C8A-A2F6-4993-9144-30A4D3721CF1@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

On Sat, Jun 6, 2020 at 10:56 AM Paul Ruizendaal <pnr@planet.nl> wrote:

> The Chaos network code made namei() break when it recognised the Chaos
> driver and left the remainder of the path for the driver to fetch & parse.
>
Yep - cute hack -- Domain (Aegis) did the same trick (same code author most
likely).  The biggest advantage is that open(2) can be used unchanged and
'parameters' are passed in ASCII to the lower code.

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
is 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.   I'm pretty sure
that wnj thought it was an ugly solution; which is why UCB did not try it.

We played with this solution also in the early Masscomp networking code (I
had seen it in the Chaos driver from MIT); but by then the UCB code was
coming out and user code was using sockets, so we just kept with that
interface for code reuse reasons.

Clem

[-- Attachment #2: Type: text/html, Size: 2241 bytes --]

  reply	other threads:[~2020-06-06 16:02 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 [this message]
2020-06-07 11:41   ` Paul Ruizendaal
2020-06-07 20:03     ` Warner Losh
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=CAC20D2M_VOM58EuCPnTzMdpshqUW6nQH+fKbj3F6gnZLHTqqdA@mail.gmail.com \
    --to=clemc@ccc.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).