Where Does openSUSE Aeon Store System Config?
Aeon manages the read-only system with transactional-update and snapper. Key configs and snapshots here.
Last updated
Aeon is the immutable MicroOS desktop with a read only root filesystem. System changes stage through transactional-update into a fresh snapshot, and a reboot activates that snapshot as the live system. Day to day behavior comes from the update config, where /etc entries override the /usr/etc defaults, while desktop apps arrive through Flatpak and Distrobox instead.
Snapper tracks each snapshot under the snapshots directory, with per-volume configs beside it. Direct writes to the live root fail by design, so package installs use the transactional-update install form and take effect after reboot. To undo a bad state, run the rollback form and reboot, then clean stale overlays so the small host config stays auditable.
Where openSUSE Aeon stores this, by platform
/etc/transactional-update.conf
Update method, reboot policy and auto import keys. /etc overrides /usr/etc defaults. Snapshots under /.snapshots with per-volume snapper configs.
Frequently asked questions
How do I install packages on Aeon?
Install with transactional-update pkg install, which stages into a new snapshot and activates on reboot. Direct zypper writes to the live root fail by design. Desktop apps come from Flatpak and Distrobox instead.
Where are Aeon snapshots and how do I roll back?
Snapshots mount under /.snapshots with configs in /etc/snapper/configs. Roll back with transactional-update rollback and reboot. /etc overlays merge per snapshot; clean stale ones with cleanup-overlays.
Notice an outdated path? Let us know.