From: Eric Van Hensbergen <ericvh@gmail.com>
To: v9fs-developer@lists.sourceforge.net,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] 9P2000 Protocol Specification
Date: Mon, 28 Feb 2005 15:12:02 -0600 [thread overview]
Message-ID: <a4e6962a0502281312717ba746@mail.gmail.com> (raw)
Uck. Let me just say, I hate RFCs, I hate XML, and I really think
I'll dislike the whole process. But for what's it worth: initial stab
conforming to Internet-Draft format-restrictions at the very least is
at http://v9fs.sf.net/rfc
Yes - it's just the man pages cut-and-pasted into their template. No
- its not finished. It's a starting point for fleshing out the
documentation of the actual protocol (and will be shortly joined by a
9P2000.u RFC). I figure this might be a more digestible form for the
liunix guys (particularly once I flesh out the content a bit more) --
this whole exercise is motivated by my attempt to get the v9fs project
accepted into the Linux kernel mainstream.
Source is in (v9fs.sf.net) CVS under v9fs/doc/rfc -- there's actually
a bunch of different swags at it there, but current stuff is generated
from 9p.xml (which there is a set of perl scripts on the net to
generate .roff, .html, or .txt from)
Comments/additions/etc. welcome from the 9fans community. I've
started with Section 5 of the man pages, but my intent is to add/shape
content to flesh out the protocol loosely following the format of the
NFS RFCs (in particular RFC 3010 which is NFSv4).
Sorry if I have not given enough credit to the real authors - I'm
going to work on that too, making it very clear that I'm just a
scribe. I'm also going to track down and tack on the appropriate
copyright/licensing information -- my only intent at this point is to
get others involved in helping me flesh things out, this is a very,
very, very early preliminary draft, so don't yell at me.
-eric
reply other threads:[~2005-02-28 21:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a4e6962a0502281312717ba746@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@cse.psu.edu \
--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 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).