Trace init systems, journal hints, and recovery modes without guessing.
Artifacts you leave class with
Every cohort ships annotated command logs, maintenance cards, and blunt mentor notes tied to real Linux administration tasks—not slide decks you never reopen.
Checklists
Boot, mount, and service sequences written for humans who inherit your shift.
Heat-mapped drills
Faults injected on purpose so muscle memory forms before production adrenaline hits.
Mentor markup
Inline reactions on your artifacts, not vague praise buried in email threads.
Async capture reviews
Rural uplink friendly: upload terminal captures when live sessions stutter.
Featured pathways
Four active tracks — prices shown in BRL for transparency.
Mount options, quotas, and integrity checks with repeatable verification steps.
Interfaces, routes, and firewall basics tied to realistic change tickets.
ACLs, sudo patterns, and group design with least-privilege stories.
05 — Rhythm on the rails
Diagnose: freeze the story in the ticket
Model: mirror risk on lab metal only
Pair: cross-read commands aloud
Ship: attach rollback language
Review: mentor marks assumptions, not typos
From our cohorts · mixed formats
“Kernel & Boot Flow Lab had me narrate each unit activation before touching production-like VMs; the mentor margin notes on my fstab sketch were uncomfortably accurate.”
— Larissa Monteiro, Systems operator, Regional water telemetry
Verified learner · 5/5 marker
“Filesystems & Mount Discipline — week three quota lab still lives in our wiki with the warning callouts intact.”
“Short: Network Plumbing labs made our ticket language match what change boards actually want.”
— Clara, João Pessoa
“Permissions & Identity Hygiene forced us to write stakeholder blurbs before chmod. Slower start, fewer Sunday pages.”
— Rodrigo Silveira, Support lead, Logistics control room
“Containers on Admin Metal was mostly great; voice notes occasionally clipped mid-sentence when mentors got excited.”
— Client in education publishing
“Observability for Small Teams: alert copy skeletons trimmed our noise. Still want one more example on rural uplinks.”
— Bianca, Night shift, Retail monitoring desk
Verified learner · 4/5 marker
“Incident Rhythm for Linux Crews — bridge scribe rotation felt awkward at first, then saved us during a real router flap.”
Surface questions
No. Labs run on shared remote images. You provide your own machine with SSH-capable browser or client.
Request the syllabus PDF
We email a printable outline with module boundaries, mentor touchpoints, and hardware expectations. No payment links inside—just scope clarity.
Open the contact desk