ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
On openSUSE Tumbleweed, a risky zypper dup can be turned into a safe, recoverable operation thanks to the default Btrfs layout and Snapper’s pre/post snapshots. This guide walks through the steps, a concrete example, and the trade‑offs you should keep in mind.
A deployment needs reproducible application behavior across updates, but openSUSE Tumbleweed continuously rebuilds its package set and identifies releases only by dated factory snapshots rather than fixed version numbers. The rolling model carries no cross-snapshot ABI guarantee, so a refresh can replace a shared library and cause a previously working applic
A repeatable development environment on openSUSE is needed where system state can be reproduced across machines and rolled back when experiments change build behavior. openSUSE MicroOS provides an immutable root filesystem with transactional-update, staging package changes offline and applying them atomically on reboot. openSUSE Tumbleweed provides a mutable
