gettydefs(4) gettydefs(4)NAME gettydefs - speed and terminal settings used by getty DESCRIPTION The /etc/gettydefs file contains information used by getty(1M) to set up the speed and terminal settings for a line. It supplies information on what the login prompt should look like. It also supplies the speed to try next if the user indicates the current speed is not correct by typ- ing an interrupt character. Each entry in /etc/gettydefs has the following format: label# initial-flags # final-flags # flow-control # login- prompt #next-label Each entry is followed by a blank line. The various fields can contain quoted characters of the form \b, \n, \c, etc., as well as \nnn, where nnn is the octal value of the desired character. The various fields are: label This is the string against which getty tries to match its second argument. It is often the speed, such as 1200, at which the termi- nal is supposed to run, but it need not be (see below). initial-flags These flags are the initial ioctl(2) settings to which the terminal is to be set if a ter- minal type is not specified to getty. The flags that getty understands are the same as the ones listed in /usr/include/sys/termio.h (see termio(7)). Normally only the speed flag is required in the initial-flags. getty automatically sets the terminal to raw input mode and takes care of most of the other flags. The initial-flag settings remain in effect until getty executes login(1). final-flags These flags take the same values as the initial-flags and are set just prior to getty executes login. The speed flag is again re- quired. The composite flags SANE or SANE2 take care of most of the other flags that need to be set so that the processor and ter- minal are communicating in a rational fashion. The other two commonly specified final-flags are TAB3, so that tabs are sent to the terminal as spaces, and HUPCL, so that the line is hung up on the final close. Flag attributes are added from left to right, flags that start with a ~ are subtracted, April, 1990 1
gettydefs(4) gettydefs(4)e.g., SANE ~PARENB. This field specifies what type of flow control to use on the line. The currently allowed settings are APPLE (for apple flow control), DTR (for DTR flow con- trol), MODEM (for modem control), and FLOW (for hardware flow control). These modes can also be turned off by using the ~ as a pre- fix. login-prompt This entire field is printed as the login- prompt. Unlike the above fields where white space is ignored (a space, tab or newline), they are included in the login-prompt field. next-label If this entry does not specify the desired speed, indicated by the user typing a BREAK character, then getty will search for the en- try with next-label as its label field and set up the terminal for those settings. Usu- ally, a series of speeds are linked together in this fashion, into a closed set; For in- stance, 2400 linked to 1200, which in turn is linked to 300, which finally is linked to 2400. If getty is called without a second argument, then the first entry of /etc/gettydefs is used, thus making the first entry of /etc/gettydefs the default entry. It is also used if getty can not find the specified label. If /etc/gettydefs itself is missing, there is one entry built into the command which will bring up a terminal at 300 baud. It is strongly recommended that after making or modifying /etc/gettydefs, it be run through getty with the check op- tion to be sure there are no errors. The following four symbols define the SANE state. # define ISANE (BRKINT | IGNPAR | ISTRIP | ICRNL | IXON) # define OSANE (OPOST | ONLCR) # define CSANE (CS7 | PARENB | CREAD) # define LSANE (ISIG | ICANON | ECHO | ECHOK) FILES /etc/gettydefs SEE ALSO login(1), getty(1M), ioctl(2), termio(7). 2 April, 1990