drawterm - connect to Plan 9 CPU servers from other operating systems
] [-a authserver
] [-e encription_hash_algs
] [-s secstoreserver
] [-u username
[-C command args ...
is not a Plan 9 program. It is a program that users of non-Plan
9 systems can use to establish graphical cpu
(1) connections with Plan 9
CPU servers. Just as a real Plan 9 terminal does, a drawterm
local name space as well as some devices (the keyboard, mouse, and screen) to
a remote CPU server, which mounts this name space on /mnt/term
starts a shell. Typically, either explicitly or via the profile, one uses the
shell to start rio
By default, drawterm uses the CPU server $cpu
, and the
authentication server $auth
This program follows the syntax of the cpu(1) Plan 9 command.
A summary of options is included below.
- Show summary of options.
- Specifies the authentication server to use. If not present
uses the $auth environment variable, if present, or tries with a
host name of auth.
- Specifies the cpu server to use. If not present uses the
$cpu environment variable, if present, or tries with a host name of
- Specifies the username to authenticate with. If not present
uses the $USER environment variable, if present, or asks
interactively for an username.
- Specifies the secstore server to use.
- Specifies a command to be executed remotely.
- Allow for selecting the hash algorithm and keys used, they
have the same meaning as in cpu(1).
In Plan 9 distributions, /sys/src/cmd/unix/drawterm
Drawterm prints most diagnostics in its own window.
Although at first drawterm
may seem like a Plan 9 terminal, in fact it is
just a way to provide a CPU server with some terminal devices. The difference
is important because one cannot run terminal-resident programs when using
. The illusion can be improved by delicate adjustments in
Should import latest /dev/draw to allow resize of window
Should copy 9term code and make console window a real 9term window instead.
Should implement /dev/label.
(1) in the Plan 9 documentation
drawterm was written by Russ Cox <email@example.com>.
This manual page was written by Russ Cox <firstname.lastname@example.org>, with
modifications by Martín Ferrari <email@example.com> for the