path: root/9mount.1
diff options
authorAndrej Shadura <>2018-09-05 10:33:52 +0200
committerAndrej Shadura <>2018-09-05 10:33:52 +0200
commit7b7a89d37947b4cf893d0d3b23fcd4f3f10b96d9 (patch)
tree2c2256be230ceb18116c6dc041c80ecbc0d4def5 /9mount.1
Import Upstream version 1.3
Diffstat (limited to '9mount.1')
1 files changed, 115 insertions, 0 deletions
diff --git a/9mount.1 b/9mount.1
new file mode 100644
index 0000000..a4884b0
--- /dev/null
+++ b/9mount.1
@@ -0,0 +1,115 @@
+.TH "9mount" "1" "04 September 2007" "9mount" "User commands"
+9mount, 9bind, 9umount \- mount/unmount 9p filesystems
+.B 9mount
+[ insuvx ] [ -a SPEC ] [ -c CACHE ] [ -d DEBUG ] [ -m MSIZE ] DIAL MOUNTPT
+.B 9bind
+.B 9umount
+.B 9mount
+mounts a 9p filesystem served at DIAL on MOUNTPT. MOUNTPT must be
+writable by you and not sticky. DIAL is a dial string assuming one of
+the forms:
+where SOCKET is the name of a file representing a socket, HOST is a
+hostname, PORT is a port number or service name, and CHANNEL is a
+virtio channel name (currently ignored). - indicates that 9p messages
+should be read/written on stdin/stdout.
+.B 9mount
+has several options:
+mount the file system with your uid/gid
+dry-run, print mount command to stderr but don't actually mount anything
+single attach mode - all users accessing the mount point see the same
+filesystem (by default they'll each see a unique attach)
+use the 9P2000.u extensions
+use device mapping
+exclusive access - other users cannot access the mount point
+-a SPEC
+SPEC determines which file tree to mount when attaching to file servers that
+export multiple trees
+turns on caching using CACHE mode. Currently only
+.I loose
+cache mode is available, which is suitable for exclusive read-only mounts.
+comma seperated list of channels for which to enable debug output. Possible
+channels include: err, devel, 9p, vfs, conv, mux, trans, alloc, fcall.
+specifies the maximum length of a single 9p message in bytes.
+.B 9bind
+performs a bind mount, making the tree visible at directory OLD also visible
+at mount point NEW.
+.B 9umount
+unmounts a 9p filesystem previously mounted by you.
+the uname to provide to the server.
+9mount -i 'unix!/tmp/ns.'$USER'.:0/factotum' $HOME/n/factotum
+mount p9p's factotum interface
+9mount 'tcp!' $HOME/n/sources
+import plan 9's "sources"
+9mount -u -a/home/sqweek/mail 'tcp!wren!5640' $HOME/mail
+import my maildir from my server(wren), being served by ufs
+9mount -i 'tcp!wren' $HOME/n/wren; 9bind $HOME/n/wren/home/sqweek/mail $HOME/mail
+again importing my maildir, this time serving via u9fs
+.B 9mount
+truncates user names and SPECs to 249 characters.
+.B 9umount
+doesn't know this, so you won't be able to unmount anything
+outside your home directory. But you probably never bother
+logging out if your user name is that long.
+.B 9mount
+doesn't update /etc/mtab.
+.B 9bind
+only does a "shallow", non-recursive bind - any mounted filesystems
+under the OLD tree will not appear mounted in the NEW tree.
+If you
+.B 9bind
+a non-9p filesystem outside your home directory,
+.B 9umount
+won't let you unmount it.
+.BR mount (1)