The installation flow
Installing Linux is a sequence of understandable steps: download an ISO, write it to a USB drive, boot the machine from that USB drive, test the live environment, choose a disk layout, install the base system, install a bootloader, reboot, and complete post-install setup.
The dangerous part is not Linux itself; it is changing disk layout. If you slow down at partitioning and backup anything important, the rest becomes much less intimidating.
ISO files and verification
An ISO file is a disk image containing the installer or live environment. You do not copy the ISO file onto a USB drive like a normal document; you write the image so the USB becomes bootable.
Many distributions publish checksums and signatures. A checksum confirms the file downloaded correctly. A signature can also confirm the image came from the distribution maintainers.
sha256sum ubuntu.iso
# Compare the printed hash with the official hash from the distro.Bootable USB creation
A bootable USB tool writes the ISO image to a USB drive and sets up the structure firmware can boot. Popular graphical tools include Balena Etcher, Fedora Media Writer, GNOME Disks, Rufus, and distribution-specific writers.
On Linux, dd can write images, but it is unforgiving because a wrong target disk can be overwritten. Graphical USB writers reduce that risk for beginners.
BIOS vs UEFI, Secure Boot, and boot order
Firmware is the first code your computer runs. Older systems use BIOS-style boot. Modern systems generally use UEFI, which can read an EFI System Partition and launch bootloaders as files.
Secure Boot checks whether boot components are trusted before running them. Many mainstream distributions support Secure Boot, but some drivers, custom kernels, or smaller distributions may require extra steps.
Boot order tells firmware which device to try first. During installation, you usually choose the USB drive from a one-time boot menu so you do not permanently change normal startup behavior.
The live environment concept
A live environment runs Linux from the USB drive before installation. It lets you test Wi-Fi, display, audio, keyboard, touchpad, suspend, and general hardware support.
The live system is temporary unless the distribution specifically supports persistence. Files created there may disappear after reboot, so use it for testing and installation rather than long-term work.
Partitioning basics
A disk can contain partitions. A partition can contain a filesystem such as ext4 or btrfs, swap space, or a special boot partition. The installer mounts these pieces into the Linux directory tree.
The simplest beginner layout is usually an EFI System Partition plus one root filesystem and optional swap. Separate /home can make reinstalling easier, but it is not required.
| Partition | Purpose | Common notes |
|---|---|---|
| / | Root filesystem containing the operating system tree | Required |
| /home | User files and personal configuration | Optional separate partition |
| swap | Memory overflow and hibernation support | Can be a partition, file, or zram setup |
| EFI System Partition | UEFI bootloader files | Usually FAT32, mounted at /boot/efi |
Bootloader basics and GRUB
The bootloader bridges firmware and the Linux kernel. It finds the kernel, passes boot options, loads initramfs, and starts the boot process.
GRUB is the most common Linux bootloader, especially for dual-boot systems. Some distributions use systemd-boot on UEFI systems. The exact bootloader matters less than understanding that it sits before the kernel.
Single boot vs dual boot
Single boot means Linux owns the machine's boot path. Dual boot means Linux and another operating system share the disk or machine, and the bootloader or firmware lets you choose at startup.
Dual boot increases planning needs. You should shrink existing partitions from the operating system that owns them, leave free unallocated space, disable fast startup features that leave filesystems half-open, and make a recovery drive before changing partitions.
- Back up important files first.
- Know whether the machine boots in UEFI or legacy mode.
- Keep the existing EFI System Partition unless you know exactly why not.
- Leave enough free space for both systems to update comfortably.
Installing in a virtual machine
A virtual machine is the safest way to learn installation because the guest system sees a virtual disk instead of your real disk. Mistakes stay inside the VM file.
VM installation teaches the same concepts: ISO, virtual firmware, virtual disk, partitioning, bootloader, user creation, package updates, and guest tools.
Installation risks and common mistakes
Most installation disasters come from choosing the wrong disk, misunderstanding erase options, interrupting partition changes, or assuming dual boot is risk-free.
Read every storage screen carefully. If an installer says it will erase a disk, believe it. If you are unsure, stop and identify disks with size, model, and existing partitions.
- Do not install to a disk until backups are complete.
- Do not format an EFI partition unless you understand the current boot setup.
- Do not mix legacy BIOS and UEFI installs casually.
- Do not assume Wi-Fi, GPU, fingerprint reader, or sleep support without testing.
Post-install steps and recovery concepts
After installation, update packages, install needed drivers or codecs, confirm backups, set up a firewall if appropriate, enable automatic security updates if your distribution supports them, and record how to enter firmware and recovery menus.
Recovery usually means booting a live USB, mounting the installed system, inspecting logs or filesystems, repairing the bootloader, or chrooting into the installed system. You do not need to memorize every repair command immediately, but you should know recovery is possible.