Learn › Linux Foundations › Multiplexers
screen - a hands-on Linux lab on a real virtual machine.
The Multiplexers module capstone mission. Drill screen and tmux in one hands-on operation on a real Linux VM: start a named session, detach to leave it running, and list sessions to prove it survived, first with screen, then with tmux. Mission mode: no commands shown, recall required.
You have finished the Multiplexers module. Two tools are yours now. screen is the classic one: it hosts your shell inside a session that keeps running on the machine even after your connection drops. tmux is the modern twin: same superpower, a status bar, and split panes on top. Both let you detach from a running session, walk away, and reattach later to find your work exactly where you left it.
This is the final run. One real machine, four objectives, and every one of them uses a tool you already trained. The job ties them together into a single story: keep work alive across a dropped connection, first with screen, then with tmux. Nothing new is introduced here.
This is mission mode. No commands are shown. You read the objective, recall the tool, and type it. That recall is the whole point: it is how these four moves become instinct. Progress checks itself as you go, and a signal is one click away if you get stuck.
One quick rep in the practice terminal before the real machine boots. Same rules as the mission: the goal is stated, the command is not. If this comes back instantly, you are ready.
Before you start anything, prove nothing is running yet. Ask the classic multiplexer to list its sessions. On a fresh machine that list is empty, and it says so in plain words.
prompt: student@linuxcamp:~$ answer: screen -ls output: No Sockets found in /run/screen/S-student. hint: The classic multiplexer, then a dash and the letters l s for list sessions: screen -ls
That move came from memory, not from a copy button. Good. The mission asks for that same recall four more times, across both tools.
Boot the machine below and take the console. Four objectives, two per tool: start a named screen session and prove it survives a detach, then do the very same with tmux. No commands shown, progress checks itself as you type.
Practice Operation Persistence in a real Linux terminal at The Linux Camp. Progress is verified automatically as you type commands on the machine.