import – import a name space from a remote system|
import [ options ] system file [ mountpoint ] |
import –m [ options ] system mountpoint
import –B [ options ] mountpoint [ cmd [ args ... ] ]
Import allows an arbitrary file on a remote system to be imported
into the local name space. Usually file is a directory, so the
complete file tree under the directory is made available. |
A process is started on the remote machine, with authority of the user of import, to perform work for the local machine using the exportfs(4) service. The default port used is TCP 17007. If mountpoint is omitted, import uses the name of the remote file as the local mount point.
The options are:
The –m option mounts a file exported by exportfs(4) with its –r or –S options, which skip the part of its protocol that allows the importer to specify the file to export. Instead, the file or name space is selected by exportfs, and import mounts it on mountpoint as guided by the other options.
The –B option runs import in ``backwards'' mode. In this mode,
import runs a p9any authentication (as server) over its file descriptor
0 (expected to be an incoming network connection from exportfs
–B), mounts the connection onto mntpt, and optionally runs cmd
Assume a machine kremvax that has IP interfaces for the company
intranet and the global internet mounted on /net and /net.alt
respectively. Any machine inside the company can get telnet out
to the global internet using:|
bind(1), ssl(3), tls(3), exportfs(4), srv(4), intro(5), aan(8),
listen(8), cs in ndb(8)|
mnt(3) seems to interfere with mounting a srv(3) channel which
is itself mounted via an encrypted import, probably by breaking
up long records, thus requiring `–E clear' in |
SSLv2 and RC4 are deprecated.