diff --git a/xml/slemicro_update_procedure.xml b/xml/slemicro_update_procedure.xml index 105f313b06..ccff92363f 100644 --- a/xml/slemicro_update_procedure.xml +++ b/xml/slemicro_update_procedure.xml @@ -7,7 +7,7 @@ + xmlns:xlink="http://www.w3.org/1999/xlink"> Upgrading the system @@ -15,74 +15,79 @@ yes - - SUSE offers a command-line tool to upgrade a running system to a new version. The tool provides support for “rollback” to an older release. This chapter explains how to upgrade your system step by step. + + SUSE offers a command-line tool to upgrade a running system to a new + version. The tool provides support for “rollback” to an older release. This + chapter explains how to upgrade your system step by step. - - - + + - &suse; releases new version of &slema; at regular intervals. To make it easy - for customers to migrate to a new minor version and minimize downtime, - &suse; supports migrating online while the system is running. - - - - &slema; uses transactional updates to upgrade from one - version to the next. This has the following advantages: - - - - - - The system is always in a defined state until the first RPM is updated. - - - - - Canceling is possible until the first RPM is updated. - - - - - Simple recovery if there is an error. - - - - - It is possible to do a rollback via system tools—no - backup or restore needed. - - - - - Use of all active repositories. - - - - - + &suse; releases new version of &slema; at regular intervals. To make it easy + for customers to migrate to a new minor version and minimize downtime, &suse; + supports migrating online while the system is running. + + + &slema; uses transactional updates to upgrade from one + version to the next. This has the following advantages: + + + + + The system is always in a defined state until the first RPM is updated. + + + + + Canceling is possible until the first RPM is updated. + + + + + Simple recovery if there is an error. + + + + + It is possible to do a rollback via system tools—no + backup or restore needed. + + + + + Use of all active repositories. + + + + Upgrading to a new release - - - Upgrading to a new release and <command>wicked</command> - - &slema; 5.3 introduced NetworkManager as the default tool to manage networking. However, when you perform an upgrade from previous releases, the default network framework remains wicked. Automated migration from wicked to &nm; or the migration of the wicked configuration is not supported. However, you can switch from wicked to &nm; as desribed in . - - + + Upgrading to a new release and <command>wicked</command> + + &slema; 5.3 introduced NetworkManager as the default tool to manage + networking. However, when you perform an upgrade from previous releases, + the default network framework remains wicked. Automated + migration from wicked to &nm; or the migration of the + wicked configuration is not supported. However, you can + switch from wicked to &nm; as desribed in + . + + &suse; Linux Enterprise Live Patching - If you have the &suse; Linux Enterprise Live Patching extension enabled, the extension is not affected during the upgrade procedure. + If you have the &suse; Linux Enterprise Live Patching extension enabled, + the extension is not affected during the upgrade procedure. - + - If your system is registered with the &scc;, make sure - to have an Internet connection during the following procedure: + If your system is registered with the &scc;, make sure to have an Internet + connection during the following procedure: + Upgrade to a newer version @@ -124,69 +129,75 @@ - If your system is not registered, proceed as follows: + If your system is not registered, proceed as follows: + - Upgrading an unregistered system - - Change the URL of the update - repositories to point to the &productnumber;. - - - - Run the following command: - - &prompt.root;transactional-update dup - + Upgrading an unregistered system + + + Change the URL of the update repositories to point to the &productnumber;. + + + + + Run the following command: + +&prompt.root;transactional-update dup + - After you complete the upgrade procedure, if needed, you can to switch from wicked to &nm; without performing a fresh installation. To do so, proceed as follows: + After you complete the upgrade procedure, if needed, you can to switch from + wicked to &nm; without performing a fresh installation. + To do so, proceed as follows: - - Switching from <command>wicked</command> to &nm; - - - Run the following command to create a new snapshot where you perform all other changes to the system: - - &prompt.root;transactional-update shell - - - - Install &nm;: - - &prompt.root;zypper in NetworkManager - - - - Remove wicked from the system: - - &prompt.root;zypper rm wicked-service - - - - Enable the &nm; service: - - &prompt.root;systemctl enable NetworkManager - - - If needed, configure the service according to your needs. - - - - Close the transactonal-update shell: - - &prompt.root;exit - - - - Reboot your system to switch to the new snapshot. - - + + Switching from <command>wicked</command> to &nm; + + + Run the following command to create a new snapshot where you perform all + other changes to the system: + +&prompt.root;transactional-update shell + + + + Install &nm;: + +&prompt.root;zypper in NetworkManager + + + + Remove wicked from the system: + +&prompt.root;zypper rm wicked-service + + + + Enable the &nm; service: + +&prompt.root;systemctl enable NetworkManager + + + + If needed, configure the service according to your needs. + + + + + Close the transactonal-update shell: + +&prompt.root;exit + + + + Reboot your system to switch to the new snapshot. + + - Reverting the migration process @@ -201,5 +212,4 @@ . -