Get Help: Use Shell Help Tools to Answer Questions About Commands
Practice using built-in shell help tools — man, whatis, type, and apropos — to locate information about commands without leaving the terminal.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
Practice using built-in shell help tools — man, whatis, type, and apropos — to locate information about commands without leaving the terminal.
A custom application has been installed to a non-standard location. Configure the laborant user's environment so the application's directory is permanently available in $PATH for all future login shells.
The laborant user's PATH has been corrupted, causing common commands to fail with "command not found". Diagnose and fix the broken PATH so that standard system commands work again.
Practice managing Bash history by removing a specific sensitive command from history and configuring the shell to prevent space-prefixed commands from being saved.
A system administrator must verify the shell environment is clean before performing privileged tasks. Practice detecting and resolving command aliases and shell function overrides that can silently hijack administrative commands.
Master Bash quoting forms — single quotes, double quotes, backslash escaping, and ANSI-C quoting — to correctly handle filenames and arguments containing spaces, glob characters, dollar signs, and newlines.
The man page database on this system is broken — whatis and apropos return "nothing appropriate" for every query. Diagnose the root cause and restore full functionality of the shell help tools.
The laborant user is reporting that something feels wrong when running administrative tasks. Commands invoked via sudo appear to succeed, but the results are unexpected — files end up in the wrong place and critical system binaries seem to behave differently than documented. Investigate the shell environment, diagnose the root cause, and fix it permanently.
The laborant user's custom directory /opt/tools/bin was working fine last week. Now, after every login, the commands in that directory are not found — even though they worked in the previous session. Someone touched the shell profile and now the $PATH change doesn't survive a new login shell.
A shell script that processes files with spaces and special characters in their names is producing "No such file or directory" errors even though the files exist. Diagnose the quoting bug and fix the script so it runs without errors.