From: Paul Ruizendaal <pnr@planet.nl>
To: ron minnich <rminnich@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: is networking different?
Date: Tue, 5 Jul 2022 01:37:52 +0200 [thread overview]
Message-ID: <7E3B9D54-8D4A-495F-9548-CA4B1B285BE4@planet.nl> (raw)
In-Reply-To: <CAP6exYJAAXoTCJ16k60JuCUH0-CZQEiQoWwMUrsYZMuGxa622Q@mail.gmail.com>
Thank you for sharing experiences on what worked and what did not. Much appreciated!
As I’m now too much on a tangent of what might have been versus what once was, I’ll follow up with a PM.
> On 4 Jul 2022, at 23:17, ron minnich <rminnich@gmail.com> wrote:
>
> Something like what you mention: open(“/net/inet/any:80”, O_RDWR |
> O_STREAM | O_CREAT, 0600), is actually to be found in an RFC from
> around that time.
>
> You can do that, but the 1980s tried it and it did not end well.
> What's it mean, for example, when you rename("/net/harv") to
> ("/net/google") -- close and reopen socket? (there's a Lost Talk from,
> I think, Rob, that addressed this very question)
>
> While it has its flaws, https://9p.io/sys/doc/net/net.html in my view
> is the best example to date of how to get it right. Addresses are
> strings, just like paths -- well, they *are* paths in fact. Some of
> this path-like nature can be seen in the Go net package today.
>
> Oh, and, as regards how the synthetic file system looks: you never,
> never, ever, put an address in the pathname. That's important.
>
> Also consider that if you get it right, you can do all the network IO
> you want with cat and echo -- people have written telnet in Plan 9
> with those two commands. And, if you get it wrong, well -- you get
> socat.
next prev parent reply other threads:[~2022-07-04 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 20:09 [TUHS] Re.: " Paul Ruizendaal via TUHS
2022-07-04 20:44 ` [TUHS] " Larry McVoy
2022-07-04 21:31 ` Paul Ruizendaal via TUHS
2022-07-04 21:33 ` Phil Budne
2022-07-04 21:17 ` ron minnich
2022-07-04 23:37 ` Paul Ruizendaal [this message]
2022-07-05 3:02 ` [TUHS] " John Cowan
-- strict thread matches above, loose matches on Subject: below --
2022-07-03 20:32 [TUHS] " Marc Donner
2022-07-03 20:34 ` [TUHS] " Marc Donner
2022-07-03 20:57 ` Dan Stromberg
2022-07-03 21:55 ` Richard Salz
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=7E3B9D54-8D4A-495F-9548-CA4B1B285BE4@planet.nl \
--to=pnr@planet.nl \
--cc=rminnich@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).