openSUSE: Leap, Tumbleweed and Rollback That Works

openSUSE is the distribution most people have heard of and never tried. It is German, enterprise-descended, and it does two things nobody else does quite as well: YaST, a genuinely comprehensive configuration tool, and snapshot-and-rollback that is set up by default.

It is also two distributions sharing a name, and choosing the wrong one is the main way people have a bad time with it.

Leap or Tumbleweed

Leap shares its core with SUSE Linux Enterprise, so it is the free relative of a commercial product in the same way Rocky and Alma relate to RHEL — though built alongside rather than rebuilt after. Leap 16.0 arrived in October 2025 and each release now carries about two years of community support.

Tumbleweed is a rolling release, and the interesting one. Unlike Arch, it is not “whatever upstream released yesterday” — every proposed snapshot goes through openQA, an automated test suite that installs the system and drives the desktop before the update is published. It is a rolling release with a gate in front of it.

The result is a distribution that is genuinely current and noticeably less eventful than rolling releases usually are.

The rollback, which is the point

openSUSE installs on Btrfs with snapper configured out of the box. Every package transaction takes a snapshot before and after, automatically, without being asked.

When an update breaks something, the recovery is not a rescue disk and a chroot. It is choosing an earlier snapshot from the boot menu, booting into a working system, and rolling back permanently if you want to.

# What snapshots exist?
sudo snapper list

# What changed between two of them?
sudo snapper status 41..42
sudo snapper diff 41..42 /etc/ssh/sshd_config

# Undo one file from a snapshot
sudo snapper -c root undochange 41..42 /etc/ssh/sshd_config

# Roll the whole system back (after booting into that snapshot)
sudo snapper rollback

# What snapshots exist?
sudo snapper list

# What changed between two of them?
sudo snapper status 41..42
sudo snapper diff 41..42 /etc/ssh/sshd_config

# Undo one file from a snapshot
sudo snapper -c root undochange 41..42 /etc/ssh/sshd_config

# Roll the whole system back (after booting into that snapshot)
sudo snapper rollback

snapper diff deserves attention beyond disaster recovery. It answers “what did that update actually change in /etc?” — a question that is otherwise surprisingly hard to answer, and useful long before anything breaks.

This combination is why Tumbleweed is a reasonable rolling release for someone who does not want to become a systems expert. The Arch page recommends setting up snapshots on day one; openSUSE has already done it.

The cost is the usual Btrfs one, covered in filesystems: snapshots consume space that df reports confusingly, and a machine can fill up while appearing to have room.

YaST

YaST configures nearly everything — partitioning, networking, users, firewall, services, bootloader, repositories — through one interface, and it works both graphically and as a text menu over SSH.

# Text interface, works fine over SSH
sudo yast

# Straight to one module
sudo yast firewall
sudo yast users
sudo yast lan

# Text interface, works fine over SSH
sudo yast

# Straight to one module
sudo yast firewall
sudo yast users
sudo yast lan

Opinions on it divide predictably. If you know the config files, YaST is a layer you did not ask for. If you do not — or you are configuring something unfamiliar, or handing a server to a colleague who is not a Linux specialist — it is the best tool of its kind that exists.

It writes ordinary configuration files, so nothing stops you editing them by hand afterwards. Note that openSUSE has been reducing YaST’s role in newer releases, moving some functions elsewhere — it is less central than it once was.

zypper

The package manager. It is an RPM-based system, so packages are .rpm, but the commands are its own.

The Tumbleweed row is the one that matters. On a rolling release you must use zypper dup — distribution upgrade — not zypper up. The former is what keeps a rolling system coherent; the latter updates packages individually and will eventually produce the same partial-upgrade breakage the Arch page warns about with pacman -Sy.

# Tumbleweed: this one, always
sudo zypper dup

# Leap: ordinary updates
sudo zypper up

# Leap: move to the next release
sudo zypper --releasever=16.1 dup

# Tumbleweed: this one, always
sudo zypper dup

# Leap: ordinary updates
sudo zypper up

# Leap: move to the next release
sudo zypper --releasever=16.1 dup

Codecs are the other first-hour task, for the same licensing reasons as Fedora — the Packman repository is the community answer, and the project’s own site walks through adding it.

Things that catch people out

The last row is worth knowing: openSUSE uses firewalld, so Linux firewalls applies directly, including the runtime-versus-permanent reload trap.

Who should run openSUSE

Tumbleweed, yes, if you want current software but not the maintenance burden a rolling release usually implies. Automated testing before publication plus snapshots configured by default is a materially safer arrangement than rolling releases normally offer, and it is the strongest argument the distribution has.

Leap, yes, if you want a stable base with unusually good administration tooling, or you work with SUSE Linux Enterprise and want a matching free system — the same logic as running Fedora alongside RHEL servers.

Look elsewhere if:

• You follow a lot of tutorials. This is the real cost. The overwhelming majority assume apt or dnf, and translating every command is a persistent low-grade tax. Ubuntu or Mint avoid it entirely.
• You need long support windows on servers — two years is short next to Debian‘s five or Rocky’s ten.
• Your third-party software is packaged for Debian and Red Hat only, which is common.
• You are new to Linux. Nothing here is hard, but the smaller community means fewer answers when you search a problem.

Worth being straight about that first point: openSUSE’s technical merits are real and its ecosystem is smaller. If snapshot rollback on a current system is what you want, it is the best implementation available. If you want the path everyone else is on, it is not.

Quick reference

Related reading

• Arch Linux — the other rolling release, and what it asks of you
• Fedora — the other RPM desktop
• Rocky and AlmaLinux — the enterprise-free-relative comparison
• Filesystems — Btrfs, snapshots and the disk-usage confusion
• Linux firewalls — firewalld, which openSUSE uses
• Package management — zypper next to apt and dnf