Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bind(1) [plan9 man page]

BIND(1) 						      General Commands Manual							   BIND(1)

NAME
bind, mount, unmount - change name space SYNOPSIS
bind [ option ... ] new old mount [ option ... ] servename old [ spec ] unmount [ new ] old DESCRIPTION
Bind and mount modify the file name space of the current process and other processes in the same name space group (see fork(2)). For both calls, old is the name of an existing file or directory in the current name space where the modification is to be made. For bind, new is the name of another (or possibly the same) existing file or directory in the current name space. After a successful bind, the file name old is an alias for the object originally named by new; if the modification doesn't hide it, new will also still refer to its original file. The evaluation of new (see intro(2)) happens at the time of the bind, not when the binding is later used. The servename argument to mount is the name of a file that, when opened, yields an existing connection to a file server. Almost always, servename will be a file in /srv (see srv(3)). In the discussion below, new refers to the file named by the new argument to bind or the root directory of the service available in servename after a mount. Either both old and new files must be directories, or both must not be directories. Options control aspects of the modification to the name space: (none) Replace the old file by the new one. Henceforth, an evaluation of old will be translated to the new file. If they are directo- ries (for mount, this condition is true by definition), old becomes a union directory consisting of one directory (the new file). -b Both files must be directories. Add the new directory to the beginning of the union directory represented by the old file. -a Both files must be directories. Add the new directory to the end of the union directory represented by the old file. -c This can be used in addition to any of the above to permit creation in a union directory. When a new file is created in a union directory, it is placed in the first element of the union that permits creation. The spec argument to mount is passed in the attach(5) message to the server, and selects among different file trees served by the server. The srv(3) service registry device, normally bound to /srv, is a convenient rendezvous point for services that can be mounted. After boot- strap, the file /srv/boot contains the communications port to the file system from which the system was loaded. The effects of bind and mount can be undone with the unmount command. If two arguments are given to unmount, the effect is to undo a bind or mount with the same arguments. If only one argument is given, everything bound to or mounted upon old is unmounted. EXAMPLES
To compile a program with the C library from July 16, 1992: mount /srv/boot /n/dump dump bind /n/dump/1992/0716/mips/lib/libc.a /mips/lib/libc.a mk SOURCE
/sys/src/cmd/bind.c /sys/src/cmd/mount.c /sys/src/cmd/unmount.c SEE ALSO
bind(2), open(2), srv(3), srv(4) BIND(1)

Check Out this Related Man Page

U9FS(4) 						     Kernel Interfaces Manual							   U9FS(4)

NAME
u9fs - serve 9P from Unix SYNOPSIS
u9fs [ directory ] DESCRIPTION
U9fs is not a Plan 9 program. Instead it is a program that serves Unix files to Plan 9 machines using the 9P protocol (see intro(5)). It is to be invoked on a Unix machine by inetd with its standard input, output, and error connected to a network connection, typically TCP on an Ethernet. It runs as user root and multiplexes access to multiple Plan 9 clients over the single wire. It simulates Unix permissions itself by assuming Plan 9 uids match Unix login names. If a directory is specified u9fs first does a Unix chroot system call to that directory. Plan 9 calls this service 9fs with TCP service number 564 on the Ethernet. Set up this way on a machine called, say, kremvax, u9fs may be connected to the name space of a Plan 9 process by 9fs kremvax Due to a bug in some versions of the IP software, some systems will not accept the service name 9fs, thinking it a service number because of the initial digit. If so, run the service as u9fs or 564 and do the srv and mount by hand: srv tcp!kremvax!u9fs mount -c /srv/tcp!kremvax!u9fs /n/kremvax For more information on this procedure, see srv(4) and bind(1). U9fs serves the entire file system of the Unix machine. It forbids access to devices because the program is single-threaded and may block unpredictably. Using the attach specifier device connects to a file system identical to the usual system except it permits device access (and may block unpredictably): srv tcp!kremvax!9fs mount -c /srv/tcp!kremvax!9fs /n/kremvax device (The 9fs command does not accept an attach specifier.) Even so, device access may produce unpredictable results if the block size of the device is greater than 8192, the maximum data size of a 9P message. The source to u9fs is in the Plan 9 directory /sys/src/cmd/unix/u9fs. To install u9fs on a Unix system, copy the source to a directory on that system. Edit the makefile to set LOG to a proper place for a log file and to set the compile-time configuration correctly. Then com- pile with an ANSI C compiler and install in /usr/etc/u9fs. Install this line in inetd.conf: 9fs stream tcp nowait root /usr/etc/u9fs u9fs and this in services: 9fs 564/tcp 9fs # Plan 9 fs SOURCE
/sys/src/cmd/unix/u9fs DIAGNOSTICS
Problems are reported to /tmp/u9fs.log. A compile-time flag enables chatty debugging. SEE ALSO
bind(1), srv(4), ip(3), nfsserver(8) BUGS
The implementation of devices is unsatisfactory. U9FS(4)
Man Page