Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Traveller''s Lunchbox

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 110 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       The  environment variable TERM should normally contain the
       type name of the terminal, console or display-device  type
       you  are  using.   This  information  is  critical for all
       screen-oriented  programs,  including  your   editor   and

       A  default  TERM  value will be set on a per-line basis by
       either /etc/inittab (Linux and  System-V-like  UNIXes)  or
       /etc/ttys  (BSD  UNIXes).  This will nearly always suffice
       for workstation and microcomputer consoles.

       If you use a dialup line, the type of device  attached  to
       it  may vary.  Older UNIX systems pre-set a very dumb ter­
       minal type like `dumb' or `dialup' on dialup lines.  Newer
       ones may pre-set `vt100', reflecting the prevalence of DEC
       VT100-compatible terminals  and  personal-computer  emula­

       Modern  telnets  pass  your TERM environment variable from
       the local side to the remote one.  There can  be  problems
       if  the  remote terminfo or termcap entry for your type is
       not compatible with yours, but this situation is rare  and
       can  almost  always  be  avoided  by  explicitly exporting
       `vt100' (assuming you are in fact using  a  VT100-superset
       console, terminal, or terminal emulator.)

       In any case, you are free to override the system TERM set­
       ting to your taste in your  shell  profile.   The  tset(1)
       utility  may  be  of  assistance; you can give it a set of
       rules for deducing or requesting a terminal type based  on
       the tty device and baud rate.

       Setting your own TERM value may also be useful if you have
       created a custom  entry  incorporating  options  (such  as
       visual  bell  or reverse-video) which you wish to override
       the system default type for your line.

       Terminal type descriptions are stored as files of capabil­
       ity data underneath /usr/share/terminfo.  To browse a list
       of all terminal names recognized by the system, do

            toe | more

       from your shell.  These capability files are in  a  binary
       format optimized for retrieval speed (unlike the old text-
       based termcap format they replace); to examine  an  entry,
       you  must  use  the infocmp(1) command.  Invoke it as fol­

            infocmp entry-name

       first and last (if present) are aliases for the  terminal,
       usually historical names retained for compatibility.

       There are some conventions for how to choose terminal pri­
       mary names that help keep  them  informative  and  unique.
       Here is a step-by-step guide to naming terminals that also
       explains how to parse them:

       First, choose a root name.  The root  will  consist  of  a
       lower-case  letter followed by up to seven lower-case let­
       ters or digits.  You need to avoid using punctuation char­
       acters  in  root  names,  because they are used and inter­
       preted as filenames and shell meta-characters (such as  !,
       $, *, ? etc.) embedded in them may cause odd and unhelpful
       behavior.  The slash (/), or any other character that  may
       be  interpreted  by  anyone's file system (\, $, [, ]), is
       especially dangerous  (terminfo  is  platform-independent,
       and  choosing  names with special characters could someday
       make life difficult for users of a future port).  The  dot
       (.)  character  is  relatively safe as long as there is at
       most one per root name; some historical terminfo names use

       The  root  name for a terminal or workstation console type
       should almost always begin with a vendor prefix  (such  as
       hp  for Hewlett-Packard, wy for Wyse, or att for AT&T ter­
       minals), or a common name of the terminal line (vt for the
       VT  series of terminals from DEC, or sun for Sun Microsys­
       tems workstation consoles, or regent for the  ADDS  Regent
       series.   You  can list the terminfo tree to see what pre­
       fixes are already in common use.   The  root  name  prefix
       should  be  followed  when  appropriate by a model number;
       thus vt100, hp2621, wy50.

       The root name for a PC-Unix console type should be the  OS
       name,  i.e.  linux, bsdos, freebsd, netbsd.  It should not
       be console or any other generic that might cause confusion
       in  a  multi-platform environment!  If a model number fol­
       lows, it should indicate either the OS  release  level  or
       the console driver release level.

       The root name for a terminal emulator (assuming it doesn't
       fit one of the standard ANSI or vt100 types) should be the
       program  name or a readily recognizable abbreviation of it
       (i.e. versaterm, ctrm).

       Following the root name, you may add any reasonable number
       of hyphen-separated feature suffixes.

       2p   Has two pages of memory.  Likewise 4p, 8p, etc.

       mc   Magic-cookie.   Some  terminals (notably older Wyses)

       -nl  No labels - suppress soft labels

       -nsl No status line - suppress status line

       -pp  Has a printer port which is used.

       -rv  Terminal in reverse video mode (black on white)

       -s   Enable status line.

       -vb  Use visible bell (flash) rather than beep.

       -w   Wide; terminal is in 132 column mode.

       Conventionally,   if  your  terminal  type  is  a  variant
       intended to specify a line height, that suffix  should  go
       first.  So, for a hypothetical FuBarCo model 2317 terminal
       in 30-line mode with reverse video,  best  form  would  be
       fubar-30-rv (rather than, say, `fubar-rv-30').

       Terminal types that are written not as standalone entries,
       but rather as components to be plugged into other  entries
       via  use capabilities, are distinguished by using embedded
       plus signs rather than dashes.

       Commands which use a  terminal  type  to  control  display
       often  accept  a  -T  option  that accepts a terminal name
       argument.  Such programs should  fall  back  on  the  TERM
       environment variable when no -T option is specified.


       For  maximum  compatibility  with  older  System V UNIXes,
       names and aliases should be unique  within  the  first  14


            compiled terminal capability data base

            tty line initialization (AT&T-like UNIXes).

            tty line initialization (BSD-like UNIXes).


       ncurses(3NCURSES), terminfo(5), term(5).

Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds