Terminals, TTYs, Shells, and Command Syntax

1. Five layers behind a command prompt

When you type into a graphical terminal, several layers cooperate. Treating them as one object leads to incorrect troubleshooting: changing the terminal theme does not change the shell, switching shells does not change the kernel, and closing a terminal can affect processes because the pseudo-terminal disappears.

flowchart LR
  K["Keyboard input"] --> T["Terminal emulator"]
  T --> P["Pseudo-terminal pair"]
  P --> S["Interactive shell"]
  S --> B["Built-in command"]
  S --> E["External executable"]
  B --> P
  E --> P
  P --> T
  T --> D["Displayed output"]

2. TTYs and pseudo-terminals

The term TTY comes from physical teletype devices. Modern Linux still exposes terminal interfaces through device files. A virtual console might appear as /dev/tty1; a graphical terminal or SSH session usually uses a pseudo-terminal such as /dev/pts/0.

The tty command prints the terminal connected to standard input. It can report “not a tty” when input is redirected or when the process runs non-interactively.

3. A shell is both an interface and a language

An interactive shell provides a prompt, history, completion, job control, aliases, and other conveniences. The same shell can also execute scripts non-interactively. Shell behavior depends on the executable, invocation name, options, environment, startup files, and whether the session is interactive or a login shell.

4. Anatomy of a command line

grep --ignore-case --line-number 'failed login' /var/log/auth.log

The shell removes syntactic quotes before launching an external program. The program receives an argument vector, not the original command-line text. Spaces inside a quoted argument are preserved as part of that argument.

5. Shell syntax is not ordinary punctuation

These symbols are interpreted by the shell unless quoted or escaped. Lesson 5 develops streams, pipes, redirection, and exit-status control in detail.

6. Inspect the current interactive session

printf 'Configured login shell: %s\n' "$SHELL"
printf 'Current terminal: '
tty || true

printf '\nCurrent process and parent:\n'
ps -o pid,ppid,sid,tty,stat,comm,args -p $$ -p "$PPID"

printf '\nShell flags and mode indicators:\n'
printf 'shell flags: %s\n' "$-"
case $- in
  *i*) printf 'interactive=yes\n' ;;
  *)   printf 'interactive=no\n' ;;
esac
shopt -q login_shell && printf 'login_shell=yes\n' || printf 'login_shell=no\n'

printf '\nCommand resolution:\n'
type -a printf
command -V cd
command -V ls

$$ is the current shell process ID in a normal interactive Bash session. $PPID is its parent. SID helps identify the session, TTY the controlling terminal, and STAT process state flags.

7. Hands-on lab: create a terminal-session report

Capture the session layers without changing system configuration. Run the report from a local graphical terminal and, when available, an SSH or tmux session. Compare the terminal device and process hierarchy.

lab="$HOME/devops-academy/linux/chapter03/lesson01"
mkdir -p -- "$lab"
report="$lab/session-report.txt"

{
  printf '=== timestamp ===\n'
  date --iso-8601=seconds 2>/dev/null || date

  printf '\n=== identity ===\n'
  id

  printf '\n=== shell variables ===\n'
  printf 'SHELL=%s\n' "${SHELL-}"
  printf 'BASH_VERSION=%s\n' "${BASH_VERSION-}"
  printf 'flags=%s\n' "$-"

  printf '\n=== terminal ===\n'
  tty || true
  stty -a 2>/dev/null || true

  printf '\n=== process chain ===\n'
  current=$$
  count=0
  while [ "$current" -gt 1 ] && [ "$count" -lt 8 ]; do
    ps -o pid=,ppid=,sid=,tty=,stat=,comm=,args= -p "$current"
    current=$(ps -o ppid= -p "$current" | tr -d ' ')
    [ -n "$current" ] || break
    count=$((count + 1))
  done

  printf '\n=== command resolution ===\n'
  type -a cd printf ls 2>&1
} > "$report"

less "$report"

8. Common command-line misconceptions

9. Knowledge check

10. Summary

A terminal emulator presents text, a TTY or PTY provides the terminal device interface, and a shell parses commands and starts work. Command lines contain shell syntax as well as arguments passed to programs. Reliable operators inspect the actual process, terminal, session mode, and command resolution rather than guessing from the prompt.

11. Further reading

• GNU Bash Reference Manual — shell operation, parsing, built-ins, invocation, and interactive shells.
• Linux manual pages for tty, pts, stty, ps, type, command, and bash.
• POSIX Shell Command Language — portable shell grammar and command execution model.
• The Linux Programming Interface documentation and Linux man-pages — sessions, process groups, terminals, and system calls.
• systemd documentation — service processes and non-interactive execution environments.