tapefs(1) [plan9 man page]

TAPEFS(1)						      General Commands Manual							 TAPEFS(1)

NAME

       32vfs, cpiofs, tapfs, tarfs, tpfs, v6fs, v10fs - mount archival file systems

SYNOPSIS

       fs/32vfs [ -m mountpoint ] [ -p passwd ] [ -g group ] file
       fs/cpiofs
       fs/tapfs
       fs/tarfs
       fs/tpfs
       fs/v6fs
       fs/v10fs

DESCRIPTION

       These commands interpret data from traditional tape or file system formats stored in file, and mount their contents (read-only) into a Plan
       9 file system.  The optional -p and -g flags specify Unix-format password (respectively group) files that  give	the  mapping  between  the
       numeric	user-  and  group-ID numbers on the media and the strings reported by Plan 9 status inquiries.	The -m flag introduces the name at
       which the new file system should be attached; the default is /n/tapefs.

       32vfs interprets raw disk images of 32V systems, which are ca. 1978 research Unix systems for the VAX, and also pre-FFS Berkeley  VAX  sys-
       tems (1KB block size).

       Cpiofs interprets cpio tape images (constructed with cpio's c flag).

       Tarfs interprets tar tape images.

       Tpfs interprets tp tapes from the Fifth through Seventh Edition research Unix systems.

       Tapfs interprets tap tapes from the pre-Fifth Edition era.

       V6fs interprets disk images from the Fifth and Sixth edition research Unix systems (512B block size).

       V10fs interprets disk images from the Tenth Edition research Unix systems (4KB block size).

SOURCE

       These  commands	are  constructed  in a highly stereotyped way using the files fs.c and util.c in /sys/src/cmd/tapefs, which in turn derive
       substantially from ramfs(4).

SEE ALSO

       Section 5 passim, ramfs(4).

																	 TAPEFS(1)

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)