3 cpu \- connection to CPU server
20 .I encryption-hash-algs
41 machine, or the machine named in the
43 environment variable if there is no
47 standard input, output, and error files will be
49 in the name space where the
56 window on a terminal, so
58 output goes to that window, and input comes from the keyboard
59 when that window is current.
62 the working directory of the
66 The name space for the new
68 is an analogue of the name space where the
71 it is the same except for architecture-dependent bindings such as
73 and the use of fast paths to file servers, if available.
79 uses the argument as the remote user id.
83 argument is present, the remainder of the command line is executed by
85 on the server, and then
91 argument is present, the
95 to control how much of the local name space will be exported to
100 command allows the user to specify the authentication mechanism used
101 when connecting to the remote system. The two possibilities for
107 This is the default. Authentication is done using the standard Plan 9
110 No user interaction is required.
113 Authentication is done using challenge/response and a hand held
119 The user must encrypt the challenge and type the encryption
122 This is used if the local host is in a different protection domain than
123 the server or if the user wants to log into the server as a different
129 option specifies an encryption and/or hash algorithm to
130 use for the connection. If both are specified, they must
131 be space separated and comprise a single argument, so they
132 must be quoted if in a shell command. The default is
138 for details on possible algorithms. The argument
140 specifies no encryption algorithm and can be used to talk
141 to older versions of the
147 flag specifies a key pattern to use to restrict the keys
150 call used for authentication.
152 The name space is built by running
153 .B /usr/$user/lib/profile
154 with the root of the invoking name space bound to
158 environment variable is set to
164 environment variables reflect the server's architecture.
170 to run the server (remote) side of the protocol.
171 It is run from service files such as
172 .BR /bin/service/tcp17010 .
175 flag is similar but simulates the pre-9P2000 version
180 The name space of the terminal side of the
182 command is mounted, via
184 on the CPU side on directory
188 are bound to their standard locations from there.
190 .B /sys/src/cmd/cpu.c
196 Binds and mounts done after the terminal
198 is run are not reflected in the new name space.
200 By default, the entire namespace of the local system is
201 exported to the remote system. Use of the
203 option in conjunction with a customized patternfile can
204 limit this exposure, but also limits the usefulness of