From ca6bb53dbc35efcc2b7f3cbb5c7cdff5e1d1d656 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1=C5=A1=20Ba=C5=BEant?= Date: Thu, 22 Jun 2023 13:39:09 +0200 Subject: [PATCH] Removed techpreview info + minor stylish updates --- xml/transactional_updates.xml | 60 ++++++++++++++++++----------------- 1 file changed, 31 insertions(+), 29 deletions(-) diff --git a/xml/transactional_updates.xml b/xml/transactional_updates.xml index 8271c6bfe4..0a8ff43eb8 100644 --- a/xml/transactional_updates.xml +++ b/xml/transactional_updates.xml @@ -16,14 +16,14 @@ - Transactional updates are available in &productname; as a technology - preview, for updating &slsa; when the root file system is read-only. - Transactional updates are atomic (all updates are applied only if all - updates succeed) and support rollbacks. It does not affect a running system - as no changes are activated until after the system is rebooted. As reboots - are disruptive, the administrator must decide if a reboot is more expensive than - disturbing running services. If reboots are too expensive then do not use - transactional updates. + Transactional updates are available in &productname; for updating &slsa; + when the root file system is read-only. Transactional updates are + atomic—all updates are applied only if all succeed—and support + rollbacks. It does not affect a running system as no changes are activated + until after the system is rebooted. As reboots are disruptive, the + administrator must decide if a reboot is more expensive than disturbing + running services. If reboots are too expensive then do not use transactional + updates. @@ -31,7 +31,7 @@ transactional-update script. The script checks for available updates. If there are any updates, it creates a new snapshot of the root file system in the background, and then fetches updates from the - release channels. After the new snapshot is completely updated, it is + release channels. After the new snapshot is updated, it is marked as active and will be the new default root file system after the next reboot of the system. When transactional-update is set to run automatically (which is the default behavior) it also reboots the system. @@ -52,17 +52,19 @@ - Limitations of technology preview + Limitations - As a technology preview, there are certain limitations in functionality. The - following packages will not work with transactional-update: + Currently, there are certain limitations in the functionality of + transactional updates. The following packages do not work with the + transactional-update command: - The nginx default index.html page may not be available + The nginx default index.html page + may not be available @@ -191,9 +193,9 @@ &yast; is not yet aware of transactional updates. If a YaST module needs - to install additional packages, this will not work. Normal system - operations only modifying configuration files in /etc - will work. + to install additional packages, this does not work. Normal system + operations that modify configuration files in /etc + work. @@ -253,10 +255,10 @@ Changing the subvolume layout of the root partition, or putting - sub-directories or subvolumes of the root partition on their own partitions + subdirectories or subvolumes of the root partition on their own partitions (except /home, /var, /srv, and /opt) is not supported, - and will most probably break the system. + and may break the system. @@ -280,9 +282,9 @@ The <command>transactional-update</command> command - The transactional-update command enables atomic installation - or removal of updates; updates are applied only - if all of them can be successfully installed. + The transactional-update command enables atomic + installation or removal of updates. Updates are applied only if they all can + be successfully installed. transactional-update creates a snapshot of your system before the update is applied, and you can restore this snapshot. All changes become active only after reboot. @@ -335,11 +337,11 @@ If the current root file system is identical to the active root file system (after a reboot, before transactional-update - creates a new snapshot with updates), all old snapshots without a - cleanup algorithm get a cleanup algorithm set. This ensures that old - snapshots will be deleted by Snapper. (See the section about cleanup - algorithms in snapper(8).) This also removes all unreferenced (and thus - unused) /etc overlay directories in + creates a new snapshot with updates), all old snapshots without a cleanup + algorithm get a cleanup algorithm set. This ensures that old snapshots are + deleted by Snapper. (See the section about cleanup algorithms in + snapper(8).) This also removes all unreferenced (and thus unused) + /etc overlay directories in /var/lib/overlay: &prompt.root;transactional-update cleanup @@ -433,12 +435,12 @@ This creates a new GRUB2 configuration. Sometimes it is necessary to - adjust the boot configuration, for example adding additional kernel + adjust the boot configuration, for example, adding additional kernel parameters. Edit /etc/default/grub, run transactional-update grub.cfg, and then reboot to activate the change. You must immediately reboot, or the new GRUB2 - configuration will be overwritten with the default by the next - transactional-update. + configuration gets overwritten with the default by the next + transactional-update run. &prompt.root;transactional-update grub.cfg