Linux Commands & Shell Skills
GNU screen: The Session Wrapper That Refused to Die
GNU screen predates tmux server-client multiplexing by a decade and remains preinstalled in more rescue images, older hosts, and minimal systems than its modern rival. Its feature set is smaller, its commands begin with Ctrl-a, and its honest role in 2026 is simple: the session keeper that exists when tmux doesn't, plus the muscle memory for hosts where it's the only tool installed.
Key points
- The core loop: `screen -S name` starts a named session, Ctrl-a d detaches (session alive server-side), `screen -r name` reattaches anywhere: identical workflow philosophy as tmux, different prefix and flag vocabulary.
- Scrollback lives in copy mode: Ctrl-a [ + space to set marks, PgUp for paging, search with ?, paste with Ctrl-a }; the `hardcopy -h` dump captures the visible screen with history into a file when you need evidence quickly.
- Multi-user attach is a built-in: shared sessions via acls plus multiuser mode allow two engineers in the same live view (chmod the socket, `acladd user`): a classic for pair ops before tmux made mockery of it easily. Security review: it's privileged enough to matter with the id discipline of shared-shell sessions.
- Monitoring and status: hardstatus line configuration in ~/.screenrc plus window title conventions; window logging (`Ctrl-a H`) per-window log-to-file is a built-in for capturing deployments without extra tooling.
- Splits exist (Ctrl-a S horizontal, | vertical, Tab cycles, X removes) though the pane management is clunkier than tmux's: honest use case for attached diagnostics rather than full workspace living.
- The 2026 rule table from our comparison piece: modern planned setups: tmux; hosts where only screen exists (ancient RH5-class, OpenBSD base installs pre-tmux default, minimal rescue shells): screen: the skill transfer time is minutes, and every sysadmin should carry both.
Field note
The ancient support box that only ships GNU screen was the reason one engineer learned Ctrl-a d after a decade of tmux: the honest rule is knowing both. Rescue images do not ask your preference.
Frequently asked questions
Is screen still maintained?
Maintenance mode, not development mode: quarterly bugfix releases keep it stable-but-static; for new configs and features, tmux inherited the roadmap.
Are screen and tmux configs interchangeable?
Not literally: prefix (Ctrl-a vs Ctrl-b) and command vocab differ; the mental model (sessions, windows, detach/attach) transfers in minutes, which is why learning both is standard practice.
Can I migrate running sessions between hosts?
Not directly, either tool: sessions are server processes on their host. The migration path is process-level: detach, move the work (or restart under a supervisor/log wrapper), reattach on the new host.
Why do rescue images ship screen and not tmux?
Small binary, decades of packaging history, and base-repository practices that predate tmux's arrival: the reason every sysadmin's muscle memory should include Ctrl-a d even in a tmux-normalized decade.
How Kinetikatech helps with linux commands & shell skills
This is what we do every day: The commands and scripting habits that decide whether an administrator operates a server or fights it: search, transform, transfer, and supervise text and processes with the tools that live in every base install. Our Linux Server Security and Server Management service covers it end to end, assessment, implementation, 24/7 monitoring, and emergency response within 30 minutes.