LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-10-17 22:49:21 +00:00
parent 2816b14588
commit c073951092
1 changed files with 187 additions and 167 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

354
LDP/howto/linuxdoc/Text-Terminal-HOWTO.sgml
View File

@ -3,9 +3,10 @@
<title> Text-Terminal-HOWTO </title>
<author> David S. Lawyer <url url="mailto:dave@lafn.org">
<date> v1.14, October 2000
<date> v1.15, October 2000
<!--
Change log:
v1.15 October 2000 Thin Clients; some broken url's changed or deleted
v1.14 October 2000 Suse distribution uses /etc/securetty (didn't
formerly), url of terminfo source, Serial Terminal Linux, pseudo
terminals, ctty (DOS)
@ -75,16 +76,17 @@ name="Quick Install">.
<!-- license.H begin -->
Please freely copy and distribute (sell or give away) this document
in any format. Forward any corrections and comments to the document
in any format. Send any corrections and comments to the document
maintainer. You may create a derivative work and distribute it
provided that you:
<enum>
<item> Send your derivative work (in the most suitable format such as
sgml) to the LDP (Linux Documentation Project) or the like for
posting on the Internet. If not the LDP, then let the LDP know
<item> Send your derivative work to the LDP (Linux Documentation
Project) or the like for free distribution on the Internet in a
format they will accept. If not the LDP, then let the LDP know
where it is available. Except for a translation, send a copy to the
previous maintainer's url as shown in the latest version.
<item>License the derivative work in the spirit of this license or use
GPL. Include a copyright notice and at least a pointer to the
license used.
@ -142,10 +144,9 @@ sites see: <url url="http://linuxdoc.org/mirrors.html">.
Various formats are available. If you only want to quickly check the
date of the latest version look at <url
url="http://linuxdoc.org/HOWTO/Text-Terminal-HOWTO.html">. The
version your are currently reading is: v1.14, October 2000 . New in this version
is: Suse distribution uses /etc/securetty (didn't
formerly), url of terminfo source, Serial Terminal Linux, pseudo
terminals, ctty (DOS).
version your are currently reading is: v1.15, October 2000 . New in this version
is: Thin Clients; some broken url's changed or
deleted.
<sect1> Related HOWTO's <label id="related_howtos">
<p> Go to the websites shown above to get these.
@ -270,79 +271,137 @@ the computer all at once. Block mode (as of late 1998) is not
supported by Linux. See section <ref id="block" name="Block
Mode">.
<sect1> Graphics Terminals
<sect1> Graphic Capabilities of Text Terminals
<p> Many text terminals can display bit-mapped images, but not in
color. Unfortunately, the popular image formats used on the Internet
are not supported. The protocols for such graphics include: Tektronix
Vector Graphics, ReGIS (DEC), Sixel (DEC), and NAPLPS (North American
Presentation Level Protocol Syntax).
<p> To a limited degree some ASCII symbols can provide graphics on
text terminals. One may form arrows <--- and draw boxes with _ and
|. With special graphic character sets, even more is possible. None
of these are really graphics terminals. However, the term "graphics
terminal" is sometimes applied to all text-only terminals since text
is a limited form of graphics. <label id="vector_graphics">
Even without bit-mapped images, ordinary text terminals can sort of
display images. One may form arrows <--- and draw boxes with _ and
|. With special graphic character sets, even more is possible. By
using all the letters, one may produce "ascii graphics" art. The term
"graphics terminal" usually means a terminal that can display bit
mapped images. However, this term is sometimes applied to all
text-only terminals since text is a limited form of graphics. <label
id="vector_graphics">
There are two basic types of graphics displays: raster and vector
<sect1> Thin Clients (Terminals ?)
<p> These are either terminals or thin (minimal) computers. In
contrast to text-terminals, they all display a high-speed GUI. They
are dependent on higher power computers (servers) for their operation.
For a true terminal, the computing work and disk storage will all be
done on the server. At the other extreme, most of this work and
storage is done at the client but some things such as administration,
still depend on the server. Since the client here is not "thin" it's
not clear that this is really a thin client. Some claim that
text-terminals are also thin clients.
<sect2> Graphics Displays
<p> There are two basic types of graphics displays: raster and vector
(rarely used). Raster graphics (bit-mapped) puts dots on the screen
by horizontal scan lines drawn by an electron beam (or by activating
pixels or dots on a flat screen). Vector graphic displays are usually
for monochrome screens that don't have any dots. They use smart
electronics to draw lines and curves with an electron beam that can
move in any direction (at any angle and location). Vector graphics
draws high quality lines without zig-zags but is both rare and
expensive. Raster graphics is almost universally used today. For
PC's, images encoded in vector graphic format are sometimes used but
they are translated to raster graphics format for display (with a drop
in image quality).
pixels or dots on a flat screen). Vector graphic displays were
intended to be used for monochrome screens that don't have any dots.
They use smart electronics to draw lines and curves with an electron
beam that can move in any direction (at any angle and location). True
vector graphics draws high quality lines without zig-zags but is both
rare and expensive. Raster graphics is almost universally used today.
For PC's, images encoded in vector graphic format are sometimes used
but they are translated to raster graphics format for display (with a
drop in image quality).
<sect2> Serial Line Graphics Terminals
<p> Most of this document also applies to these. Most of these can
also function as text terminals. The protocols for such graphics
include: Tektronix Vector Graphics, ReGIS (DEC), Sixel (DEC), and
NAPLPS (North American Presentation Level Protocol Syntax).
<sect2> Full Graphics Terminals (often known by other names)
<p> None of these are covered in this document. A terminal that
deserves to be called smart is a graphics terminal which can rapidly
display full-screen graphics just like a PC monitor. It will also
have a mouse. Bytes sent to it often represent bit-maps for pictures
(and other graphics). It will often use a high-speed connection to
its host computer using twisted pair or coax cable. X-Window
terminals are such devices. See the link to Xterminal-HOWTO at <ref
id="related_howtos" name="Related HOWTO's">. So are some "thin
clients" including ones which have a MS-Windows GUI which comes from a
remote Windows Terminal Server.
<sect2> Fast Graphics Terminals (often known by other names)
<p> None of these covered in this document. A terminal that deserves
to be called smart is a graphics terminal which can rapidly display
full-screen graphics just like a PC monitor. It will also have a
mouse. Bytes sent to it often represent bit-maps for pictures (and
other graphics). It will often use a high-speed connection to its
host computer using twisted pair or coax cable. X-Window terminals
are such devices. See the link to Xterminal-HOWTO at <ref
id="related_howtos" name="Related HOWTO's">
For displaying the MS-Windows GUI, Citrix was (and is) a major player
with what was called Winterm using it's WinFrame software (which
supported Windows 3.1). Microsoft licensed some of this and then came
out with Hydra (code name), also known as "Windows Terminal Server".
It works with versions 4 or higher of MS Windows NT. Then other
companies that had their own proprietary systems decided to support
Microsoft's system.
For displaying a MS-Windows GUI there are at various types of
interfaces and terminals: Winterm using WinFrame software from Citrix
is one. Another (based in part on Citrix's code) is Hydra (code name)
by Microsoft, also known as "Windows Terminal Server" which works with
versions 4 or higher of MS Windows NT. Citrix uses its ICA protocol
and has created an add-on to Hydra known as pICAsso so that WinFrame
(ICA) based terminals can use the Hydra system. Hydra is also
multi-user. There is also the "MultiConsole Personal Terminal" by
Unbounded Technologies and Tektronix had its own multi-user interface
but will now support Hydra. A magazine article in 1997 called Winterm
a "dumb terminal" but it's really pretty smart. Such terminals are
often called "thin clients", but some thin clients are more that just
terminals as they can execute Java code sent to them, etc.
Citrix uses its ICA protocol and has created an add-on to Hydra known
as pICAsso so that WinFrame (ICA) based terminals can use the Hydra
system. There exits a Linux ICA client. Microsoft has substituted
RDP (Remote Desktop Protocol) for ICA. Citrix has replaced WinFrame
with MetaFrame which supports Windows 95 and is used in conjunction
with "Windows NT Terminal Server Edition". There is also the
"MultiConsole Personal Terminal" by Unbounded Technologies. Tektronix
had its own multi-user interface but will now support Hydra.
<sect1> Network Computers (NCs)
<p> These are neither true computers nor terminals but are something
in-between. One type of network computer (NC's) is a computer with a
CPU but no hard Disk. They are full-graphics and connect to a server
computer. They are different from terminals since the programs they
run execute on their own CPU chips. Java code may be sent to them for
execution. IBM calls this a "Network Station". They should work on
IP networks and might work under a server running Linux. Wintel
established a "NetPC" which, unlike the above, is almost a PC
computer. However, it has no removable disks so users can't install
their own software or obtain copies of anything. For using the Sun
JavaStation NC under Linux see the JavaStation-HOWTO released in Apr.
24, 2000.
The above is sometimes called "network computing" since the terminals
and servers connect to each other over a network. Network computers
are something different as described below.
Although the promoters of NCs and related Window-Terminals projected
that they would replace millions of PCs, it hasn't yet happened. A
major reason is that PCs have come down in price in recent years so
that they are often even cheaper than NCs, etc. Thus for terminals,
the Text-Terminal still predominates.
<sect2> Network Computers (NCs)
<p>These are neither true computers nor terminals but are something
in-between. They are also a type of thin client. One type of network
computer (NC's) is a computer with a CPU but no hard Disk. They are
full-graphics and connect to a server computer. They are different
from terminals since the programs they run execute on their own CPU
chips. Java code may be sent to them for execution. IBM calls this a
"Network Station". They should work on IP networks and might work
under a server running Linux. Wintel established a "NetPC" which,
unlike the above, is almost a PC computer. However, it has no
removable disks so users can't install their own software or obtain
copies of anything.
<sect2> Thin Clients Under Linux
<p> Linux provides NFS (Network File System) so that if ordinary
computers (not thin clients) are connected to each other via a
network, then a person on one computer can run programs on another
computer. It works also with X-Windows so that one may see GUI images
generated on another computer. Linux also allows a computer to be
diskless (see Diskless-HOWTO) and boot over a network. Thus using a
diskless computer which runs NFS is just like using a NC (Network
Computer). It's not really a NC but it's emulating a type of NC.
It's also sometimes referred to (incorrectly ?) as a "terminal".
Thus if you have an old PC with an ethernet card (NIC) you may be able
to use it as a NC. Even if it doesn't have a NIC, you could use it as
a text-terminal. See <ref id="term_emulation" name="Terminal
Emulation">. So Linux too supports a type of thin client which is the
subject of Thinclient-HOWTO. For using the Sun JavaStation NC under
Linux see the JavaStation-HOWTO.
<sect2> Hardware hookups
<p> There are 3 different hardware arrangements for thin clients.
One just uses a PC computer as a thin client by emulating a thin
client. It really isn't a thin client but it behaves like one.
Another type looks just like a text-terminal. It just looks like a
monitor, with a connector for a keyboard and another connector for a
network cable. It's a dedicated thin client and can't be used for
anything else. The third type looks like a tiny computer. It uses a
standard PC monitor and keyboard both of which plug into a small box
which is a "thin" computer. This box provides an interface between
the monitor/keyboard and the network.
<sect2> History and the Future
<p> Promoters of NCs and related Window-Terminals projected that they
would soon replace millions of PCs. In 1998 about 700,000 thin
clients were sold with about 27% of them being NCs. But in 1999 only
about 600,000 thin clients were sold. A major reason that more were
not sold is that PCs have come down in price in recent years so that
they are often no more expensive. However, it's argued that even
though thin clients may cost the same as PCs, the maintenance and
administration costs are less. Note that thin clients sometimes
replace text terminals instead of PCs.
<sect1> Emulation on a PC
<p> Since a PC has a screen and keyboard (as does a terminal) but also
has much more computing power, it's easy to use some of this computing
power to make the PC computer behave like a text terminal. This is
@ -495,12 +554,12 @@ same quality of display). This wasn't always the case since around
costs for memory and processors, one could make a text terminal smart
for only about a 10% or 20% increase in hardware cost.
The reasons that text terminals are not yet obsolete are:
The reasons that text terminals are fully obsolete are:
<itemize>
<item> There is no satisfactory standard interface for smart graphics
terminals. The MS Hydra system is for MS Windows NT, while X-Windows
is not as efficient as it should be (and X-Windows terminals are too
costly).
terminals that can be used with Linux (but there is for MS Windows).
However one can run a diskless PC under Linux on a network where the
diskless PC is a substitute for a smart graphics terminal.
<item> Many people don't need full screen graphics.
<item> Text terminals are low in cost and allegedly take longer to
become obsolete, yet can give access to a much newer (and powerful)
@ -1191,8 +1250,7 @@ to help determine if a terminal behaves correctly like a vt53, vt100,
vt102, vt220, vt320, vt420 etc. There is no documentation but it has
menus and is easy to use. To compile it run the configure script and
then type "make". It may be downloaded from: <url
url="ftp://ftp.clark/net:/pub/dickey/vttest/">. An alternate download
site is: <url url="http://sunsite.unc.edu/pub/Linux/utils/console/">
url="http://sunsite.unc.edu/pub/Linux/utils/console/">
<sect1> The Linux Console <label id="console_">
<p> The console for a PC Linux system is normally the computer
@ -1246,18 +1304,19 @@ ADM-1l; WANG 2110. Block mode is available for IBM and Wyse. It runs
on a Linux PC.
<sect2> Make a non-Linux PC a terminal
<p> Emulators exist which run on non-Linux PCs. They permit you to
use a non-Linux-PC as a terminal connected to a Linux-PC. Under DOS
there is <tt/telix/ and <tt/procomm/. Windows comes with
"HyperTerminal" (formerly simply called "Terminal" in Windows 3.x and
DOS). Competing with this is "HyperTerminal Private Edition" <url
url="http://www/hilgraeve.com/htpe/index.html"> which is non-free to
url="http://www.hilgraeve.com/htpe/index.html"> which is non-free to
business. It can emulate vt-220. Turbosoft's (Australia) TTWin <url
url="http://www.turbosoft.com.au/"> can emulate over 80 different
terminals under Windows.
For the Mac Computer there is emulation by Carnation Software <url
url="http://www.webcom.com/carn/carnation/panel-default.html">
url="http://www.carnationsoftware.com/carnation/HT.Carn.Home.html">
One place to check terminal emulation products is Shuford's site, but
it seems to lists old products (which may still work OK). The fact
@ -1547,10 +1606,8 @@ server.
<sect1> Multiport I/O Cards (Adapters)
<p> Additional serial cards may be purchased which have many serial
ports on them called "multiport boards". These boards are not covered
in this HOWTO but there is quite a lot of coverage in the Serial-HOWTO
One company which had (in 1998) below average prices is <url
url="http://www.byterunner.com/cgi-bin/goto.cgi?FILE=iocards.html"
name="ByteRunner">.
in this HOWTO but there is a list of them (with URLs) in the
Serial-HOWTO.
<sect1> Direct Cable Connection.
<p> The simplest way to connect a terminal to a host computer is via a
@ -2440,13 +2497,8 @@ In some older terminals, only the manual tells how to save. For many
of these you press Ctrl-S to save.
<sect1> Set-Up Options/Parameters <label id="set_up_pars">
<p> See the Teemworld's <url
url="http://www.pericom-usa.com/twdocs/doc/twusec7.htm"
name="Set-Up"> for a description of many of these parameter as used in
terminal emulation. Emulation is often a little different than an
actual terminal.
What follows in this section describes some of the options which are
<p> What follows in this section describes some of the options which are
available in the set-up menus of many terminals. Options are also
called parameters or features. Many options may be called "modes".
Setting options is often called "configuring". Many of these options
@ -2879,7 +2931,7 @@ text-terminal.
If you don't have the getty you want check other distributions and the
<tt/alien/ program to convert between RPM and Debian packages. The source
code may be downloaded from <url url=
"http://sunsite.unc.edu/pub/Linux/system/serial/" name="Serial
"http://sunsite.unc.edu/pub/Linux/system/serial/getty" name="Getty
Software">.
If you are not using modem control lines (for example if you only use
@ -2947,10 +2999,11 @@ process will be garbled and parity will be set wrong. Thus it doesn't
seem feasible to try to use 8-bit data bytes with parity.
<sect2> getty (part of getty_ps) <label id="getty_ps">
<p> (This is from the old Serial-HOWTO by Greg Hankins) <newline>
Add entries for <tt/getty/ to use for your terminal in the
configuration file <tt>/etc/gettydefs</tt> if there they aren't
already there:
<p> (Most of this is from the old Serial-HOWTO by Greg Hankins)<newline>
For this getty one needs to both put entries in a configuration file
and add an entry in <tt>/etc/inittab</tt>. Here are some example
entries to use for your terminal that you put into the configuration
file <tt>/etc/gettydefs</tt>.
<tscreen><verb>
# 38400 bps Dumb Terminal entry
@ -2962,7 +3015,9 @@ DT19200# B19200 CS8 CLOCAL # B19200 SANE -ISTRIP CLOCAL #@S @L login: #DT19200
# 9600 bps Dumb Terminal entry
DT9600# B9600 CS8 CLOCAL # B9600 SANE -ISTRIP CLOCAL #@S @L login: #DT9600
</verb></tscreen>
<p>
<p> Note that the DT number you use here must be the same as the DT
number that you use in <tt>/etc/inittab</tt>.
If you want, you can make <tt/getty/ print interesting things in the
login banner. In my examples, I have the system name and the serial
line printed. You can add other things:
@ -2985,12 +3040,12 @@ the syntax is correct by doing:
linux# getty -c /etc/gettydefs
</verb></tscreen>
Make sure there is no <tt/getty/ or <tt/uugetty/ config file for the
serial port that your terminal is attached to
(<tt>/etc/default/{uu}getty.ttyS</tt><em/N/ or
<tt>/etc/conf.{uu}getty.ttyS</tt><em/N/), as this will probably
interfere with running <tt/getty/ on a terminal. Remove the file if
it exits.
Make sure there is no other <tt/getty/ or <tt/uugetty/ config file for
the serial port that your terminal is attached to such as
(<tt>/etc/default/{uu}getty.ttyS</tt><em/N/ or
<tt>/etc/conf.{uu}getty.ttyS</tt><em/N/), as this will probably
interfere with running <tt/getty/ on a terminal. Remove such
conflicting files if they exits.
Edit your <tt>/etc/inittab</tt> file to run <tt/getty/ on the serial
port (substituting in the correct information for your environment -
@ -3873,7 +3928,7 @@ sends the init string and sets TERM to this terminal name (type).
/etc/termcap have info about various versions of termcap files,
naming conventions for terminals, and special capabilities code named
u6-u9. If you don't have one, go to <url
url="http://sagan.earthspace.net/terminfo">
url="http://www.tuxedo.org/terminfo">
<item> "Termcap and Terminfo" is a book published by O'Reilly in
1988.
</itemize>
@ -5201,23 +5256,18 @@ fly up into the air when taking apart a key switch.
name= "Shuford's Website"> at the University of Tennessee has a great
deal of useful information about text terminals.
<item> VT terminal information and history <url url="http://www.vt100.net/">
<item> <url url="http://www.boundless.com/textterm/" name="Boundless">
<item> <url url="http://www.boundless.com/Text_Terminals/" name="Boundless">
purchased the VT and Dorio terminal business from DEC. To get Specs
select either ADDS, VT, or DORIO links. Then select a "data
sheet" link. Then on the data sheet select the "Go to Specs" link.
<item> <url
<item> Wyse is a major manufacturer of terminals. <url
url="http://www.wyse.com/service/support/kbase/wyseterm.asp"
name="Wyse text-terminals kbase"> is a major manufacturer of terminals.
For new models see <url
url="http://www.wyse.com/terminal/" name="Wyse terminal"> See also
<url url="http://www.wyse.com/service/faq/wysetter.htm" name="Old
Wyse terminal Specs">
<item> <url url="http://www.pericom-usa.com/twdocs/doc/twproae.htm"
name="Escape Seqs.; N. America"> or
<url url="http://www.pericom.co.uk/teemworld/doc/twproae.htm"
name="Escape Seqs.; Europe"> is a list of escape sequences (and control
codes) for some terminal emulations (including VT 100, 300, 420, and
Wyse).
name="Wyse text-terminals database"> For current models see <url
url="http://www.wyse.com/products/gpt/index.htm" name="Wyse terminals">.
<item> <url url="http://www.ecc400.com/java/twproae.htm"
name="Teemworld Escape Sequences"> is a list of escape sequences (and
control codes) for some terminal emulations (including VT 100, 300,
420, and Wyse).
<item> comp.terminals is the newsgroup for terminals
</itemize>
@ -5333,15 +5383,13 @@ escape sequences options will not be repeated here.
<sect1> Esc Sequence List <label id="esc_seq_list">
<p> For a list of many (but not all) escape sequences for various
terminals see <url
url="http://www.pericom-usa.com/twdocs/doc/twproae.htm"
name="Escape Seqs.; N. America"> or <url
url="http://www.pericom.co.uk/teemworld/doc/twproae.htm" name="Escape
Seqs.; Europe">. These are used for terminal emulation and are not
always the same as on the corresponding real terminal..
A list for VT (not maintained) may be found at <url
terminals see <url url="http://www.ecc400.com/java/twproae.htm"
name="Teemworld Escape Sequences">. These are used for terminal
emulation and are not always the same as on the corresponding real
terminal. A list for VT (not maintained) may be found at <url
url="http://www.cs.ruu.nl/wais/html/na-dir/emulators-faq/part3.html"
name="Emulators FAQ">. Search for "VT".
name="Emulators FAQ">. Search for "VT". For downloading manuals see
<url url="http://www.vt100.net/" name="VT Manuals">.
<sect1> 8-bit Control Codes
<p> Table of 8-bit DEC control codes (in hexadecimal). Work on VT2xx or
@ -5566,46 +5614,17 @@ located nearby, the need for high speed and longer distance
transmission was apparently not recognized.
<sect2> Successors to EIA-232 <label id="non_232">
<p> A number of EIA standards have been established for higher speeds
and longer distances using twisted-pair (balanced) technology.
Balanced transmission can sometimes be a hundred times faster than
unbalanced EIA-232. For a given speed, the distance (maximum cable
length) may be many times longer with twisted pair. But PC-s keep
being made with the "obsolete" EIA-232 since it works OK with modems
connected to slow telephone lines, and it works OK with mice.
One exception is Apple's Mac computer with its EIA-232/EIA-422 GeoPort
which provides twisted-pairs (balanced) for transmit and receive. It
uses a small round "mini-DIN" connector. It also provides
conventional EIA-232 but only at 5 volts (which is still legal
EIA-232). However, due to the fact that Macs cost more than PC's,
they are seldom used as a host computer for terminals. Some newer
terminals use EIA-423 but this is just like the unbalanced EIA-232 and
can be connected to a EIA-232 port. This EIA-423 is only 5 volts, but
the specs call for higher speeds than the EIA-232 (which will be of no
help on a long run where it's the unbalance that causes interference).
EIA-485 is also balanced and is used as a "bus" like ethernet and USB.
One device connected to it is the "master" and polls the "slaves" for
input. Since many computers may share the twisted pair its sometimes
called "multidrop". Another twisted pair is used for traffic from the
master to the slaves. The output voltage on the pins must be tristate
with the third state being open circuit to permit other units to use
the "bus". It's been claimed that protocols are not standardized for
multidrop and that's bad news. See <url
url="http://www.hw.cz/english/docs/rs485/rs485.html">
EIA-530-A (balanced but can also be used unbalanced) at 2Mbits/s
(balanced) was intended to be a replacement for EIA-232 but few have
been installed. It uses the same 25-pin connector as EIA-232.
The High Speed Serial Interface ( HSSI = EIA-612/613) uses a 50-pin
connector and goes up to about 50 Mbits/s but the distance is limited
to only several meters. The Universal Serial Bus (USB) is being built
into PCI chips. It is 12 Mbits/s over a twisted pair with a 4-pin
connector (2 wires are power supply) but it also is limited to short
distances of at most 5 meters (depends on configuration).
<p> See the Serial-HOWTO section "Other Serial Devices" for a longer
discussion about non-EIA-232 ports. A number of EIA standards have
been established for higher speeds and longer distances using
twisted-pair (balanced) technology. Balanced transmission can
sometimes be a hundred times faster than unbalanced EIA-232. For a
given speed, the distance (maximum cable length) may be many times
longer with twisted pair. Few terminals seem to support them. While
many terminals also support EIA-423 is is almost like EIA-232 but is
only 5 volts and somewhat higher speeds (without using twisted pair).
Twisted pair includes EIA-422, EIA-530-A, HSSI (High Speed Serial
Interface), USB (Universal Serial Bus), and of course ethernet.
<sect2> Line Drivers
<p> For a text terminal, the EIA-232 speeds are fast enough but the
@ -5855,10 +5874,11 @@ Sometimes people erroneously think this is for an ethernet connection.
VT520: Supports full DTR/DSR flow control.
<sect1> Wyse
<p> Wyse has some FAQ's for terminal numbers under 100 (such as WY60).
See <url url="http://www.wyse.com/service/faq/wysetter.htm">
For the specs on more recent terminals see
See <url url="http://www.wyse.com/terminal/">.
<p> For specs on terminals see <url
url="http://www.wyse.com/service/support/kbase/wyseterm.asp">. This
will also lead to some FAQ's for terminal numbers under 100 (such as
WY60). For the specs on more recent terminals see See <url
url="http://www.wyse.com/products/gpt/index.htm" name="Wyse terminals">.
<sect2> Wyse 60
<p> Display adjustments (must remove cover): Brightness VR202, Height