Servers Linux topic checklist

Topic: Servers linux

Convergence checklist for the servers-linux topic: ensure you have covered fundamentals, operations, failure recovery, and hardening. Use this to confirm you have the right guides for your role and to find the next step when you are stuck.

Intent: Checklist

Quick answer

  • Root: what is a server, users/permissions, filesystem layout, shell commands, packages and updates; do these first if new to Linux servers.
  • Operations: install packages, systemd, users, mount/fstab, SSH, firewall, cron, logs; use these for day-to-day admin.
  • Failure: disk full, service won't start, OOM, high CPU, permission denied, SSH failure, network failure, corrupt package; use when something is broken.

Prerequisites

Steps

  1. Fundamentals

    Complete: what is a server, users/groups/permissions, filesystem hierarchy, shell essentials, packages and updates. Then add/remove users, mount disks, and secure SSH.

  2. Operations

    Install packages, manage systemd units, configure network and firewall, set up cron and log rotation, back up and restore files.

  3. Failure and recovery

    Know how to fix: disk full, service won't start, OOM, high CPU, permission denied, SSH failure, network failure, corrupt package, read-only fs.

  4. Go-live

    Run server hardening checklist, pre-deployment checklist, and incident response checklist; document and monitor.

Summary

You will use this checklist to confirm coverage of servers-linux: fundamentals, operations, failure recovery, and go-live. Use it to plan learning or to find the right guide when stuck.

Prerequisites

  • At least one of: server hardening, pre-deployment, or incident response checklist done or in progress.

Steps

Step 1: Fundamentals

Cover: what is a server, users/groups/permissions, filesystem layout, shell commands, packages and updates. Then users, mounts, and SSH.

Step 2: Operations

Packages, systemd, network, firewall, cron, log rotation, backup and restore.

Step 3: Failure and recovery

Know where to look for: disk full, service failures, OOM, high CPU, permission denied, SSH, network, package issues, read-only fs.

Step 4: Go-live

Run hardening, pre-deployment, and incident response checklists; document and monitor.

Verification

  • You can point to a guide for each area; checklists are run before production and after incidents.

Troubleshooting

Missing a guide — Use the topic index or search; start from root guides and follow next links.

Next steps

Continue to