From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Plumber architecture question
Date: Sat, 5 Jan 2019 14:53:56 +0000 [thread overview]
Message-ID: <1546700036.2620681.1626275168.4E9AE621@webmail.messagingengine.com> (raw)
In-Reply-To: <e9113002-aa20-4c22-aef9-9eecdaaa89aa@email.android.com>
On Sat, Jan 5, 2019, at 2:12 PM, erik quanstrom wrote:
> you need plumber so cpu can be transparent to plumbing.
Good point. I think it could be done with multi-/srv, but I see one problem: you wouldn't want cpu to export all of /srv. (Right?) I think it could be dealt with by mounting a separate #s instance (for want of a better name) just for the plumber-replacement pipes.
prev parent reply other threads:[~2019-01-05 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 8:47 Ethan Gardener
2019-01-05 14:12 ` erik quanstrom
2019-01-05 14:53 ` Ethan Gardener [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=1546700036.2620681.1626275168.4E9AE621@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).