Making Debian or Fedora persistent live images

Developers and advanced users can now create Debian and Fedora live ISO images with persistent storage, allowing user changes to survive reboots, through specific configuration methods.

Recent updates provide detailed procedures for enabling persistence in Debian and Fedora live images. For Debian, the process involves creating a partition with the label ‘persistence’ and adding a persistence.conf file with the line ‘/ union’. The kernel parameter ‘persistence’ must be added to the ISO’s boot configuration, which can be done by extracting and editing the ISO or by a byte-level swap in the ISO file.

Fedora’s approach relies on creating separate ext4 and FAT32 images, labeled appropriately, and combining them into a single GPT-partitioned USB drive. The kernel parameter ‘rd.live.overlay=LABEL=foo:/bar’ is used, with ‘foo’ and ‘bar’ matching the label and directory inside the overlay. This method involves extracting the squashfs image, creating new images, and rebuilding the ISO structure, which is more complex but offers space for persistent data without overlay layers.

Why It Matters

Enabling persistence in live images allows users to customize and save their environment across reboots, which is valuable for portable workflows, testing, and troubleshooting. It also impacts how distributions can be used for persistent environments, especially in scenarios where data retention is critical.

Background

Traditionally, live ISO images are read-only, and persistent storage requires additional configuration. Ubuntu pioneered a simple ‘persistent’ kernel parameter with a labeled ‘casper-rw’ partition, but implementations vary across distributions. Fedora’s recent shift to using an EROFS image and separate partitions reflects evolving strategies to improve persistence and usability in live environments.

“Creating persistent live images involves specific partition labels and kernel parameters, but the implementation varies widely between distros.”

— Source developer

“Our approach uses separate images and kernel parameters, providing more space and flexibility for persistence.”

— Fedora community member

What Remains Unclear

It remains unclear whether these methods will be standardized across future releases or if new techniques will emerge. The exact process for automating ISO modifications and ensuring compatibility with updates is still under development.

What’s Next

Expect further updates from distribution maintainers to streamline persistence setup, possibly including official tools or scripts. Community discussions and testing will likely refine these methods, making persistence more accessible.

Key Questions

Can I add persistence to any live ISO?

Not all ISOs support persistence out of the box. You need to modify the ISO with specific labels, kernel parameters, and possibly recreate parts of the image, depending on the distribution.

How reliable are these persistence methods?

Methods vary in reliability; Fedora’s approach with separate images tends to be more stable, while manual ISO modifications can be fragile and may break after updates.

Is there an official tool for creating persistent live images?

As of now, most methods involve manual modifications or community scripts. Official tools are limited, but some distributions are working toward integrated solutions.

Will these persistence methods work with UEFI and Secure Boot?

Yes, but additional steps may be required to sign images or configure UEFI settings, especially when modifying bootloaders or creating custom images.

Source: Hacker News