Linux
Linux Shell Ops for Release Engineers
Weeknight drills on systemd units, journalctl triage, and package pinning for predictable deploy hosts.
- Format
- Cohort labs + async drills
- Duration
- 6 weeks · 2 live mentor blocks
- Tuition (informational)
- KRW 980,000
- Mentor
- Haneul Park
Program narrative
You rehearse the same shell workflows our mentors use during weekend workshop intensives: user permissions, cgroup-aware services, and log shipping without guesswork. Each lab ships with a disposable VM image so you can break things safely, then rebuild with Ansible snippets we review live.
What is included
- systemd timer labs mirroring cron-to-timer migrations
- strace/tcpdump micro-exercises for latency hunts
- immutable baseline checklist for staging nodes
- rsync + SSH hardening patterns for artifact sync
- disk pressure simulations with btrfs snapshots
- SELinux/AppArmor toggles explained with rollback paths
- hand-off templates for support engineers joining night rotations
Outcomes you can show
- Document a repeatable boot-to-service verification path
- Ship a journalctl filter pack your team can reuse
- Pair with a mentor on a staged outage drill
Haneul Park
Former SRE lead for a SaaS operations group in Busan; now coaches cohort check-ins.
Cohort FAQ
Accordion stays compact—one limitation answer is baked into each course.
Yes, on lab hosts only. Production credentials are never shared; you mirror patterns locally.
Recordings land within 12 hours, but the paired rehearsal is not re-run individually—plan for the alternate office hour.
No. You need a machine capable of nested virtualization; we publish minimum specs two weeks before kickoff.
Experience notes
The systemd timer lab finally made our patch Tuesday prep legible—especially the hand-off template from week four.
Minseo K. · Support engineer · 5/5 · survey
Short: strace walkthrough paid off immediately. Wanted one more hour on btrfs but the async notes covered it.
Leo · 4/5