glenda.party
term% ls -F
term% cat index.txt
CPU(1)                      General Commands Manual                     CPU(1)



NAME
       cpu - connection to cpu server

SYNOPSIS
       cpu [ -h server ] [ -c cmd args ...  ]

DESCRIPTION
       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  stan‐
       dard 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  8½(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.

       The  name  space  for the new rc is an analogue of the name space where
       the cpu command was invoked: it is the same except for architecture-de‐
       pendent  bindings  such  as  /bin  and  the  use  of fast paths to file
       servers, if available.

       If a -c argument is present, the remainder of the command line is  exe‐
       cuted by rc on the server, and then cpu exits.

       The name space is built by running /usr/$user/lib/profile with the root
       of the invoking name space bound to /mnt/term.  The service environment
       variable  is  set to cpu; the cputype and objtype environment variables
       reflect the server's architecture.

FILES
       The name space of the terminal side of the cpu command  is  mounted  on
       the CPU side on directory /mnt/term.

SOURCE
       /sys/src/cmd/cpu.c

SEE ALSO
       rc(1), 8½(1)

BUGS
       Binds and mounts done after the terminal lib/profile is run are not re‐
       flected in the new name space.



                                                                        CPU(1)