v9fs.txt 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. V9FS: 9P2000 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@lanl.gov>
  7. and Maya Gokhale <maya@lanl.gov>. Additional development by Greg Watson
  8. <gwatson@lanl.gov> and most recently Eric Van Hensbergen
  9. <ericvh@gmail.com> and Latchesar Ionkov <lucho@ionkov.net>.
  10. USAGE
  11. =====
  12. For remote file server:
  13. mount -t 9P 10.10.1.2 /mnt/9
  14. For Plan 9 From User Space applications (http://swtch.com/plan9)
  15. mount -t 9P `namespace`/acme /mnt/9 -o proto=unix,name=$USER
  16. OPTIONS
  17. =======
  18. proto=name select an alternative transport. Valid options are
  19. currently:
  20. unix - specifying a named pipe mount point
  21. tcp - specifying a normal TCP/IP connection
  22. fd - used passed file descriptors for connection
  23. (see rfdno and wfdno)
  24. name=name user name to attempt mount as on the remote server. The
  25. server may override or ignore this value. Certain user
  26. names may require authentication.
  27. aname=name aname specifies the file tree to access when the server is
  28. offering several exported file systems.
  29. debug=n specifies debug level. The debug level is a bitmask.
  30. 0x01 = display verbose error messages
  31. 0x02 = developer debug (DEBUG_CURRENT)
  32. 0x04 = display 9P trace
  33. 0x08 = display VFS trace
  34. 0x10 = display Marshalling debug
  35. 0x20 = display RPC debug
  36. 0x40 = display transport debug
  37. 0x80 = display allocation debug
  38. rfdno=n the file descriptor for reading with proto=fd
  39. wfdno=n the file descriptor for writing with proto=fd
  40. maxdata=n the number of bytes to use for 9P packet payload (msize)
  41. port=n port to connect to on the remote server
  42. noextend force legacy mode (no 9P2000.u semantics)
  43. uid attempt to mount as a particular uid
  44. gid attempt to mount with a particular gid
  45. afid security channel - used by Plan 9 authentication protocols
  46. nodevmap do not map special files - represent them as normal files.
  47. This can be used to share devices/named pipes/sockets between
  48. hosts. This functionality will be expanded in later versions.
  49. RESOURCES
  50. =========
  51. The Linux version of the 9P server is now maintained under the npfs project
  52. on sourceforge (http://sourceforge.net/projects/npfs).
  53. There are user and developer mailing lists available through the v9fs project
  54. on sourceforge (http://sourceforge.net/projects/v9fs).
  55. News and other information is maintained on SWiK (http://swik.net/v9fs).
  56. Bug reports may be issued through the kernel.org bugzilla
  57. (http://bugzilla.kernel.org)
  58. For more information on the Plan 9 Operating System check out
  59. http://plan9.bell-labs.com/plan9
  60. For information on Plan 9 from User Space (Plan 9 applications and libraries
  61. ported to Linux/BSD/OSX/etc) check out http://swtch.com/plan9
  62. STATUS
  63. ======
  64. The 2.6 kernel support is working on PPC and x86.
  65. PLEASE USE THE SOURCEFORGE BUG-TRACKER TO REPORT PROBLEMS.