cpu(1) [plan9 man page]

CPU(1)							      General Commands Manual							    CPU(1)

NAME

       cpu - connection to cpu server

SYNOPSIS

       cpu [ -h server ] [ -c cmd args ...  ]

DESCRIPTION

       Cpu  starts  an	rc(1) running on the server machine, or the machine named in the $cpu environment variable if there is no -h option.  Rc's
       standard input, output, and error files will be /dev/cons in the name space where the cpu command was invoked.  Normally, cpu is run in	an
       81/2(1)	window	on a terminal, so rc output goes to that window, and input comes from the keyboard when that window is current.  Rc's cur-
       rent directory is the working directory of the cpu command itself.

       The name space for the new rc is an analogue of the name space where the cpu command was invoked: it is the same except	for  architecture-
       dependent bindings such as /bin and the use of fast paths to file servers, if available.

       If a -c argument is present, the remainder of the command line is executed by rc on the server, and then cpu exits.

       The  name  space is built by running /usr/$user/lib/profile with the root of the invoking name space bound to /mnt/term.  The service envi-
       ronment variable is set to cpu; the cputype and objtype environment variables reflect the server's architecture.

FILES

       The name space of the terminal side of the cpu command is mounted on the CPU side on directory /mnt/term.

SOURCE

       /sys/src/cmd/cpu.c

SEE ALSO

       rc(1), 81/2(1)

BUGS

       Binds and mounts done after the terminal lib/profile is run are not reflected in the new name space.

																	    CPU(1)

EXPORTFS(4)						     Kernel Interfaces Manual						       EXPORTFS(4)

NAME

       exportfs, srvfs - network file server plumbing

SYNOPSIS

       exportfs [ -an ] [ -c ctlfile ]

       srvfs name dir

DESCRIPTION

       Exportfs  is  a	user  level  file  server that allows Plan 9 compute servers, rather than file servers, to export portions of a name space
       across networks.  The service is started either by the cpu(1) command or by a network listener process.	An initial protocol establishes  a
       root  directory	for the exported name space.  The connection to exportfs is then mounted, typically on /mnt/term.  Exportfs then acts as a
       relay file server: operations in the imported file tree are executed on the remote server and the results returned.  This gives the appear-
       ance of exporting a name space from a remote machine into a local file tree.

       The -a option instructs exportfs to authenticate the user, usually because it is being invoked from a remote machine.

       The -n option disallows export to user none.

       The  -c options specifies a network control file onto which exportfs will push the fcall line discipline.  This option is intended for net-
       works that do not preserve read/write boundaries.

       The cpu command uses exportfs to serve device files in the terminal.  The import(4) command calls exportfs on a remote machine,	permitting
       users to access arbitrary pieces of name space on other systems.

       Srvfs  uses  exportfs to create a mountable file system from a name space: a subsequent mount (see bind(1)) of /srv/name will reproduce the
       name space rooted at dir.  One might use srvfs to enable mounting of an FTP file system (see ftpfs(4)) in several windows.

SOURCE

       /sys/src/cmd/exportfs
       /sys/src/cmd/srvfs.c

																       EXPORTFS(4)