From: Rob Landley <rlandley@parallels.com>
To: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
v9fs-developer@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [V9fs-developer] Breaking out virtfs as a standalone server?
Date: Tue, 12 Apr 2011 12:24:47 -0500 [thread overview]
Message-ID: <4DA48ADF.1040406@parallels.com> (raw)
In-Reply-To: <4DA462EC.8010500@linux.vnet.ibm.com>
On 04/12/2011 09:34 AM, Venkateswararao Jujjuri wrote:
> On 04/11/2011 10:52 PM, Rob Landley wrote:
>> On 04/11/2011 03:28 PM, Venkateswararao Jujjuri wrote:
>>> On 04/11/2011 06:42 AM, Rob Landley wrote:
>>>> 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.)
>>> This statement is true for 9P2000.L protocol;
>> According to my research on the topic, anyway:
>>
>> http://landley.livejournal.com/48698.html
>
> You wrote " And at the moment write support seems to be broken for me.
> But I was able to mount a directory from the host system and cat a file,
> which is progress."
>
> Can you please explain where it is broken. IT should be working good.
That's an old blog entry, we already dealt with that a while back:
http://sourceforge.net/mailarchive/message.php?msg_id=26950979
What I hadn't found was a better server, until the new diod release.
(Hence my interest in possibly getting the code in qemu factored out and
more flexible.)
Rob
prev parent reply other threads:[~2011-04-12 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 13:42 [Qemu-devel] Breaking out virtfs as a standalone server? Rob Landley
2011-04-11 20:28 ` 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 ` Rob Landley [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=4DA48ADF.1040406@parallels.com \
--to=rlandley@parallels.com \
--cc=ericvh@gmail.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=v9fs-developer@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.