LINUX CHEAT SHEET SERIES — PART 1 OF 10

Linux Commands for Beginners: The Ultimate Quick Reference Guide

Every Linux expert started exactly where you are right now — staring at a blinking cursor, wondering what to type next. In this first part of our 10-part Linux Cheat Sheet series, we’re building your foundation: the core commands you’ll use every single day when working with a Linux server, whether it’s a Linux VPS, a dedicated server, or your own home lab.

1. What Is the Linux Terminal (and Why Should You Care)?

The terminal — also called the shell, console, or command line — is a text-based way to talk directly to your computer’s operating system. Instead of clicking icons, you type instructions (commands) and the system executes them instantly.

On a server, there usually isn’t a graphical desktop at all — the terminal is the interface. That’s why learning these commands isn’t optional if you’re managing a VPS, RDP, or dedicated server: it’s the fastest, most reliable, and often the only way to get things done.

Once you connect to your server (typically via SSH), you’ll see a prompt that looks something like this:

user@server:~$ 

Everything after that dollar sign ($) is where you type your command. Press Enter to run it. That’s it — that’s the whole loop: type a command, press Enter, read the output, repeat.

2. File & Directory Basics

In Linux, everything is organized into files and directories (what Windows calls “folders”). These are the first commands every beginner needs, because you’ll use them dozens of times per session just to move around and see what’s there.

📂 Navigating the Filesystem

Try it yourself:

$ pwd
/home/user

$ ls -lh
drwxr-xr-x  2 user user 4.0K Jul 20 10:15 backups
-rw-r--r--  1 user user  312 Jul 22 09:03 notes.txt

$ cd backups
$ pwd
/home/user/backups

$ cd ..
$ pwd
/home/user

📁 Creating & Removing Directories

Example — setting up a project folder:

$ mkdir my-website
$ cd my-website
$ mkdir images css js
$ ls
css  images  js

Note that rmdir only works on empty folders — if a directory has files inside, you’ll need rm -r <dir> (covered in the Permissions article later in this series, since deleting files is powerful and needs to be handled carefully).

3. Viewing & Editing Files

You’ll spend a huge amount of time reading configuration files, log files, and code on a server. These commands let you look inside files without needing a graphical text editor.

👀 Reading File Contents

$ tail -f /var/log/syslog

✏️ Editing Files

For beginners, start with nano. It shows the available keyboard shortcuts right at the bottom of the screen (like Ctrl+O to save and Ctrl+X to exit), so you don’t need to memorize anything up front. Vim is more powerful once you’re comfortable, but it has a steeper learning curve — we’ll cover it properly in a later part of this series.

🔍 Searching & Sorting

Example — finding every “error” mention in a log file:

$ grep -i "error" /var/log/syslog
Jul 29 10:02:14 server kernel: error: disk read failure
Jul 29 10:15:41 server app: error connecting to database

The -i flag makes the search case-insensitive, so it catches “Error”, “ERROR”, and “error” all at once.

4. Process & System Commands

A “process” is simply a running program. Your web server, database, and even the shell itself are all processes. Knowing how to see what’s running — and stop it if needed — is essential server admin skill.

Example — a website is running slow, so you check what’s eating resources:

$ top
PID   USER   %CPU  %MEM  COMMAND
4821  mysql  86.3  12.1  mysqld
2210  www    4.2   1.8   apache2

Here, mysqld (the MySQL database) is using 86% CPU — that’s your culprit. From here you could investigate slow queries, or if it’s completely frozen, stop it safely with kill <PID> and restart the service properly.

5. Permissions, Users & Groups

Linux is a multi-user system at its core, so every file has an owner, a group, and a set of permissions controlling who can read, write, or execute it. (We’ll dedicate an entire, deep-dive article to this topic later in the series — Part 8 — but here’s the essential starting point.)

Understanding the permission numbers:

Each permission type has a number: read = 4, write = 2, execute = 1. Add them together for each of the three groups — owner, group, others:

chmod 755 script.sh
   ↓    ↓    ↓
 owner group others
  7  =  5  =  5
 rwx    r-x    r-x

7 = 4(read) + 2(write) + 1(execute)
5 = 4(read) + 0        + 1(execute)

So 755 is a very common permission set for scripts and websites: the owner can do everything, and everyone else can only read and run it (not modify it).

6. Archives & Compression

Whether you’re backing up a website or downloading software, you’ll constantly work with compressed archives. Here are the core tools:

Example — backing up your website’s files before making changes:

$ tar -czvf website-backup-2026-07-29.tar.gz /var/www/html/
$ ls -lh website-backup-2026-07-29.tar.gz
-rw-r--r-- 1 user user 42M Jul 29 20:14 website-backup-2026-07-29.tar.gz

A single command, and your entire site is safely bundled and compressed into one portable file. We’ll cover tar and compression tools in much greater depth — including bzip2, xz, and password protection — in Part 5 of this series.

7. Networking & Connectivity

Example — checking if your VPS can reach the internet:

$ ping -c 4 google.com
64 bytes from google.com: icmp_seq=1 ttl=115 time=12.4 ms
64 bytes from google.com: icmp_seq=2 ttl=115 time=11.9 ms
64 bytes from google.com: icmp_seq=3 ttl=115 time=12.1 ms
64 bytes from google.com: icmp_seq=4 ttl=115 time=12.7 ms

The -c 4 flag limits the ping to 4 attempts instead of running forever — a small but handy habit to build early.

8. Miscellaneous Utilities

man is the single most important command on this list, because it means you never have to memorize everything — you can always ask Linux to explain itself:

$ man tar

9. Tips & Good Practices

10. Practice Exercise & What’s Next

Before moving to Part 2, try this 5-minute exercise on your own server or VPS:

1. Check where you are: pwd
2. Create a folder called practice and move into it: mkdir practice && cd practice
3. Create a file: echo "Hello Linux" > hello.txt
4. View it: cat hello.txt
5. Check its permissions: ls -l hello.txt
6. Compress it: tar -czvf hello.tar.gz hello.txt
7. Confirm it worked: ls -lh

If all seven steps ran without errors, congratulations — you’ve just used commands from four different categories in this guide. That’s real progress.

📚 Coming Up in This Series

1. Part 1 (this article): Linux Commands — Your Quick Reference Cheat Sheet
2. Part 2: Viewing Files & Content — Deep Dive into grep, sed, awk & Redirection
3. Part 3: Permissions, Users & Groups — Complete Guide
4. Part 4: Process & System Commands — Monitoring & Managing Your Server
5. Part 5: Archive & Compress Files — tar, gzip, bzip2, zip Explained
6. Part 6: Shell Scripting Basics — Automate Your First Task
7. Part 7: Shell Scripting Basics II — Arrays, Functions & String Operations
8. Part 8: User & Permissions Basics — SetUID, SetGID, Sticky Bit & Umask
9. Part 9: System & Network Basics — Ports, Services & Logs
10. Part 10: Advanced Essentials & Productivity — Cron, Firewalls & Job Control

Frequently Asked Questions

Next up: In Part 2, we’ll go much deeper into viewing and filtering file content — including grep, sed, awk, pipes, and redirection — with real log-file examples you’ll use constantly when managing a server.