#include <sys/ioctl.h>
This section describes the interface to the terminal drivers in the system.
Each terminal on the system usually has a terminal special device file associated with it in the directory /dev/ (for example, /dev/ttyn02). When a user logs into the system on one of these terminals, the system has already opened the associated device and prepared the line for normal interactive use. There is also a special case of a terminal file that connects not to a hardware terminal port, but to another program on the other side. These special terminal devices are called ptys and provide the mechanism necessary to give users the same interface to the system when logging in over a network (using telnet(1) for example.) Even in these cases the details of how the terminal file was opened and set up is already handled by special software in the system. Thus, users do not normally need to worry about the details of how these lines are opened or used.
When an interactive user logs in, the system prepares the line to behave in a certain way (called a line discipline the particular details of which is described in stty(1) at the command level, and in termios(1) at the programming level. A user may be concerned with changing settings associated with his particular login terminal and should refer to the preceding man pages for the common cases. The remainder of this man page is concerned with describing details of using and controlling terminal devices at a low level, such as that possibly required by a program wishing to provide features similar to those provided by the system.
A terminal file is used like any other file in the system in that it can be opened, read, and written to using standard system calls. For each existing terminal file, there is a software processing module called a line discipline is associated with it. The line discipline essentially glues the low level device driver code with the high level generic interface routines (such as read(2) and write(2)), and is responsible for implementing the semantics associated with the device. When a terminal file is first opened by a program, the default line discipline called the termios line discipline is associated with the file. This is the primary line discipline that is used in most cases and provides the semantics that users normally associate with a terminal. When the termios line discipline is in effect, the terminal file behaves and is operated according to the rules described in termios(1). Please refer to that man page for a full description of the terminal semantics. The operations described here generally represent features common across all line disciplines however some of these calls may not make sense in conjunction with a line discipline other than termios, and some may not be supported by the underlying hardware (or lack thereof, as in the case of ptys).
The majority of terminal settings can be handled through the tc family of interfaces. Termios(1) defines them as function calls, not ioctl(2) requests. The following section lists the available ioctl(2) requests. The name of the request, a description of its purpose, and the typed argp parameter (if any) are listed. For example, the first entry says
TIOCGWINSZ
and would be called on the terminal associated with file descriptor zero by the following code fragment:
struct winsize ws;
ioctl(0, TIOCGWINSZ, &ws);
int
ldisc
int
ldisc
void
void
void
void
void
void
int *
tpgrp
int *
tpgrp
struct termios
*
term
struct termios
*
term
struct termios
*
term
struct termios
*
term
struct termios
*
term
int *
num
char *
cp
void
void
void
void
void
void
int *
what
struct winsize
*
ws
struct winsize
*
ws
int *
on
int *
state
CM_DTR | Data Terminal Ready |
TIOCM_RTS | Request To Send |
TIOCM_CTS | Clear To Send |
TIOCM_CAR | Carrier Detect |
TIOCM_CD | Carrier Detect |
TIOCM_RNG | Ring Indication |
TIOCM_RI | Ring Indication |
TIOCM_DSR | Data Set Ready |
int *
state
int *
state
int *
state
stty(1)
fcntl(2)
ioctl(2)
tcgetattr(2)
tcsetattr(2)
pty(4)
termios(4)