Linux File System Hierarchy for DevOps Engineers

Day 07 of #90DaysOfDevOps 🚀 Linux File System Hierarchy: Know Where Everything Lives Today I stopped treating Linux as a black box. Time to think like an operator. Every DevOps engineer should know where to look first: → `/etc` — configuration files (nginx, ssh, hosts) → `/var/log` — first stop during incidents → `/tmp` — temporary files → `/opt` — third-party tools (Jenkins, Grafana) → `/home` / `/root` — user environments and permissions What I practiced today: ✅ Mapped core Linux directories with real-world use cases ✅ Diagnosed a failed service using `systemctl status` + `journalctl` ✅ Identified CPU-heavy processes with `ps aux --sort=-%cpu` ✅ Resolved permission issues using `chmod +x` ✅ Located service logs with `journalctl -u <service>` 💡 Most useful takeaway: A service failing after reboot isn't always a crash issue — sometimes it was never enabled to start. Verified with `systemctl is-enabled`. 🔑 Mindset Shift: In production, speed comes from knowing where to check, what to run, and what signal matters first. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Linux #DevOps

To view or add a comment, sign in

Explore content categories