From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] the import/exportfs protocol and a proposed import -z flag
Date: Wed, 27 Feb 2013 13:25:28 +0000 [thread overview]
Message-ID: <CAOw7k5h4Va9RT+xetkRhVU8-_CmV-m5BPQUwW_3MXR7wCTWncg@mail.gmail.com> (raw)
In-Reply-To: <dc593bcc78d8be3026fe48978121caab@sphericalharmony.com>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
On 27 February 2013 08:24, <mycroftiv@sphericalharmony.com> wrote:
> I hope this post leads to constructive discussion of the import/exportfs
> protocol.
As you'll have noticed, it isn't a great protocol as it stands. I don't
think your option makes it worse.
Thanks for the detailed discussion. I think at least one existing system
already does what you say, using the -m option ([just] mount, skipping the
tree spec),
and if you were to use that in a patch to sources, then eventually that
private change could be eliminated.
Note that in your example
import -z tcp!server!9876 somefiles /n/authedimport
with the existing import you don't need to specify the (now unused)
somefiles. If I write {import system /net} it sends "/net" as the tree by
default.
I think all you'd need to do to make the option tidier is to reject the
case argc == 3 in the relevant switch if the option is set. Then you could
write
(changing the option letter):
import -m tcp!server!9876 /n/authedimport
which reads as import by mounting the 9P service on the given connection on
the given mount point. It's otherwise a little strange to have an
argument (your "somefiles") that's completely ignored.
As you say, this could also reasonably be an option to srv to authenticate
its connection to a remote exportfs, but the fewer commands that know
this particular protocol, the better, and both import and exportfs already
do that.
[-- Attachment #2: Type: text/html, Size: 2615 bytes --]
next prev parent reply other threads:[~2013-02-27 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 8:24 mycroftiv
2013-02-27 13:25 ` Charles Forsyth [this message]
2013-02-28 1:38 mycroftiv
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=CAOw7k5h4Va9RT+xetkRhVU8-_CmV-m5BPQUwW_3MXR7wCTWncg@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--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).