os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Make the question I added on TERM mismatches when logging onto remote systems

Browse source 
clearer.
This commit is contained in:
Joseph Koshy 1999-08-24 08:54:28 +00:00
parent a938e63860
commit 613d6c2cc6
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=5441
2 changed files with 48 additions and 26 deletions
en_US.ISO8859-1/books/faq
book.sgml
en_US.ISO_8859-1/books/faq
book.sgml

37
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -10,7 +10,7 @@
</author>
</authorgroup>
<pubdate>$Date: 1999-08-24 05:01:13 $</pubdate>
<pubdate>$Date: 1999-08-24 08:54:28 $</pubdate>
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
@ -2593,36 +2593,47 @@ message.</para>
</answer></qandaentry>
<qandaentry><question>
<para>Full screen applications on remote machines misbehave!
</para></question><answer>
<para>Full screen applications on remote machines misbehave</para></question>
<answer>
<para>The remote machine may be setting your terminal type
to something other than the <emphasis remap=tt>cons25</emphasis> terminal type used
by the FreeBSD console.</para>
to something other than the <emphasis remap=tt>cons25</emphasis> terminal type
required by the FreeBSD console.</para>
<para>There are a number of work-arounds for this problem:
<para>There are a number of possible work-arounds for this problem:
<itemizedlist>
<listitem>
<para>After logging on to the remote machine, set your TERM shell
variable to either <emphasis remap=tt>ansi</emphasis> or <emphasis remap=tt>sco</emphasis>.</para>
variable to <emphasis remap=tt>ansi</emphasis> or
<emphasis remap=tt>sco</emphasis> if the remote machine knows
about these terminal types.</para>
</listitem>
<listitem>
<para>Use a VT100 emulator like <ulink URL="http://www.FreeBSD.org/cgi/ports.cgi?screen-">screen</ulink>
locally. <emphasis remap=tt>screen</emphasis> offers you the ability to run
multiple concurrent sessions from one terminal, and is a neat
program in its own right.</para>
at the FreeBSD console.
<emphasis remap=tt>screen</emphasis> offers you the ability to run multiple
concurrent sessions from one terminal, and is a neat program in its own right.
Each <emphasis remap=tt>screen</emphasis> window behaves like a VT100 terminal,
so the TERM variable at the remote end should be set to <emphasis remap=tt>
vt100</emphasis>.
</para>
</listitem>
<listitem>
<para>Install the <emphasis remap=tt>cons25</emphasis> terminal database entry on
the remote machine.</para>
the remote machine. The way to do this depends on the operating system on the
remote machine. The system administration manuals for the remote system
should be able to help you here.</para>
</listitem>
<listitem>
<para>Fire up X and login to the remote machine from an
<emphasis remap=tt>xterm</emphasis>.</para>
<para>Fire up an X server at the FreeBSD end and login to the remote machine
using an X based terminal emulator such as <emphasis remap=tt>xterm</emphasis> or
<emphasis remap=tt>rxvt</emphasis>. The TERM variable at the remote host
should be set to <emphasis remap=tt>xterm</emphasis> or <emphasis remap=tt>vt100
</emphasis>.</para>
</listitem>
</itemizedlist>

37
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -10,7 +10,7 @@
</author>
</authorgroup>
<pubdate>$Date: 1999-08-24 05:01:13 $</pubdate>
<pubdate>$Date: 1999-08-24 08:54:28 $</pubdate>
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
@ -2593,36 +2593,47 @@ message.</para>
</answer></qandaentry>
<qandaentry><question>
<para>Full screen applications on remote machines misbehave!
</para></question><answer>
<para>Full screen applications on remote machines misbehave</para></question>
<answer>
<para>The remote machine may be setting your terminal type
to something other than the <emphasis remap=tt>cons25</emphasis> terminal type used
by the FreeBSD console.</para>
to something other than the <emphasis remap=tt>cons25</emphasis> terminal type
required by the FreeBSD console.</para>
<para>There are a number of work-arounds for this problem:
<para>There are a number of possible work-arounds for this problem:
<itemizedlist>
<listitem>
<para>After logging on to the remote machine, set your TERM shell
variable to either <emphasis remap=tt>ansi</emphasis> or <emphasis remap=tt>sco</emphasis>.</para>
variable to <emphasis remap=tt>ansi</emphasis> or
<emphasis remap=tt>sco</emphasis> if the remote machine knows
about these terminal types.</para>
</listitem>
<listitem>
<para>Use a VT100 emulator like <ulink URL="http://www.FreeBSD.org/cgi/ports.cgi?screen-">screen</ulink>
locally. <emphasis remap=tt>screen</emphasis> offers you the ability to run
multiple concurrent sessions from one terminal, and is a neat
program in its own right.</para>
at the FreeBSD console.
<emphasis remap=tt>screen</emphasis> offers you the ability to run multiple
concurrent sessions from one terminal, and is a neat program in its own right.
Each <emphasis remap=tt>screen</emphasis> window behaves like a VT100 terminal,
so the TERM variable at the remote end should be set to <emphasis remap=tt>
vt100</emphasis>.
</para>
</listitem>
<listitem>
<para>Install the <emphasis remap=tt>cons25</emphasis> terminal database entry on
the remote machine.</para>
the remote machine. The way to do this depends on the operating system on the
remote machine. The system administration manuals for the remote system
should be able to help you here.</para>
</listitem>
<listitem>
<para>Fire up X and login to the remote machine from an
<emphasis remap=tt>xterm</emphasis>.</para>
<para>Fire up an X server at the FreeBSD end and login to the remote machine
using an X based terminal emulator such as <emphasis remap=tt>xterm</emphasis> or
<emphasis remap=tt>rxvt</emphasis>. The TERM variable at the remote host
should be set to <emphasis remap=tt>xterm</emphasis> or <emphasis remap=tt>vt100
</emphasis>.</para>
</listitem>
</itemizedlist>