Introduction
Linux is a free, open-source operating system that quietly runs most of the internet. The servers behind websites, Android phones, cloud platforms like AWS and Azure, and nearly every container you will ever meet in DevOps are all powered by Linux. If you want a career in cloud engineering or DevOps, Linux isn't optional. It is the ground you build on.
I'll be honest about where I started. I'm used to writing, designing and clicking my way through friendly screens, so a black window with a blinking cursor felt intimidating. I assumed one wrong command would break the whole computer, and that only "real programmers" could use it. I was wrong on both counts.
After finishing the Basic Linux Commands module, the terminal feels less like a locked door and more like a very fast, very literal assistant. In this post I'll share the commands I learned, show them in action with annotated screenshots, explain how they apply to real DevOps work, and admit where I struggled.
Note on the screenshots: they're captured from real command output in a practice environment, then annotated with numbered callouts.
Key Commands Learned
Everything in Linux lives inside one tree that starts at / (root). Once I understood that, navigation made sense.
1. Filesystem navigation
Think of these as moving around a building: pwd tells you which room you're in, cd walks you to another, and ls shows what's inside.
| Command | What it does |
|---|---|
pwd | Shows where you are right now |
ls / ls -l | Lists files (-l adds permissions, owner, size) |
cd | Moves into another directory |
mkdir | Creates a directory (-p makes parents too) |
rm | Deletes files (rm -r for folders, and there's no undo) |
2. File management
These are the everyday tools for handling files. The one that impressed me most was grep, which finds a needle in a haystack of text. Combining commands with && (run the next one only if the first succeeds) felt like writing my first tiny script.
| Command | What it does |
|---|---|
touch | Creates an empty file |
cp | Copies a file |
mv | Moves or renames a file |
cat | Prints a file's contents |
grep | Searches for text inside files |
3. Users and permissions
| Command | What it does |
|---|---|
sudo | Runs one command with admin rights |
usermod | Changes a user account (e.g. sudo usermod -aG docker nnamdi) |
chmod | Changes who can read, write or execute |
chown | Changes a file's owner |
sudo is the key: use it sparingly, because it lets you change almost anything. Permissions confused me until I saw them as three groups of three letters:
4. Process management
Every running program is a process with an ID (PID). Knowing how to see and stop one is how you rescue a frozen server.
| Command | What it does |
|---|---|
ps | Snapshot of running processes |
top | Live view of CPU, memory and processes |
kill | Stops a process by its PID |
5. Package management
Instead of hunting for installers online, Linux uses a package manager that downloads, installs and updates software for you in one command (usually with sudo). Which one you use depends on your Linux family:
Real-World Application
These aren't classroom exercises. They are the daily tools of the jobs I'm aiming for.
- System administration: Admins use
ps,topandkillto find and stop a runaway process,chmodandchownto control access, andaptordnfto keep servers updated. - Cybersecurity:
grepis a detective's magnifying glass. Searching a log for failed logins, like theERRORsearch in my demo, is how suspicious activity gets spotted. Tight file permissions also follow the principle of least privilege. - DevOps: Deployment scripts are Linux commands in a file. A CI/CD pipeline typically logs into a server, copies files with
cp/mv, sets permissions withchmod, and installs dependencies with a package manager. - Cloud computing: Launch an AWS EC2 instance and you're handed a Linux terminal. Docker containers and Kubernetes nodes run on Linux too, so these commands follow you everywhere in the cloud. In short, learning Linux basics is learning the language that DevOps teams use to talk to their servers.
Challenges & Takeaways
Challenges. The biggest was fear of destructive commands. rm has no recycle bin, and I double-checked every path before pressing Enter. Second, permission numbers like 750 looked like random digits until I learned the r=4, w=2, x=1 trick. Third, small typos matter: Linux is case-sensitive and takes spaces seriously. Finally, I kept mixing up apt, yum and dnf before realising they are the same idea for different distributions.
Most exciting command. grep wins for me. Pulling the two error lines out of a log in a split second felt like a superpower, and I can already see how useful it will be with thousands of lines. A close second is chmod, because it taught me that security is built from small, deliberate decisions.
Takeaway. The terminal isn't scary once you read commands as short sentences: a verb (cp, mv), then what you're acting on. Practising in a safe test folder removed most of my fear.
Conclusion
This module changed how I see computers. I started out nervous about the command line, and I'm finishing with real confidence in navigating files, managing permissions and processes, and installing software. More importantly, I now understand why Linux is the foundation of DevOps and cloud engineering.
To keep improving, I plan to practise daily in a Linux virtual machine, write small Bash scripts to automate repetitive tasks, and explore commands like find, ssh and systemctl. I also want to document each new lesson in a blog post like this one, because teaching is how I learn best.
If you're just starting out, open a terminal, make a practice folder, and break things safely. That's where the learning happens.
Thanks for reading! What was the first Linux command you learned? Tell me in the comments.








