Course Content
🗓️ Day 1 – Getting Started with Linux
• Understand what Linux is and why it’s essential for DevOps and AI. • Learn basic terminal commands: pwd, ls, cd. • Explore the filesystem hierarchy and directory structure. • Practice moving around the shell confidently.
0/6
🗓️ Day 2 – Working with Files and Directories
• Create, view, and edit files using touch, cat, nano. • Organize directories with mkdir, rmdir, cp, mv. • Understand absolute vs. relative paths. • Hands‑on: build a mini project folder structure.
0/6
🗓️ Day 3 – Permissions and Ownership
• Learn how Linux manages read, write, and execute permissions. • Commands: chmod, chown, chgrp. • Understand user roles (root, user, group). • Practice fixing permission errors and securing files.
0/6
🗓️ Day 4 – Processes and Services
• Understand what processes are and how to monitor them. • Commands: ps, top, kill, systemctl. • Learn how services start, stop, and restart. • Hands‑on: manage a simple service like nginx or ssh.
0/6
🗓️ Day 5 – Networking and Remote Access
• Basics of IP addresses, ports, and protocols. • Commands: ping, ip, ssh, scp. • Learn secure remote connections and file transfers. • Practice connecting to a remote server.
0/6
🗓️ Day 6 – Shell Scripting Essentials
• Introduction to shell scripting and variables. • Write simple scripts using echo, loops, and conditionals. • Learn how to make scripts executable. • Hands‑on: automate a daily task (e.g., backup or log cleanup).
0/6
Introduction to the Linux Terminal

Now that you understand why files are the absolute bedrock of Linux, it is time to build them. In this section, you will learn the exact sequence used by cloud engineers to generate documents, view their contents instantly, and make rapid live modifications.

1. Dropping Files into Existence: touch

The fastest way to create a completely blank file in Linux is with the touch command. It takes a single argument: the name of the file you want to build.

  • Command Syntax: touch config.txt

When you run this command, the shell silently creates an empty file named config.txt in your current folder. If you run ls immediately afterward, you will see it sitting there.

Gotcha Check: Beginners often assume they need to add file extensions like .txt or .conf for Linux to understand what the file is. Linux does not care about file extensions. You could name a file database_blueprint with no extension at all, and Linux will manage it just fine. Extensions are mostly used just to help humans keep track of data formats.

2. Peeking at Content Instantly: cat

Once a file contains data, you need a quick way to read it without launching a heavy, full-screen program. For this, we use cat (short for concatenate).

While cat can technically glue multiple files together, its primary daily use is to instantly dump the contents of a file directly onto your terminal screen.

  • Command Syntax: cat /etc/hostname

When you type this, the shell opens the file, spits out every line of text contained inside it, and immediately returns you to your active prompt line. It is fast, efficient, and perfect for verifying scripts or looking up configuration variables.

3. Modifying Text in the Terminal: nano

Eventually, you will need to actively change text inside a configuration or note file. Because you do not have a mouse or a windowed interface on a server, you must use a terminal-native text editor.

The easiest, most friendly terminal editor for beginners is Nano. To open any file inside Nano, simply type the editor’s name followed by the file target:

  • Command Syntax: nano notes.txt

The moment you hit Enter, your terminal window will change into a simple text editing screen. You can type directly into it using your keyboard.

Navigating the Nano Interface

At the very bottom of the Nano screen, you will see a menu with shortcuts that look like this: ^O Write Out and ^X Exit.

The caret symbol (^) simply stands for the Ctrl key on your keyboard. Memorize these two essential combinations to save your work and escape:

  • Ctrl + O (Write Out): This is the “Save” command. It writes your edits safely to the storage drive.

  • Ctrl + X (Exit): This closes the editor and returns you safely to your black terminal screen. If you forgot to save your work, Nano will politely ask you Save modified buffer? before letting you leave.

4. The Legendary Rivalry: Nano vs. Vim

As you advance in your technology career, you will inevitably hear engineers arguing about terminal text editors. The primary divide is between Nano and Vim.

   [ Nano ]                        [ Vim ]
 Friendly & Basic             Extremely Fast & Complex
 (Like a notepad)              (Like a flight cockpit)
  • Nano is designed for simplicity. It works right out of the box like a very basic notepad. You type, you use your arrow keys, and you save. It is perfect for freshers.

  • Vim (Vi Improved) is a highly sophisticated modal text editor. It has no mouse support, completely different keyboard tracking states, and a steep learning curve. However, because it relies on pure keyboard configurations, experienced systems engineers can edit thousands of lines of code with blazing speed.

For this introductory course, stick to Nano. It is more than enough to handle basic file tasks, and it ensures you don’t get trapped inside an editor you can’t figure out how to close!