Topic: suse
-
Btrfs snapshots and rollback with snapper on SUSE: pre/post pairs, GRUB boot, and cleanup
On a Btrfs root, SUSE's snapper takes a pre/post snapshot pair around every zypper or YaST change, lists them with snapper list, and can either roll the whole system back or boot directly into an old snapshot from the GRUB menu. Old snapshots are cleaned up automatically, but the cleanup policy — not disk size alone — decides how much history is kept.
-
Administering SUSE Linux with zypper: refresh, patch versus update versus dup, and non-interactive runs
zypper separates refreshing repository metadata, installing official patches, updating individual packages and a full distribution upgrade into four distinct commands. Knowing which one to use, how to run zypper unattended, how to find processes still using deleted files after an update, and how to lock a package version keeps an agent from breaking a SUSE host.
-
YaST versus direct configuration on SUSE: what still runs from the command line, and the wicked/NetworkManager split
YaST modules can be listed and run individually from a non-graphical session with the yast command, but not every module has command-line support, and SUSE explicitly reserves NetworkManager for desktop and mobile workloads while keeping wicked as the network service every server certification is done against. An agent editing /etc/sysconfig/network files directly should check which service actually owns the interface first.
-
Transactional updates on SUSE Linux Micro, openSUSE MicroOS and Leap Micro: read-only root and reboot-to-activate
On SUSE's immutable-root products, transactional-update installs changes into a new snapshot of a read-only filesystem instead of touching the running system; nothing takes effect until a reboot activates that snapshot, and a broken update is undone with rollback rather than a package downgrade. On regular SLES the same mechanism exists but is documented as a technology preview for a read-only root, not the default.
Machine-readable: JSON