From: Rob Landley <rob@landley.net>
To: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Breaking out virtfs as a standalone server?
Date: Mon, 11 Apr 2011 08:42:01 -0500 [thread overview]
Message-ID: <4DA30529.1080501@landley.net> (raw)
Right now, there's no decent userspace server for the 9p filesystem that
I can find. (In part because the 9P2000.L spec is an undocumented work
in progress.)
The only up-to-date server seems to be virtfs in qemu, which has no TCP
transport layer.
Are there any plans to:
A) Add a TCP transport layer so we can test with something we can
intercept/examine/log/redirect with netcat and such?
B) Break the 9p server out so it could be built as a standalone
userspace program?
Rob
next reply other threads:[~2011-04-11 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 13:42 Rob Landley [this message]
2011-04-11 20:28 ` [Qemu-devel] Breaking out virtfs as a standalone server? Venkateswararao Jujjuri
2011-04-11 23:28 ` [Qemu-devel] [V9fs-developer] " Jim Garlick
2011-04-12 5:52 ` [Qemu-devel] " Rob Landley
2011-04-12 14:34 ` Venkateswararao Jujjuri
2011-04-12 17:24 ` [Qemu-devel] [V9fs-developer] " Rob Landley
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=4DA30529.1080501@landley.net \
--to=rob@landley.net \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).