1 v9fs: Plan 9 Resource Sharing for Linux
2 =======================================
7 v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol.
9 This software was originally developed by Ron Minnich <rminnich@lanl.gov>
10 and Maya Gokhale <maya@lanl.gov>. Additional development by Greg Watson
11 <gwatson@lanl.gov> and most recently Eric Van Hensbergen
12 <ericvh@gmail.com>, Latchesar Ionkov <lucho@ionkov.net> and Russ Cox
18 For remote file server:
20 mount -t 9p 10.10.1.2 /mnt/9
22 For Plan 9 From User Space applications (http://swtch.com/plan9)
24 mount -t 9p `namespace`/acme /mnt/9 -o proto=unix,uname=$USER
29 proto=name select an alternative transport. Valid options are
31 unix - specifying a named pipe mount point
32 tcp - specifying a normal TCP/IP connection
33 fd - used passed file descriptors for connection
36 uname=name user name to attempt mount as on the remote server. The
37 server may override or ignore this value. Certain user
38 names may require authentication.
40 aname=name aname specifies the file tree to access when the server is
41 offering several exported file systems.
43 debug=n specifies debug level. The debug level is a bitmask.
44 0x01 = display verbose error messages
45 0x02 = developer debug (DEBUG_CURRENT)
46 0x04 = display 9p trace
47 0x08 = display VFS trace
48 0x10 = display Marshalling debug
49 0x20 = display RPC debug
50 0x40 = display transport debug
51 0x80 = display allocation debug
53 rfdno=n the file descriptor for reading with proto=fd
55 wfdno=n the file descriptor for writing with proto=fd
57 maxdata=n the number of bytes to use for 9p packet payload (msize)
59 port=n port to connect to on the remote server
61 noextend force legacy mode (no 9p2000.u semantics)
63 uid attempt to mount as a particular uid
65 gid attempt to mount with a particular gid
67 afid security channel - used by Plan 9 authentication protocols
69 nodevmap do not map special files - represent them as normal files.
70 This can be used to share devices/named pipes/sockets between
71 hosts. This functionality will be expanded in later versions.
76 Our current recommendation is to use Inferno (http://www.vitanuova.com/inferno)
77 as the 9p server. You can start a 9p server under Inferno by issuing the
79 ; styxlisten -A tcp!*!564 export '#U*'
81 The -A specifies an unauthenticated export. The 564 is the port # (you may
82 have to choose a higher port number if running as a normal user). The '#U*'
83 specifies exporting the root of the Linux name space. You may specify a
84 subset of the namespace by extending the path: '#U*'/tmp would just export
85 /tmp. For more information, see the Inferno manual pages covering styxlisten
88 A Linux version of the 9p server is now maintained under the npfs project
89 on sourceforge (http://sourceforge.net/projects/npfs). There is also a
90 more stable single-threaded version of the server (named spfs) available from
91 the same CVS repository.
93 There are user and developer mailing lists available through the v9fs project
94 on sourceforge (http://sourceforge.net/projects/v9fs).
96 News and other information is maintained on SWiK (http://swik.net/v9fs).
98 Bug reports may be issued through the kernel.org bugzilla
99 (http://bugzilla.kernel.org)
101 For more information on the Plan 9 Operating System check out
102 http://plan9.bell-labs.com/plan9
104 For information on Plan 9 from User Space (Plan 9 applications and libraries
105 ported to Linux/BSD/OSX/etc) check out http://swtch.com/plan9
111 The 2.6 kernel support is working on PPC and x86.
113 PLEASE USE THE KERNEL BUGZILLA TO REPORT PROBLEMS. (http://bugzilla.kernel.org)