</>

Linux Cheat Sheet

Practical Linux cheat sheet with setup steps, core workflows, debugging, and copy-paste examples.

linux terminal commands productivity

Linux cheat sheet with real commands and snippets for setup, core workflows, debugging, and production-safe automation patterns. If you are working across tools, pair this with the Bash Cheat Sheet and awk Cheat Sheet.

Setup and Installation

Goal: Verify installation and CLI metadata

# Resolve command path from current shell
command -v bash

# Print installed version to confirm runtime
bash --version

# Read top-level help before using subcommands
bash --help

Goal: Install or upgrade the tool on a workstation

# Install package with Homebrew on macOS
brew install linux

# Upgrade to the latest available package
brew upgrade linux

# Re-check version after upgrade
bash --version

Goal: Run day-to-day commands

# Inspect files in long format
ls -lah

# Find large files for cleanup
find . -type f -size +100M

# Search recursively for text
rg "TODO" .

# Show recent system journal messages
journalctl -n 100

Core Workflows

Goal: Capture command help for quick offline lookup

# Create docs folder for generated command references
mkdir -p docs/cli

# Write help output to a timestamped file
bash --help > docs/cli/linux-help.txt

# Search help output for a keyword
rg "config|auth|deploy" docs/cli/linux-help.txt

Goal: Wrap repetitive commands in a script

# Create scripts directory for local automation
mkdir -p scripts

# Write repeatable health-check script
cat > scripts/check-linux.sh <<'SH'
#!/usr/bin/env bash
set -euo pipefail
bash --version
bash --help >/dev/null
SH

# Make script executable and run it
chmod +x scripts/check-linux.sh && ./scripts/check-linux.sh

Configuration and Environment

Goal: Pin environment variables for predictable runs

# Define environment profile for local commands
export LINUX_PROFILE=dev

# Persist profile in local shell configuration
echo 'export LINUX_PROFILE=dev' >> ~/.zshrc

# Reload shell profile changes
source ~/.zshrc

Automation and CI

Goal: Add tool checks to CI pipeline

# Run lint/test/build in strict mode
set -euo pipefail

# Verify CLI exists before invoking workflow
command -v bash

# Exit quickly if command is unavailable
bash --version

Debugging and Troubleshooting

Goal: Collect diagnostics when commands fail

# Capture command output and exit code
bash --help > /tmp/linux-debug.log 2>&1; echo $?

# Inspect captured diagnostics
tail -n 80 /tmp/linux-debug.log

# Check current shell PATH entries
echo $PATH | tr ':' '\n'

Common Gotchas

  • Pin Linux versions in CI so local and pipeline behavior match.
  • Check tool authentication context before running write or deploy commands.
  • Prefer non-interactive flags in scripts to avoid stalled jobs.
  • Capture stderr logs in CI artifacts for faster incident triage.
  • Keep secrets in environment variables, not committed scripts.

Related Cheat Sheets