cpu – connection to CPU server|
cpu [ –h server ] [ –u user ] [ –a auth–method ] [ –P patternfile ]
[ –e encryption–hash–algs ] [ –k keypattern ] [ –c cmd args ... ]
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 rio(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 current directory is the working
directory of the cpu command itself.
p9 This is the default. Authentication is done using the standard Plan 9 mechanisms, (see authsrv(6)). No user interaction is required.
netkey Authentication is done using challenge/response and a hand held authenticator or the netkey program (see passwd(1)). The user must encrypt the challenge and type the encryption back to cpu. This is used if the local host is in a different protection domain than the server or if the user wants to log into the
The name space of the terminal side of the cpu command is mounted,
via exportfs(4), on the CPU side on directory /mnt/term. The files
such as /dev/cons are bound to their standard locations from there.|
rc(1), rio(1), exportfs(4)|
Binds and mounts done after the terminal lib/profile is run are
not reflected in the new name space.