{"id":1934,"date":"2026-07-29T20:54:21","date_gmt":"2026-07-29T15:24:21","guid":{"rendered":"https:\/\/kwikserver.com\/tutorials\/?p=1934"},"modified":"2026-07-29T21:53:20","modified_gmt":"2026-07-29T16:23:20","slug":"linux-cheat-sheet-series-part-1-of-10","status":"publish","type":"post","link":"https:\/\/kwikserver.com\/tutorials\/linux-cheat-sheet-series-part-1-of-10\/","title":{"rendered":"Linux Cheat Sheet Series (Part 1 of 10)"},"content":{"rendered":"\n\n\n
\n\n \n

\n LINUX CHEAT SHEET SERIES \u2014 PART 1 OF 10\n <\/p>\n\n

\n Linux Commands for Beginners: The Ultimate Quick Reference Guide\n <\/h1>\n\n

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

\n

\n \ud83d\udca1 New to this series?<\/strong> We’re turning a popular 10-part Linux cheat sheet into a\n full beginner course \u2014 one topic per article, with plain-English explanations and real examples\n you can copy-paste. No prior Linux experience needed. Bookmark this page and follow along!\n <\/p>\n <\/div>\n\n \n

\n

\ud83d\udccb What You’ll Learn<\/p>\n

    \n
  1. What Is the Linux Terminal (and Why Should You Care)?<\/a><\/li>\n
  2. File & Directory Basics<\/a><\/li>\n
  3. Viewing & Editing Files<\/a><\/li>\n
  4. Process & System Commands<\/a><\/li>\n
  5. Permissions, Users & Groups<\/a><\/li>\n
  6. Archives & Compression<\/a><\/li>\n
  7. Networking & Connectivity<\/a><\/li>\n
  8. Miscellaneous Utilities<\/a><\/li>\n
  9. Tips & Good Practices<\/a><\/li>\n
  10. Practice Exercise & What’s Next<\/a><\/li>\n <\/ol>\n <\/div>\n\n \n

    \n 1. What Is the Linux Terminal (and Why Should You Care)?\n <\/h2>\n

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

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

    Once you connect to your server (typically via SSH), you’ll see a prompt that looks something like this:<\/p>\n\n 

    user@server:~$ <\/code><\/pre>\n\n  
    \n    Everything after that dollar sign ($<\/code>)\n    is where you type your command. Press Enter<\/strong> to run it. That’s it \u2014 that’s the whole loop:\n    type a command, press Enter, read the output, repeat.\n  <\/p>\n\n  \n  
    \n    2. File & Directory Basics\n  <\/h2>\n  
    \n    In Linux, everything is organized into files<\/strong> and directories<\/strong> (what\n    Windows calls “folders”). These are the first commands every beginner needs, because you’ll use\n    them dozens of times per session just to move around and see what’s there.\n  <\/p>\n\n  
    \ud83d\udcc2 Navigating the Filesystem<\/h3>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    pwd<\/code><\/td>Print Working Directory \u2014 shows where you currently are<\/td><\/tr>\n    
    ls<\/code><\/td>Lists files and folders in the current directory<\/td><\/tr>\n    
    ls -l<\/code><\/td>Long listing format \u2014 shows permissions, owner, size, date<\/td><\/tr>\n    
    ls -a<\/code><\/td>Shows hidden files too (names starting with a dot)<\/td><\/tr>\n    
    ls -lh<\/code><\/td>Long format with human-readable sizes (KB, MB, GB)<\/td><\/tr>\n    
    cd <dir><\/code><\/td>Change directory \u2014 moves you into a folder<\/td><\/tr>\n    
    cd ..<\/code><\/td>Go up one directory level<\/td><\/tr>\n    
    cd ~<\/code><\/td>Jump straight to your home directory<\/td><\/tr>\n    
    cd -<\/code><\/td>Go back to the previous directory you were in<\/td><\/tr>\n  <\/table>\n\n  
    Try it yourself:<\/strong><\/p>\n  
    $ pwd\n\/home\/user\n\n$ ls -lh\ndrwxr-xr-x  2 user user 4.0K Jul 20 10:15 backups\n-rw-r--r--  1 user user  312 Jul 22 09:03 notes.txt\n\n$ cd backups\n$ pwd\n\/home\/user\/backups\n\n$ cd ..\n$ pwd\n\/home\/user<\/code><\/pre>\n\n  
    \n    
    \u2b50 Beginner Tip:<\/strong> Press the Tab<\/strong> key while typing a\n    file or folder name \u2014 Linux will auto-complete it for you. This saves time and avoids typos, which\n    matter a lot on servers.<\/p>\n  <\/div>\n\n  
    \ud83d\udcc1 Creating & Removing Directories<\/h3>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    mkdir <dir><\/code><\/td>Creates a new directory<\/td><\/tr>\n    
    rmdir <dir><\/code><\/td>Removes an empty<\/em> directory<\/td><\/tr>\n  <\/table>\n\n  
    Example \u2014 setting up a project folder:<\/strong><\/p>\n  
    $ mkdir my-website\n$ cd my-website\n$ mkdir images css js\n$ ls\ncss  images  js<\/code><\/pre>\n\n  
    \n    Note that rmdir<\/code> only works on empty<\/em> folders \u2014 if a directory has files inside,\n    you’ll need rm -r <dir><\/code> (covered in the Permissions article later in this series,\n    since deleting files is powerful and needs to be handled carefully).\n  <\/p>\n\n  \n  
    \n    3. Viewing & Editing Files\n  <\/h2>\n  
    \n    You’ll spend a huge amount of time reading configuration files, log files, and code on a server.\n    These commands let you look inside files without needing a graphical text editor.\n  <\/p>\n\n  
    \ud83d\udc40 Reading File Contents<\/h3>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    cat <file><\/code><\/td>Prints the entire file to the screen at once<\/td><\/tr>\n    
    less <file><\/code><\/td>Opens the file page-by-page (best for large files)<\/td><\/tr>\n    
    more <file><\/code><\/td>Similar to less, older\/simpler scrolling viewer<\/td><\/tr>\n    
    head <file><\/code><\/td>Shows the first 10 lines of a file<\/td><\/tr>\n    
    head -n 20 <file><\/code><\/td>Shows the first 20 lines<\/td><\/tr>\n    
    tail <file><\/code><\/td>Shows the last 10 lines of a file<\/td><\/tr>\n    
    tail -f <file><\/code><\/td>“Follows” a file live \u2014 new lines appear as they’re written<\/td><\/tr>\n    
    wc -l <file><\/code><\/td>Counts the number of lines in a file<\/td><\/tr>\n  <\/table>\n\n  
    \n    
    \ud83d\udd25 Real-world use case:<\/strong> Something on your website\n    just broke. Instead of guessing, you’d run:<\/p>\n    
    $ tail -f \/var\/log\/syslog<\/code><\/pre>\n    
    This shows you errors as they happen<\/em>, in real time \u2014 one of the\n    most useful debugging tricks you’ll learn as a sysadmin.<\/p>\n  <\/div>\n\n  
    \u270f\ufe0f Editing Files<\/h3>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    nano <file><\/code><\/td>Opens a beginner-friendly text editor (recommended to start)<\/td><\/tr>\n    
    vim <file><\/code><\/td>Opens the powerful (but harder to learn) Vim editor<\/td><\/tr>\n  <\/table>\n\n  
    \n    For beginners, start with nano<\/code>.<\/strong> It shows the available keyboard shortcuts\n    right at the bottom of the screen (like Ctrl+O<\/code> to save and Ctrl+X<\/code> to exit), so\n    you don’t need to memorize anything up front. Vim is more powerful once you’re comfortable, but it has\n    a steeper learning curve \u2014 we’ll cover it properly in a later part of this series.\n  <\/p>\n\n  
    \ud83d\udd0d Searching & Sorting<\/h3>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    grep \"text\" <file><\/code><\/td>Searches for a word or phrase inside a file<\/td><\/tr>\n    
    grep -r \"text\" .<\/code><\/td>Searches recursively through every file in a folder<\/td><\/tr>\n    
    sort <file><\/code><\/td>Sorts the lines of a file alphabetically<\/td><\/tr>\n    
    uniq <file><\/code><\/td>Removes duplicate adjacent lines<\/td><\/tr>\n    
    cut -d, -f1 <file><\/code><\/td>Extracts the 1st column from a comma-separated (CSV) file<\/td><\/tr>\n    
    paste f1 f2<\/code><\/td>Merges two files side by side, column by column<\/td><\/tr>\n  <\/table>\n\n  
    Example \u2014 finding every “error” mention in a log file:<\/strong><\/p>\n  
    $ grep -i \"error\" \/var\/log\/syslog\nJul 29 10:02:14 server kernel: error: disk read failure\nJul 29 10:15:41 server app: error connecting to database<\/code><\/pre>\n  
    The -i<\/code> flag makes the search case-insensitive, so it catches “Error”, “ERROR”, and “error” all at once.<\/p>\n\n  \n  
    \n    4. Process & System Commands\n  <\/h2>\n  
    \n    A “process” is simply a running program. Your web server, database, and even the shell itself are\n    all processes. Knowing how to see what’s running \u2014 and stop it if needed \u2014 is essential server admin skill.\n  <\/p>\n\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    ps aux<\/code><\/td>Lists all running processes, in detail<\/td><\/tr>\n    
    top<\/code><\/td>Live, real-time view of CPU\/memory usage per process<\/td><\/tr>\n    
    htop<\/code><\/td>A friendlier, color-coded version of top<\/code> (install separately)<\/td><\/tr>\n    
    kill <PID><\/code><\/td>Politely asks a process to stop, using its Process ID<\/td><\/tr>\n    
    kill -9 <PID><\/code><\/td>Force-kills a process immediately (last resort)<\/td><\/tr>\n    
    df -h<\/code><\/td>Shows disk space usage in human-readable form<\/td><\/tr>\n    
    free -h<\/code><\/td>Shows how much RAM is used vs. free<\/td><\/tr>\n    
    uname -a<\/code><\/td>Displays system\/kernel information<\/td><\/tr>\n    
    uptime<\/code><\/td>Shows how long the server has been running<\/td><\/tr>\n    
    whoami<\/code><\/td>Tells you which user you’re currently logged in as<\/td><\/tr>\n  <\/table>\n\n  
    Example \u2014 a website is running slow, so you check what’s eating resources:<\/strong><\/p>\n  
    $ top\nPID   USER   %CPU  %MEM  COMMAND\n4821  mysql  86.3  12.1  mysqld\n2210  www    4.2   1.8   apache2<\/code><\/pre>\n  
    \n    Here, mysqld<\/code> (the MySQL database) is using 86% CPU \u2014 that’s your culprit. From here you\n    could investigate slow queries, or if it’s completely frozen, stop it safely with\n    kill <PID><\/code> and restart the service properly.\n  <\/p>\n\n  
    \n    
    \u26a0\ufe0f Be careful with kill -9<\/code>.<\/strong> It force-terminates a\n    process with no cleanup, which can corrupt open files or database transactions. Always try a normal\n    kill<\/code> first, and only use -9<\/code> when a process is truly unresponsive.<\/p>\n  <\/div>\n\n  \n  
    \n    5. Permissions, Users & Groups\n  <\/h2>\n  
    \n    Linux is a multi-user system at its core, so every file has an owner<\/strong>, a\n    group<\/strong>, and a set of permissions<\/strong> controlling who can read, write, or\n    execute it. (We’ll dedicate an entire, deep-dive article to this topic later in the series \u2014 Part 8 \u2014\n    but here’s the essential starting point.)\n  <\/p>\n\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    chmod <mode> <file><\/code><\/td>Changes file permissions<\/td><\/tr>\n    
    chmod 755 <file><\/code><\/td>Owner: read\/write\/execute, everyone else: read\/execute<\/td><\/tr>\n    
    chmod 644 <file><\/code><\/td>Owner: read\/write, everyone else: read-only<\/td><\/tr>\n    
    chown <user> <file><\/code><\/td>Changes who owns a file<\/td><\/tr>\n    
    useradd <user><\/code><\/td>Creates a new user account<\/td><\/tr>\n    
    passwd <user><\/code><\/td>Sets or changes a user’s password<\/td><\/tr>\n    
    id <user><\/code><\/td>Shows a user’s ID and group memberships<\/td><\/tr>\n  <\/table>\n\n  
    Understanding the permission numbers:<\/strong><\/p>\n  
    Each permission type has a number: read = 4<\/code>, write = 2<\/code>, execute = 1<\/code>. Add them together for each of the three groups \u2014 owner, group, others:<\/p>\n\n  
    chmod 755 script.sh\n   \u2193    \u2193    \u2193\n owner group others\n  7  =  5  =  5\n rwx    r-x    r-x\n\n7 = 4(read) + 2(write) + 1(execute)\n5 = 4(read) + 0        + 1(execute)<\/code><\/pre>\n\n  
    \n    So 755<\/code> is a very common permission set for scripts and websites: the owner can do\n    everything, and everyone else can only read and run it (not modify it).\n  <\/p>\n\n  \n  
    \n    6. Archives & Compression\n  <\/h2>\n  
    \n    Whether you’re backing up a website or downloading software, you’ll constantly work with compressed\n    archives. Here are the core tools:\n  <\/p>\n\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    tar -cvf file.tar <files><\/code><\/td>Bundles files into a single .tar archive<\/td><\/tr>\n    
    tar -xvf file.tar<\/code><\/td>Extracts a .tar archive<\/td><\/tr>\n    
    tar -czvf file.tar.gz <files><\/code><\/td>Creates a compressed .tar.gz archive<\/td><\/tr>\n    
    tar -xzvf file.tar.gz<\/code><\/td>Extracts a .tar.gz archive<\/td><\/tr>\n    
    gzip <file><\/code><\/td>Compresses a single file into .gz<\/td><\/tr>\n    
    zip -r archive.zip <dir><\/code><\/td>Creates a .zip archive from a directory<\/td><\/tr>\n    
    unzip archive.zip<\/code><\/td>Extracts a .zip archive<\/td><\/tr>\n  <\/table>\n\n  
    Example \u2014 backing up your website’s files before making changes:<\/strong><\/p>\n  
    $ tar -czvf website-backup-2026-07-29.tar.gz \/var\/www\/html\/\n$ ls -lh website-backup-2026-07-29.tar.gz\n-rw-r--r-- 1 user user 42M Jul 29 20:14 website-backup-2026-07-29.tar.gz<\/code><\/pre>\n  
    \n    A single command, and your entire site is safely bundled and compressed into one portable file. We’ll\n    cover tar<\/code> and compression tools in much greater depth \u2014 including bzip2, xz, and password\n    protection \u2014 in Part 5 of this series.\n  <\/p>\n\n  \n  
    \n    7. Networking & Connectivity\n  <\/h2>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    ip a<\/code><\/td>Shows all IP addresses assigned to the server<\/td><\/tr>\n    
    ping <host><\/code><\/td>Tests whether a server\/website is reachable<\/td><\/tr>\n    
    traceroute <host><\/code><\/td>Shows the network path\/hops to reach a destination<\/td><\/tr>\n    
    curl <url><\/code><\/td>Fetches data from a URL (great for testing APIs\/websites)<\/td><\/tr>\n    
    wget <url><\/code><\/td>Downloads a file from a URL<\/td><\/tr>\n    
    ss -tulnp<\/code><\/td>Lists which ports are open and listening<\/td><\/tr>\n    
    ssh user@host<\/code><\/td>Securely logs in to a remote server<\/td><\/tr>\n    
    scp file user@host:\/path<\/code><\/td>Securely copies a file to a remote server<\/td><\/tr>\n  <\/table>\n\n  
    Example \u2014 checking if your VPS can reach the internet:<\/strong><\/p>\n  
    $ ping -c 4 google.com\n64 bytes from google.com: icmp_seq=1 ttl=115 time=12.4 ms\n64 bytes from google.com: icmp_seq=2 ttl=115 time=11.9 ms\n64 bytes from google.com: icmp_seq=3 ttl=115 time=12.1 ms\n64 bytes from google.com: icmp_seq=4 ttl=115 time=12.7 ms<\/code><\/pre>\n  
    The -c 4<\/code> flag limits the ping to 4 attempts instead of running forever \u2014 a small but handy habit to build early.<\/p>\n\n  \n  
    \n    8. Miscellaneous Utilities\n  <\/h2>\n  \n    \n      
    Command<\/th>\n      What It Does<\/th>\n    <\/tr>\n    
    echo \"text\"<\/code><\/td>Prints text to the screen<\/td><\/tr>\n    
    alias ll='ls -l'<\/code><\/td>Creates a shortcut\/alias for a longer command<\/td><\/tr>\n    
    which <command><\/code><\/td>Shows the full path of a command<\/td><\/tr>\n    
    man <command><\/code><\/td>Opens the full manual page for any command<\/td><\/tr>\n    
    history<\/code><\/td>Shows previously run commands<\/td><\/tr>\n    
    env<\/code><\/td>Shows environment variables<\/td><\/tr>\n  <\/table>\n\n  
    \n    man<\/code> is the single most important command on this list, because it means you never have\n    to memorize everything \u2014 you can always ask Linux to explain itself:\n  <\/p>\n  
    $ man tar<\/code><\/pre>\n\n  \n  
    \n    9. Tips & Good Practices\n  <\/h2>\n  
    \n