9p.txt 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144
  1. v9fs: Plan 9 Resource Sharing for Linux
  2. =======================================
  3. ABOUT
  4. =====
  5. v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol.
  6. This software was originally developed by Ron Minnich <rminnich@sandia.gov>
  7. and Maya Gokhale. Additional development by Greg Watson
  8. <gwatson@lanl.gov> and most recently Eric Van Hensbergen
  9. <ericvh@gmail.com>, Latchesar Ionkov <lucho@ionkov.net> and Russ Cox
  10. <rsc@swtch.com>.
  11. The best detailed explanation of the Linux implementation and applications of
  12. the 9p client is available in the form of a USENIX paper:
  13. http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html
  14. Other applications are described in the following papers:
  15. * XCPU & Clustering
  16. http://www.xcpu.org/xcpu-talk.pdf
  17. * KVMFS: control file system for KVM
  18. http://www.xcpu.org/kvmfs.pdf
  19. * CellFS: A New ProgrammingModel for the Cell BE
  20. http://www.xcpu.org/cellfs-talk.pdf
  21. * PROSE I/O: Using 9p to enable Application Partitions
  22. http://plan9.escet.urjc.es/iwp9/cready/PROSE_iwp9_2006.pdf
  23. USAGE
  24. =====
  25. For remote file server:
  26. mount -t 9p 10.10.1.2 /mnt/9
  27. For Plan 9 From User Space applications (http://swtch.com/plan9)
  28. mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
  29. OPTIONS
  30. =======
  31. trans=name select an alternative transport. Valid options are
  32. currently:
  33. unix - specifying a named pipe mount point
  34. tcp - specifying a normal TCP/IP connection
  35. fd - used passed file descriptors for connection
  36. (see rfdno and wfdno)
  37. virtio - connect to the next virtio channel available
  38. (from lguest or KVM with trans_virtio module)
  39. uname=name user name to attempt mount as on the remote server. The
  40. server may override or ignore this value. Certain user
  41. names may require authentication.
  42. aname=name aname specifies the file tree to access when the server is
  43. offering several exported file systems.
  44. cache=mode specifies a caching policy. By default, no caches are used.
  45. loose = no attempts are made at consistency,
  46. intended for exclusive, read-only mounts
  47. debug=n specifies debug level. The debug level is a bitmask.
  48. 0x01 = display verbose error messages
  49. 0x02 = developer debug (DEBUG_CURRENT)
  50. 0x04 = display 9p trace
  51. 0x08 = display VFS trace
  52. 0x10 = display Marshalling debug
  53. 0x20 = display RPC debug
  54. 0x40 = display transport debug
  55. 0x80 = display allocation debug
  56. rfdno=n the file descriptor for reading with trans=fd
  57. wfdno=n the file descriptor for writing with trans=fd
  58. maxdata=n the number of bytes to use for 9p packet payload (msize)
  59. port=n port to connect to on the remote server
  60. noextend force legacy mode (no 9p2000.u semantics)
  61. dfltuid attempt to mount as a particular uid
  62. dfltgid attempt to mount with a particular gid
  63. afid security channel - used by Plan 9 authentication protocols
  64. nodevmap do not map special files - represent them as normal files.
  65. This can be used to share devices/named pipes/sockets between
  66. hosts. This functionality will be expanded in later versions.
  67. access there are three access modes.
  68. user = if a user tries to access a file on v9fs
  69. filesystem for the first time, v9fs sends an
  70. attach command (Tattach) for that user.
  71. This is the default mode.
  72. <uid> = allows only user with uid=<uid> to access
  73. the files on the mounted filesystem
  74. any = v9fs does single attach and performs all
  75. operations as one user
  76. RESOURCES
  77. =========
  78. Our current recommendation is to use Inferno (http://www.vitanuova.com/inferno)
  79. as the 9p server. You can start a 9p server under Inferno by issuing the
  80. following command:
  81. ; styxlisten -A tcp!*!564 export '#U*'
  82. The -A specifies an unauthenticated export. The 564 is the port # (you may
  83. have to choose a higher port number if running as a normal user). The '#U*'
  84. specifies exporting the root of the Linux name space. You may specify a
  85. subset of the namespace by extending the path: '#U*'/tmp would just export
  86. /tmp. For more information, see the Inferno manual pages covering styxlisten
  87. and export.
  88. A Linux version of the 9p server is now maintained under the npfs project
  89. on sourceforge (http://sourceforge.net/projects/npfs). The currently
  90. maintained version is the single-threaded version of the server (named spfs)
  91. available from the same CVS repository.
  92. There are user and developer mailing lists available through the v9fs project
  93. on sourceforge (http://sourceforge.net/projects/v9fs).
  94. News and other information is maintained on SWiK (http://swik.net/v9fs).
  95. Bug reports may be issued through the kernel.org bugzilla
  96. (http://bugzilla.kernel.org)
  97. For more information on the Plan 9 Operating System check out
  98. http://plan9.bell-labs.com/plan9
  99. For information on Plan 9 from User Space (Plan 9 applications and libraries
  100. ported to Linux/BSD/OSX/etc) check out http://swtch.com/plan9
  101. STATUS
  102. ======
  103. The 2.6 kernel support is working on PPC and x86.
  104. PLEASE USE THE KERNEL BUGZILLA TO REPORT PROBLEMS. (http://bugzilla.kernel.org)