ramfs(4) [plan9 man page]

RAMFS(4)						     Kernel Interfaces Manual							  RAMFS(4)

NAME

       ramfs  - memory file system

SYNOPSIS

       ramfs [ -i ] [ -s ] -m [ mountpoint ]

DESCRIPTION

       Ramfs  starts  a process that mounts itself (see bind(2)) on mountpoint (default /tmp).	The ramfs process implements a file tree rooted at
       dir, keeping all files in memory.  Initially the file tree is empty.

       The -i flag tells ramfs to use file descriptors 0 and 1 for its communication channel rather than create a pipe.  This makes it possible to
       use  ramfs as a file server on a remote machine: the file descriptors 0 and 1 will be the network channel from ramfs to the client machine.
       The -s flag causes ramfs to post its channel on /srv/ramfs rather than mounting it on mountpoint, enabling multiple clients to  access  its
       files.  However, it does not authenticate its clients and its implementation of groups is simplistic, so it should not be used for precious
       data.

       This program is useful mainly as an example of how to write a user-level file server.  It can also be used to provide high-performance tem-
       porary files.

SOURCE

       /sys/src/cmd/ramfs.c

SEE ALSO

       bind(2)

																	  RAMFS(4)

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)