GETTYTAB(5)

πŸ“¦
version 1042.100.6.0.1 Β· 3 versions
, in nixpkgs unstable

GETTYTAB(5) Β· File Formats Manual β€” okay bestie, we’re about to read the terminal configuration data base page together, and it’s honestly giving vintage Unix main-character energy.

🌸 NAME 🌸

gettytab β€” terminal configuration data base.

πŸ’– SYNOPSIS πŸ’–

gettytab

✨ DESCRIPTION ✨

The gettytab file is a simplified version of the termcap(5) data base used to describe terminal lines. The initial terminal login process getty(8) reads the gettytab file every time it starts, which makes reconfiguring terminal characteristics simpler. Each entry in the data base describes one class of terminals.

There’s a default terminal class, default, that sets global defaults for all the other classes. (Like, the default entry gets read first, then the entry for the class you actually need is used to override particular settings. Slay.)

πŸŽ€ CAPABILITIES πŸŽ€

Peep termcap(5) for a description of the file layout. The defaults listed below are what you get when there’s no entry in the table you looked up and no entry in the special default table either. Here’s the full roster: name Β· type Β· default Β· what it does.

  • ac β€” str Β· default unused β€” expect-send chat script for modem answer.
  • al β€” str Β· default unused β€” user to auto-login instead of prompting.
  • ap β€” bool Β· default false β€” terminal uses any parity.
  • bk β€” str Β· default 0377 β€” alternate end of line character (input break).
  • c0 β€” num Β· default unused β€” tty control flags to write messages.
  • c1 β€” num Β· default unused β€” tty control flags to read login name.
  • c2 β€” num Β· default unused β€” tty control flags to leave terminal as.
  • ce β€” bool Β· default false β€” use crt erase algorithm.
  • ck β€” bool Β· default false β€” use crt kill algorithm.
  • cl β€” str Β· default NULL.
  • co β€” bool Β· default false β€” console β€” add \n after login prompt.
  • ct β€” num Β· default 10 β€” chat timeout for ac and ic scripts.
  • dc β€” num Β· default 0 β€” chat debug bitmask.
  • de β€” num Β· default 0 β€” delay secs and flush input before writing first prompt.
  • df β€” str Β· default %+ β€” the strftime(3) format used for %d in the banner message.
  • ds β€” str Β· default β€˜^Y’ β€” delayed suspend character.
  • dx β€” bool Β· default false β€” set DECCTLQ.
  • ec β€” bool Β· default false β€” leave echo OFF.
  • ep β€” bool Β· default false β€” terminal uses even parity.
  • er β€” str Β· default β€˜^?’ β€” erase character.
  • et β€” str Β· default β€˜^D’ β€” end of text (EOF) character.
  • ev β€” str Β· default NULL.
  • fl β€” str Β· default β€˜^O’ β€” output flush character.
  • hc β€” bool Β· default false β€” do NOT hangup line on last close.
  • he β€” str Β· default NULL.
  • hn β€” str Β· default hostname β€” hostname.
  • ht β€” bool Β· default false β€” terminal has real tabs.
  • hw β€” bool Β· default false β€” do cts/rts hardware flow control.
  • i0 β€” num Β· default unused β€” tty input flags to write messages.
  • i1 β€” num Β· default unused β€” tty input flags to read login name.
  • i2 β€” num Β· default unused β€” tty input flags to leave terminal as.
  • ic β€” str Β· default unused β€” expect-send chat script for modem initialization.
  • if β€” str Β· default unused β€” display named file before prompt, like /etc/issue.
  • ig β€” bool Β· default false β€” ignore garbage characters in login name.
  • im β€” str Β· default NULL.
  • iM β€” str Β· default NULL.
  • in β€” str Β· default β€˜^C’ β€” interrupt character.
  • is β€” num Β· default unused β€” input speed.
  • kl β€” str Β· default β€˜^U’ β€” kill character.
  • l0 β€” num Β· default unused β€” tty local flags to write messages.
  • l1 β€” num Β· default unused β€” tty local flags to read login name.
  • l2 β€” num Β· default unused β€” tty local flags to leave terminal as.
  • lm β€” str Β· default login: β€” login prompt.
  • ln β€” str Β· default β€˜^V’ β€” β€œliteral next” character.
  • lo β€” str Β· default /usr/bin/login.
  • mb β€” bool Β· default false β€” do flow control based on carrier.
  • nc β€” bool Β· default false β€” terminal does not supply carrier (set clocal).
  • nl β€” bool Β· default false β€” terminal has (or might have) a newline character.
  • np β€” bool Β· default false β€” terminal uses no parity (i.e., 8-bit characters).
  • nx β€” str Β· default default β€” next table (for auto speed selection).
  • o0 β€” num Β· default unused β€” tty output flags to write messages.
  • o1 β€” num Β· default unused β€” tty output flags to read login name.
  • o2 β€” num Β· default unused β€” tty output flags to leave terminal as.
  • op β€” bool Β· default false β€” terminal uses odd parity.
  • os β€” num Β· default unused β€” output speed.
  • pc β€” str Β· default β€˜\0’ β€” pad character.
  • pe β€” bool Β· default false β€” use printer (hard copy) erase algorithm.
  • pf β€” num Β· default 0 β€” delay between first prompt and following flush (seconds).
  • pl β€” bool Β· default false β€” start PPP login program unconditionally if pp is specified.
  • pp β€” str Β· default unused β€” PPP login program.
  • ps β€” bool Β· default false β€” line connected to a MICOM port selector.
  • qu β€” str Β· default β€˜^\’ β€” quit character.
  • rp β€” str Β· default β€˜^R’ β€” line retype character.
  • rt β€” num Β· default unused β€” ring timeout when using ac.
  • rw β€” bool Β· default false β€” do NOT use raw for input, use cbreak.
  • sp β€” num Β· default unused β€” line speed (input and output).
  • su β€” str Β· default β€˜^Z’ β€” suspend character.
  • tc β€” str Β· default none β€” table continuation.
  • to β€” num Β· default 0 β€” timeout (seconds).
  • tt β€” str Β· default NULL.
  • ub β€” bool Β· default false β€” do unbuffered output (of prompts etc).
  • we β€” str Β· default β€˜^W’ β€” word erase character.
  • xc β€” bool Β· default false β€” do NOT echo control chars as ^X.
  • xf β€” str Β· default β€˜^S’ β€” XOFF (stop output) character.
  • xn β€” str Β· default β€˜^Q’ β€” XON (start output) character.
  • Lo β€” str Β· default C β€” the locale name used for %d in the banner message.

πŸ’€ the ones getty(8) no longer supports πŸ’€

These capabilities are no longer supported by getty(8) β€” they’re still listed here, but bestie, do not expect them to be doing anything for you:

  • bd β€” num Β· default 0 β€” backspace delay.
  • cb β€” bool Β· default false β€” use crt backspace mode.
  • cd β€” num Β· default 0 β€” carriage-return delay.
  • f0 β€” num Β· default unused β€” tty mode flags to write messages.
  • f1 β€” num Β· default unused β€” tty mode flags to read login name.
  • f2 β€” num Β· default unused β€” tty mode flags to leave terminal as.
  • fd β€” num Β· default 0 β€” form-feed (vertical motion) delay.
  • lc β€” bool Β· default false β€” terminal has lower case.
  • nd β€” num Β· default 0 β€” newline (line-feed) delay.
  • uc β€” bool Β· default false β€” terminal is known upper case only.

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 the stated direction only.

The terminal modes used for outputting the message, for reading the login name, and for leaving the terminal set when it’s done are derived from the boolean flags you specify. If that derivation proves inadequate, any (or all) of these three can be overridden with one of the c0, c1, c2, i0, i1, i2, l0, l1, l2, o0, o1, or o2 numeric specifications. Those let you specify (usually in octal, with a leading '0') the exact values of the flags. These flags correspond to the termios c_cflag, c_iflag, c_lflag, and c_oflag fields, respectively. Each of these sets must be completely specified to be effective.

Should getty(8) 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 re-use its original table.

Delays are specified in milliseconds, and the nearest possible delay available in the tty driver will be used. If greater certainty is 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, login message, and initial file β€” im, lm, and if β€” may include any of the following character sequences, which expand to information about the environment in which getty(8) is running:

  • %d β€” the current date and time formatted according to the Lo and df strings.
  • %h β€” the hostname of the machine, normally obtained from the system using gethostname(3), but also possibly overridden by the hn table entry. In either case it may be edited with the he POSIX β€œextended” regular expression, which is matched against the hostname. If there are no parenthesized subexpressions in the pattern, the entire matched string is used as the final hostname; otherwise, the first matched subexpression is used instead. If the pattern does not match, the original hostname is not modified.
  • %t β€” the tty name.
  • %m, %r, %s, %v β€” the type of machine, release of the operating system, name of the operating system, and version of the kernel, respectively, as returned by uname(3).
  • %% β€” a β€œ%” character.

When getty execs the login process, given in the lo string (usually /usr/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 non-zero 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(1), or having received an alarm signal, and exited. This may be useful to hangup dial in lines.

Output from getty(8) is even parity unless op or np is specified. The op string may be specified with ap to allow any parity on input, but generate odd parity output. Note: this only applies while getty is being run β€” terminal driver limitations prevent a more complete implementation. getty(8) does not check parity of input characters in RAW mode. 🫢

If a pp string is specified and a PPP link bring-up sequence is recognized, getty will invoke the program referenced by the pp option. This can be used to handle incoming PPP calls. If the pl option is true as well, getty(8) will skip the user name prompt and the PPP detection phase, and will invoke the program specified by pp instantly. ✨

Getty provides some basic intelligent modem handling by providing a chat script feature available via two capabilities:

  • ic β€” Chat script to initialize modem. πŸŽ€
  • ac β€” Chat script to answer a call. πŸ¦‹

A chat script is a set of expect/send string pairs. When a chat string starts, getty will wait for the first string, and if it finds it, will send the second, and so on. Strings specified are separated by one or more tabs or spaces. Strings may contain standard ASCII characters and special 'escapes', which consist of a backslash character followed by one or more characters which are interpreted as follows:

  • \a β€” bell character. πŸ””
  • \b β€” backspace.
  • \n β€” newline.
  • \e β€” escape.
  • \f β€” formfeed.
  • \p β€” half-second pause.
  • \r β€” carriage return.
  • \S, \s β€” space character.
  • \t β€” tab.
  • \xNN β€” hexadecimal byte value.
  • \0NNN β€” octal byte value.
Note that the \p sequence is only valid for send strings and causes a half-second pause between sending the previous and next characters. Hexadecimal values are, at most, 2 hex digits long, and octal values are a maximum of 3 octal digits. ⏳

The ic chat sequence is used to initialize a modem or similar device. A typical example of an init chat script for a modem with a hayes compatible command set might look like this:

:ic="" ATE0Q0V1\r OK\r ATS0=0\r OK\r:

This script waits for nothing (which always succeeds), sends a sequence to ensure that the modem is in the correct mode (suppress command echo, send responses in verbose mode), and then disables auto-answer. It waits for an "OK" response before it terminates. The init sequence is used to check modem responses to ensure that the modem is functioning correctly. If the init script fails to complete, getty considers this to be fatal, and results in an error logged via syslogd(8), and exiting. 😭

Similarly, an answer chat script is used to manually answer the phone in response to (usually) a "RING". When run with an answer script, getty opens the port in non-blocking mode, clears any extraneous input and waits for data on the port. As soon as any data is available, the answer chat script is started and scanned for a string, and responds according to the answer chat script. With a hayes compatible modem, this would normally look something like:

:ac=RING\r ATA\r CONNECT:

This causes the modem to answer the call via the "ATA" command, then scans input for a "CONNECT" string. If this is received before a ct timeout, then a normal login sequence commences. πŸ”₯

The ct capability specifies a timeout for all send and expect strings. This timeout is set individually for each expect wait and send string and must be at least as long as the time it takes for a connection to be established between a remote and local modem (usually around 10 seconds). ⏱️

In most situations, you will want to flush any additional input after the connection has been detected, and the de capability may be used to do that, as well as delay for a short time after the connection has been established during which all of the connection data has been sent by the modem. πŸ’œ


🌈 SEE ALSO 🌈

Your reference besties: login(1), gethostname(3), uname(3), termcap(5), getty(8). πŸ’…

πŸ¦‹ HISTORY πŸ¦‹

The gettytab file format appeared in 4.2BSD. ⭐

πŸ’€ BUGS πŸ’€

The special characters (erase, kill, etc.) are reset to system defaults by login(1). In all cases, # or ^H typed in a login name will be treated as an erase character, and @ will be treated as a kill character. πŸ™ˆ

The delay stuff is a real crock. Apart form its general lack of flexibility, some of the delay algorithms are not implemented. The terminal driver should support sane delay settings. πŸ˜­πŸ’€

The termcap(5) format is horrid, something more rational should have been chosen. πŸ“

xoxo, bestie πŸ’– β€” this one's from Debian, dated September 29, 2022, and it's the GETTYTAB(5) page. πŸŽ€

πŸ“¦ where this page comes from