Sophie

Sophie

distrib > Mandriva > 2010.1 > x86_64 > by-pkgid > 965e33040dd61030a94f0eb89877aee8 > files > 6167

howto-html-en-20080722-2mdv2010.1.noarch.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
 <TITLE> Text-Terminal-HOWTO: Introduction </TITLE>
 <LINK HREF="Text-Terminal-HOWTO-2.html" REL=next>

 <LINK HREF="Text-Terminal-HOWTO.html#toc1" REL=contents>
</HEAD>
<BODY>
<A HREF="Text-Terminal-HOWTO-2.html">Next</A>
Previous
<A HREF="Text-Terminal-HOWTO.html#toc1">Contents</A>
<HR>
<H2><A NAME="intro"></A> <A NAME="s1">1.</A> <A HREF="Text-Terminal-HOWTO.html#toc1">Introduction </A></H2>

<P> For a quick attempt to install a terminal see 
<A HREF="Text-Terminal-HOWTO-4.html#quick_install">Quick Install</A>.</P>

<H2><A NAME="ss1.1">1.1</A> <A HREF="Text-Terminal-HOWTO.html#toc1.1">Copyright, Trademarks, Disclaimer, &amp; Credits</A>
</H2>

<H3>Copyright</H3>

<P> Copyright 1998-2007 by David S. Lawyer.
<A HREF="mailto:dave@lafn.org">mailto:dave@lafn.org</A></P>
<P>Please freely copy and distribute (sell or give away) this 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:</P>
<P>
<OL>
<LI> If it's not a translation: Email a copy of your derivative work
(in a format LDP accepts) to the author(s) and maintainer (could be
the same person).  If you don't get a response then email the LDP
(Linux Documentation Project): submit@en.tldp.org.</LI>
<LI>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.</LI>
<LI>Give due credit to previous authors and major contributors.</LI>
</OL>
</P>
<P>If you're considering making a derived work other than a
translation, it's requested that you discuss your plans with the
current maintainer.</P>

<H3>Disclaimer</H3>

<P> While I haven't intentionally tried to mislead you, there are
likely a number of errors in this document.  Please let me know about
them.  Since this is free documentation, it should be obvious that I
cannot be held legally responsible for any errors.</P>

<H3>Trademarks.</H3>

<P> Any brand names (starts with a capital letter such as MS Windows)
should be assumed to be a trademark).  Such trademarks belong to their
respective owners. </P>


<H3>Credits</H3>

<P> 
Greg Hankin's  Serial-HOWTO v.1.11 (1997) section "How Do I Set Up A
Terminal Connected To My PC?" was incorporated into v1.00 at various
places (with Greg's permission).  v1.09 has about 25 changes (and
error corrections) suggested by Alessandro Rubini who reviewed this
terminal as a console for a monitorless PC (using ttysnoop).  
(v1.26) I fixed about 25 typos, etc. found by Alain Cochard.  Jeremy
Spykerman told me about using a keyboardless terminal as a console
for a monitorless PC (using ttysnoop).  Numerous other people have
made a suggestion or two or found a few typos.  Thanks.</P>

<H2><A NAME="ss1.2">1.2</A> <A HREF="Text-Terminal-HOWTO.html#toc1.2">Future Plans: You Can Help</A>
</H2>

<P> Please let me know of any errors in facts, opinions, logic,
spelling, grammar, clarity, links, etc.  But first, if the date is
over a few months old, check to see that you have the latest version.
Please send me any info that you think belongs in this document.</P>
<P>In order to fully utilize all the features of a certain real terminal,
one needs the terminal manuals that came with the terminal when it was
new.  If you don't have a manual, this HOWTO may be of some help.  One
way to solve this problem would be for terminal manufacturers put
their manuals on the Internet.  </P>

<H2><A NAME="ss1.3">1.3</A> <A HREF="Text-Terminal-HOWTO.html#toc1.3">New Versions of this HOWTO</A>
</H2>

<P> New versions of the Text-Terminal-HOWTO should be released every
year or so.  To get the latest version go to an LDP mirror sites (see:
<A HREF="http://www.tldp.org/mirrors.html">http://www.tldp.org/mirrors.html</A>).   To quickly check the date
of the latest version look at 
<A HREF="http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Text-Terminal-HOWTO.html">Text-Terminal-HOWTO.html</A>.  The version your are currently
reading is: v1.41 February 2008 .  </P>
<P>For a full revision history going back to the first version in
1998 see the source file (in linuxdoc format):
<A HREF="http://cvs.tldp.org/go.to/LDP/LDP/howto/linuxdoc/Text-Terminal-HOWTO.sgml?view=markup">(cvs) Text-Terminal-HOWTO.sgml</A></P>
<P>
<UL>
<LI>v1.41 Feb. 2008" Better clarity re emulation.  Illusion when
revere-video is reversed.  Problem with slow scrolling.  Wyse text
terminals discontinued and Boundless was bankrupt.  Update on text web
browsers.  gtkterm, X Window now has many terminal emulators. 
Symantec no longer selling Procomm.</LI>
<LI>v1.40 Dec. 2006 Picocom is like minicom.  Devfs obsolete so removed
tts/1, etc.  Updated pseudo terminals.  More about telnet, ssh, and
non-serial port interfaces.  IBM terminal emulation over telnet.
Kermit for MS does terminal emulation.  Ports of minicom to Mac.
Fixed/removed broken links.  "reset" is an alias for "tset"</LI>
<LI>v1.39 Aug. 2006 Typo your -> you're; Termcap Manual = Termcap
Library; Fixed several broken links.  Found link to mapchan program.</LI>
</UL>
</P>

<H2><A NAME="related_howtos"></A> <A NAME="ss1.4">1.4</A> <A HREF="Text-Terminal-HOWTO.html#toc1.4">Related HOWTOs, etc. </A>
</H2>

<P> Go to the nearest mirror site (per above) to get HOWTOs.
<UL>
<LI> Serial-HOWTO has info on Multiport Serial Cards used for both
terminals and banks of modems.  It has general technical info on the
serial port including troubleshooting it.</LI>
<LI> 
<A HREF="www.gnu.org/manual/glibc/html_chapter/libc_12.html">Low-Level Terminal Interface</A> part of "GNU C Library Reference
Manual" (in libc (or glibc) docs package).  It covers the detailed
meaning of "stty" commands, etc.</LI>
<LI> NCURSES-Programming-HOWTO</LI>
<LI> MacTerminal mini-HOWTO</LI>
<LI> Modem-HOWTO</LI>
<LI> Serial-Programming-HOWTO</LI>
<LI> NC mini-HOWTO</LI>
<LI> NCD-X-Terminal mini-HOWTO</LI>
<LI> XDM-and-X-Terminal mini-HOWTO</LI>
<LI> Connecting-X-Terminals-to-Linux-Mini-HOWTO</LI>
<LI> NCD-HOWTO</LI>
<LI> Thinclient-HOWTO</LI>
<LI> Xterminals-HOWTO </LI>
<LI> Xterm-Title-HOWTO (only for changing the title of a window)</LI>
</UL>
</P>

<H2><A NAME="ss1.5">1.5</A> <A HREF="Text-Terminal-HOWTO.html#toc1.5">Terminology Used in this Document</A>
</H2>

<P> Configuration means the same as set-up.  While Linux commands take
options (using - or -- symbols), options in a broader sense include
various other types of choices.  Install in the broad sense includes
setting up (configuring) software and hardware.  A statement that I
suspect is true (but may not be) ends with 2 question marks: ??  If
you know for sure, let me know.</P>

<H2><A NAME="ss1.6">1.6</A> <A HREF="Text-Terminal-HOWTO.html#toc1.6">What is a Terminal ?</A>
</H2>

<P> A terminal consists of a screen and keyboard that one uses to
communicate remotely with a (host) computer.  One uses it almost like
it was a personal computer but the terminal is remote from its host
computer (on the other side of the room or even on the other side of
the world).  Programs execute on the host computer but the results
display on the terminal screen.  The terminal's computational ability
is relatively low compared to the host computer but often the terminal
is just a personal computer (PC) itself which has been programmed to
behave like a terminal.  It often doesn't allow the user full
access to either the pc it runs on nor the host it is connected to.
you formerly found this type of terminal at libraries and schools.
But some terminals permitted the user to log into the host computer and
provide access dependent on the user's status.</P>

<H2><A NAME="ss1.7">1.7</A> <A HREF="Text-Terminal-HOWTO.html#toc1.7">What is a Text-Terminal ?</A>
</H2>

<P>A text-terminal is a terminal which only displays text on the
screen without pictures.  Today, it's mostly done by PCs which emulate
the terminals of olden days.</P>

<H3>Real text terminals</H3>

<P> In the olden days of mainframes, from the mid 1970's to the mid
1980's, most people used real text-terminals to communicate with large
computers.  These real text-terminals were neither computers nor
emulated text-terminals.  They consisted only of a screen, keyboard,
and only enough memory to store a screenfull or so of text (a few
kilobytes).  Users typed in programs, ran programs, wrote documents,
issued printing commands, etc.  A cable connected the terminal to the
computer (often indirectly).  It was called a terminal since it was
located at the terminal end of this cable.  Some text-terminals were
called "graphic" but the resolution was poor and the speed slow by
today's standards due to the high cost of memory and the limited speed
of the conventional serial port, etc.</P>
<P>Today, real terminals are becoming rarities and most people that use
terminals use a personal computer to emulate a terminal.  Almost
everyone who uses Linux uses terminal emulation.  When you are not
using an X Window GUI at a Linux PC, you are likely using a text
interface (virtual terminal).  It's also called a command line
interface.  In X Window one can also get a command line interface
using one or more terminal windows by using an x-terminal-emulator
with names such as xterm, gnome-terminal, or konsole (KDE).  All these
use software to emulate a real terminal.</P>
<P>A real text-terminal is different from a monitor or
x-terminal-emulator because the simple character images that get
displayed on the text-terminal are stored right inside the terminal in
it's memory.  For a monitor or x-terminal-emulator, the images  are
stored in the video card of the PC and/or in the PC's memory itself.
The text-terminal's keyboard plugs into the the terminal and is part
of the terminal while a PC's keyboard plugs into the computer.</P>
<P>For a monitor, the video images are sent by a short cable running from
the video card to the monitor while for a text-terminal there is a
bi-directional flow of character bytes in a long cable between the
computer's serial port and the PC it's connected to.  Most text
terminals do not have mice.</P>
<P>In network client-server terminology, one might think that a real
terminal is the client and that the host computer is the server.  The
terminal has been called a "thin client" by some.  But it is not
actually a "client" nor is the host a "server".  The only "service"
the host provides is to receive every letter typed at the keyboard and
react to this just like a computer would if you typed at its keyboard.
The terminal is like a window into the computer just like a monitor
(and keyboard) are.  You may have already used virtual terminals in
Linux (by pressing Left Alt-F2, etc.).  A real terminal is just like
running such a virtual terminal but you run it on its own terminal
screen instead of having to share the monitor screen.  In contrast to
using a virtual terminal at the console (monitor), this allows another
person to sit at a terminal and use the same computer simultaneously
with others.  Such user interfaces are not "clients".</P>

<HR>
<A HREF="Text-Terminal-HOWTO-2.html">Next</A>
Previous
<A HREF="Text-Terminal-HOWTO.html#toc1">Contents</A>
</BODY>
</HTML>