gettytab(5)

NAME

gettytab − terminal configuration data base

SYNTAX

/etc/gettytab

DESCRIPTION

The gettytab file is a simplified version of the termcap() data base used to describe terminal lines. The initial terminal login process getty() accesses the gettytab file each time it starts, allowing simpler reconfiguration of terminal characteristics. Each entry in the data base is used to describe one class of terminal.

There is a default terminal class, default, that is used to set global defaults for all other classes. That is, the default entry is read, then the entry for the class required is used to override particular settings.

CAPABILITIES

Refer to termcap() for a description of the file layout. The default column below lists defaults obtained if there is no entry in the table obtained, nor one in the special default table.

NameTypeDefault Description
abboolfalseauto-baud speed selection mechanism
apboolfalseterminal uses any parity
bdnum0backspace delay
bkstr0377alternate end of line character (input break)
cbboolfalseuse crt backspace mode
cdnum0carriage-return delay
ceboolfalseuse crt erase algorithm
ckboolfalseuse crt kill algorithm
clstrNULLscreen clear sequence
coboolfalseconsole - add \n after login prompt
dsstr^Ydelayed suspend character
ecboolfalseleave echo OFF
epboolfalseterminal uses even parity
erstr^?erase character
etstr^Dend of text (EOF) character
evstrNULLinitial environment
f0numunusedtty mode flags to write messages
f1numunusedtty mode flags to read login name
f2numunusedtty mode flags to leave terminal as
fdnum0form-feed (vertical motion) delay
flstr^Ooutput flush character
hcboolfalsedo NOT hangup line on last close
hestrNULLhostname editing string
hnstrhostnamehostname
htboolfalseterminal has real tabs
igboolfalseignore garbage characters in login name
imstrNULLinitial (banner) message
instr^Cinterrupt character
isnumunusedinput speed
klstr^Ukill character
lcboolfalseterminal has lower case
lmstrlogin:login prompt
lnstr^V“literal next” character
lostr/bin/loginprogram to exec when name obtained
ndnum0newline (line-feed) delay
nlboolfalseterminal has (or might have) a newline character
nxstrdefaultnext table (for auto speed selection)
opboolfalseterminal uses odd parity
osnumunusedoutput speed
p8boolfalseuse eight bit characters
pcstr\0pad character
pdboolfalsedisable parity on output
peboolfalseuse printer (hard copy) erase algorithm
pfnum0delay between first prompt and following flush (seconds)
psboolfalseline connected to a MICOM port selector
qustr^\quit character
rpstr^Rline retype character
rwboolfalsedo NOT use raw for input, use cbreak
spnumunusedline speed (input and output)
sustr^Zsuspend character
tcstrnonetable continuation
tonum0timeout (seconds)
ttstrNULLterminal type (for environment)
ubboolfalsedo unbuffered output (of prompts etc)
ucboolfalseterminal is known upper case only
westr^Wword erase character
xcboolfalsedo NOT echo control chars as ^X
xfstr^SXOFF (stop output) character
xnstr^QXON (start output) character

If no line speed is specified, speed will not be altered from that which prevails when getty is entered. Specifying an input or output speed will override line speed for stated direction only.

Terminal modes to be used for the output of the message, for input of the login name, and to leave the terminal set as upon completion, are derived from the boolean flags specified. If the derivation should prove inadequate, any (or all) of these three may be overriden with one of the f0, f1, or f2 numeric specifications, which can be used to specify (usually in octal, with a leading ’0’) the exact values of the flags. Local (new tty) flags are set in the top 16 bits of this (32 bit) value.

Should getty receive a null character (presumed to indicate a line break), it will restart using the table indicated by the nx entry. If there is none, it will reuse its original table.

Delays are specified in milliseconds, the nearest possible delay available in the tty driver will be used. Should greater certainty be desired, delays with values 0, 1, 2, and 3 are interpreted as choosing that particular delay algorithm from the driver.

The cl screen clear string may be preceded by a (decimal) number of milliseconds of delay required (a la termcap). This delay is simulated by repeated use of the pad character pc.

The initial message, and login message, im and lm may include the character sequence %h to obtain the host name, B%t to obtain the terminal name, and %d to obtain the date. (%% obtains a single ’%’ character.) The host name is normally obtained from the system, but may be set by the hn table entry. In either case it may be edited with he. The he string is a sequence of characters, each character that is neither ’@’ nor ’#’ is copied into the final host name. A ’@’ in the he string, causes one character from the real host name to be copied to the final host name. A ’#’ in the he string, causes the next character of the real host name to be skipped. Surplus ’@’ and ’#’ characters are ignored.

When getty execs the login process, given in the lo string (usually "/bin/login"), it will have set the environment to include the terminal type, as indicated by the tt string (if it exists). The ev string, can be used to enter additional data into the environment. It is a list of comma-separated strings, each of which will presumably be of the form name=value.

If a nonzero timeout is specified, with to, then getty will exit within the indicated number of seconds, either having received a login name and passed control to login, or having received an alarm signal, and exited. This may be useful to hang up dial-in lines.

The p8 flag allows use of 8 bit characters.

The pd flag turns off parity on output. Output from getty is even parity unless the op flag, the pd flag, or the p8 flag is specified. The ap flag is used to allow any parity on input. The op(ep) flag may be specified with the ap flag to allow any parity on input, but generate odd(even) parity on output. Note: the parity on output is accomplished by using the 8th bit as the parity bit. getty(8) does not check parity of input characters in RAW mode or 8 bit mode.

Terminals which are setup to operate in 8-bit mode should use gettytab entries which include the p8 flag. If a terminal which is setup in 8-bit mode fails to use an appropriate gettytab entry the output from getty and login may appear as multinational characters. This is due to the fact that getty uses the 8-th bit of characters to provide software generated parity. The software parity generation will transform certain ascii characters into multinational characters. Earlier releases of the ULTRIX operating system did not display these multinational characters due to the lack of full 8-bit support in the terminal subsystem.

RESTRICTIONS

Because some users insist on changing their default special characters, it is wise to define at least the erase, kill, and interrupt characters in the default table. In all cases, ’#’ or ’CTRL/H’ typed in a login name will be treated as an erase character, and ’@’ will be treated as a kill character.

Museum