Free tools Windows power users keep installed
One-click scans. No signup required.
First check which openSUSE Leap release you are installing: Leap 15.6 offers the Transactional Server role, while the openSUSE project identifies Leap 16.1 as the first Leap release with a separately named Immutable Mode. Both choices are made during installation in the documented instructions; the available sources do not describe a supported way to convert an existing standard installation in place. Updates use transactional-update, and changes take effect after a reboot.
Check your Leap version and installation situation
The setup depends on the release, so do not treat “immutable mode” as one universal switch. Leap 15.6 documents a server-focused system role called Transactional Server. Leap 16.1 adds a distinct installer choice called Immutable Mode, according to the openSUSE project’s post about the 16.1 release candidate.
As an Amazon Associate I earn from qualifying purchases.
| Release and installer choice | What the documentation establishes | Update guidance |
|---|---|---|
| Leap 15.6 — Transactional Server | A server role with a read-only root filesystem and transactional updates, selected during installation. Leap 15.6 Release Notes | Use the role-specific transactional-update commands in the release notes, rather than YaST or Zypper for software management. |
| Leap 16.1 — Immutable Mode | The project describes this as a new installer option for Leap 16.1. The cited announcement discusses the release candidate, so confirm the final installer’s wording in current release documentation. openSUSE Leap 16.1 RC announcement | The project’s example is sudo transactional-update dup, then reboot. Follow the instructions for your exact release. |
If Leap is already installed in a standard configuration, the cited instructions do not provide an in-place conversion procedure. Plan on selecting the relevant role or mode in the installer rather than assuming a post-install toggle exists.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Select the option during installation
Leap 15.6: choose Transactional Server
During Leap 15.6 installation, select Transactional Server if you want the documented server role with a read-only root filesystem and transactional updates. This is a server role; the release notes do not establish that it is equivalent to Leap 16.1’s separately named Immutable Mode or make broader claims about desktop suitability.
#1 Best Overall
Leap 16.1: choose Immutable Mode
For Leap 16.1, boot the usual installation image and select Immutable Mode in the installer, following the project’s announcement. That post covers the 16.1 release-candidate context, so verify the final-release availability and current screen labels before installing.
Update Leap 15.6 Transactional Server
The Leap 15.6 release notes direct Transactional Server users to transactional-update for software management. They explicitly say YaST is unsupported for transactional updates because it applies changes immediately and cannot edit a read-only filesystem. The release notes document these commands:
transactional-update up— update the system.transactional-update pkg in PACKAGE_NAME— install a package, replacingPACKAGE_NAMEwith the package’s name.transactional-update pkg rm PACKAGE_NAME— remove a package, replacingPACKAGE_NAMEwith its name.
These commands are documented for the Leap 15.6 Transactional Server role; do not assume they are the right commands for every Leap release or system role.
Update Leap 16.1 Immutable Mode
The openSUSE project’s Leap 16.1 announcement gives this example for Immutable Mode:
Rank #3
- openSUSE is a Linux-based operating system for your PC, Laptop or Server. You can surf the Web, manage your e-mails and photos, do office work, play videos or music and have a lot of fun!
- You can surf the Web, manage your e-mails and photos, do office work, play videos or music and have a lot of fun!
- Run
sudo transactional-update dup. - When the command completes, run
sudo rebootto activate the prepared changes.
There is a release-context difference worth noting: the 16.1 project post uses dup, while the transactional-update configuration documentation describes up for regular releases such as Leap and dup for rolling releases; the Leap 16.0 manual also identifies dup as its default. Do not silently substitute one command for another. Use the command specified by documentation for your precise Leap release and role.
Know what the reboot and rollback do
transactional-update uses Btrfs snapshots with the distribution’s package-management tools. It prepares changes separately from the currently running system; the updated snapshot becomes active after a reboot. Until then, the running system has not switched to the prepared changes.
The Leap 15.6 manual describes rollback to an earlier root snapshot. That is a way to return the system root to an earlier snapshot; it should not be treated as a guarantee that arbitrary changes outside that snapshot will be reversed.
Understand Leap 15.6 automatic updates
The Leap 15.6 release notes state that Transactional Server runs a daily update by default and reboots between 03:30 and 05:00, using systemd-based mechanisms that can be disabled if needed. This schedule is documented for that role, not as a default for every Leap installation. If an unattended reboot would disrupt a service, check the role’s systemd configuration and adjust it for your maintenance requirements.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
