Wikipedia Open wikipedia design.

Simplified structure of the Linux kernel: Terminals and character device drivers, a.k.a. the "TTY subsystem".

devpts is a virtual filesystem available in the Linux kernel since version 2.1.93 (April 1998). It is normally mounted at /dev/pts and contains solely device files which represent slaves to the multiplexing master located at /dev/ptmx.[1]

The creation of devpts resulted from the wish to abandon the need for a setuid helper program, e.g. /usr/libexec/pt_chown. It is a distinct implementation of the pseudoterminal idea; the previous implementation provided a fixed number of master/slave pairs which had permanent device nodes, for example the master-slave pair /dev/ptyp63 and /dev/ttyp63, cf. The Linux Programming Interface chapter 62 "Terminals" and chapter 64 "Pseudoterminals".

A pseudoterminal ("pseudo TTY" or "PTY") is a pair of pseudo-devices – a slave and a master – that provide a special sort of communication channel. The slave pseudo-device emulates a physical computer text terminal, like e.g. the DEC VT100, it can read and write text as though it was such a physical terminal. The master pseudo-device provides the means by which a program providing a text-based user interface acts with and controls its slave. Widely spread programs with a text-based user interface are terminal emulators, e.g. xterm, gnome-terminal or Konsole, or programs using SSH or telnet. Writing to the master is exactly like typing on a terminal, thus the master pseudo-device acts kind of like the person sitting in front of the physical computer text terminal.

A pseudoterminal pair is similar to a bidirectional pipe. Anything that is written on the master appears as input on the slave, and anything that is written on the slave appears as input on the master. Like pipes, pseudoterminals have a limited capacity. On Linux, the pseudoterminal capacity is about 4 KiB in each direction.

A typical Linux kernel-based operating system provides lots of PTYs to support text-based interfaces as provided by terminal emulators (such as xterm or gnome-terminal) and remote access interfaces like SSH.

Implementation history[edit]

In February 1998, Linux 2.1.87 brought support for the /dev/ptmx multiplexing master device.[2] Opening this device provides access to an otherwise unused pseudo TTY master and allows the matching slave to be identified using an ioctl(). In April of that year, Linux 2.1.93 added a new virtual filesystem called devpts that is normally mounted at /dev/pts. Whenever a new master/slave pair is created, a device node for the slave is created in that virtual filesystem.

To facilitate moving the terminal emulation into userland, while still keeping the TTY subsystem (session management and line discipline) intact, the pseudoterminal was invented.[3]

The reason why the line discipline is inside the kernel, is to avoid context switches at the reception of each character (which in the early times of small core memories, would imply swap-outs and swap-ins!). So the line discipline keeps in a kernel buffer a line of input, and since it is simple enough to test for a specific byte and decrement a counter to implement the backspace "editing" (and a few other simple editing functions), it's done there.

The alternative is to use the raw mode, where the characters are forwarded to the application as soon as they're received, which is needed for more sophisticated editors, like the (at the time) famously known Emacs. And indeed, since emacs had to use this raw mode, which implies a context switch at the reception of each character typed, it was constantly swapping when the computers hadn't enough memory to keep emacs and all the other programs in core.

With the addition of pseudo terminals (PTYs), the TTY code has also become a sort of interprocess communication mechanism, with all of the weird TTY semantics preserved. The TTY code also needs to support networking protocols like PPP without creating performance bottlenecks.[4]


This page is based on a Wikipedia article written by contributors (read/edit).
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.