commit 9c566c15949971bc60d73ebd7171d5dce253aa79
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Apr 16 14:27:48 2015 +0200
Change 'Yum' to 'DNF'
en-US/DNF.xml | 342 ++++++++++++++++++++++++++++----------------------------
1 files changed, 171 insertions(+), 171 deletions(-)
---
diff --git a/en-US/DNF.xml b/en-US/DNF.xml
index 461903a..ca62f53 100644
--- a/en-US/DNF.xml
+++ b/en-US/DNF.xml
@@ -4,21 +4,21 @@
<chapter id="ch-DNF">
<title>DNF</title>
<para>
- <application>Yum</application> is the &OSORG; package manager that is
able to query for information about packages, fetch packages from repositories, install
and uninstall packages using automatic dependency resolution, and update an entire system
to the latest available packages. Yum performs automatic dependency resolution on packages
you are updating, installing or removing, and thus is able to automatically determine,
fetch and install all available dependent packages. Yum can be configured with new,
additional repositories, or <firstterm>package sources</firstterm>, and also
provides many plug-ins which enhance and extend its capabilities. Yum is able to perform
many of the same tasks that <application>RPM</application> can; additionally,
many of the command line options are similar. Yum enables easy and simple package
management on a single machine or on groups of them.
+ <application>DNF</application> is the &OSORG; package manager that is
able to query for information about packages, fetch packages from repositories, install
and uninstall packages using automatic dependency resolution, and update an entire system
to the latest available packages. DNF performs automatic dependency resolution on packages
you are updating, installing or removing, and thus is able to automatically determine,
fetch and install all available dependent packages. DNF can be configured with new,
additional repositories, or <firstterm>package sources</firstterm>, and also
provides many plug-ins which enhance and extend its capabilities. DNF is able to perform
many of the same tasks that <application>RPM</application> can; additionally,
many of the command line options are similar. DNF enables easy and simple package
management on a single machine or on groups of them.
</para>
<important
id="important-Secure_Package_Management_with_GPG-Signed_Packages">
<title>Secure package management with GPG-signed packages</title>
<para>
- Yum provides secure package management by enabling GPG (Gnu Privacy Guard; also
known as GnuPG) signature verification on GPG-signed packages to be turned on for all
package repositories (i.e. package sources), or for individual repositories. When
signature verification is enabled, Yum will refuse to install any packages not GPG-signed
with the correct key for that repository. This means that you can trust that the
<application>RPM</application> packages you download and install on your
system are from a trusted source, such as &OSORG;, and were not modified during
transfer. See <xref linkend="sec-Configuring_Yum_and_Yum_Repositories" />
for details on enabling signature-checking with Yum, or <xref
linkend="s1-check-rpm-sig" /> for information on working with and verifying
GPG-signed <application>RPM</application> packages in general.
+ DNF provides secure package management by enabling GPG (Gnu Privacy Guard; also
known as GnuPG) signature verification on GPG-signed packages to be turned on for all
package repositories (i.e. package sources), or for individual repositories. When
signature verification is enabled, DNF will refuse to install any packages not GPG-signed
with the correct key for that repository. This means that you can trust that the
<application>RPM</application> packages you download and install on your
system are from a trusted source, such as &OSORG;, and were not modified during
transfer. See <xref linkend="sec-Configuring_DNF_and_DNF_Repositories" />
for details on enabling signature-checking with DNF, or <xref
linkend="s1-check-rpm-sig" /> for information on working with and verifying
GPG-signed <application>RPM</application> packages in general.
</para>
</important>
<para>
- Yum also enables you to easily set up your own repositories of
<application>RPM</application> packages for download and installation on other
machines.
+ DNF also enables you to easily set up your own repositories of
<application>RPM</application> packages for download and installation on other
machines.
</para>
<para>
- Learning Yum is a worthwhile investment because it is often the fastest way to
perform system administration tasks, and it provides capabilities beyond those provided by
the <application>PackageKit</application> graphical package management
tools.</para>
- <note id="note-Note_Yum_and_Superuser_Privileges">
- <title>Yum and superuser privileges</title>
+ Learning DNF is a worthwhile investment because it is often the fastest way to
perform system administration tasks, and it provides capabilities beyond those provided by
the <application>PackageKit</application> graphical package management
tools.</para>
+ <note id="note-Note_DNF_and_Superuser_Privileges">
+ <title>DNF and superuser privileges</title>
<para>
You must have superuser privileges in order to use
<command>yum</command> to install, update or remove packages on your system.
All examples in this chapter assume that you have already obtained superuser privileges by
using either the <command>su</command> or <command>sudo</command>
command.
</para>
@@ -28,7 +28,7 @@
<section id="sec-Checking_For_Updates">
<title>Checking For Updates</title>
<indexterm>
- <primary>Yum Updates</primary>
+ <primary>DNF Updates</primary>
<secondary>checking for updates</secondary>
</indexterm>
<para>
@@ -82,13 +82,13 @@ yum.noarch 3.2.29-5.fc15
fedora</scree
</listitem>
</itemizedlist>
<para>
- The output also shows us that we can update the kernel (the kernel package), Yum
and <application>RPM</application> themselves (the
<filename>yum</filename> and <filename>rpm</filename> packages),
as well as their dependencies (such as the <package>kernel-firmware</package>,
<package>rpm-libs</package>, and <package>rpm-python</package>
packages), all using <command>yum</command>.
+ The output also shows us that we can update the kernel (the kernel package), DNF
and <application>RPM</application> themselves (the
<filename>yum</filename> and <filename>rpm</filename> packages),
as well as their dependencies (such as the <package>kernel-firmware</package>,
<package>rpm-libs</package>, and <package>rpm-python</package>
packages), all using <command>yum</command>.
</para>
</section>
<section id="sec-Updating_Packages">
<title>Updating Packages</title>
<indexterm>
- <primary>Yum Updates</primary>
+ <primary>DNF Updates</primary>
<secondary>updating packages</secondary>
</indexterm>
<para>
@@ -98,7 +98,7 @@ yum.noarch 3.2.29-5.fc15
fedora</scree
Updating a Single Package
</bridgehead>
<indexterm>
- <primary>Yum Updates</primary>
+ <primary>DNF Updates</primary>
<secondary>updating a single package</secondary>
</indexterm>
<para>
@@ -139,7 +139,7 @@ Is this ok [y/N]:</screen>
<orderedlist>
<listitem>
<para>
- <computeroutput>Loaded plugins:</computeroutput> —
<command>yum</command> always informs you which
<application>Yum</application> plug-ins are installed and enabled. Here,
<command>yum</command> is using the
<application>langpacks</application>,
<application>presto</application>, and
<application>refresh-packagekit</application> plug-ins. See <xref
linkend="sec-Yum_Plugins" /> for general information on
<application>Yum</application> plug-ins, or to <xref
linkend="sec-Plugin_Descriptions" /> for descriptions of specific plug-ins.
+ <computeroutput>Loaded plugins:</computeroutput> —
<command>yum</command> always informs you which
<application>DNF</application> plug-ins are installed and enabled. Here,
<command>yum</command> is using the
<application>langpacks</application>,
<application>presto</application>, and
<application>refresh-packagekit</application> plug-ins. See <xref
linkend="sec-DNF_Plugins" /> for general information on
<application>DNF</application> plug-ins, or to <xref
linkend="sec-Plugin_Descriptions" /> for descriptions of specific plug-ins.
</para>
</listitem>
<listitem>
@@ -152,12 +152,12 @@ Is this ok [y/N]:</screen>
<command>yum</command> presents the update information and then
prompts you as to whether you want it to perform the update;
<command>yum</command> runs interactively by default. If you already know
which transactions <command>yum</command> plans to perform, you can use the
<option>-y</option> option to automatically answer
<command>yes</command> to any questions <command>yum</command> may
ask (in which case it runs non-interactively). However, you should always examine which
changes <command>yum</command> plans to make to the system so that you can
easily troubleshoot any problems that might arise.
</para>
<para>
- If a transaction does go awry, you can view Yum's transaction history by
using the <command>yum history</command> command as described in <xref
linkend="sec-Yum-Transaction_History" />.
+ If a transaction does go awry, you can view DNF's transaction history by
using the <command>yum history</command> command as described in <xref
linkend="sec-DNF-Transaction_History" />.
</para>
</listitem>
</orderedlist>
- <important
id="important-Important-Updating_and_Installing_Kernels_with_Yum">
- <title>Updating and installing kernels with Yum</title>
+ <important
id="important-Important-Updating_and_Installing_Kernels_with_DNF">
+ <title>Updating and installing kernels with DNF</title>
<para>
<command>yum</command> always
<emphasis>installs</emphasis> a new kernel in the same sense that
<application>RPM</application> installs a new kernel when you use the command
<command>rpm -i kernel</command>. Therefore, you do not need to worry about
the distinction between <emphasis>installing</emphasis> and
<emphasis>upgrading</emphasis> a kernel package when you use
<command>yum</command>: it will do the right thing, regardless of whether you
are using the <command>yum update</command> or <command>yum
install</command> command.
</para>
@@ -169,7 +169,7 @@ Is this ok [y/N]:</screen>
Updating All Packages and Their Dependencies
</bridgehead>
<indexterm>
- <primary>Yum Updates</primary>
+ <primary>DNF Updates</primary>
<secondary>updating all packages and dependencies</secondary>
</indexterm>
<para>
@@ -180,7 +180,7 @@ Is this ok [y/N]:</screen>
Updating Security-Related Packages
</bridgehead>
<indexterm>
- <primary>Yum Updates</primary>
+ <primary>DNF Updates</primary>
<secondary>updating security-related packages</secondary>
</indexterm>
<indexterm>
@@ -194,7 +194,7 @@ Is this ok [y/N]:</screen>
<see>Security</see>
</indexterm>
<para>
- Discovering which packages have security updates available and then updating
those packages quickly and easily is important. Yum provides the plug-in for this purpose.
The <application>security</application> plug-in extends the
<command>yum</command> command with a set of highly-useful security-centric
commands, subcommands and options. See <xref
linkend="sec-Plugin_Descriptions" /> for specific information.
+ Discovering which packages have security updates available and then updating
those packages quickly and easily is important. DNF provides the plug-in for this purpose.
The <application>security</application> plug-in extends the
<command>yum</command> command with a set of highly-useful security-centric
commands, subcommands and options. See <xref
linkend="sec-Plugin_Descriptions" /> for specific information.
</para>
</section>
<section id="sec-Preserving_Configuration_File_Changes">
@@ -203,7 +203,7 @@ Is this ok [y/N]:</screen>
<primary>Configuration File Changes</primary>
</indexterm>
<para>
- You will inevitably make changes to the configuration files installed by packages
as you use your &MAJOROS; system. <application>RPM</application>, which
Yum uses to perform changes to the system, provides a mechanism for ensuring their
integrity. See <xref linkend="sec-Installing_and_Upgrading" /> for details
on how to manage changes to configuration files across package upgrades.
+ You will inevitably make changes to the configuration files installed by packages
as you use your &MAJOROS; system. <application>RPM</application>, which
DNF uses to perform changes to the system, provides a mechanism for ensuring their
integrity. See <xref linkend="sec-Installing_and_Upgrading" /> for details
on how to manage changes to configuration files across package upgrades.
</para>
</section>
</section>
@@ -214,19 +214,19 @@ Is this ok [y/N]:</screen>
<secondary>packages and package groups</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>packages and package groups</secondary>
</indexterm>
<section id="sec-Searching_Packages">
<title>Searching Packages</title>
<indexterm>
<primary>packages</primary>
- <secondary>searching packages with Yum</secondary>
+ <secondary>searching packages with DNF</secondary>
<tertiary>yum search</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>searching packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>searching packages with DNF</secondary>
<tertiary>yum search</tertiary>
</indexterm>
<para>
@@ -248,12 +248,12 @@ komparator.x86_64 : Kompare and merge two folders
Name and summary matches only, use "search all" for
everything.</screen>
<indexterm>
<primary>packages</primary>
- <secondary>searching for packages with Yum</secondary>
+ <secondary>searching for packages with DNF</secondary>
<tertiary>yum search</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>searching for packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>searching for packages with DNF</secondary>
<tertiary>yum search</tertiary>
</indexterm>
<para>
@@ -264,30 +264,30 @@ komparator.x86_64 : Kompare and merge two folders
<title>Listing Packages</title>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum search</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list</tertiary>
</indexterm>
<para>
<command>yum list</command> and related commands provide information
about packages, package groups, and repositories.
</para>
<para>
- All of Yum's list commands allow you to filter the results by appending one
or more <firstterm>glob expressions</firstterm> as arguments. Glob expressions
are normal strings of characters which contain one or more of the wildcard characters
<command>*</command> (which expands to match any character multiple times) and
<command>?</command> (which expands to match any one character).
+ All of DNF's list commands allow you to filter the results by appending one
or more <firstterm>glob expressions</firstterm> as arguments. Glob expressions
are normal strings of characters which contain one or more of the wildcard characters
<command>*</command> (which expands to match any character multiple times) and
<command>?</command> (which expands to match any one character).
</para>
<note id="note-Tip-Filtering_Results_with_Glob_Expressions">
<title>Filtering results with glob expressions</title>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary> Glob expressions</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>Glob expressions</tertiary>
</indexterm>
<para>
@@ -342,12 +342,12 @@ abrt-plugin-rhtsupport.x86_64 2.0.2-5.fc15
updates</screen>
<term>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list all</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list all</tertiary>
</indexterm>
<command>yum list all</command>
@@ -379,12 +379,12 @@ NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15
@fedora
<term>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list installed</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list installed</tertiary>
</indexterm>
<command>yum list installed</command>
@@ -409,12 +409,12 @@ krb5-libs.x86_64 1.9-7.fc15
@fedora</screen>
<term>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list available</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum list available</tertiary>
</indexterm>
<command>yum list available</command>
@@ -451,12 +451,12 @@ gstreamer-plugins-good-devel-docs.noarch 0.10.29-1.fc15
updates</scre
<term>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum grouplist</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum grouplist</tertiary>
</indexterm>
<command>yum grouplist</command>
@@ -484,12 +484,12 @@ Installed Groups:
<term>
<indexterm>
<primary>packages</primary>
- <secondary>listing packages with Yum</secondary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum repolist</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>listing packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>listing packages with DNF</secondary>
<tertiary>yum repolist</tertiary>
</indexterm>
<command>yum repolist</command>
@@ -515,12 +515,12 @@ repolist: 23,213</screen>
<title>Displaying Package Information</title>
<indexterm>
<primary>packages</primary>
- <secondary>displaying packages with Yum</secondary>
+ <secondary>displaying packages with DNF</secondary>
<tertiary>yum info</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>displaying packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>displaying packages with DNF</secondary>
<tertiary>yum info</tertiary>
</indexterm>
<para>
@@ -552,15 +552,15 @@ Description : abrt is a tool to help users to detect defects in
applications and
<tertiary>yum info</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>displaying packages</secondary>
<tertiary>yum info</tertiary>
</indexterm>
<para>
- The <command>yum info
<replaceable>package_name</replaceable></command> command is similar to
the <command>rpm -q --info
<replaceable>package_name</replaceable></command> command, but provides
as additional information the ID of the Yum repository the RPM package is found in (look
for the <computeroutput>From repo:</computeroutput> line in the output).
+ The <command>yum info
<replaceable>package_name</replaceable></command> command is similar to
the <command>rpm -q --info
<replaceable>package_name</replaceable></command> command, but provides
as additional information the ID of the DNF repository the RPM package is found in (look
for the <computeroutput>From repo:</computeroutput> line in the output).
</para>
<para>
- You can also query the Yum database for alternative and useful information about
a package by using the following command:
+ You can also query the DNF database for alternative and useful information about
a package by using the following command:
</para>
<synopsis><command>yumdb</command>
<option>info</option>
<replaceable>package_name</replaceable></synopsis>
<para>
@@ -585,14 +585,14 @@ yum-3.2.29-4.fc15.noarch
<title>Installing Packages</title>
<indexterm>
<primary>packages</primary>
- <secondary>installing with Yum</secondary>
+ <secondary>installing with DNF</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>installing with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>installing with DNF</secondary>
</indexterm>
<para>
- Yum allows you to install both a single package and multiple packages, as well as
a package group of your choice.
+ DNF allows you to install both a single package and multiple packages, as well as
a package group of your choice.
</para>
<bridgehead id="bh-Installing_Individual_packages">
Installing Individual Packages
@@ -641,11 +641,11 @@ Filename : /usr/sbin/named</screen>
</bridgehead>
<indexterm>
<primary>packages</primary>
- <secondary>installing a package group with Yum</secondary>
+ <secondary>installing a package group with DNF</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>installing a package group with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>installing a package group with DNF</secondary>
</indexterm>
<para>
A package group is similar to a package: it is not useful by itself, but
installing one pulls a group of dependent packages that serve a common purpose. A package
group has a name and a <firstterm>groupid</firstterm>. The <command>yum
grouplist -v</command> command lists the names of all package groups, and, next to
each of them, their groupid in parentheses. The groupid is always the term in the last
pair of parentheses, such as <literal>kde-desktop</literal> in the following
example:
@@ -658,7 +658,7 @@ Loading "refresh-packagekit" plugin
Not loading "whiteout" plugin, as it is disabled
Adding en_US to language list
Config time: 0.900
-Yum Version: 3.2.29
+DNF Version: 3.2.29
Setting up Group Process
rpmdb time: 0.002
group time: 0.995
@@ -689,26 +689,26 @@ Done</screen>
<title>Removing Packages</title>
<indexterm>
<primary>packages</primary>
- <secondary>uninstalling packages with Yum</secondary>
+ <secondary>uninstalling packages with DNF</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>uninstalling packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>uninstalling packages with DNF</secondary>
</indexterm>
<para>
- Similarly to package installation, Yum allows you to uninstall (remove in
<application>RPM</application> and Yum terminology) both individual packages
and a package group.
+ Similarly to package installation, DNF allows you to uninstall (remove in
<application>RPM</application> and DNF terminology) both individual packages
and a package group.
</para>
<bridgehead id="bh-Removing_Individual_Packages">
Removing Individual Packages
</bridgehead>
<indexterm>
<primary>packages</primary>
- <secondary>uninstalling packages with Yum</secondary>
+ <secondary>uninstalling packages with DNF</secondary>
<tertiary>yum remove package_name</tertiary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>uninstalling packages with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>uninstalling packages with DNF</secondary>
<tertiary>yum remove package_name</tertiary>
</indexterm>
<para>
@@ -747,7 +747,7 @@ Done</screen>
<warning
id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It">
<title>Removing a package when other packages depend on it</title>
<para>
- Yum is not able to remove a package without also removing packages which depend
on it. This type of operation can only be performed by
<application>RPM</application>, is not advised, and can potentially leave your
system in a non-functioning state or cause applications to misbehave and/or crash. For
further information, refer to <xref linkend="s2-rpm-uninstalling" /> in
the <application>RPM</application> chapter.
+ DNF is not able to remove a package without also removing packages which depend
on it. This type of operation can only be performed by
<application>RPM</application>, is not advised, and can potentially leave your
system in a non-functioning state or cause applications to misbehave and/or crash. For
further information, refer to <xref linkend="s2-rpm-uninstalling" /> in
the <application>RPM</application> chapter.
</para>
</warning>
<bridgehead id="bh-Removing_a_Package_Group">
@@ -768,23 +768,23 @@ Done</screen>
<title>Intelligent package group removal</title>
<indexterm>
<primary>packages</primary>
- <secondary>removing package groups with Yum</secondary>
+ <secondary>removing package groups with DNF</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>uninstalling package groups with Yum</secondary>
+ <primary>DNF</primary>
+ <secondary>uninstalling package groups with DNF</secondary>
</indexterm>
<para>
When you tell <application>yum</application> to remove a package
group, it will remove every package in that group, even if those packages are members of
other package groups or dependencies of other installed packages. However, you can
instruct <command>yum</command> to remove only those packages which are not
required by any other packages or groups by adding the
<option>groupremove_leaf_only=1</option> directive to the
<literal>[main]</literal> section of the
<filename>/etc/yum.conf</filename> configuration file. For more information on
this directive, refer to <xref linkend="sec-Setting_main_Options" />.
</para>
</important>
</section>
- <section id="sec-Yum-Transaction_History">
+ <section id="sec-DNF-Transaction_History">
<title>Working with Transaction History</title>
<para>
- The <command>yum history</command> command allows users to review
information about a timeline of Yum transactions, the dates and times on when they
occurred, the number of packages affected, whether transactions succeeded or were aborted,
and if the RPM database was changed between transactions. Additionally, this command can
be used to undo or redo certain transactions.
+ The <command>yum history</command> command allows users to review
information about a timeline of DNF transactions, the dates and times on when they
occurred, the number of packages affected, whether transactions succeeded or were aborted,
and if the RPM database was changed between transactions. Additionally, this command can
be used to undo or redo certain transactions.
</para>
- <bridgehead id="bh-Yum-Transaction_History-Listing">
+ <bridgehead id="bh-DNF-Transaction_History-Listing">
Listing Transactions
</bridgehead>
<para>
@@ -837,16 +837,16 @@ history list</screen>
</listitem>
<listitem>
<para>
- <computeroutput>Action(s)</computeroutput> — a list of
actions that were performed during a transaction as described in <xref
linkend="tabl-Yum-Transaction_History-Actions" />.
+ <computeroutput>Action(s)</computeroutput> — a list of
actions that were performed during a transaction as described in <xref
linkend="tabl-DNF-Transaction_History-Actions" />.
</para>
</listitem>
<listitem>
<para>
- <computeroutput>Altered</computeroutput> — the number
of packages that were affected by a transaction, possibly followed by additional
information as described in <xref
linkend="tabl-Yum-Transaction_History-Altered" />.
+ <computeroutput>Altered</computeroutput> — the number
of packages that were affected by a transaction, possibly followed by additional
information as described in <xref
linkend="tabl-DNF-Transaction_History-Altered" />.
</para>
</listitem>
</itemizedlist>
- <table id="tabl-Yum-Transaction_History-Actions">
+ <table id="tabl-DNF-Transaction_History-Actions">
<title>Possible values of the Action(s) field</title>
<tgroup cols="3">
<colspec colname="Action" colnum="1"
colwidth="20*" />
@@ -935,7 +935,7 @@ history list</screen>
</tbody>
</tgroup>
</table>
- <table id="tabl-Yum-Transaction_History-Altered">
+ <table id="tabl-DNF-Transaction_History-Altered">
<title>Possible values of the Altered field</title>
<tgroup cols="2">
<colspec colname="Symbol" colnum="1"
colwidth="20*" />
@@ -956,7 +956,7 @@ history list</screen>
<literal><</literal>
</entry>
<entry>
- Before the transaction finished, the
<filename>rpmdb</filename> database was changed outside Yum.
+ Before the transaction finished, the
<filename>rpmdb</filename> database was changed outside DNF.
</entry>
</row>
<row>
@@ -964,7 +964,7 @@ history list</screen>
<literal>></literal>
</entry>
<entry>
- After the transaction finished, the
<filename>rpmdb</filename> database was changed outside Yum.
+ After the transaction finished, the
<filename>rpmdb</filename> database was changed outside DNF.
</entry>
</row>
<row>
@@ -1011,7 +1011,7 @@ history list</screen>
</tgroup>
</table>
<para>
- Yum also allows you to display a summary of all past transactions. To do so, run
the command in the following form as <systemitem
class="username">root</systemitem>:
+ DNF also allows you to display a summary of all past transactions. To do so, run
the command in the following form as <systemitem
class="username">root</systemitem>:
</para>
<synopsis><command>yum</command>
<option>history</option>
<option>summary</option></synopsis>
<para>
@@ -1061,7 +1061,7 @@ history package-list</screen>
<para>
In this example, three packages were installed during the initial system
installation: <package>subscription-manager</package>,
<package>subscription-manager-firstboot</package>, and
<package>subscription-manager-gnome</package>. In the third transaction, all
these packages were updated from version 0.95.11 to version 0.95.17.
</para>
- <bridgehead id="bh-Yum-Transaction_History-Examining">
+ <bridgehead id="bh-DNF-Transaction_History-Examining">
Examining Transactions
</bridgehead>
<para>
@@ -1124,12 +1124,12 @@ history addon-info</screen>
<itemizedlist>
<listitem>
<para>
- <computeroutput>config-main</computeroutput> — global
Yum options that were in use during the transaction. See <xref
linkend="sec-Setting_main_Options" /> for information on how to change global
options.
+ <computeroutput>config-main</computeroutput> — global
DNF options that were in use during the transaction. See <xref
linkend="sec-Setting_main_Options" /> for information on how to change global
options.
</para>
</listitem>
<listitem>
<para>
- <computeroutput>config-repos</computeroutput> — options
for individual Yum repositories. See <xref
linkend="sec-Setting_repository_Options" /> for information on how to change
options for individual repositories.
+ <computeroutput>config-repos</computeroutput> — options
for individual DNF repositories. See <xref
linkend="sec-Setting_repository_Options" /> for information on how to change
options for individual repositories.
</para>
</listitem>
<listitem>
@@ -1142,7 +1142,7 @@ history addon-info</screen>
To display selected type of additional information, run the following command as
<systemitem class="username">root</systemitem>:
</para>
<synopsis><command>yum</command>
<option>history</option> <option>addon-info</option>
<replaceable>id</replaceable>
<replaceable>information</replaceable></synopsis>
- <bridgehead id="bh-Yum-Transaction_History-Reverting">
+ <bridgehead id="bh-DNF-Transaction_History-Reverting">
Reverting and Repeating Transactions
</bridgehead>
<para>
@@ -1160,7 +1160,7 @@ history addon-info</screen>
Note that both <command>yum history undo</command> and
<command>yum history redo</command> commands merely revert or repeat the steps
that were performed during a transaction: if the transaction installed a new package, the
<command>yum history undo</command> command will uninstall it, and vice versa.
If possible, this command will also attempt to downgrade all updated packages to their
previous version, but these older packages may no longer be available. If you need to be
able to restore the system to the state before an update, consider using the
<application>fs-snapshot</application> plug-in described in <xref
linkend="sec-Plugin_Descriptions" />.
</para>
<para>
- When managing several identical systems, Yum also allows you to perform a
transaction on one of them, store the transaction details in a file, and after a period of
testing, repeat the same transaction on the remaining systems as well. To store the
transaction details to a file, type the following at a shell prompt as <systemitem
class="username">root</systemitem>:
+ When managing several identical systems, DNF also allows you to perform a
transaction on one of them, store the transaction details in a file, and after a period of
testing, repeat the same transaction on the remaining systems as well. To store the
transaction details to a file, type the following at a shell prompt as <systemitem
class="username">root</systemitem>:
</para>
<synopsis><command>yum</command> <option>-q</option>
<option>history</option> <option>addon-info</option>
<replaceable>id</replaceable> <option>saved_tx</option> >
<filename>file_name</filename></synopsis>
<para>
@@ -1170,11 +1170,11 @@ history addon-info</screen>
<para>
Note, however that the <literal>rpmdb</literal> version stored in the
file must by identical to the version on the target system. You can verify the
<literal>rpmdb</literal> version by using the <command>yum version
nogroups</command> command.
</para>
- <bridgehead id="bh-Yum-Transaction_History-New">
+ <bridgehead id="bh-DNF-Transaction_History-New">
Starting New Transaction History
</bridgehead>
<para>
- Yum stores the transaction history in a single SQLite database file. To start new
transaction history, run the following command as <systemitem
class="username">root</systemitem>:
+ DNF stores the transaction history in a single SQLite database file. To start new
transaction history, run the following command as <systemitem
class="username">root</systemitem>:
</para>
<synopsis><command>yum</command>
<option>history</option> <option>new</option></synopsis>
<para>
@@ -1182,19 +1182,19 @@ history addon-info</screen>
</para>
</section>
</section>
- <section id="sec-Configuring_Yum_and_Yum_Repositories">
- <title>Configuring Yum and Yum Repositories</title>
+ <section id="sec-Configuring_DNF_and_DNF_Repositories">
+ <title>Configuring DNF and DNF Repositories</title>
<indexterm>
- <primary>Yum</primary>
- <secondary>configuring Yum and Yum repositories</secondary>
+ <primary>DNF</primary>
+ <secondary>configuring DNF and DNF repositories</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
- <secondary>Yum repositories</secondary>
- <tertiary>configuring Yum and Yum repositories</tertiary>
+ <primary>DNF</primary>
+ <secondary>DNF repositories</secondary>
+ <tertiary>configuring DNF and DNF repositories</tertiary>
</indexterm>
<para>
- The configuration file for <command>yum</command> and related utilities
is located at <filename>/etc/yum.conf</filename>. This file contains one
mandatory <literal>[main]</literal> section, which allows you to set Yum
options that have global effect, and may also contain one or more
<literal>[<replaceable>repository</replaceable>]</literal>
sections, which allow you to set repository-specific options. However, best practice is to
define individual repositories in new or existing <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/yum.repos.d/</filename>directory. The values you
define in the <literal>[main]</literal> section of the
<filename>/etc/yum.conf</filename> file may override values set in individual
<literal>[<replaceable>repository</replaceable>]</literal>
sections.
+ The configuration file for <command>yum</command> and related utilities
is located at <filename>/etc/yum.conf</filename>. This file contains one
mandatory <literal>[main]</literal> section, which allows you to set DNF
options that have global effect, and may also contain one or more
<literal>[<replaceable>repository</replaceable>]</literal>
sections, which allow you to set repository-specific options. However, best practice is to
define individual repositories in new or existing <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/yum.repos.d/</filename>directory. The values you
define in the <literal>[main]</literal> section of the
<filename>/etc/yum.conf</filename> file may override values set in individual
<literal>[<replaceable>repository</replaceable>]</literal>
sections.
</para>
<para>
This section shows you how to:
@@ -1202,7 +1202,7 @@ history addon-info</screen>
<itemizedlist>
<listitem>
<para>
- set global Yum options by editing the <literal>[main]</literal>
section of the <filename>/etc/yum.conf</filename> configuration file;
+ set global DNF options by editing the <literal>[main]</literal>
section of the <filename>/etc/yum.conf</filename> configuration file;
</para>
</listitem>
<listitem>
@@ -1212,28 +1212,28 @@ history addon-info</screen>
</listitem>
<listitem>
<para>
- use Yum variables in <filename>/etc/yum.conf</filename> and files
in the <filename>/etc/yum.repos.d/</filename> directory so that dynamic
version and architecture values are handled correctly;
+ use DNF variables in <filename>/etc/yum.conf</filename> and files
in the <filename>/etc/yum.repos.d/</filename> directory so that dynamic
version and architecture values are handled correctly;
</para>
</listitem>
<listitem>
<para>
- add, enable, and disable Yum repositories on the command line; and,
+ add, enable, and disable DNF repositories on the command line; and,
</para>
</listitem>
<listitem>
<para>
- set up your own custom Yum repository.
+ set up your own custom DNF repository.
</para>
</listitem>
</itemizedlist>
<section id="sec-Setting_main_Options">
<title>Setting [main] Options</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>setting [main] options</secondary>
</indexterm>
<para>
- The <filename>/etc/yum.conf</filename> configuration file contains
exactly one <literal>[main]</literal> section, and while some of the key-value
pairs in this section affect how <command>yum</command> operates, others
affect how Yum treats repositories.
+ The <filename>/etc/yum.conf</filename> configuration file contains
exactly one <literal>[main]</literal> section, and while some of the key-value
pairs in this section affect how <command>yum</command> operates, others
affect how DNF treats repositories.
You can add many additional options under the <literal>[main]</literal>
section heading in <filename>/etc/yum.conf</filename>.
</para>
@@ -1277,10 +1277,10 @@ installonly_limit=3
<term><option>cachedir</option>=<replaceable>directory</replaceable></term>
<listitem>
<para>
- …where <replaceable>directory</replaceable> is an
absolute path to the directory where Yum should store its cache and database files. By
default, Yum's cache directory is <filename
class="directory">/var/cache/yum/$basearch/$releasever</filename>.
+ …where <replaceable>directory</replaceable> is an
absolute path to the directory where DNF should store its cache and database files. By
default, DNF's cache directory is <filename
class="directory">/var/cache/yum/$basearch/$releasever</filename>.
</para>
<para>
- See <xref linkend="sec-Using_Yum_Variables" /> for
descriptions of the <varname>$basearch</varname> and
<varname>$releasever</varname> Yum variables.
+ See <xref linkend="sec-Using_DNF_Variables" /> for
descriptions of the <varname>$basearch</varname> and
<varname>$releasever</varname> DNF variables.
</para>
</listitem>
</varlistentry>
@@ -1430,19 +1430,19 @@ installonly_limit=3
…where <replaceable>value</replaceable> is one of:
</para>
<para>
- <literal>0</literal> — Disable all Yum plug-ins globally.
+ <literal>0</literal> — Disable all DNF plug-ins globally.
</para>
<important
id="important-Disabling_all_plugins_is_not_advised-main_options">
<title>Disabling all plug-ins is not advised</title>
<para>
- Disabling all plug-ins is not advised because certain plug-ins provide
important <command>Yum</command> services. Disabling plug-ins globally is
provided as a convenience option, and is generally only recommended when diagnosing a
potential problem with <command>Yum</command>.
+ Disabling all plug-ins is not advised because certain plug-ins provide
important <command>DNF</command> services. Disabling plug-ins globally is
provided as a convenience option, and is generally only recommended when diagnosing a
potential problem with <command>DNF</command>.
</para>
</important>
<para>
- <literal>1</literal> — Enable all Yum plug-ins globally. With
<option>plugins=1</option>, you can still disable a specific Yum plug-in by
setting <option>enabled=0</option> in that plug-in's configuration file.
+ <literal>1</literal> — Enable all DNF plug-ins globally. With
<option>plugins=1</option>, you can still disable a specific DNF plug-in by
setting <option>enabled=0</option> in that plug-in's configuration file.
</para>
<para>
- For more information about various Yum plug-ins, refer to <xref
linkend="sec-Yum_Plugins" />. For further information on controlling
plug-ins, see <xref
linkend="sec-Enabling_Configuring_and_Disabling_Yum_Plugins" />.
+ For more information about various DNF plug-ins, refer to <xref
linkend="sec-DNF_Plugins" />. For further information on controlling
plug-ins, see <xref
linkend="sec-Enabling_Configuring_and_Disabling_DNF_Plugins" />.
</para>
</listitem>
</varlistentry>
@@ -1470,11 +1470,11 @@ installonly_limit=3
<section id="sec-Setting_repository_Options">
<title>Setting [repository] Options</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>setting [repository] options</secondary>
</indexterm>
<para>
- The
<literal>[<replaceable>repository</replaceable>]</literal>
sections, where <replaceable>repository</replaceable> is a unique repository
ID such as <literal>my_personal_repo</literal> (spaces are not permitted),
allow you to define individual Yum repositories.
+ The
<literal>[<replaceable>repository</replaceable>]</literal>
sections, where <replaceable>repository</replaceable> is a unique repository
ID such as <literal>my_personal_repo</literal> (spaces are not permitted),
allow you to define individual DNF repositories.
</para>
<para>
The following is a bare-minimum example of the form a
<literal>[<replaceable>repository</replaceable>]</literal> section
takes:
@@ -1527,7 +1527,7 @@
baseurl=<replaceable>repository_url</replaceable></programlisting>
</para>
<programlisting>baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</programlisting>
<para>
- Note that Yum always expands the
<varname>$releasever</varname>, <varname>$arch</varname>, and
<varname>$basearch</varname> variables in URLs. For more information about Yum
variables, refer to <xref linkend="sec-Using_Yum_Variables" />.
+ Note that DNF always expands the
<varname>$releasever</varname>, <varname>$arch</varname>, and
<varname>$basearch</varname> variables in URLs. For more information about DNF
variables, refer to <xref linkend="sec-Using_DNF_Variables" />.
</para>
</listitem>
</varlistentry>
@@ -1558,21 +1558,21 @@
baseurl=<replaceable>repository_url</replaceable></programlisting>
Many more
<literal>[<replaceable>repository</replaceable>]</literal> options
exist. For a complete list, refer to the <literal>[repository]
OPTIONS</literal> section of the <emphasis
role="bold">yum.conf</emphasis>(5) manual page.
</para>
</section>
- <section id="sec-Using_Yum_Variables">
- <title>Using Yum Variables</title>
+ <section id="sec-Using_DNF_Variables">
+ <title>Using DNF Variables</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>variables</secondary>
</indexterm>
<para>
- You can use and reference the following built-in variables in
<command>yum</command> commands and in all Yum configuration files (that is,
<filename>/etc/yum.conf</filename> and all <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/yum.repos.d/</filename> directory):
+ You can use and reference the following built-in variables in
<command>yum</command> commands and in all DNF configuration files (that is,
<filename>/etc/yum.conf</filename> and all <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/yum.repos.d/</filename> directory):
</para>
<variablelist>
<varlistentry>
<term><varname>$releasever</varname></term>
<listitem>
<para>
- You can use this variable to reference the release version of
&MAJOROS;. Yum obtains the value of <varname>$releasever</varname> from
the
<literal>distroverpkg=<replaceable>value</replaceable></literal>
line in the <filename>/etc/yum.conf</filename> configuration file. If there is
no such line in <filename>/etc/yum.conf</filename>, then
<command>yum</command> infers the correct value by deriving the version number
from the <package>redhat-release</package> package.
+ You can use this variable to reference the release version of
&MAJOROS;. DNF obtains the value of <varname>$releasever</varname> from
the
<literal>distroverpkg=<replaceable>value</replaceable></literal>
line in the <filename>/etc/yum.conf</filename> configuration file. If there is
no such line in <filename>/etc/yum.conf</filename>, then
<command>yum</command> infers the correct value by deriving the version number
from the <package>redhat-release</package> package.
</para>
</listitem>
</varlistentry>
@@ -1616,7 +1616,7 @@
baseurl=<replaceable>repository_url</replaceable></programlisting>
<section id="sec-Viewing_the_Current_Configuration">
<title>Viewing the Current Configuration</title>
<para>
- To display the current values of global Yum options (that is, the options
specified in the <literal>[main]</literal> section of the
<filename>/etc/yum.conf</filename> file), run the
<command>yum-config-manager</command> with no command line options:
+ To display the current values of global DNF options (that is, the options
specified in the <literal>[main]</literal> section of the
<filename>/etc/yum.conf</filename> file), run the
<command>yum-config-manager</command> with no command line options:
</para>
<synopsis><command>yum-config-manager</command></synopsis>
<para>
@@ -1641,17 +1641,17 @@ bugtracker_url =
https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20E
cache = 0
<lineannotation>[output truncated]</lineannotation></screen>
</section>
- <section id="sec-Managing_Yum_Repositories">
- <title>Adding, Enabling, and Disabling a Yum Repository</title>
+ <section id="sec-Managing_DNF_Repositories">
+ <title>Adding, Enabling, and Disabling a DNF Repository</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>repository</secondary>
</indexterm>
<para>
- <xref linkend="sec-Setting_repository_Options" /> described
various options you can use to define a Yum repository. This section explains how to add,
enable, and disable a repository by using the
<command>yum-config-manager</command> command.
+ <xref linkend="sec-Setting_repository_Options" /> described
various options you can use to define a DNF repository. This section explains how to add,
enable, and disable a repository by using the
<command>yum-config-manager</command> command.
</para>
- <bridgehead id="bh-Managing_Yum_Repositories-Adding">
- Adding a Yum Repository
+ <bridgehead id="bh-Managing_DNF_Repositories-Adding">
+ Adding a DNF Repository
</bridgehead>
<para>
To define a new repository, you can either add a
<literal>[<replaceable>repository</replaceable>]</literal> section
to the <filename>/etc/yum.conf</filename> file, or to a <filename
class="extension">.repo</filename> file in the <filename
class="directory">/etc/yum.repos.d/</filename> directory. All files
with the <filename class="extension">.repo</filename> file extension
in this directory are read by <command>yum</command>, and best practice is to
define your repositories here instead of in
<filename>/etc/yum.conf</filename>.
@@ -1663,7 +1663,7 @@ cache = 0
</para>
</warning>
<para>
- Yum repositories commonly provide their own <filename
class="extension">.repo</filename> file. To add such a repository to
your system and enable it, run the following command as <systemitem
class="username">root</systemitem>:
+ DNF repositories commonly provide their own <filename
class="extension">.repo</filename> file. To add such a repository to
your system and enable it, run the following command as <systemitem
class="username">root</systemitem>:
</para>
<synopsis><command>yum-config-manager</command>
<option>--add-repo</option>
<replaceable>repository_url</replaceable></synopsis>
<para>
@@ -1675,8 +1675,8 @@ adding repo from:
http://www.example.com/example.repo
grabbing file
http://www.example.com/example.repo to /etc/yum.repos.d/example.repo
example.repo | 413 B 00:00
repo saved to /etc/yum.repos.d/example.repo</screen>
- <bridgehead id="bh-Managing_Yum_Repositories-Enabling">
- Enabling a Yum Repository
+ <bridgehead id="bh-Managing_DNF_Repositories-Enabling">
+ Enabling a DNF Repository
</bridgehead>
<para>
To enable a particular repository or repositories, type the following at a shell
prompt as <systemitem class="username">root</systemitem>:
@@ -1702,11 +1702,11 @@ cachedir = /var/cache/yum/x86_64/6Server/example
<para>
When successful, the <command>yum-config-manager --enable</command>
command displays the current repository configuration.
</para>
- <bridgehead id="bh-Managing_Yum_Repositories-Disabling">
- Disabling a Yum Repository
+ <bridgehead id="bh-Managing_DNF_Repositories-Disabling">
+ Disabling a DNF Repository
</bridgehead>
<para>
- To disable a Yum repository, run the following command as <systemitem
class="username">root</systemitem>:
+ To disable a DNF repository, run the following command as <systemitem
class="username">root</systemitem>:
</para>
<synopsis><command>yum-config-manager</command>
<option>--disable</option>
<replaceable>repository</replaceable>…</synopsis>
<para>
@@ -1717,16 +1717,16 @@ cachedir = /var/cache/yum/x86_64/6Server/example
When successful, the <command>yum-config-manager --disable</command>
command displays the current configuration.
</para>
</section>
- <section id="sec-Creating_a_Yum_Repository">
- <title>Creating a Yum Repository</title>
+ <section id="sec-Creating_a_DNF_Repository">
+ <title>Creating a DNF Repository</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>repository</secondary>
</indexterm>
<para>
- To set up a Yum repository, follow these steps:
+ To set up a DNF repository, follow these steps:
</para>
- <procedure id="procedure-Setting_Up_a_Yum_repository">
+ <procedure id="procedure-Setting_Up_a_DNF_repository">
<step>
<para>
Install the <package>createrepo</package> package:
@@ -1746,18 +1746,18 @@ cachedir = /var/cache/yum/x86_64/6Server/example
</step>
</procedure>
<para>
- This creates the necessary metadata for your Yum repository, as well as the
<application>sqlite</application> database for speeding up
<command>yum</command> operations.
+ This creates the necessary metadata for your DNF repository, as well as the
<application>sqlite</application> database for speeding up
<command>yum</command> operations.
</para>
</section>
</section>
- <section id="sec-Yum_Plugins">
- <title>Yum Plug-ins</title>
+ <section id="sec-DNF_Plugins">
+ <title>DNF Plug-ins</title>
<indexterm>
- <primary>Yum</primary>
- <secondary>Yum plug-ins</secondary>
+ <primary>DNF</primary>
+ <secondary>DNF plug-ins</secondary>
</indexterm>
<para>
- Yum provides plug-ins that extend and enhance its operations. Certain plug-ins are
installed by default. Yum always informs you which plug-ins, if any, are loaded and active
whenever you call any <command>yum</command> command. For example:
+ DNF provides plug-ins that extend and enhance its operations. Certain plug-ins are
installed by default. DNF always informs you which plug-ins, if any, are loaded and active
whenever you call any <command>yum</command> command. For example:
</para>
<screen>~]# <command>yum info yum</command>
Loaded plugins: langpacks, presto, refresh-packagekit
@@ -1765,22 +1765,22 @@ Loaded plugins: langpacks, presto, refresh-packagekit
<para>
Note that the plug-in names which follow <command>Loaded
plugins</command> are the names you can provide to the
<option>--disableplugin=<replaceable>plugin_name</replaceable></option>
option.
</para>
- <section id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins">
- <title>Enabling, Configuring, and Disabling Yum Plug-ins</title>
+ <section id="sec-Enabling_Configuring_and_Disabling_DNF_Plugins">
+ <title>Enabling, Configuring, and Disabling DNF Plug-ins</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>enabling plug-ins</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>configuring plug-ins</secondary>
</indexterm>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>disabling plug-ins</secondary>
</indexterm>
<para>
- To enable Yum plug-ins, ensure that a line beginning with
<command>plugins=</command> is present in the
<literal>[main]</literal> section of
<filename>/etc/yum.conf</filename>, and that its value is set to
<literal>1</literal>:
+ To enable DNF plug-ins, ensure that a line beginning with
<command>plugins=</command> is present in the
<literal>[main]</literal> section of
<filename>/etc/yum.conf</filename>, and that its value is set to
<literal>1</literal>:
</para>
<programlisting>plugins=1</programlisting>
<para>
@@ -1789,7 +1789,7 @@ Loaded plugins: langpacks, presto, refresh-packagekit
<important
id="important-Disabling_all_plugins_is_not_advised-plugins">
<title>Disabling all plug-ins is not advised</title>
<para>
- Disabling all plug-ins is not advised because certain plug-ins provide
important <command>Yum</command> services. Disabling plug-ins globally is
provided as a convenience option, and is generally only recommended when diagnosing a
potential problem with <command>Yum</command>.
+ Disabling all plug-ins is not advised because certain plug-ins provide
important <command>DNF</command> services. Disabling plug-ins globally is
provided as a convenience option, and is generally only recommended when diagnosing a
potential problem with <command>DNF</command>.
</para>
</important>
<para>
@@ -1798,16 +1798,16 @@ Loaded plugins: langpacks, presto, refresh-packagekit
<programlisting>[main]
enabled=1</programlisting>
<para>
- Plug-in configuration files always contain a
<literal>[main]</literal> section (similar to Yum's
<filename>/etc/yum.conf</filename> file) in which there is (or you can place
if it is missing) an <literal>enabled=</literal> option that controls whether
the plug-in is enabled when you run <command>yum</command> commands.
+ Plug-in configuration files always contain a
<literal>[main]</literal> section (similar to DNF's
<filename>/etc/yum.conf</filename> file) in which there is (or you can place
if it is missing) an <literal>enabled=</literal> option that controls whether
the plug-in is enabled when you run <command>yum</command> commands.
</para>
<para>
If you disable all plug-ins by setting <command>enabled=0</command>
in <filename>/etc/yum.conf</filename>, then all plug-ins are disabled
regardless of whether they are enabled in their individual configuration files.
</para>
<para>
- If you merely want to disable all Yum plug-ins for a single
<command>yum</command> command, use the
<option>--noplugins</option> option.
+ If you merely want to disable all DNF plug-ins for a single
<command>yum</command> command, use the
<option>--noplugins</option> option.
</para>
<para>
- If you want to disable one or more Yum plug-ins for a single
<command>yum</command> command, add the
<option>--disableplugin=<replaceable>plugin_name</replaceable></option>
option to the command. For example, to disable the
<application>presto</application> plug-in while updating a system, type:
+ If you want to disable one or more DNF plug-ins for a single
<command>yum</command> command, add the
<option>--disableplugin=<replaceable>plugin_name</replaceable></option>
option to the command. For example, to disable the
<application>presto</application> plug-in while updating a system, type:
</para>
<screen>~]# <command>yum update
--disableplugin=presto</command></screen>
<para>
@@ -1815,23 +1815,23 @@ enabled=1</programlisting>
</para>
<screen>~]# <command>yum update
--disableplugin=presto,refresh-pack*</command></screen>
</section>
- <section id="sec-Installing_More_Yum_Plugins">
- <title>Installing Additional Yum Plug-ins</title>
+ <section id="sec-Installing_More_DNF_Plugins">
+ <title>Installing Additional DNF Plug-ins</title>
<para>
- Yum plug-ins usually adhere to the
<filename>yum-plugin-<replaceable>plugin_name</replaceable></filename>
package-naming convention, but not always: the package which provides the
<application>presto</application> plug-in is named
<filename>yum-presto</filename>, for example. You can install a Yum plug-in in
the same way you install other packages. For instance, to install the
<application>security</application> plug-in, type the following at a shell
prompt:
+ DNF plug-ins usually adhere to the
<filename>yum-plugin-<replaceable>plugin_name</replaceable></filename>
package-naming convention, but not always: the package which provides the
<application>presto</application> plug-in is named
<filename>yum-presto</filename>, for example. You can install a DNF plug-in in
the same way you install other packages. For instance, to install the
<application>security</application> plug-in, type the following at a shell
prompt:
</para>
<screen>~]# <command>yum install
yum-plugin-security</command></screen>
</section>
<section id="sec-Plugin_Descriptions">
<title>Plug-in Descriptions</title>
<para>
- The following list provides descriptions of a few useful Yum plug-ins:
+ The following list provides descriptions of a few useful DNF plug-ins:
</para>
<variablelist>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>fs-snapshot</application></tertiary>
</indexterm>
@@ -1839,7 +1839,7 @@ enabled=1</programlisting>
</term>
<listitem>
<para>
- The <application>fs-snapshot</application> plug-in extends Yum
to create a snapshot of a file system before proceeding with a transaction such as a
system update or package removal. When a user decides that the changes made by the
transaction are unwanted, this mechanism allows the user to roll back to the changes that
are stored in a snapshot.
+ The <application>fs-snapshot</application> plug-in extends DNF
to create a snapshot of a file system before proceeding with a transaction such as a
system update or package removal. When a user decides that the changes made by the
transaction are unwanted, this mechanism allows the user to roll back to the changes that
are stored in a snapshot.
</para>
<para>
In order for the plug-in to work, the root file system (that is,
<filename class="directory">/</filename>) must be on an
<systemitem class="filesystem">LVM</systemitem> (Logical Volume
Manager) or <systemitem class="filesystem">Btrfs</systemitem>
volume.
@@ -1896,7 +1896,7 @@ enabled=1</programlisting>
</step>
</substeps>
<para>
- See <xref
linkend="tabl-Yum-Plugin_Descriptions-fs-snapshot" /> for a complete list of
available configuration options.
+ See <xref
linkend="tabl-DNF-Plugin_Descriptions-fs-snapshot" /> for a complete list of
available configuration options.
</para>
</step>
<step>
@@ -1993,7 +1993,7 @@ enabled=1</programlisting>
<para>
For more information on logical volume management, Btrfs, and file system
snapshots, see the <ulink
url="https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/h...
pubwork="book">&MAJOROSVER; Storage Administration
Guide</citetitle></ulink>. For additional information about the plug-in and
its configuration, refer to the <emphasis
role="bold">yum-fs-snapshot</emphasis>(1) and <emphasis
role="bold">yum-fs-snapshot.conf</emphasis>(5) manual pages.
</para>
- <table id="tabl-Yum-Plugin_Descriptions-fs-snapshot">
+ <table id="tabl-DNF-Plugin_Descriptions-fs-snapshot">
<title>Supported <filename>fs-snapshot.conf</filename>
directives</title>
<tgroup cols="3">
<colspec colname="section" colnum="1"
colwidth="15*" />
@@ -2060,7 +2060,7 @@ enabled=1</programlisting>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>kabi</application></tertiary>
</indexterm>
@@ -2071,9 +2071,9 @@ enabled=1</programlisting>
The <application>kabi</application> plug-in checks whether a
driver update package conforms with official &OSORG; <firstterm>kernel
Application Binary Interface</firstterm> (<acronym>kABI</acronym>). With
this plug-in enabled, when a user attempts to install a package that uses kernel symbols
which are not on a whitelist, a warning message is written to the system log.
Additionally, configuring the plug-in to run in enforcing mode prevents such packages from
being installed at all.
</para>
<para>
- To configure the <application>kabi</application> plug-in, edit
the configuration file located in
<filename>/etc/yum/pluginconf.d/kabi.conf</filename>. See <xref
linkend="tabl-Yum-Plugin_Descriptions-kabi" /> for a list of directives that
can be used in the <option>[main]</option> section.
+ To configure the <application>kabi</application> plug-in, edit
the configuration file located in
<filename>/etc/yum/pluginconf.d/kabi.conf</filename>. See <xref
linkend="tabl-DNF-Plugin_Descriptions-kabi" /> for a list of directives that
can be used in the <option>[main]</option> section.
</para>
- <table id="tabl-Yum-Plugin_Descriptions-kabi">
+ <table id="tabl-DNF-Plugin_Descriptions-kabi">
<title>Supported <filename>kabi.conf</filename>
directives</title>
<tgroup cols="2">
<colspec colname="directive" colnum="1"
colwidth="30*" />
@@ -2122,7 +2122,7 @@ enabled=1</programlisting>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>presto</application></tertiary>
</indexterm>
@@ -2130,7 +2130,7 @@ enabled=1</programlisting>
</term>
<listitem>
<para>
- The <application>presto</application> plug-in adds support to
Yum for downloading <firstterm>delta RPM</firstterm> packages, during updates,
from repositories which have <application>presto</application> metadata
enabled. Delta RPMs contain only the differences between the version of the package
installed on the client requesting the RPM package and the updated version in the
repository.
+ The <application>presto</application> plug-in adds support to
DNF for downloading <firstterm>delta RPM</firstterm> packages, during updates,
from repositories which have <application>presto</application> metadata
enabled. Delta RPMs contain only the differences between the version of the package
installed on the client requesting the RPM package and the updated version in the
repository.
</para>
<para>
Downloading a delta RPM is much quicker than downloading the entire updated
package, and can speed up updates considerably. Once the delta RPMs are downloaded, they
must be rebuilt to apply the difference to the currently-installed package and thus create
the full, updated package. This process takes CPU time on the installing machine. Using
delta RPMs is therefore a tradeoff between time-to-download, which depends on the network
connection, and time-to-rebuild, which is CPU-bound. Using the
<application>presto</application> plug-in is recommended for fast machines and
systems with slower network connections, while slower machines on very fast connections
<emphasis>may</emphasis> benefit more from downloading normal RPM packages,
that is, by disabling <application>presto</application>.
@@ -2141,7 +2141,7 @@ enabled=1</programlisting>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>protect-packages</application></tertiary>
</indexterm>
@@ -2160,7 +2160,7 @@ enabled=1</programlisting>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>refresh-packagekit</application></tertiary>
</indexterm>
@@ -2175,7 +2175,7 @@ enabled=1</programlisting>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>rhnplugin</application></tertiary>
</indexterm>
@@ -2193,7 +2193,7 @@ enabled=1</programlisting>
<varlistentry>
<term>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>plug-ins</secondary>
<tertiary><application>security</application></tertiary>
</indexterm>
@@ -2201,7 +2201,7 @@ enabled=1</programlisting>
</term>
<listitem>
<para>
- Discovering information about and applying security updates easily and
often is important to all system administrators. For this reason Yum provides the
<application>security</application> plug-in, which extends
<command>yum</command> with a set of highly-useful security-related commands,
subcommands and options.
+ Discovering information about and applying security updates easily and
often is important to all system administrators. For this reason DNF provides the
<application>security</application> plug-in, which extends
<command>yum</command> with a set of highly-useful security-related commands,
subcommands and options.
</para>
<para>
You can check for security-related updates as follows:
@@ -2255,7 +2255,7 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15
updates
<section id="sec-Additional_Resources">
<title>Additional Resources</title>
<indexterm>
- <primary>Yum</primary>
+ <primary>DNF</primary>
<secondary>Additional Resources</secondary>
</indexterm>
<variablelist>
@@ -2265,7 +2265,7 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15
updates
</term>
<listitem>
<para>
- The <literal>Yum Guides</literal> section of the Yum wiki
contains more documentation.
+ The <literal>DNF Guides</literal> section of the DNF wiki
contains more documentation.
</para>
</listitem>
</varlistentry>