faq: mail-loopback
- update full-screeen terminal question answer to be accurate now that we use xterm and not cons25 Submitted by: Daniel O'Connor Mangled by: me
This commit is contained in:
parent
90500489bd
commit
772d34db7c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46427
1 changed files with 18 additions and 43 deletions
|
@ -2090,52 +2090,27 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>The remote machine may be setting the terminal type
|
||||
to something other than the <literal>cons25</literal>
|
||||
terminal type required by the &os; console.</para>
|
||||
<para>The remote machine may be setting the terminal type to
|
||||
something other than <literal>xterm</literal> which is
|
||||
required by the &os; console. Alternatively the kernel
|
||||
may have the wrong values for the width and height of the
|
||||
terminal.</para>
|
||||
|
||||
<para>There are a number of possible work-arounds for this
|
||||
problem:</para>
|
||||
<para>Check the value of the <envar>TERM</envar>
|
||||
enviroment variable is <literal>xterm</literal>. If the
|
||||
remote machine does not support that try
|
||||
<literal>vt100</literal>.</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>After logging on to the remote machine, set the
|
||||
<envar>TERM</envar> shell variable to
|
||||
<literal>ansi</literal> or <literal>sco</literal> if
|
||||
the remote machine knows about these terminal
|
||||
types.</para>
|
||||
</listitem>
|
||||
<para>Run <command>stty -a</command> to check what the
|
||||
kernel thinks the terminal dimensions are. If they are
|
||||
incorrect, they can be changed by running
|
||||
<command>stty rows <replaceable>RR</replaceable> cols
|
||||
<replaceable>CC</replaceable></command>.</para>
|
||||
|
||||
<listitem>
|
||||
<para>Use a VT100 emulator like
|
||||
<application>screen</application> at the &os; console.
|
||||
<application>screen</application> provides the
|
||||
ability to run multiple concurrent sessions from one
|
||||
terminal.
|
||||
Each <application>screen</application> window behaves
|
||||
like a VT100 terminal, so the <envar>TERM</envar>
|
||||
variable at the remote end should be set to
|
||||
<literal>vt100</literal>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Install the <literal>cons25</literal> terminal
|
||||
database entry on the remote machine. The way to do
|
||||
this depends on the operating system on the remote
|
||||
machine. Refer to the system administration manuals for the
|
||||
remote system.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Fire up an X server at the &os; end and login to
|
||||
the remote machine using an X based terminal emulator
|
||||
such as <command>xterm</command> or
|
||||
<command>rxvt</command>. The <envar>TERM</envar>
|
||||
variable at the remote host should be set to
|
||||
<literal>xterm</literal> or
|
||||
<literal>vt100</literal>.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>Alternatively, if the client machine has
|
||||
<package>x11/xterm</package> installed, then running
|
||||
<command>resize</command> will query the terminal for the
|
||||
correct dimensions and set them.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
Loading…
Reference in a new issue