Exercise 2: Installing Screen and Seeing Its Terminal — Possible Solution
===========================================================================

Commands:

  screen -v                  # check whether it's installed
  sudo apt install screen    # Debian/Ubuntu (use dnf or pacman elsewhere)
  screen -v                  # e.g. "Screen version 4.09.01 ..." or 5.x

Outside screen:

  ps -o pid,tty,comm

Example output (numbers will differ):

    PID TT       COMMAND
   2140 pts/0    bash
   2311 pts/0    ps

Now start a session and run the same command inside it:

  screen
  ps -o pid,tty,comm

Example output:

    PID TT       COMMAND
   2330 pts/1    bash
   2345 pts/1    ps

Type `exit` to leave the screen session.

What changes:

The TTY column changes from pts/0 to a different pseudo-terminal
(pts/1 here). The shell inside screen is attached to a new terminal
that the screen server created and owns — not to the terminal of your
SSH login. That is exactly why it survives a dropped connection.

WHY THIS WORKS AS AN ANSWER
------------------------------
It turns Chapter 1's diagram into something you can see: the change in
the TTY column is direct evidence that the job is attached to screen's
own terminal. Exact version numbers and pts numbers vary by system,
which is expected.