Red Hat Linux Commands: Complete Reference Guide

The first time I logged into a production RHEL server, I froze. I had memorized the basics — ls, cd, cat — but the senior admin next to me was typing commands I had never seen: journalctl -p err -b, firewall-cmd --list-all, setsebool -P httpd_can_network_connect on. That day I realized RHEL isn't just another Linux distribution — it's an enterprise platform with its own tooling, and knowing the right commands is what separates a beginner from someone the team can rely on.

This guide is a practical reference for Red Hat Enterprise Linux (RHEL). It covers the commands you'll actually use in administration, production support, shell scripting, and troubleshooting. Because RHEL installs hundreds of tools depending on packages and role, no single list is truly complete. Instead, this reference is organized by category so you can find what you need fast. Use the search in your browser (Ctrl+F) to jump to a command, or browse the sections to learn the ecosystem.

1. Basic Linux Commands

Every RHEL session starts here. These are the commands you'll type hundreds of times a day.

2. File Search and Text Processing

RHEL gives you a deep toolkit for finding files and manipulating text. These commands are the backbone of scripting and log analysis.

3. File Permissions and Ownership

In enterprise environments, file permissions are not optional — they are audited. These commands let you control who can read, write, and execute every file.

4. User and Group Management

Adding, modifying, and removing users is a daily task for any RHEL administrator. Understanding these commands — and their configuration files — is essential for compliance.

5. Process and Job Management

Knowing what's running on a server — and how to stop it — is the core of production support. These commands let you inspect, prioritize, and terminate processes.

6. Disk, Filesystem and Storage

Storage management is where mistakes hurt the most. The commands in this section control partitions, filesystems, and logical volumes — and some of them can destroy data if used incorrectly.

7. Networking Commands

Networking is where most production incidents begin. Knowing how to check connectivity, inspect sockets, and manage firewall rules is a survival skill on RHEL.

8. Services, Boot and System Administration

RHEL runs on systemd. These commands are what you'll use to start, stop, enable, and inspect services — and to understand what happened during boot.

9. Package Management in RHEL

RHEL uses dnf as the primary package manager, with rpm as the underlying layer for querying and installing individual packages. Prefer dnf for normal work; use rpm for package queries and specific RPM tasks.

10. Archive and Compression

Backups, log shipping, and software packaging all rely on these tools. RHEL ships with the common ones by default.

11. Logs and Production Troubleshooting

When something breaks in production, these are the commands that get you answers fast. Bookmark this section.

A quick "triage" block you can run on any struggling server:

uptime
free -h
df -h
df -i
ps -ef
top
ss -lntp
systemctl --failed
journalctl -p err -b
tail -100 /var/log/messages

These ten commands will tell you most of what you need to know about CPU, memory, disk, network, and recent errors.

12. Hardware and System Information

When you need to know exactly what's inside the box — CPU features, BIOS version, loaded kernel modules — these commands have you covered.

13. Security and Access Control

RHEL ships with SELinux enabled by default, and enterprise environments almost always have additional security tooling in place. These commands help you understand and manage that layer.

14. Bash Shell Built-in Commands

These commands are handled by Bash itself, not by external binaries. That's why help works on them but man sometimes does not. Knowing which commands are built-ins helps you understand why some things behave differently across shells.

To list all Bash built-ins, run help. For a specific one, try help read or help set.

15. Development and Scripting Tools

RHEL servers frequently host development workloads or shell scripts. These tools are useful whether you're compiling code, running interpreters, or inspecting binaries.

16. How to Get the Actual Command List from Your RHEL Server

The lists above are a practical reference, not an exhaustive inventory. These commands will help you discover what's available on your specific system:

• List commands available in your PATH: compgen -c | sort -u
• List external executables in standard directories: find /usr/bin /usr/sbin /bin /sbin -maxdepth 1 -type f -executable 2>/dev/null | sort -u
• List Bash built-ins: enable -a
• List installed RPM packages: rpm -qa | sort
• Find which package provides a command: command -v systemctl then rpm -qf "$(command -v systemctl)"
• Search for a command's manual: man ls or apropos network

17. Recommended Command Learning Order

If you're starting out with RHEL production support, learn these categories in order:

• Files: ls, cd, find, grep, cat, less, tail, awk, sed
• Permissions: chmod, chown, umask, getfacl
• Processes: ps, top, kill, pgrep, lsof
• Storage: df, du, lsblk, mount, pvs, vgs, lvs
• Services: systemctl, journalctl, crontab
• Networking: ip, ss, ping, curl, dig, ssh
• Packages: dnf, rpm
• Scripting: if, case, for, while, functions, read, grep, awk, sed

Key Takeaways

• RHEL ships with hundreds of commands; the practical ones fall into a handful of categories.
• Learn file, permission, process, storage, service, and network commands first — they cover 90% of daily work.
• Distinguish installed utilities (like systemctl) from Bash built-ins (like cd).
• Storage commands (mkfs, fdisk, dd) can destroy data; always verify the target first.
• Use compgen -c and enable -a to discover what's actually available on your system.

Frequently Asked Questions

What is the difference between a Bash built-in and an external command?

Bash built-ins (like cd, read, export) are handled directly by the shell and don't require a separate binary. External commands (ls, systemctl, dnf) are programs on disk that the shell launches. Use type to check which category a command falls into.

Why do some commands have a man page and others don't?

Built-in commands are documented via help rather than man. External commands usually have a manual page installed with their package. If man doesn't work, try help <command> or command --help.

Which commands are most dangerous on a production server?

Commands that modify storage or security: mkfs, fdisk, dd, fsck, pvcreate, vgcreate, lvcreate, lvextend, setenforce, firewall-cmd, auditctl. Always confirm the target and have a rollback plan.

How can I list all commands available on my system?

Run compgen -c | sort -u to list everything Bash knows about, or find /usr/bin /usr/sbin /bin /sbin -maxdepth 1 -type f -executable 2>/dev/null | sort -u for external executables. Neither is exhaustive, but together they cover most commands.

Do I need to memorize all of these commands?

No. Even experienced administrators memorize only the ones they use daily and look up the rest. Keep this page bookmarked and use man, --help, and apropos when you need details.