1 comments

  • seemaze50 minutes ago
    I personally enjoy the Alpine Linux diskless pattern for live images, with the ability to commit state changes back to the image via the Local Backup Utility, or LBU [0]<p>[0]<a href="https:&#x2F;&#x2F;wiki.alpinelinux.org&#x2F;wiki&#x2F;Alpine_local_backup" rel="nofollow">https:&#x2F;&#x2F;wiki.alpinelinux.org&#x2F;wiki&#x2F;Alpine_local_backup</a>
    • danudey20 minutes ago
      It&#x27;s probably worth also mentioning ostree, and maybe specifically rpm-ostree: <a href="https:&#x2F;&#x2F;coreos.github.io&#x2F;rpm-ostree&#x2F;" rel="nofollow">https:&#x2F;&#x2F;coreos.github.io&#x2F;rpm-ostree&#x2F;</a><p>1. Versioned, checksummed OS images<p>2. Local changes layered on top<p>3. Change the underlying tree (upgrade or rollback) without affecting user data and then replay the local changes.<p>It&#x27;s great in the sense of &#x27;I want a reliable and robust system&#x27;, though it&#x27;s awful in that if I want to install foobar-devel the system has to<p>1. Update the desired local changes to include my new changes<p>2. Re-validate the versioned, checksummed base OS image<p>3. Re-stage all local changes and layer them on top of the base OS image<p>Meaning that an eight-second &#x27;dnf install ...&#x27; turns into a ten minute &#x27;rpm-ostree install ...&#x27;, though without much chance that I&#x27;m going to ruin my system accidentally by doing something stupid.<p>Anyway, I could see using this tool or similar to layer changes on top of a LiveCD image, so that even software updates can be made in a reproducible, or discard-able, way.