Introduction: Beyond the Static GRUB2 Menu

GRUB2 (GRand Unified Bootloader, version 2) is the cornerstone of many Linux systems, serving as the primary interface between your hardware’s firmware and your operating system. While incredibly powerful, most users interact with GRUB2 through its default, largely static menu generated by os-prober and basic configuration files. This approach, while functional, often falls short for advanced users, system administrators, and developers who require a more intelligent, adaptive, and dynamic boot environment. Imagine a boot menu that automatically detects new kernel images, offers conditional recovery options, or provides specific entries only when certain conditions are met. This article will guide you through unlocking GRUB2’s full potential by leveraging advanced scripting techniques.

Moving beyond static entries allows for unparalleled customization, improved system resilience, and a more streamlined user experience. We’ll dive deep into GRUB2’s modular architecture, demonstrating how to write custom scripts that inject dynamic logic into your boot process, transforming your boot menu from a simple list into a powerful, automated decision-maker.

Understanding GRUB2’s Architecture: The /etc/grub.d/ Directory

The Core Configuration: /etc/default/grub

Before diving into scripting, it’s crucial to understand GRUB2’s fundamental configuration mechanism. The primary configuration file, /etc/default/grub, contains variables that control GRUB2’s general behavior, appearance, and default boot options. These variables are read by the GRUB2 configuration generation script, grub-mkconfig, and influence how your final grub.cfg is built. Common examples include:

• GRUB_DEFAULT: Sets the default boot entry.
• GRUB_TIMEOUT: Defines the duration GRUB2 waits before booting the default entry.
• GRUB_CMDLINE_LINUX_DEFAULT: Appends parameters to the Linux kernel command line for regular boots.
• GRUB_GFXMODE: Sets the graphical resolution of the boot menu.

Here’s a typical snippet:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(lsb_release -i -s 2> /dev/null || echo Debian)"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

The Script Hub: /etc/grub.d/

The true power of GRUB2’s modularity lies within the /etc/grub.d/ directory. This directory contains a collection of executable shell scripts, each responsible for generating a specific part of the grub.cfg file. When you run sudo grub-mkconfig -o /boot/grub/grub.cfg, these scripts are executed in alphanumeric order, and their output is concatenated to form the final GRUB2 configuration file. This sequential execution allows you to insert custom logic at precise points in the menu generation process.

Common scripts you’ll find include:

• 00_header: Sets up global GRUB2 variables and functions.
• 10_linux: Detects installed Linux kernels and creates menu entries.
• 20_gnulinux_theme: Configures the GRUB2 theme.
• 30_os-prober: Detects other operating systems (Windows, other Linux distributions) and adds them to the menu.
• 40_custom: An empty template script designed for user customizations.

Crafting Custom GRUB2 Scripts: Your Gateway to Dynamic Menus

Script Structure and Permissions

To create a custom GRUB2 script, you’ll place an executable shell script in the /etc/grub.d/ directory. The name of the script dictates its execution order; using prefixes like 06_, 07_, or 41_ ensures it runs before or after specific default scripts. All scripts must start with a shebang and should be executable.

#!/bin/sh
set -e

# Your custom GRUB2 menu entry generation logic goes here
# Use 'cat <> "$GRUB_TMPDIR/grub.cfg"
# echo "  echo 'Hello from custom entry!'" >> "$GRUB_TMPDIR/grub.cfg"
# echo "}" >> "$GRUB_TMPDIR/grub.cfg"

After creating your script, make it executable:

sudo chmod +x /etc/grub.d/XX_your_custom_script

Example 1: Conditional Boot for a Specific ISO Image

Let’s create a script that adds a menu entry to boot a specific ISO image, but only if that ISO file exists on your system. This is incredibly useful for recovery, testing, or having a portable live environment without needing a separate USB drive.

#!/bin/sh
set -e

# Define the path to your custom ISO and a descriptive label
CUSTOM_ISO="/home/user/isos/ubuntu-22.04.4-desktop-amd64.iso"
ISO_LABEL="Ubuntu 22.04 Live USB"

# Check if the ISO file exists
if [ -f "$CUSTOM_ISO" ]; then
    echo "Adding dynamic menu entry for $ISO_LABEL (if '$CUSTOM_ISO' exists)"
    cat << EOF
menuentry '$ISO_LABEL' --class ubuntu --class os {
    set isofile="$CUSTOM_ISO"
    loopback loop "	x"'
    linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile splash ---
    initrd (loop)/casper/initrd
}
EOF
else
    echo "Custom ISO '$CUSTOM_ISO' not found. Skipping entry for $ISO_LABEL."
fi

Save this script as, for example, /etc/grub.d/41_custom_iso_boot and make it executable. Remember to replace /home/user/isos/ubuntu-22.04.4-desktop-amd64.iso with the actual path to your ISO file.

Example 2: Dynamic Maintenance Mode Entry with Flag File

Consider a scenario where you want a