The TTY subsystem forms the backbone of Linux terminal interaction, yet its complex history and design are often overlooked. Originating from 1940s electro-mechanical teletypes and the global Telex network, the system evolved as computers adopted command-line interfaces. UNIX designers embedded low-level hardware management—like baud rate and flow control—directly into the kernel, creating a durable but intricate architecture that persists today.

A TTY device comprises three core components: a UART driver for physical byte transmission, a line discipline for basic editing and echoing, and a TTY driver for session management. The default line discipline, N_TTY, provides cooked mode with backspace and other editing features, while raw mode disables these for applications like shells and editors that handle input directly. This separation allows flexible terminal emulation, from physical serial lines to modern pseudo terminals.

Today, physical teletypes are museum pieces, replaced by software-emulated terminals like xterm. Yet the legacy code—managing sessions, signals, and line editing—remains fundamental to Linux consoles and remote connections via SSH or screen. Understanding this subsystem is not academic nostalgia; it is essential for diagnosing terminal quirks, securing device access, and grasping why Linux processes interact with the kernel through this enduring, if convoluted, interface.