ACC SHELL
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 14. Upgrading the System and System Changes</title><link rel="stylesheet" href="susebooks.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Documentation"><link rel="up" href="part.reference.administration.html" title="Part III. Administration"><link rel="prev" href="cha.util.html" title="Chapter 13. System Monitoring Utilities"><link rel="next" href="part.reference.system.html" title="Part IV. System"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header" border="0" class="bctable"><tr><td width="80%"><div class="breadcrumbs"><p><a href="index.html"> Documentation</a><span class="breadcrumbs-sep"> > </span><a href="book.opensuse.reference.html">Reference</a><span class="breadcrumbs-sep"> > </span><a href="part.reference.administration.html">Administration</a><span class="breadcrumbs-sep"> > </span><strong><a accesskey="p" title="Chapter 13. System Monitoring Utilities" href="cha.util.html"><span>◀</span></a> </strong></p></div></td></tr></table></div><div class="chapter" title="Chapter 14. Upgrading the System and System Changes"><div class="titlepage"><div><div><h2 class="title"><a name="cha.update"></a>Chapter 14. Upgrading the System and System Changes<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#cha.update">¶</a></span></h2></div></div></div><div class="toc"><p><b>Contents</b></p><dl><dt><span class="sect1"><a href="cha.update.html#sec.update.suselinux">14.1. Upgrading the System</a></span></dt><dt><span class="sect1"><a href="cha.update.html#sec.update.version">14.2. Software Changes</a></span></dt></dl></div><a class="indexterm" name="id458475"></a><a class="indexterm" name="id458484"></a><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p>
<a class="indexterm" name="id458495"></a> You can upgrade an existing system without completely
reinstalling it. There are two types of renewing the system or parts of
it: <span class="emphasis"><em>updating individual software packages</em></span> and
<span class="emphasis"><em>upgrading the entire system</em></span>. Updating individual
packages is covered in <a class="xref" href="cha.y2.sw.html" title="Chapter 3. Installing or Removing Software">Chapter 3, <i>Installing or Removing Software</i></a> and
<a class="xref" href="cha.onlineupdate.you.html" title="Chapter 4. YaST Online Update">Chapter 4, <i>YaST Online Update</i></a>. Two ways to upgrade the system
are discussed in the following sections— see
<a class="xref" href="cha.update.html#sec.upgrade.yast" title="14.1.3. Upgrading with YaST">Section 14.1.3, “Upgrading with YaST”</a> and
<a class="xref" href="cha.update.html#sec.update.zypper" title="14.1.4. Distribution Upgrade with zypper">Section 14.1.4, “Distribution Upgrade with zypper”</a>.
</p></div><div class="sect1" title="14.1. Upgrading the System"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.update.suselinux"></a>14.1. Upgrading the System<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.update.suselinux">¶</a></span></h2></div></div></div><p>
Software tends to <span class="quote">“<span class="quote">grow</span>”</span> from version to version. Therefore,
take a look at the available partition space with <span class="command"><strong>df</strong></span>
before updating. If you suspect you are running short of disk space,
secure your data before you update and repartition your system. There is
no general rule regarding how much space each partition should have.
Space requirements depend on your particular partitioning profile, the
software selected, and the version numbers of the system.
</p><div class="sect2" title="14.1.1. Preparations"><div class="titlepage"><div><div><h3 class="title"><a name="sec.update.prep"></a>14.1.1. Preparations<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.update.prep">¶</a></span></h3></div></div></div><p>
Before upgrading, copy the old configuration files to a separate medium
(such as removable hard disk or USB flash drive) to secure
the data. This primarily applies to files stored in
<code class="filename">/etc</code> as well as some of the directories and files
in <code class="filename">/var</code>. You may also want to write the user data
in <code class="filename">/home</code> (the <code class="envar">HOME</code> directories) to a
backup medium. Back up this data as
<code class="systemitem">root</code>. Only
<code class="systemitem">root</code> has read permission
for all local files.
</p><p>
Before starting your update, make note of the root partition. The
command <span class="command"><strong>df /</strong></span> lists the device name of the root
partition. In <a class="xref" href="cha.update.html#aus.update.df" title="Example 14.1. List with df -h">Example 14.1, “List with <span class="command">df -h</span>”</a>, the root partition
to write down is <code class="filename">/dev/sda3</code> (mounted as
<code class="filename">/</code>).
</p><div class="example"><a name="aus.update.df"></a><p class="title"><b>Example 14.1. List with <span class="command">df -h</span></b><span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#aus.update.df">¶</a></span></p><div class="example-contents"><pre class="screen">Filesystem Size Used Avail Use% Mounted on
/dev/sda3 74G 22G 53G 29% /
udev 252M 124K 252M 1% /dev
/dev/sda5 116G 5.8G 111G 5% /home
/dev/sda1 39G 1.6G 37G 4% /windows/C
/dev/sda2 4.6G 2.6G 2.1G 57% /windows/D</pre></div></div><br class="example-break"></div><div class="sect2" title="14.1.2. Possible Problems"><div class="titlepage"><div><div><h3 class="title"><a name="id458642"></a>14.1.2. Possible Problems<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#id458642">¶</a></span></h3></div></div></div><a class="indexterm" name="id458647"></a><p>
If you upgrade a default system from the previous version to this
version, YaST works out the necessary changes and performs them.
Depending on your customizations, some steps (or the entire upgrade
procedure) may fail and you must resort to copying back your backup
data. Check the following issues before starting the system update.
</p><div class="sect3" title="14.1.2.1. Checking passwd and group in /etc"><div class="titlepage"><div><div><h4 class="title"><a name="id458663"></a>14.1.2.1. Checking passwd and group in /etc<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#id458663">¶</a></span></h4></div></div></div><a class="indexterm" name="id458668"></a><a class="indexterm" name="id458677"></a><a class="indexterm" name="id458685"></a><p>
Before upgrading the system, make sure that
<code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> do
not contain any syntax errors. For this purpose, start the verification
utilities <span class="command"><strong>pwck</strong></span> and <span class="command"><strong>grpck</strong></span> as
<code class="systemitem">root</code> to eliminate any
reported errors.
</p></div><div class="sect3" title="14.1.2.2. PostgreSQL"><div class="titlepage"><div><div><h4 class="title"><a name="id458722"></a>14.1.2.2. PostgreSQL<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#id458722">¶</a></span></h4></div></div></div><a class="indexterm" name="id458727"></a><p>
Before updating <span class="productname">PostgreSQL</span>
(<code class="systemitem">postgres</code>), dump the
databases. See the manual page of <span class="command"><strong>pg_dump</strong></span>. This is
only necessary if you actually used PostgreSQL prior to your update.
</p></div></div><div class="sect2" title="14.1.3. Upgrading with YaST"><div class="titlepage"><div><div><h3 class="title"><a name="sec.upgrade.yast"></a>14.1.3. Upgrading with YaST<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.upgrade.yast">¶</a></span></h3></div></div></div><a class="indexterm" name="id458766"></a><a class="indexterm" name="id458775"></a><a class="indexterm" name="id458783"></a><p>
Following the preparation procedure outlined in
<a class="xref" href="cha.update.html#sec.update.prep" title="14.1.1. Preparations">Section 14.1.1, “Preparations”</a>, you can now upgrade your system:
</p><div class="procedure"><ol class="procedure" type="1"><li><p>
Boot the system as for the installation, described in
Section “System Start-Up for Installation” (Chapter 1, <i>Installation with YaST</i>, ↑Start-Up). In YaST, choose a
language and select <span class="guimenu">Update</span> in the
<span class="guimenu">Installation Mode</span> dialog. Do not select
<span class="guimenu">New Installation</span>. Also add repositories to make
sure to get all available software updated whenever possible. Find
more information about installation repositories in
Section “Add-On Products” (Chapter 1, <i>Installation with YaST</i>, ↑Start-Up).
</p></li><li><p>
YaST determines if there are multiple root partitions. If there is
only one, continue with the next step. If there are several, select
the right partition and confirm with <span class="guimenu">Next</span>
(<code class="filename">/dev/sda3</code> was selected in the example in
<a class="xref" href="cha.update.html#sec.update.prep" title="14.1.1. Preparations">Section 14.1.1, “Preparations”</a>). YaST reads the old
<code class="filename">fstab</code> on this partition to analyze and mount the
file systems listed there.
</p><div class="warning"><table border="0" cellpadding="3" cellspacing="0" width="100%" summary="Warning: Persistent Device Names"><tr class="head"><td width="32"><img alt="[Warning]" src="admon/warning.png"></td><th align="left">Persistent Device Names</th></tr><tr><td colspan="2" align="left" valign="top"><p>
All entries in <code class="filename">/etc/fstab</code> that specify
partitions to be mounted using the kernel-device name must be changed
to any of the other supported methods prior to performing an update.
Kernel-device names are not persistent and are therefore unreliable
for use during the update process. This can be done using the YaST
System Partitioner by changing the method used in the fstab options
settings.
</p></td></tr></table></div></li><li><p>
Check the previously used repositories, if there are any. Enable all
the repositories you still want to use and from where you want to
update third-party software. Click the <span class="guimenu">Toggle
Status</span> for every list item, if appropriate.
</p></li><li><p>
If you added repositories during the upgrade procedure as recommended
above, you now can activate those you are actually interested in.
</p></li><li><p>
In the <span class="guimenu">Installation Settings</span> dialog, adjust the
settings according to your requirements. Normally, you can leave the
default settings untouched. If you intend to enhance your system,
however, check the packages and patterns offered in the
<span class="guimenu">Packages</span> and <span class="guimenu">Update Options</span>
submenus, or add support for additional languages.
</p><p>
You also have the possibility to make backups of various system
components. Selecting backups slows down the upgrade process. Use this
option if you do not have a recent system backup.
</p></li><li><p>
Confirm the upgrade by clicking <span class="guimenu">Start Update</span>.
</p></li></ol></div><p>
Once the basic upgrade installation is finished, YaST reboots the
system.
Finally, YaST updates the remaining software, if
any
and displays the release notes, if wanted.
</p></div><div class="sect2" title="14.1.4. Distribution Upgrade with zypper"><div class="titlepage"><div><div><h3 class="title"><a name="sec.update.zypper"></a>14.1.4. Distribution Upgrade with zypper<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.update.zypper">¶</a></span></h3></div></div></div><a class="indexterm" name="id458977"></a><a class="indexterm" name="id458985"></a><p>
With the <span class="command"><strong>zypper</strong></span> command line utility you can upgrade to
the next version of the distribution. Most importantly, you can initiate
the system upgrade process from within the running system.
</p><p>
This feature is attractive for advanced users who want to run remote
upgrades or upgrades on many similarly configured systems. Inexperienced
users will prefer the upgrade with YaST using a boot medium as described
in <a class="xref" href="cha.update.html#sec.upgrade.yast" title="14.1.3. Upgrading with YaST">Section 14.1.3, “Upgrading with YaST”</a>.
</p><div class="sect3" title="14.1.4.1. Before Starting the Upgrade with zypper"><div class="titlepage"><div><div><h4 class="title"><a name="id459014"></a>14.1.4.1. Before Starting the Upgrade with zypper<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#id459014">¶</a></span></h4></div></div></div><p>
To avoid unexpected errors during the upgrade process using
<span class="command"><strong>zypper</strong></span>, minimize risky constellations.
</p><p>
Upgrade from the previous version (e.g., 11.3) to this version
(11.4)—do not skip any minor version inbetween (this means, do not
upgrade from 11.2 or earlier to 11.4 in one go). Make sure all available
11.3 online updates are successfully applied.
</p><p>
Close as many applications and unneeded services as possible and log out
all regular users.
</p><p>
Disable third party or openSUSE Build Service repositories before
starting the upgrade, or lower the priority of these repositories to make
sure packages from the default system repositories will get preference.
Enable them again after the upgrade and edit their version string to
match the version number of the distribution of the upgraded now running
system.
</p><p>
For more information, see
<a class="ulink" href="http://en.opensuse.org/SDB:System_upgrade" target="_top">http://en.opensuse.org/SDB:System_upgrade</a>.
</p></div><div class="sect3" title="14.1.4.2. The Upgrade Procedure"><div class="titlepage"><div><div><h4 class="title"><a name="id459062"></a>14.1.4.2. The Upgrade Procedure<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#id459062">¶</a></span></h4></div></div></div><div class="warning"><table border="0" cellpadding="3" cellspacing="0" width="100%" summary="Warning: Check Your System Backup"><tr class="head"><td width="32"><img alt="[Warning]" src="admon/warning.png"></td><th align="left">Check Your System Backup</th></tr><tr><td colspan="2" align="left" valign="top"><p>
Before actually starting the upgrade procedure, check that your system
backup is up-to-date and restorable. This is especially important
because you must enter many of the following steps manually.
</p></td></tr></table></div><div class="procedure"><ol class="procedure" type="1"><li><p>
Run the online update to make sure the software management stack is
up-to-date. For more information, see
<a class="xref" href="cha.onlineupdate.you.html" title="Chapter 4. YaST Online Update">Chapter 4, <i>YaST Online Update</i></a>.
</p></li><li><p>
Configure the repositories you want to use as an update source. Getting
this right is essential. Either use YaST (see
<a class="xref" href="cha.y2.sw.html#sec.y2.sw.instsource" title="3.4. Managing Software Repositories and Services">Section 3.4, “Managing Software Repositories and Services”</a>) or <span class="command"><strong>zypper</strong></span>
(see <a class="xref" href="cha.sw_cl.html#sec.zypper" title="7.1. Using Zypper">Section 7.1, “Using Zypper”</a>).
The name of the repositories as used in the following steps could vary
a little bit depending on your customizations.
</p><p>
To view your current repositories enter:
</p><pre class="screen">zypper lr -u
</pre><div class="tip"><table border="0" cellpadding="3" cellspacing="0" width="100%" summary="Tip: zypper command names"><tr class="head"><td width="32"><img alt="[Tip]" src="admon/tip.png"></td><th align="left">zypper command names</th></tr><tr><td colspan="2" align="left" valign="top"><p>zypper supports long and short command names. For example, you can
abbreviate <span class="command"><strong>zypper install</strong></span> as <span class="command"><strong>zypper in</strong></span>.
In the following text, the short variant is used.</p></td></tr></table></div><ol type="a" class="substeps"><li><p>
Increase the version number of the system repositories from 11.3 to
11.4; add the new 11.4 repositories with commands such as:
</p><pre class="screen">server=http://download.opensuse.org
new_ver=11.4
zypper ar $server/distribution/$new_ver/repo/oss/ openSUSE-$new_ver-Oss
zypper ar $server/update/$new_ver/ openSUSE-$new_ver-Update
</pre><p>
And remove the old repositories:
</p><pre class="screen">
old_ver=11.3
zypper rr openSUSE-$old_ver-Oss
zypper rr openSUSE-$old_ver-Update
</pre></li><li><p>
Disable third party repositories or other openSUSE Build Service
repositories, because <span class="command"><strong>zypper dup</strong></span> is guaranteed to
work with the default repositories only (replace
<em class="replaceable"><code>repo-alias</code></em> with the name of the repository
you want to disable):
</p><pre class="screen">zypper mr -d <em class="replaceable"><code>repo-alias</code></em>
</pre><p>
Alternatively, you can lower the priority of these repositories.
</p><div class="note"><table border="0" cellpadding="3" cellspacing="0" width="100%" summary="Note: Handling of Unresolved Dependencies"><tr class="head"><td width="32"><img alt="[Note]" src="admon/note.png"></td><th align="left">Handling of Unresolved Dependencies</th></tr><tr><td colspan="2" align="left" valign="top"><p>
<span class="command"><strong>zypper dup</strong></span> will remove all packages having
unresolved dependencies, but it keeps packages of disabled
repositories as long as their dependencies are satisfied.
</p></td></tr></table></div><p>
<span class="command"><strong>zypper dup</strong></span> ensures that all installed packages
come from one of the available repositories. It does not consider the
version, architecture, or vendor of the installed packages; thus it
emulates a fresh installation. Packages that are no longer available
in the repositories are considered orphaned. Such packages get
uninstalled if their dependencies can not be satisfied. If they can
be satisfied, such packages stay installed.
</p></li><li><p>
Once done, check your repository configuration with:
</p><pre class="screen">zypper lr -d
</pre></li></ol></li><li><p>
Refresh local metadata and repository contents with <span class="command"><strong>zypper
ref</strong></span>.
</p></li><li><p>
Pull in zypper and the package management stack from the 11.4
repository with <span class="command"><strong>zypper up zypper</strong></span>.
</p></li><li><p>
Run the actual distribution upgrade with <span class="command"><strong>zypper dup</strong></span>.
You are asked to confirm the license.
</p></li><li><p>
Perform basic system configuration with <span class="command"><strong>SuSEconfig</strong></span>.
</p></li><li><p>
Reboot the system with <span class="command"><strong>shutdown -r now</strong></span>.
</p></li></ol></div></div></div><div class="sect2" title="14.1.5. Updating Individual Packages"><div class="titlepage"><div><div><h3 class="title"><a name="sec.update.packages"></a>14.1.5. Updating Individual Packages<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.update.packages">¶</a></span></h3></div></div></div><p>
Regardless of your overall updated environment, you can always update
individual packages. From this point on, however, it is your
responsibility to ensure that your system remains consistent. Update
advice can be found at
<a class="ulink" href="http://www.novell.com/linux/download/updates/" target="_top">http://www.novell.com/linux/download/updates/</a>.
</p><p>
Select components from the YaST package selection list according to
your needs. If you select a package essential for the overall operation
of the system, YaST issues a warning. Such packages should be updated
only in the update mode. For example, many packages contain
<span class="emphasis"><em>shared libraries</em></span>. Updating these programs and
applications in the running system may lead to system instability.
</p></div></div><div class="sect1" title="14.2. Software Changes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec.update.version"></a>14.2. Software Changes<span class="permalink"><a alt="Permalink" title="Copy Permalink" href="#sec.update.version">¶</a></span></h2></div></div></div><p>
The individual modifications from version to version are outlined in the
following in detail. This summary indicates, for example, whether basic
settings have been completely reconfigured, configuration files have been
moved to other places, or common applications have been significantly
changed. Significant modifications that affect the daily use of the
system at either the user level or the administrator level are mentioned
here.
</p><p>
Problems and special issues of the various versions are published online
as they are identified. See the links listed below. Important updates of
individual packages can be accessed at
<a class="ulink" href="http://www.novell.com/products/linuxprofessional/downloads/" target="_top">http://www.novell.com/products/linuxprofessional/downloads/</a>
using the YaST Online Update. For more information, see
<a class="xref" href="cha.onlineupdate.you.html" title="Chapter 4. YaST Online Update">Chapter 4, <i>YaST Online Update</i></a>.
</p><p>
Refer to the <code class="literal">Product highlights</code>
(<a class="ulink" href="http://wiki.opensuse.org/Product_highlights" target="_top">http://wiki.opensuse.org/Product_highlights</a> and the
<code class="literal">Bugs</code> article in the openSUSE wiki at
<a class="ulink" href="http://en.opensuse.org/openSUSE:Most_annoying_bugs" target="_top">http://en.opensuse.org/openSUSE:Most_annoying_bugs</a> for
information about recent changes and issues.
</p></div></div><div class="navfooter"><table width="100%" summary="Navigation footer" border="0" class="bctable"><tr><td width="80%"><div class="breadcrumbs"><p><a href="index.html"> Documentation</a><span class="breadcrumbs-sep"> > </span><a href="book.opensuse.reference.html">Reference</a><span class="breadcrumbs-sep"> > </span><a href="part.reference.administration.html">Administration</a><span class="breadcrumbs-sep"> > </span><strong><a accesskey="p" title="Chapter 13. System Monitoring Utilities" href="cha.util.html"><span>◀</span></a> </strong></p></div></td></tr></table></div></body></html>
ACC SHELL 2018