LFCA 6 🐧 Installing Linux — Overview and Requirements - KandZ

Installing Linux is not one task — it’s a family of tasks, each with different requirements, tools, and trade-offs. A bare-metal install on a laptop is a different process from provisioning a cloud VM, which is different again from running a container. The LFCA exam expects you to understand the concepts behind each install method, the requirements they share, and the decisions you make before you touch a keyboard. This chapter covers the landscape: what an installation actually does, what you need before you start, and how the major install methods compare.

Key point: Every Linux installation, regardless of method, does the same three things: places the kernel and system files on storage, configures the bootloader to find them, and sets up the initial system state. The methods differ in where and how, not in what. Understand the three jobs, and every install method becomes a variation on a theme.

What an installation actually does

An installation is the process of taking a Linux distribution and making it bootable and usable on a target system. It does three jobs.

1. Places the system files on storage. The kernel, the bootloader, the userland tools, the package manager, and the default configuration all need to be written to disk. This is often called “unpacking the root filesystem.”

2. Configures the bootloader. The machine needs a way to find and start the kernel at boot. On BIOS systems, that’s typically GRUB in the MBR. On UEFI systems, it’s GRUB or systemd-boot in the EFI System Partition.

3. Sets up the initial system state. Users, hostname, timezone, locale, network configuration, and often the initial package set. This varies by distribution and install method.

What every installation must decide:

Decision	Options
Where to install	Entire disk, partition, VM disk, cloud volume
Filesystem	ext4, Btrfs, XFS, ZFS
Partitioning	Automatic, manual, LVM, encrypted
Bootloader	GRUB, systemd-boot, other
Desktop	None, minimal, full
Users	Root only, additional users
Network	DHCP, static, none

What an installation does not do:

It doesn’t configure every service — that’s post-install
It doesn’t harden the system — that’s separate
It doesn’t install every tool you’ll need — that’s the package manager’s job after
It doesn’t back up existing data — that’s your responsibility before

Why this matters: The exam tests the concepts, not the exact clicks. Knowing that every install does the same three jobs means you can reason about any installation — bare-metal, VM, cloud, container — without memorizing each one’s steps.

Requirements — hardware

Every Linux installation has minimum hardware requirements. The specific numbers vary by distribution and desktop environment.

Minimum vs recommended:

Resource	Minimum	Recommended
CPU	1 GHz, 64-bit	2+ GHz, multi-core
RAM	512 MB – 1 GB (server)	2–4 GB (server), 8+ GB (desktop)
Disk	5–10 GB (server)	20+ GB (desktop), more for data
Network	Optional	Recommended
Display	None (server)	Required (desktop)

These numbers depend heavily on the distro and use case:

Alpine Linux runs in 128 MB RAM and a few hundred MB of disk
Ubuntu Server typically wants 1 GB RAM and 5 GB disk minimum
Ubuntu Desktop wants 4 GB RAM and 25 GB disk
Fedora Workstation wants similar to Ubuntu Desktop
Enterprise distros (RHEL, SLES) have higher minimums for supported configurations

Architecture matters:

x86_64 (amd64) — the dominant architecture for servers, desktops, and cloud
ARM64 (aarch64) — Raspberry Pi, AWS Graviton, Apple Silicon via VMs
32-bit x86 — mostly obsolete but still supported by some distros
Other — RISC-V, POWER, s390x for specific hardware

Firmware:

BIOS — legacy firmware, MBR partitioning
UEFI — modern firmware, GPT partitioning, Secure Boot support
UEFI with Secure Boot — requires signed bootloaders; most distros support this

Why minimums matter: A machine below minimum specs won’t install or won’t run well. A server doesn’t need a desktop environment, so its minimums are lower. A desktop needs graphics, so its minimums are higher. Matching the distro to the hardware is the first decision.

Why the exam tests requirements: Choosing the wrong distro for the hardware is a common mistake. A beginner might try to install a heavy desktop distro on an old laptop and fail. Knowing minimums lets you pick a distro that actually runs. It’s the same reasoning as choosing a distro in Chapter 5 — requirements first, then options.

Requirements — preparation

Before installing, you need three things prepared.

1. A backup of existing data. An install that repartitions the disk wipes everything on it. If the machine has data you care about, back it up first.

2. Installation media or access. Depending on the method:

A bootable USB drive (bare-metal)
An ISO in a VM (virtualization)
Cloud console access (cloud)
Docker or container runtime (container)

3. A plan for the disk. Automatic partitioning is fine for most users. Manual partitioning is needed when:

Dual-booting with another OS
Preserving existing data partitions
Using LVM, encryption, or a specific layout
Installing on a cloud volume with specific mount points

What to gather before starting:

Item	Why
Backup of existing data	Install may wipe the disk
Installation media	USB, ISO, or cloud access
Network details	Wi-Fi password or Ethernet
Hostname	To identify the machine
User credentials	Username, password
Time zone	For correct timestamps
Disk layout plan	If not using automatic

For cloud installs:

Cloud account and credentials
Region and availability zone
Instance type and size
SSH key pair
VPC and security group configuration

For VMs:

Hypervisor installed (VirtualBox, VMware, KVM, Hyper-V)
ISO or cloud image downloaded
VM configured with adequate CPU, RAM, and disk

Why preparation matters: Most install failures come from missing preparation — no backup, no bootable media, wrong firmware mode, no network. Five minutes of preparation prevents hours of troubleshooting. The exam tests this indirectly: scenario questions often involve “what’s the first step?”

Installation methods overview

There are four main methods. Each serves a different scenario.

1. Bare-metal installation

Installing Linux directly on a physical machine’s disk. The most traditional method.

Requires: Bootable USB, physical access
Used for: Desktops, laptops, physical servers, homelab
Installer runs: Locally, on the target machine
Disk: The physical disk
Persistence: Full — the OS is on the hardware

2. Virtual machine installation

Installing Linux inside a VM running on a hypervisor.

Requires: Hypervisor (VirtualBox, VMware, KVM, Hyper-V), ISO or cloud image
Used for: Development, testing, learning, some production workloads
Installer runs: Inside the VM
Disk: A virtual disk file
Persistence: Full, but virtualized

3. Cloud installation

Provisioning a Linux instance from a cloud provider.

Requires: Cloud account, SSH key, image selection
Used for: Production workloads, scalable infrastructure
Installer runs: Provider’s tooling provisions the image
Disk: A cloud volume (EBS, persistent disk, etc.)
Persistence: Full, but managed by the provider

4. Container base image

Starting from a Linux base image inside a container.

Requires: Container runtime (Docker, Podman, containerd)
Used for: Applications, microservices, CI/CD
Installer runs: Pulls a pre-built image
Disk: Overlay filesystem on the host
Persistence: Ephemeral by default

Comparison:

Aspect	Bare-metal	VM	Cloud	Container
Physical access	✅	⚠️ to host	❌	❌
Setup time	30–60 min	20–40 min	1–5 min	Seconds
Persistence	✅	✅	✅	⚠️
Cost	Hardware	Host hardware	Per hour	Host
Use case	Production, personal	Dev, test	Scalable prod	Microservices

Why multiple methods exist: They serve different needs. A laptop needs a bare-metal install. Testing needs a VM. Scalable production needs the cloud. Microservices need containers. The method matches the use case — not the other way around.

Why the exam covers all four: Modern IT uses all four methods. A sysadmin might install bare-metal for a database server, spin up a VM for testing, provision a cloud instance for a web app, and deploy a container for a microservice — all in one week. Knowing each method’s shape is expected.

Choosing a method

The decision tree is simple.

Choose bare-metal when:

You’re installing on physical hardware you own or control
The machine is the destination — laptop, desktop, homelab server
You need full disk access and performance
You’re not going to migrate the system

Choose a VM when:

You’re learning or testing
You need a safe sandbox
You want to snapshot and revert
You’re running multiple OSes on one machine

Choose cloud when:

You need scalable, on-demand infrastructure
The workload has variable load
You want managed services around the VM
You’re deploying for production

Choose a container when:

You’re deploying an application, not a system
You need portability and fast startup
You’re building microservices
You want a minimal, reproducible image

Combinations are common:

A physical host running VMs for various purposes
A cloud VM running containers
A bare-metal server running containers for production

What you’ll see in practice:

Context	Common method
Personal laptop	Bare-metal
Dev environment	VM or container
Production server	Cloud or bare-metal
Microservice	Container
CI/CD runner	Container or ephemeral VM
Learning Linux	VM
Testing before upgrade	VM
Homelab	Bare-metal + VMs

Why method matters: Each method has different tooling, preparation, and constraints. The install itself is conceptual — the same three jobs — but the execution is specific. Knowing which method fits which scenario is the practical skill.

Requirements by method

The specific requirements shift by install method.

Bare-metal:

Physical machine with supported CPU and enough RAM/disk
Bootable USB drive (usually 8+ GB)
BIOS/UEFI access to change boot order
Network for downloading packages during install
Backup of existing data
UEFI vs BIOS compatibility

VM:

Hypervisor installed (VirtualBox, VMware, KVM, Hyper-V)
Host with enough resources for the VM
ISO or cloud image
Allocated VM resources (CPU, RAM, disk)
Network mode (NAT, bridged, host-only)

Cloud:

Cloud account (AWS, Azure, GCP, etc.)
Credentials with permission to create instances
SSH key pair
Region/zone selection
Instance type (CPU, RAM, GPU options)
Storage volume size
VPC and security group rules

Container:

Container runtime (Docker, Podman, containerd)
Host with enough resources
Container image reference (e.g., ubuntu:24.04)
Network configuration
Volume mounts for persistent data
Environment variables for configuration

Common to all:

Understand the use case
Know the persistence requirements
Plan for updates and security

What the exam tests: Not the clicks for each method, but the requirements — what each method needs, and which method fits which scenario. Match the method to the need.

Why requirements vary by method: A cloud install needs a credit card and an SSH key. A bare-metal install needs a USB and physical access. A VM needs a hypervisor. A container needs a runtime. The core requirements — CPU, RAM, disk, network — are the same, but the specifics shift. The exam expects you to know the differences.

Post-installation basics

After installation, every Linux system needs some baseline configuration.

Common post-install tasks:

Task	Purpose
Update packages	Get security patches
Create users	Avoid working as root
Set hostname	Identify the machine
Configure time zone	Correct timestamps
Configure locale	Correct language and formats
Enable firewall	Basic security
Set up SSH	Remote access
Install essential tools	Editor, git, curl, etc.

Typical commands:

# Update everything
sudo apt update && sudo apt upgrade    # Debian family
sudo dnf upgrade                        # Red Hat family
sudo zypper update                      # SUSE family
sudo pacman -Syu                        # Arch

# Set hostname
sudo hostnamectl set-hostname my-server

# Set time zone
sudo timedatectl set-timezone Europe/Oslo

# Create a user
sudo useradd -m -s /bin/bash alice
sudo passwd alice

# Add to sudo (Debian family)
sudo usermod -aG sudo alice

# Add to sudo (Red Hat family)
sudo usermod -aG wheel alice

Cloud-specific post-install:

SSH key is often the only initial credential
No root password by default
First user has sudo access
Cloud-init may run first-boot scripts
Instance metadata service provides configuration

VM-specific post-install:

Often a full desktop or server setup
Snapshot before major changes
Shared folders or clipboard with the host
Network sharing via NAT or bridged mode

Container-specific post-install:

Nothing — containers are ephemeral
Configuration via environment variables or mounted files
Data persistence via volumes
Not designed for interactive use

Why post-install matters: A freshly installed system is minimal and unconfigured. Post-install is where you make it useful, secure, and consistent. Skipping it leaves the system vulnerable and inefficient.

Why the exam covers this: Installation isn’t the end — it’s the start. The exam expects you to know the baseline steps after install: update, users, hostname, timezone, firewall, SSH. These are the first tasks on any new system, in any method.

A full example

Walking through preparation for a bare-metal install.

# ============================================
# STEP 1: CHECK THE HARDWARE
# ============================================

# CPU architecture
uname -m
# [ x86_64 ]

# Memory
free -h
# [               total        used        free ]
# [ Mem:           16Gi        2.1Gi        13Gi ]

# Disk
lsblk
# [ NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS ]
# [ sda      8:0    0 500G  0 disk                ]

# Firmware
[ -d /sys/firmware/efi ] && echo "UEFI" || echo "BIOS"
# [ UEFI ]

# ============================================
# STEP 2: BACK UP EXISTING DATA
# ============================================

# Before repartitioning, back up anything important
sudo rsync -av --progress /home/ /mnt/backup/home/

# ============================================
# STEP 3: DOWNLOAD THE ISO
# ============================================

# Verify the checksum after downloading
sha256sum ubuntu-24.04-desktop-amd64.iso
# [ e240e4b1... ubuntu-24.04-desktop-amd64.iso ]

# Compare with the official checksum from the distro site

# ============================================
# STEP 4: CREATE BOOTABLE USB
# ============================================

# On Linux
sudo dd if=ubuntu-24.04-desktop-amd64.iso of=/dev/sdb bs=4M status=progress

# On macOS
# sudo dd if=ubuntu-24.04-desktop-amd64.iso of=/dev/rdiskN bs=4m

# On Windows — use Rufus or balenaEtcher

# ============================================
# STEP 5: PLAN THE DISK LAYOUT
# ============================================

# If wiping the disk — automatic is fine
# If dual-booting — plan partitions
# If using LUKS + LVM — plan volume groups

# Example layout for a server:
# /boot/efi   →  512 MB (EFI System Partition)
# /boot       →  1 GB (kernel and initramfs)
# /           →  30 GB (root)
# /home       →  rest (user data)
# swap        →  = RAM (or 2 GB min)

# ============================================
# STEP 6: GATHER NETWORK INFO
# ============================================

# Wi-Fi SSID and password
# Or Ethernet is available
# Hostname choice
# User credentials

# ============================================
# STEP 7: ENTER BIOS/UEFI
# ============================================

# Reboot and press the setup key (varies by vendor)
# F2, F10, F12, Del, Esc
# Set boot order to USB first
# Ensure UEFI mode if installing 64-bit Linux

# ============================================
# STEP 8: BOOT FROM USB
# ============================================

# The installer starts
# Follow prompts:
#   - Language, keyboard
#   - Network
#   - Disk layout
#   - User creation
#   - Package selection

# ============================================
# STEP 9: FIRST BOOT
# ============================================

# After install, remove the USB and reboot
# Log in with the user created during install

# ============================================
# STEP 10: POST-INSTALL
# ============================================

sudo apt update && sudo apt upgrade -y
sudo timedatectl set-timezone Europe/Oslo
sudo hostnamectl set-hostname my-server
sudo apt install -y curl git vim ufw
sudo ufw enable

This sequence works for a bare-metal install. The VM and cloud versions are similar but with virtualization or provider tooling replacing USB and BIOS steps.

Why this walkthrough: It covers preparation, media creation, planning, and post-install — the whole flow. For the exam, remember the concepts: check hardware, back up, plan the disk, create the media, boot, install, configure. The method changes; the shape doesn’t.

Complete Example Session

# ============================================
# PART 1: HARDWARE CHECKS
# ============================================

echo "=== Architecture ==="
uname -m
# [ x86_64 ]

echo "=== CPU ==="
lscpu | grep -E 'Model name|CPU\(s\)|Architecture'
# [ Model name:  AMD Ryzen 5 5600X ]
# [ CPU(s):      12 ]
# [ Architecture: x86_64 ]

echo "=== Memory ==="
free -h
# [               total   used   free ]
# [ Mem:           16Gi   2.1Gi  13Gi ]

echo "=== Disk ==="
lsblk
# [ NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS ]
# [ sda      8:0    0 500G  0 disk                ]

echo "=== Firmware ==="
[ -d /sys/firmware/efi ] && echo "UEFI" || echo "BIOS"
# [ UEFI ]

# ============================================
# PART 2: DISTRO CHOICE
# ============================================

cat << 'EOF'
Choose based on use case:

Personal laptop → Ubuntu LTS / Fedora / Mint
Server         → Ubuntu LTS / Debian / RHEL
Cloud          → Ubuntu LTS / Amazon Linux
Container      → Alpine / Debian slim
Learning       → Ubuntu first, then Arch/Debian
EOF

# ============================================
# PART 3: PREPARE INSTALL MEDIA
# ============================================

# Verify the ISO checksum
# Create a USB installer
# Test that the USB boots

# ============================================
# PART 4: PLAN PARTITIONS
# ============================================

cat << 'EOF'
Sample partition plan:

Single-disk desktop:
  /boot/efi   512 MB   FAT32 (EFI)
  /           30 GB    ext4
  /home       rest     ext4
  swap        = RAM    swap

Server:
  /boot/efi   512 MB   FAT32 (EFI)
  /boot       1 GB     ext4
  /           30 GB    ext4
  /var        20 GB    ext4
  /home       rest     ext4
  swap        2 GB     swap

Encrypted:
  LUKS container holding LVM volume group
  LVM logical volumes for /, /home, swap
EOF

# ============================================
# PART 5: INSTALL
# ============================================

# Bare-metal:
#   - Boot from USB
#   - Follow installer prompts
#   - Reboot

# VM:
#   - Create VM in hypervisor
#   - Attach ISO
#   - Start and follow installer

# Cloud:
#   - Launch instance from image
#   - Select size, region, SSH key
#   - Wait for boot

# Container:
#   - docker run -it ubuntu:24.04 bash

# ============================================
# PART 6: POST-INSTALL
# ============================================

echo "=== Update ==="
# sudo apt update && sudo apt upgrade -y

echo "=== Hostname ==="
# sudo hostnamectl set-hostname myserver

echo "=== Timezone ==="
# sudo timedatectl set-timezone Europe/Oslo

echo "=== User ==="
# sudo useradd -m -s /bin/bash alice
# sudo passwd alice
# sudo usermod -aG sudo alice

echo "=== Firewall ==="
# sudo ufw allow OpenSSH
# sudo ufw enable

echo "=== SSH ==="
# sudo systemctl enable --now ssh

echo "=== Essentials ==="
# sudo apt install -y curl git vim htop

# ============================================
# PART 7: VERIFY
# ============================================

echo "=== Kernel ==="
uname -r

echo "=== Distro ==="
cat /etc/os-release | head -2

echo "=== Bootloader ==="
ls /boot/efi/EFI/ 2>/dev/null

echo "=== Installed packages ==="
dpkg -l | wc -l

Each step matches a concept from this chapter — hardware check, distro choice, media preparation, partitioning, installation, post-install, verification.

Why this exercise helps: It walks through a complete install flow without committing to a specific distribution. The commands are conceptual — the exact syntax varies by distro. Understanding the flow is what the exam tests.

Quick Reference

Installation Does Three Jobs

Job	Result
Place system files	Kernel, userland, config on disk
Configure bootloader	Machine can boot
Set initial state	Users, hostname, network

Minimum Hardware (Typical)

Use case	CPU	RAM	Disk
Minimal server	1 GHz	512 MB	5 GB
Standard server	2 GHz+	2 GB	20 GB
Desktop	2 GHz+	4 GB	25 GB
Container base	Any	Shared	Shared

Firmware Options

Firmware	Partitioning	Boot
BIOS	MBR	GRUB in MBR
UEFI	GPT	GRUB/systemd-boot in ESP
UEFI + Secure Boot	GPT	Signed bootloader

Install Methods

Method	Prep	Setup time	Use case
Bare-metal	USB	30–60 min	Production, personal
VM	Hypervisor + ISO	20–40 min	Dev, test, learning
Cloud	Cloud account	1–5 min	Scalable prod
Container	Runtime	Seconds	Microservices

Preparation Checklist

Item	Why
Backup existing data	Install may wipe the disk
Installation media	USB, ISO, or cloud access
Network details	Wi-Fi password or Ethernet
Hostname	Identify the machine
User credentials	Username and password
Time zone	Correct timestamps
Disk plan	If not using automatic

Partition Layouts (Example)

Mount	Size	Purpose
`/boot/efi`	512 MB	EFI System Partition (UEFI only)
`/boot`	1 GB	Kernel and initramfs
`/`	20–30 GB	Root filesystem
`/home`	Rest	User data
`/var`	10–20 GB	Logs, databases (servers)
`swap`	= RAM or 2 GB	Swap space

Filesystem Options

FS	Use case
ext4	Default, widely supported
XFS	Large files, high performance
Btrfs	Snapshots, subvolumes
ZFS	Advanced features (data integrity, snapshots)
FAT32	EFI System Partition

Bootloader Options

Bootloader	Firmware	Notes
GRUB	BIOS, UEFI	Standard
systemd-boot	UEFI	Simpler, modern
rEFInd	UEFI	Alternative

Cloud Instance Setup

Requirement	Detail
Account	AWS, Azure, GCP, etc.
Credentials	IAM user or role
SSH key	For initial access
Region	Geographic location
Instance type	CPU, RAM, GPU
Storage	EBS, persistent disk, etc.
Security group	Firewall rules
VPC	Network configuration

Container Setup

Requirement	Detail
Runtime	Docker, Podman, containerd
Image	`ubuntu:24.04`, `alpine:latest`
Network	Bridge, host, custom
Volume	For persistence
Env vars	Configuration

Post-Install Tasks

Task	Command (Debian)	Command (Red Hat)
Update	`apt update && apt upgrade`	`dnf upgrade`
Hostname	`hostnamectl set-hostname`	same
Time zone	`timedatectl set-timezone`	same
Add user	`useradd -m -s /bin/bash`	same
Sudo group	`usermod -aG sudo`	`usermod -aG wheel`
Firewall	`ufw enable`	`firewall-cmd`
SSH	`systemctl enable ssh`	`systemctl enable sshd`

Common Install Issues

Issue	Cause	Fix
Won’t boot from USB	Boot order	Change BIOS/UEFI order
“No bootable device”	Wrong firmware mode	Match UEFI/BIOS to ISO
Installer can’t find disk	RAID/driver	Enable AHCI or drivers
No network	Wi-Fi firmware	Use Ethernet or install firmware
Secure Boot blocks	Unsigned bootloader	Disable Secure Boot or use signed
Disk too small	Insufficient space	Resize or free space

Choosing a Method

Need	Method
Physical laptop/desktop	Bare-metal
Sandbox / testing	VM
Scalable production	Cloud
Microservice	Container
Homelab	Bare-metal + VMs
CI/CD runner	Container or ephemeral VM
Learning	VM

Best Practices

✅ Do This:

# Back up existing data before installing
rsync -av /home/ /mnt/backup/home/                     # ✅

# Check hardware compatibility
lscpu; free -h; lsblk                                  # ✅

# Verify the ISO checksum
sha256sum ubuntu-24.04-desktop-amd64.iso               # ✅

# Test the USB before installing
# Boot from USB and use "Try" mode                     # ✅

# Plan the disk layout
# Automatic for most users; manual for dual-boot      # ✅

# Note the firmware mode
[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS     # ✅

# Update immediately after install
sudo apt update && sudo apt upgrade -y                 # ✅

# Create a non-root user with sudo
sudo useradd -m -s /bin/bash alice                     # ✅

# Enable a firewall
sudo ufw enable                                        # ✅

# Snapshot a VM before major changes
# Use hypervisor's snapshot feature                    # ✅

# Use cloud-init for cloud instances
# User data scripts for first-boot config              # ✅

❌ Don’t Do This:

# Don't install without a backup
# Repartitioning wipes the disk                        # ❌

# Don't skip checksum verification
# A corrupted ISO produces a broken install            # ❌

# Don't install in the wrong firmware mode
# UEFI-only ISO on BIOS mode → won't boot              # ❌

# Don't ignore hardware minimums
# Too little RAM → installer crashes                   # ❌

# Don't work as root permanently
# Create a user with sudo instead                      # ❌

# Don't skip updates
# A fresh install has vulnerabilities until patched    # ❌

# Don't leave the firewall off
# Enable it before connecting to a network             # ❌

# Don't assume the install is done
# Post-install configuration is required               # ❌

# Don't use the same partitioning for every use case
# Desktop, server, and containers have different needs # ❌

Common Pitfalls

Pitfall	Problem	Solution
No backup	Data loss on repartition	Back up first
Wrong firmware mode	Won’t boot	Match UEFI/BIOS to ISO
Bad ISO	Failed install	Verify checksum
Insufficient disk	Install fails	Check minimums
No network	Can’t fetch packages	Plan network access
Working as root	Security risk	Create a user
Skipping updates	Vulnerabilities	Update immediately
No firewall	Exposed	Enable before connecting
Wrong filesystem	Performance/feature mismatch	Choose deliberately
Missing drivers	Hardware doesn’t work	Install firmware post-setup

Real-World Examples

1. Check architecture

uname -m
# x86_64

2. Check memory

free -h

3. Check disk

lsblk

4. Check firmware

[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS

5. Verify ISO checksum

sha256sum ubuntu-24.04-desktop-amd64.iso

6. Create a bootable USB

sudo dd if=ubuntu-24.04-desktop-amd64.iso of=/dev/sdb bs=4M status=progress

7. Boot from USB

Change BIOS/UEFI boot order; select USB.

8. Partition plan

/boot/efi  512M
/          30G
/home      rest
swap       = RAM

9. Install via VM

Create VM in VirtualBox, attach ISO, start.

10. Install via cloud

Launch EC2 instance with Ubuntu AMI, SSH key, security group.

11. Install container base

docker run -it ubuntu:24.04 bash

12. Update after install

sudo apt update && sudo apt upgrade -y

13. Set hostname

sudo hostnamectl set-hostname myserver

14. Set time zone

sudo timedatectl set-timezone Europe/Oslo

15. Create user

sudo useradd -m -s /bin/bash alice

16. Grant sudo

# Debian
sudo usermod -aG sudo alice

# Red Hat
sudo usermod -aG wheel alice

17. Enable firewall

sudo ufw enable

18. Enable SSH

sudo systemctl enable --now ssh

19. Snapshot a VM

Use hypervisor snapshot before major changes.

20. Cloud-init for first boot

Provide user data on instance launch.

Visual: Installation Does Three Jobs

┌──────────────────────────────────────────────┐
│  Installer                                   │
│                                              │
│  1. Place system files ──► disk              │
│  2. Configure bootloader ──► boot            │
│  3. Set initial state ──► users, hostname    │
│                                              │
└──────────────────────────────────────────────┘
                  │
                  ▼
┌──────────────────────────────────────────────┐
│  Bootable, usable Linux system               │
│                                              │
└──────────────────────────────────────────────┘

Visual: Four Installation Methods

┌──────────────────────────────────────────────┐
│  Bare-metal                                  │
│  ─ physical disk                             │
│  ─ bootable USB                              │
│  ─ physical access                           │
│                                              │
├──────────────────────────────────────────────┤
│  Virtual machine                             │
│  ─ virtual disk                              │
│  ─ hypervisor                                │
│  ─ ISO image                                 │
│                                              │
├──────────────────────────────────────────────┤
│  Cloud                                       │
│  ─ provider tooling                          │
│  ─ SSH key                                   │
│  ─ managed by provider                       │
│                                              │
├──────────────────────────────────────────────┤
│  Container                                   │
│  ─ runtime + image                           │
│  ─ ephemeral                                 │
│  ─ layered filesystem                        │
│                                              │
└──────────────────────────────────────────────┘

Visual: Preparation Flow

┌──────────────────────────────────────────────┐
│  1. Back up existing data                    │
│                                              │
│  2. Check hardware compatibility             │
│     ─ CPU, RAM, disk, firmware               │
│                                              │
│  3. Choose a distribution                    │
│                                              │
│  4. Download the ISO                         │
│                                              │
│  5. Verify checksum                          │
│                                              │
│  6. Create bootable media                    │
│                                              │
│  7. Plan the disk layout                     │
│                                              │
│  8. Gather network details                   │
│                                              │
│  9. Note the boot firmware                   │
│                                              │
│ 10. Install                                  │
│                                              │
│ 11. Post-install setup                       │
│                                              │
└──────────────────────────────────────────────┘

Visual: Typical Partition Layout

┌──────────────────────────────────────────────┐
│  /boot/efi    512 MB   FAT32 (EFI System)    │
│                                              │
│  /boot        1 GB     ext4 (kernel)         │
│                                              │
│  /            30 GB    ext4 (root)           │
│                                              │
│  /home        Rest     ext4 (user data)      │
│                                              │
│  swap         = RAM    swap                  │
│                                              │
└──────────────────────────────────────────────┘

┌──────────────────────────────────────────────┐
│  Encrypted (LUKS + LVM)                      │
│                                              ││  /dev/sda1    512 MB  EFI (unencrypted)      │
│  /dev/sda2    Rest    LUKS container         │
│       └── LVM volume group                   │
│           ├── lv_root  →  /                  │
│           ├── lv_home  →  /home              │
│           └── lv_swap  →  swap               │
│                                              │
└──────────────────────────────────────────────┘

Visual: Firmware Modes

┌──────────────────────────────────────────────┐
│  BIOS (legacy)                               │
│  ─ MBR partitioning                          │
│  ─ GRUB in MBR                               │
│  ─ Max 2 TB boot disk                        │
│  ─ 4 primary partitions                      │
│                                              │
└──────────────────────────────────────────────┘

┌──────────────────────────────────────────────┐
│  UEFI (modern)                               │
│  ─ GPT partitioning                          │
│  ─ Bootloader in EFI System Partition        │
│  ─ Supports > 2 TB disks                     │
│  ─ Secure Boot option                        │
│                                              │
└──────────────────────────────────────────────┘

┌──────────────────────────────────────────────┐
│  UEFI + Secure Boot                          │
│  ─ Signed bootloader required                │
│  ─ Some distros support out of the box       │
│  ─ Disable for unsigned kernels              │
│                                              │
└──────────────────────────────────────────────┘

Visual: Method Decision Tree

┌──────────────────────────────────────────────┐
│  Physical machine?                           │
│       │                                      │
│       ├── Yes ──► Bare-metal                 │
│       │                                      │
│       └── No                                  │
│            │                                 │
│            ├── Need scalability? ──► Cloud   │
│            │                                 │
│            ├── Need isolation? ──► VM        │
│            │                                 │
│            └── Deploying an app? ──► Container│
│                                              │
└──────────────────────────────────────────────┘

Visual: Post-Install Checklist

┌──────────────────────────────────────────────┐
│  Immediately after install:                  │
│                                              │
│  [ ] Update packages                         │
│  [ ] Create a non-root user                  │
│  [ ] Grant sudo                              │
│  [ ] Set hostname                            │
│  [ ] Set time zone                           │
│  [ ] Enable firewall                         │
│  [ ] Enable SSH if remote                    │
│  [ ] Install essential tools                 │
│                                              │
│  For servers:                                │
│  [ ] Harden SSH                              │
│  [ ] Configure logs                          │
│  [ ] Set up monitoring                       │
│  [ ] Configure backups                       │
│                                              │
└──────────────────────────────────────────────┘

Visual: Common Install Issues

┌──────────────────────────────────────────────┐
│  Won't boot from USB                         │
│  ─ boot order                                │
│  ─ USB not bootable                          │
│  ─ Secure Boot blocking                      │
│                                              │
│  No bootable device after install            │
│  ─ wrong firmware mode                       │
│  ─ bootloader not installed                  │
│  ─ MBR/GPT mismatch                          │
│                                              │
│  Installer can't find disk                   │
│  ─ RAID mode not supported                   │
│  ─ drivers missing                           │
│                                              │
│  No network during install                   │
│  ─ Wi-Fi firmware missing                    │
│  ─ wrong network config                      │
│                                              │
└──────────────────────────────────────────────┘

Visual: Requirements by Method

┌──────────────────────────────────────────────┐
│  Bare-metal                                  │
│  ─ Physical machine                          │
│  ─ USB drive                                 │
│  ─ BIOS/UEFI access                          │
│  ─ Backup                                    │
│                                              │
├──────────────────────────────────────────────┤
│  VM                                          │
│  ─ Hypervisor                                │
│  ─ Host resources                            │
│  ─ ISO                                       │
│                                              │
├──────────────────────────────────────────────┤
│  Cloud                                       │
│  ─ Account + credentials                     │
│  ─ SSH key                                   │
│  ─ Region and instance type                  │
│                                              │
├──────────────────────────────────────────────┤
│  Container                                   │
│  ─ Container runtime                         │
│  ─ Image                                     │
│  ─ Volume for persistence                    │
│                                              │
└──────────────────────────────────────────────┘

Summary

Concept	Meaning
Installation	Place files, configure boot, set state
Bare-metal	Install on physical hardware
VM	Install in virtualized environment
Cloud	Provision from provider image
Container	Start from base image
Firmware	BIOS (legacy) or UEFI (modern)
Partitioning	MBR (BIOS) or GPT (UEFI)
Bootloader	GRUB, systemd-boot
Minimum specs	Varies by distro and use case
Post-install	Update, users, security

Key takeaways:

Every Linux installation does three jobs — place files, configure boot, set state
Four install methods — bare-metal, VM, cloud, container — each suited to a different scenario
Minimum hardware depends on the distro and use case — servers can run on less
Firmware is BIOS or UEFI — UEFI is modern, supports GPT and Secure Boot
Preparation matters — back up, verify media, plan the disk, gather network details
Partitioning can be automatic or manual — manual for dual-boot, encryption, or specific layouts
Filesystem choice — ext4 default, XFS for scale, Btrfs for snapshots, FAT32 for EFI
Cloud installs need an account, SSH key, region, instance type, security group
Container installs need a runtime and image — no full system, just an app environment
Post-install is required — update, create users, set hostname and timezone, enable firewall
Match the install method to the use case — physical machine, sandbox, production, or microservice

Remember: Installing Linux is a concept before it’s a procedure. Every method — bare-metal, VM, cloud, container — does the same three jobs: put the system on storage, make it bootable, set up the initial state. The steps differ; the shape doesn’t. Prepare carefully, choose the method that fits the scenario, and finish with the post-install basics. That’s what the exam tests — not the clicks, but the concepts.

linux, installation, distros, bootloader

Stop using slow, ad-bloated tool sites! 🤮

🔎 Search “KandZ Tools” on Google to use many professional utilities for free.

KandZ.me is the ultimate minimalist hub for:
✅ Finance (Mortgage, Interest, Inflation)
✅ Tech (Base64, JSON, Dev Suite, IP)
✅ Health (BMI, BMR, TDEE)
✅ Productivity (Timer, Workspace, QR)

⚡️ Fast & Private
🔒 No data leaves your device
💎 100% Free

🔗 Use it now: https://tools.kandz.me
🔖 Bookmark it—you’ll need it later!