Awesome question—let’s unpack these boot parameters step by step, since they’re key to understanding how your system fires up.

1. The boot and root Kernel Options: Core Basics #

First, let’s clarify what each parameter does at a fundamental level:

• root parameter: This is a universal kernel parameter (used across nearly all distros) that tells the kernel which device to mount as the root filesystem (/)—the top-level directory where all system files and processes live. Examples include root=/dev/sda1 (pointing to a physical partition) or root=UUID=abc123-def456 (using a unique identifier for reliability, since device names can change between boots). Without this, the kernel can’t find the system’s core files and will drop you into an emergency shell or fail to boot entirely.
• boot parameter: Unlike root, this isn’t a standard kernel-wide parameter. It’s a distro-specific flag that triggers special initialization behavior. Think of it as a signal to the initramfs (initial RAM filesystem) or boot scripts to load a specific set of tools or follow a non-standard boot flow. boot=casper is a perfect example of this in action for Ubuntu.

2. What Does boot=casper Do in Ubuntu’s GRUB? #

boot=casper is the magic flag that enables Ubuntu’s live system functionality (whether you’re booting from a USB, CD, or ISO file). Here’s what it does:

• It tells the initramfs to use the casper framework—a set of scripts designed specifically for live environments.
• Casper mounts the Ubuntu ISO’s system files into a temporary in-memory filesystem (or a temporary disk partition) instead of installing them to your local hard drive.
• It handles live-system specifics: creating a temporary user session, loading hardware drivers on the fly, and ensuring no changes are written to your local storage (unless you choose to install the system).
• In short: without boot=casper, your Ubuntu Live USB/CD wouldn’t run as a "try before you install" environment—it’d just fail to find a root filesystem.

3. The Exact Role of the root Parameter #

To elaborate on root (since it’s critical for all boot scenarios):

• Right after the kernel loads into memory, its first major task is to mount the root filesystem. The root parameter gives it the exact location to do this.
• For installed systems (not live), root points to the partition where you installed your OS (e.g., root=UUID=xyz789). Once mounted, the kernel launches the init system (like systemd) to start all user-space services, daemons, and the desktop environment.
• For live systems, root might still be set, but it’s often overridden by the boot=casper logic to point to the live image instead of a local disk.

4. Equivalent Settings in Other Distros #

Yes, most live distros have their own flags or parameters to enable live-mode booting:

• Debian Live: Uses boot=casper just like Ubuntu—since Ubuntu is based on Debian, casper originated from Debian’s live-initramfs tooling.
• Fedora Live: Uses parameters like inst.stage2=live:CDLABEL=Fedora-Workstation-Live-x86_64-39-1.5 to specify the location of the live image (instead of boot=casper).
• Arch Linux Live: Doesn’t need a dedicated boot parameter—its initramfs automatically detects and mounts the live image. You might see archisobasedir=arch if the image is nested in a directory, but no equivalent to boot=casper is required.
• openSUSE Live: Uses the livecd parameter (e.g., livecd=USB) to trigger live-mode initialization, similar to how boot=casper works for Ubuntu.

内容的提问来源于stack exchange，提问作者Hugo Trentesaux