Linux Commands Every IT Professional Should Know: A Beginner-Friendly Guide

Linux appears everywhere in IT: servers, cloud platforms, cybersecurity labs, DevOps tools and network appliances. This tutorial gives you a practical starting point.

What you will learn

• Navigate folders from the terminal
• Inspect files safely
• Check disk and memory usage
• Find processes and network information
• Use a simple troubleshooting checklist

1. Navigation commands

The first skill is moving around the file system. Think of the terminal as a text-based file explorer.

pwd        # show current directory
ls         # list files
cd /var    # move to /var
cd ~       # go to home directory

2. Reading files safely

IT professionals often need to check logs or configuration files. Start with read-only commands before editing anything.

less /var/log/syslog
tail -n 50 /var/log/syslog
head -n 20 filename.txt

Good habit: read first, understand second, edit last.

3. Checking system health

When a server is slow, start with CPU, memory and disk checks.

top
free -h
df -h
uptime

• top shows active processes.
• free -h shows memory usage.
• df -h shows disk usage.
• uptime shows load and running time.

4. Network checks

Linux is powerful for network troubleshooting.

ip addr
ip route
ping 8.8.8.8
ss -tulpen

Use these commands to check IP addresses, routing, connectivity and listening services.

5. Beginner troubleshooting workflow

1. Confirm the error message.
2. Check disk space with df -h.
3. Check memory with free -h.
4. Check recent logs with tail.
5. Check if the service is running.
6. Document what changed.

Quick check

1. Which command shows your current directory?
2. Which command checks disk usage?
3. Which command can show live processes?
4. Why should you read logs before editing configuration files?

Next steps

• Open a Linux terminal or WSL and practice the commands.
• Create your own cheat sheet.
• Never run destructive commands on production systems without backup and approval.

---

Educational note: This tutorial is for learning purposes. Always test commands and configuration changes carefully in a safe environment before using them on production systems.