Introduction
Introduction Statistics Contact Development Disclaimer Help
tnew mount unmount doc - plan9port - [fork] Plan 9 from user space
git clone git://src.adamsgaard.dk/plan9port
Log
Files
Refs
README
LICENSE
---
commit 3fd3a9dfc3d78282b5c1dd0fa9481c14c821ec36
parent b898a330110e110a7046393378bb0de97fa7c566
Author: rsc <devnull@localhost>
Date: Sun, 23 Jul 2006 02:59:43 +0000
new mount unmount doc
Diffstat:
A man/man1/mount.1 | 69 ++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+), 0 deletions(-)
---
diff --git a/man/man1/mount.1 b/man/man1/mount.1
t@@ -0,0 +1,69 @@
+.TH MOUNT 1
+.SH NAME
+mount, unmount \- change name space
+.SH SYNOPSIS
+.B mount
+.I servename
+.I mtpt
+.PP
+.B unmount
+.I mtpt
+.SH DESCRIPTION
+.I Mount
+mounts a 9P server's files into the file system.
+.I Servename
+is typically
+either the name of a Unix domain socket
+(see
+.IR namespace (4))
+or the name or IP address of a machine
+serving 9P over TCP port 564.
+.PP
+.I Unmount
+undoes the effects of the
+.I mount
+command.
+.PP
+9P services can be mounted on Unix systems in multiple ways.
+On Linux,
+.I mount
+uses the native 9P kernel module when present.
+Otherwise it tries to use
+.IR 9pfuse (4)
+with the FUSE file system module.
+Using the 9P kernel module requires root access.
+FUSE can often be used by regular users.
+On FreeBSD,
+.I mount
+tries to use FUSE.
+.PP
+Since Unix already has a
+.I mount
+command, the version described in this manual page
+should be invoked as
+.B 9
+.BR mount .
+.SH EXAMPLES
+Mount
+.IR acme (4)
+onto
+.B /mnt/acme :
+.IP
+.EX
+9 mount `namespace`/acme /mnt/acme
+.EE
+.PP
+View your plumbing rules:
+.IP
+.EX
+9 mount `namespace`/plumb /mnt/plumb
+cat /mnt/plumb/rules
+.EE
+.SH SOURCE
+.B \*9/bin/mount
+.br
+.B \*9/bin/unmount
+.SH SEE ALSO
+.IR intro (4),
+.IR intro (9p),
+.IR 9pfuse (4)
You are viewing proxied material from mx1.adamsgaard.dk. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.