Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 37 ยท Getting Started

What a Linux System Administrator Does

Learn what Linux system administration covers: users, packages, services, storage, networking, security and monitoring, plus the habits that keep servers healthy.

A Linux system administrator keeps computers running, secure and useful for the people and programs that depend on them. The machines might be a single web server, a fleet of virtual machines in the cloud, or a rack of database hosts. The job is the same at every scale: make changes safely, notice problems early and fix them quickly.

This tutorial follows the real life of a server. You install it, create accounts, add software, attach disks, connect it to a network, lock it down, watch it, automate the boring parts and rescue it when something breaks. This first lesson maps the territory so every later lesson has a place to land.

About the examples. The site cannot run a Linux server for you, so commands appear in read-only blocks. We never show output we cannot be sure of. The runnable editors contain small Python programs that model the same ideas, such as parsing a file or doing the arithmetic you would do by hand. Each one says it is a stand-in.

The areas of the job

The six areas of administration

Accounts Users, groups, permissions
Software Packages, updates, services
Storage Disks, filesystems, backups
Network Addresses, DNS, firewall

Security and monitoring cut across all of them.

1 / 2
  • Accounts and access. Who may log in, what they may read and write, and who may become root (Users and the passwd files).
  • Software. Installing, updating and removing packages, and running long-lived programs as services (Package managers).
  • Storage. Partitions, filesystems, logical volumes, RAID, quotas and backups (Disks and partitions).
  • Networking. Addresses, routes, DNS, firewalls and remote access.
  • Security. Reducing the attack surface, patching, auditing.
  • Observation. Logs, metrics and alerts so you hear about trouble before users do.

Principles that matter more than commands

  1. Least privilege. Give every person and program only the access it needs.
  2. Change one thing at a time. If you change five things and the server breaks, you do not know which one did it.
  3. Have a way back. Take a backup or snapshot before risky changes, and keep a second terminal open when editing remote access settings.
  4. Write it down. Notes, comments and version-controlled configuration turn a surprising server into a documented one.
  5. Automate repeated work. A command you type three times belongs in a script.
  6. Treat servers as replaceable when you can. Rebuilding from a script beats nursing a hand-tuned machine.

Pets and cattle

Old-style administration treated each server as a pet: named, hand-configured, irreplaceable. Modern practice prefers cattle: identical machines created from a recipe, replaced rather than repaired. Most real environments are a mixture. You will meet both, and the same Linux skills apply.

flowchart LR
    A["Plan"] --> B["Change"]
    B --> C["Verify"]
    C --> D["Document"]
    D --> A

A safe change loop: plan it, make it, check it, record it.

Tools you will use all the time

Task Typical tools
Remote access ssh, scp, rsync
Look around ls, cat, less, grep, find
Edit files nano, vim
Processes ps, top, systemctl
Disk lsblk, df, du
Network ip, ss, ping
Logs journalctl, files in /var/log

A stand-in: a daily checklist

Real administrators use checklists because routine work is easy to skip. This runnable model records which areas were reviewed and what is missing.

Python Stand-in: daily review checklist

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A stand-in: change log

Writing down what you changed is half of good administration. This model keeps a timestamped log in memory.

Python Stand-in: a tiny change log

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common beginner mistakes

  • Working as root all the time. Use a normal account and elevate only when needed (sudo).
  • Editing a config and restarting without testing it first. Many services can check a file before reloading.
  • Skipping backups until after the failure.
  • Copying commands from the internet without reading them.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why change only one thing at a time on a production server?

    Small, isolated changes make failures easy to trace and to undo.
  2. 2. Which principle says every user and program gets only the access it needs?

    Least privilege limits the damage from mistakes and attacks.
  3. 3. What is a good reason to keep a second terminal open while editing remote access settings?

    A working session lets you revert a bad change that blocks new logins.
  4. 4. In the pets and cattle idea, what do cattle servers have in common?

    Identical, recipe-built machines can be replaced instead of nursed.

Summary

  • Administration covers accounts, software, storage, networking, security and monitoring.
  • Work with least privilege, small changes, backups and notes.
  • Automate repeated tasks and prefer reproducible builds.
  • This tutorial's runnable editors are labelled stand-ins; real commands appear read-only.

Next: Choosing a Linux Distribution