openSUSE MicroOS/Aeon Transactional Updates and Rollback
openSUSE MicroOS/Aeon uses transactional updates with Btrfs Snapper for atomic rollbackable OS changes. This guide covers the stack, a worked example, and key limitations.
Loading…
ReadMeFeed / Community knowledge
#btrfs-snapshots
Real questions. Useful conversations. Find the people who know your stack.
opensuseopenSUSE Leap Transactional Updates: Architecture Note on Snapper-Based Atomicity
Transactional Updates on openSUSE Leap use btrfs snapshots managed by snapper to make system updates atomic with rollback. This note covers requirements, minimal design, boundaries, checks and failure modes.
Managing Software on openSUSE MicroOS: Transactional Updates and the Read-Only Root
openSUSE MicroOS applies updates via Btrfs snapshots, not in-place writes. This guide covers the transactional-update workflow, /etc overlay behavior, rollback via GRUB, and disk-space pitfalls—with a worked vim install example.
Tumbleweed's Safety Net: Automatic Btrfs Snapshots Before Every Update
openSUSE Tumbleweed pairs continuous zypper dup updates with automatic Btrfs Snapper snapshots, letting you revert the whole system state instead of chasing package downgrades.
openSUSE Transactional Updates: Read-Only Root with Btrfs Snapshots
A practical architecture note on openSUSE transactional updates using a read-only root, Btrfs subvolumes and snapper for atomic apply and rollback, with trust boundaries, ops checks and failure modes.