OS: Linux Installation & Getting Started

Learning Linux is not just about theory—it is about hands-on practice. To get started, you need to install Linux on your system.

Installing Linux (Dual Boot, Virtual Machine, WSL)

Depending on your needs, hardware, and comfort level, there are several installation approaches. Each has its advantages and trade-offs.

Dual Boot Installation

Dual booting means installing Linux alongside your existing operating system (Windows or macOS) and choosing which one to start at boot.

  • Advantages: Full access to hardware, ideal if Linux will be your main system.
  • Considerations: Requires partitioning disks; reboot needed to switch OS.
  • Steps (high-level): Download ISO → Create bootable USB → Boot → Install alongside Windows/macOS → Restart.

    • Virtual Machine (VM) Installation

    A VM lets you run Linux inside another OS using software like VirtualBox or VMware.

  • Advantages: Safe setup, no disk changes, snapshots possible.
  • Considerations: Slower performance, limited GPU support.
  • Steps (high-level): Install VM software → Create VM → Mount ISO → Install Linux.

Windows Subsystem for Linux (WSL)

WSL allows Linux distributions to run directly inside Windows.

  • Advantages: Easy install, integrates with Windows, great for devs.
  • Considerations: Not a full Linux desktop, limited hardware access.
  • Steps (high-level): Enable WSL → Download Ubuntu from Store → Set up user.

Choosing the Right Option

  • Beginners → Virtual Machine
  • Windows Developers → WSL
  • Full Linux immersion → Dual Boot

Understanding the Boot Process

The boot process in Linux refers to the sequence of steps a computer follows from the moment it is powered on until the operating system is fully loaded and ready to use. Knowing this process helps in troubleshooting startup issues and understanding how Linux initializes its components.

1. Power-On and Firmware Initialization

When you press the power button:

  • The BIOS (Basic Input/Output System) or UEFI (Unified Extensible Firmware Interface) firmware starts running.
  • It performs a Power-On Self-Test (POST) to check hardware components (RAM, CPU, storage).
  • The firmware then looks for a bootable device (HDD, SSD, USB, or network).

2. Boot Loader Stage

The firmware hands control to the boot loader, a small program stored on the boot sector of the disk. Common boot loaders in Linux are:

  • GRUB (GNU GRUB) – the most widely used boot loader.
  • LILO – an older boot loader, now rarely used.

At this stage:

  • You may see a boot menu (choose between Linux, Windows, recovery mode, etc.).
  • The boot loader loads the Linux kernel into memory.

3. Kernel Initialization

Once loaded, the Linux kernel takes over:

  • Initializes CPU, memory, and hardware drivers.
  • Mounts the root filesystem (where Linux system files are stored).
  • Starts the first user-space process.

4. Init System (PID 1)

The kernel starts the init system, which is the first process in user space (always PID 1). Different Linux distributions may use:

  • System V init (older).
  • Upstart (intermediate).
  • systemd (modern, most common).

The init system:

  • Starts background services (networking, logging, display managers).
  • Spawns user login prompts (TTYs, GUI login screen).

5. User Login and Shell

Finally, the system is ready for you:

  • On a server or terminal-only system, you’ll see a text-based login prompt.
  • On a desktop system, a graphical login screen (GDM, LightDM, SDDM) appears.
  • After login, the shell (like bash or zsh) or desktop environment (like GNOME or KDE) starts.

In summary, the Linux boot process flows as:

Firmware (BIOS/UEFI) → Boot Loader (GRUB) → Kernel → Init system (systemd) → User login → Shell/Desktop

The Linux Desktop vs Command Line

When using Linux, you can interact with the system in two main ways: through a Graphical User Interface (GUI), often called the “Linux desktop,” or through the Command Line Interface (CLI), also known as the terminal or shell. Both offer different experiences, and knowing when to use each is a key skill for any Linux user.

Linux Desktop (GUI)

The Linux desktop environment provides a visual interface similar to Windows or macOS. It includes windows, icons, menus, and panels for interacting with applications and settings. Popular desktop environments are GNOME, KDE Plasma, XFCE, and Cinnamon.

  • Advantages:
  • Easy to use for beginners.
  • Familiar experience for users coming from Windows/macOS.
  • Rich ecosystem of desktop apps (web browsers, office suites, multimedia tools).
  • Limitations:
  • Consumes more system resources (CPU, RAM, GPU).
  • Less efficient for repetitive or automation-heavy tasks.
  • Some server-focused Linux distributions don’t include a GUI at all.

Linux Command Line (CLI)

The command line is a text-based interface where you type commands into a terminal. It might feel intimidating at first, but it provides powerful control over the system. The most common shell is Bash, though others like Zsh and Fish are also popular.

  • Advantages:
  • Lightweight and resource-efficient.
  • Extremely powerful for automation, scripting, and remote management.
  • Essential for system administration, development, and troubleshooting.
  • Limitations:
  • Steeper learning curve for beginners.
  • Requires memorizing commands and syntax.
  • No graphical feedback — only text output.

When to Use Which?

  • Use the Desktop GUI when: browsing the web, editing documents, watching videos, or if you’re new to Linux.
  • Use the Command Line when: managing servers, installing software, configuring systems, or performing repetitive tasks efficiently.

In short, the Linux desktop makes Linux user-friendly, while the command line makes Linux powerful. A skilled Linux user learns to combine both, using the GUI for convenience and the CLI

for control.