5. Linux and macOS Administration¶
systemd: Linux's service manager¶
Modern Linux (including every container and VM in this lab) manages background services with systemd, using the systemctl command. This isn't theoretical for this course — the lab itself runs on it:
[email protected] # the systemd template running each student's personal MUD
lab-force-quorum.service # added after the Oct 2026 outage, forces quorum so guests autostart
A few commands that work on any systemd-based Linux system, including CT 250:
systemctl status NAME # is it running? when did it last start/fail?
systemctl restart NAME # stop then start it again
systemctl enable NAME # make it start automatically at boot
Package managers¶
Linux distributions install software through a package manager rather than downloading installers from random websites — apt on Ubuntu/Debian (what every container in this lab uses), dnf on Fedora, pacman on Arch.
macOS¶
Built on a Unix foundation, macOS has its own service manager (launchd, systemd's rough equivalent) and its own GUI settings app (System Settings, roughly Windows' Control Panel/Settings equivalent) — conceptually parallel to Linux and Windows, just with its own names for everything.
Try it
On the Linux Terminal tile, run systemctl status ssh (or another service your instructor points you to) and read what it reports — is it running, and since when?
Tip
systemctl status output includes the most recent log lines right at the bottom — often enough to diagnose why a service won't start without digging through separate log files at all.
Play it
Open the Operating Systems Lab and use the Linux & macOS tab.