From: Andrew Warkentin <andreww591@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] My BSDcan talk
Date: Sat, 6 Jun 2020 23:15:42 -0600 [thread overview]
Message-ID: <CAD-qYGrPe_sYvaCPDCX=YkXBJEAZxx-q7rw6CZ8g=t4dFMu5RQ@mail.gmail.com> (raw)
In-Reply-To: <9E4F4C8A-A2F6-4993-9144-30A4D3721CF1@planet.nl>
On 6/6/20, Paul Ruizendaal <pnr@planet.nl> wrote:
>
> In my view, exposing the host names through integration in the Unix file
> name space makes a lot of conceptual sense, but it unfortunately falls down
> on the practicalities, with the host name set being hard to enumerate (it is
> large, distributed and not stable - even back then).
>
With a proper dynamic VFS architecture, there is no reason why a
resolver with a filesystem API has to bother supporting enumeration at
all. All it needs to be able to do is respond to open() and stat()
calls, returning ENOENT when resolution fails.
next prev parent reply other threads:[~2020-06-07 5:16 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
2020-06-07 5:15 ` Andrew Warkentin [this message]
-- 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='CAD-qYGrPe_sYvaCPDCX=YkXBJEAZxx-q7rw6CZ8g=t4dFMu5RQ@mail.gmail.com' \
--to=andreww591@gmail.com \
--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).