commit 2db43358a31c23792336e73f48516b61fd9fa3e8
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Apr 16 14:54:23 2015 +0200
change all yum to dnf except in package names
en-US/DNF.xml | 460 ++++++++++++++++++++++++++++----------------------------
1 files changed, 230 insertions(+), 230 deletions(-)
---
diff --git a/en-US/DNF.xml b/en-US/DNF.xml
index ca62f53..8eb17fb 100644
--- a/en-US/DNF.xml
+++ b/en-US/DNF.xml
@@ -20,7 +20,7 @@
<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.
+ You must have superuser privileges in order to use
<command>dnf</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>
</note>
<section id="sec-Checking_For_and_Updating_Packages">
@@ -34,11 +34,11 @@
<para>
To see which installed packages on your system have updates available, use the
following command:
</para>
- <synopsis><command>yum</command>
<option>check-update</option></synopsis>
+ <synopsis><command>dnf</command>
<option>check-update</option></synopsis>
<para>
For example:
</para>
- <screen>~]# <command>yum check-update</command>
+ <screen>~]# <command>dnf check-update</command>
Loaded plugins: langpacks, presto, refresh-packagekit
PackageKit.x86_64 0.6.14-2.fc15 fedora
@@ -82,7 +82,7 @@ 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), 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>.
+ The output also shows us that we can update the kernel (the kernel package), DNF
and <application>RPM</application> themselves (the
<filename>dnf</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>dnf</command>.
</para>
</section>
<section id="sec-Updating_Packages">
@@ -104,11 +104,11 @@ yum.noarch 3.2.29-5.fc15
fedora</scree
<para>
To update a single package, run the following command as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>yum</command>
<option>update</option>
<replaceable>package_name</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>update</option>
<replaceable>package_name</replaceable></synopsis>
<para>
For example, to update the <package>udev</package> package, type:
</para>
- <screen>~]# <command>yum update udev</command>
+ <screen>~]# <command>dnf update udev</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Updating Red Hat repositories.
INFO:rhsm-app.repolib:repos updated: 0
@@ -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>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.
+ <computeroutput>Loaded plugins:</computeroutput> —
<command>dnf</command> always informs you which
<application>DNF</application> plug-ins are installed and enabled. Here,
<command>dnf</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>
@@ -149,17 +149,17 @@ Is this ok [y/N]:</screen>
</listitem>
<listitem>
<para>
- <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.
+ <command>dnf</command> presents the update information and then
prompts you as to whether you want it to perform the update;
<command>dnf</command> runs interactively by default. If you already know
which transactions <command>dnf</command> plans to perform, you can use the
<option>-y</option> option to automatically answer
<command>yes</command> to any questions <command>dnf</command> may
ask (in which case it runs non-interactively). However, you should always examine which
changes <command>dnf</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 DNF's transaction history by
using the <command>yum history</command> command as described in <xref
linkend="sec-DNF-Transaction_History" />.
+ If a transaction does go awry, you can view DNF's transaction history by
using the <command>dnf history</command> command as described in <xref
linkend="sec-DNF-Transaction_History" />.
</para>
</listitem>
</orderedlist>
<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.
+ <command>dnf</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>dnf</command>: it will do the right thing, regardless of whether you
are using the <command>dnf update</command> or <command>dnf
install</command> command.
</para>
<para>
When using <application>RPM</application>, on the other hand, it is
important to use the <command>rpm -i kernel</command> command (which installs
a new kernel) instead of <command>rpm -u kernel</command> (which
<emphasis>replaces</emphasis> the current kernel). See <xref
linkend="sec-Installing_and_Upgrading" /> for more information on
installing/updating kernels with <application>RPM</application>.
@@ -173,9 +173,9 @@ Is this ok [y/N]:</screen>
<secondary>updating all packages and dependencies</secondary>
</indexterm>
<para>
- To update all packages and their dependencies, simply enter <command>yum
update</command> (without any arguments):
+ To update all packages and their dependencies, simply enter <command>dnf
update</command> (without any arguments):
</para>
- <screen><command>yum update</command></screen>
+ <screen><command>dnf update</command></screen>
<bridgehead id="bh-Updating_Security-Related_Packages">
Updating Security-Related Packages
</bridgehead>
@@ -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. 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.
+ 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>dnf</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">
@@ -222,21 +222,21 @@ Is this ok [y/N]:</screen>
<indexterm>
<primary>packages</primary>
<secondary>searching packages with DNF</secondary>
- <tertiary>yum search</tertiary>
+ <tertiary>dnf search</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>searching packages with DNF</secondary>
- <tertiary>yum search</tertiary>
+ <tertiary>dnf search</tertiary>
</indexterm>
<para>
You can search all <acronym>RPM</acronym> package names, descriptions
and summaries by using the following command:
</para>
- <synopsis><command>yum</command>
<option>search</option>
<replaceable>term</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>search</option>
<replaceable>term</replaceable>…</synopsis>
<para>
This command displays the list of matches for each term. For example, to list all
packages that match <quote>meld</quote> or <quote>kompare</quote>,
type:
</para>
- <screen>~]# <command>yum search meld kompare</command>
+ <screen>~]# <command>dnf search meld kompare</command>
Loaded plugins: langpacks, presto, refresh-packagekit
============================== N/S Matched: meld ===============================
meld.noarch : Visual diff and merge tool
@@ -249,15 +249,15 @@ komparator.x86_64 : Kompare and merge two folders
<indexterm>
<primary>packages</primary>
<secondary>searching for packages with DNF</secondary>
- <tertiary>yum search</tertiary>
+ <tertiary>dnf search</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>searching for packages with DNF</secondary>
- <tertiary>yum search</tertiary>
+ <tertiary>dnf search</tertiary>
</indexterm>
<para>
- The <command>yum search</command> command is useful for searching for
packages you do not know the name of, but for which you know a related term.
+ The <command>dnf search</command> command is useful for searching for
packages you do not know the name of, but for which you know a related term.
</para>
</section>
<section id="sec-Listing_Packages">
@@ -265,15 +265,15 @@ komparator.x86_64 : Kompare and merge two folders
<indexterm>
<primary>packages</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum search</tertiary>
+ <tertiary>dnf search</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list</tertiary>
+ <tertiary>dnf list</tertiary>
</indexterm>
<para>
- <command>yum list</command> and related commands provide information
about packages, package groups, and repositories.
+ <command>dnf list</command> and related commands provide information
about packages, package groups, and repositories.
</para>
<para>
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).
@@ -291,7 +291,7 @@ komparator.x86_64 : Kompare and merge two folders
<tertiary>Glob expressions</tertiary>
</indexterm>
<para>
- Be careful to escape the glob expressions when passing them as arguments to a
<command>yum</command> command, otherwise the Bash shell will interpret these
expressions as <firstterm>pathname expansions</firstterm>, and potentially
pass all files in the current directory that match the globs to
<command>yum</command>. To make sure the glob expressions are passed to
<command>yum</command> as intended, either:
+ Be careful to escape the glob expressions when passing them as arguments to a
<command>dnf</command> command, otherwise the Bash shell will interpret these
expressions as <firstterm>pathname expansions</firstterm>, and potentially
pass all files in the current directory that match the globs to
<command>dnf</command>. To make sure the glob expressions are passed to
<command>dnf</command> as intended, either:
</para>
<itemizedlist>
<listitem>
@@ -312,7 +312,7 @@ komparator.x86_64 : Kompare and merge two folders
<variablelist>
<varlistentry>
<term>
- <command>yum list
<replaceable>glob_expression</replaceable>…</command>
+ <command>dnf list
<replaceable>glob_expression</replaceable>…</command>
</term>
<listitem>
<para>
@@ -323,7 +323,7 @@ komparator.x86_64 : Kompare and merge two folders
<para>
Packages with various ABRT addons and plug-ins either begin with
<quote>abrt-addon-</quote>, or <quote>abrt-plugin-</quote>. To
list these packages, type the following at a shell prompt:
</para>
- <screen>~]# <command>yum list abrt-addon\*
abrt-plugin\*</command>
+ <screen>~]# <command>dnf list abrt-addon\*
abrt-plugin\*</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
abrt-addon-ccpp.x86_64 2.0.2-5.fc15 @fedora
@@ -343,14 +343,14 @@ abrt-plugin-rhtsupport.x86_64 2.0.2-5.fc15
updates</screen>
<indexterm>
<primary>packages</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list all</tertiary>
+ <tertiary>dnf list all</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list all</tertiary>
+ <tertiary>dnf list all</tertiary>
</indexterm>
- <command>yum list all</command>
+ <command>dnf list all</command>
</term>
<listitem>
<para>
@@ -358,7 +358,7 @@ abrt-plugin-rhtsupport.x86_64 2.0.2-5.fc15
updates</screen>
</para>
<example
id="ex-Listing_all_installed_and_available_packages">
<title>Listing all installed and available packages</title>
- <screen>~]# <command>yum list all</command>
+ <screen>~]# <command>dnf list all</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
ConsoleKit.x86_64 0.4.4-1.fc15 @fedora
@@ -380,14 +380,14 @@ NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15
@fedora
<indexterm>
<primary>packages</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list installed</tertiary>
+ <tertiary>dnf list installed</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list installed</tertiary>
+ <tertiary>dnf list installed</tertiary>
</indexterm>
- <command>yum list installed</command>
+ <command>dnf list installed</command>
</term>
<listitem>
<para>
@@ -398,7 +398,7 @@ NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15
@fedora
<para>
To list all installed packages that begin with
<quote>krb</quote> followed by exactly one character and a hyphen, type:
</para>
- <screen>~]# <command>yum list installed
"krb?-*"</command>
+ <screen>~]# <command>dnf list installed
"krb?-*"</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
krb5-libs.x86_64 1.9-7.fc15 @fedora</screen>
@@ -410,14 +410,14 @@ krb5-libs.x86_64 1.9-7.fc15
@fedora</screen>
<indexterm>
<primary>packages</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list available</tertiary>
+ <tertiary>dnf list available</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum list available</tertiary>
+ <tertiary>dnf list available</tertiary>
</indexterm>
- <command>yum list available</command>
+ <command>dnf list available</command>
</term>
<listitem>
<para>
@@ -428,7 +428,7 @@ krb5-libs.x86_64 1.9-7.fc15
@fedora</screen>
<para>
To list all available packages with names that contain
<quote>gstreamer</quote> and then <quote>plugin</quote>, run the
following command:
</para>
- <screen>~]# <command>yum list available
gstreamer\*plugin\*</command>
+ <screen>~]# <command>dnf list available
gstreamer\*plugin\*</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Available Packages
gstreamer-plugin-crystalhd.x86_64 3.5.1-1.fc14 fedora
@@ -452,14 +452,14 @@ gstreamer-plugins-good-devel-docs.noarch 0.10.29-1.fc15
updates</scre
<indexterm>
<primary>packages</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum grouplist</tertiary>
+ <tertiary>dnf grouplist</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum grouplist</tertiary>
+ <tertiary>dnf grouplist</tertiary>
</indexterm>
- <command>yum grouplist</command>
+ <command>dnf grouplist</command>
</term>
<listitem>
<para>
@@ -467,7 +467,7 @@ gstreamer-plugins-good-devel-docs.noarch 0.10.29-1.fc15
updates</scre
</para>
<example id="ex-Listing_all_package_groups">
<title>Listing all package groups</title>
- <screen>~]# <command>yum grouplist</command>
+ <screen>~]# <command>dnf grouplist</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Group Process
Installed Groups:
@@ -485,14 +485,14 @@ Installed Groups:
<indexterm>
<primary>packages</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum repolist</tertiary>
+ <tertiary>dnf repolist</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>listing packages with DNF</secondary>
- <tertiary>yum repolist</tertiary>
+ <tertiary>dnf repolist</tertiary>
</indexterm>
- <command>yum repolist</command>
+ <command>dnf repolist</command>
</term>
<listitem>
<para>
@@ -500,7 +500,7 @@ Installed Groups:
</para>
<example id="ex-Listing_enabled_repositories">
<title>Listing enabled repositories</title>
- <screen>~]# <command>yum repolist</command>
+ <screen>~]# <command>dnf repolist</command>
Loaded plugins: langpacks, presto, refresh-packagekit
repo id repo name status
fedora Fedora 15 - i386 19,365
@@ -516,21 +516,21 @@ repolist: 23,213</screen>
<indexterm>
<primary>packages</primary>
<secondary>displaying packages with DNF</secondary>
- <tertiary>yum info</tertiary>
+ <tertiary>dnf info</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>displaying packages with DNF</secondary>
- <tertiary>yum info</tertiary>
+ <tertiary>dnf info</tertiary>
</indexterm>
<para>
To display information about one or more packages (glob expressions are valid
here as well), use the following command:
</para>
- <synopsis><command>yum</command>
<option>info</option>
<replaceable>package_name</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>info</option>
<replaceable>package_name</replaceable>…</synopsis>
<para>
For example, to display information about the <package>abrt</package>
package, type:
</para>
- <screen>~]# <command>yum info abrt</command>
+ <screen>~]# <command>dnf info abrt</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
Name : abrt
@@ -549,24 +549,24 @@ Description : abrt is a tool to help users to detect defects in
applications and
<indexterm>
<primary>packages</primary>
<secondary>displaying packages</secondary>
- <tertiary>yum info</tertiary>
+ <tertiary>dnf info</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>displaying packages</secondary>
- <tertiary>yum info</tertiary>
+ <tertiary>dnf 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 DNF repository the RPM package is found in (look
for the <computeroutput>From repo:</computeroutput> line in the output).
+ The <command>dnf 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 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>
+ <synopsis><command>dnfdb</command>
<option>info</option>
<replaceable>package_name</replaceable></synopsis>
<para>
- This command provides additional information about a package, including the
checksum of the package (and algorithm used to produce it, such as SHA-256), the command
given on the command line that was invoked to install the package (if any), and the reason
that the package is installed on the system (where
<computeroutput>user</computeroutput> indicates it was installed by the user,
and <computeroutput>dep</computeroutput> means it was brought in as a
dependency). For example, to display additional information about the
<package>yum</package> package, type:
+ This command provides additional information about a package, including the
checksum of the package (and algorithm used to produce it, such as SHA-256), the command
given on the command line that was invoked to install the package (if any), and the reason
that the package is installed on the system (where
<computeroutput>user</computeroutput> indicates it was installed by the user,
and <computeroutput>dep</computeroutput> means it was brought in as a
dependency). For example, to display additional information about the
<package>dnf</package> package, type:
</para>
- <screen>~]# <command>yumdb info yum</command>
+ <screen>~]# <command>dnfdb info dnf</command>
Loaded plugins: langpacks, presto, refresh-packagekit
yum-3.2.29-4.fc15.noarch
checksum_data = 249f21fb43c41381c8c9b0cd98d2ea5fa0aa165e81ed2009cfda74c05af67246
@@ -578,7 +578,7 @@ yum-3.2.29-4.fc15.noarch
reason = user
releasever = $releasever</screen>
<para>
- For more information on the <command>yumdb</command> command, refer
to the <emphasis role="bold">yumdb</emphasis>(8) manual page.
+ For more information on the <command>dnfdb</command> command, refer
to the <emphasis role="bold">dnfdb</emphasis>(8) manual page.
</para>
</section>
<section id="sec-Installing">
@@ -600,32 +600,32 @@ yum-3.2.29-4.fc15.noarch
<para>
To install a single package and all of its non-installed dependencies, enter a
command in the following form:
</para>
- <synopsis><command>yum</command>
<option>install</option>
<replaceable>package_name</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>install</option>
<replaceable>package_name</replaceable></synopsis>
<para>
You can also install multiple packages simultaneously by appending their names as
arguments:
</para>
- <synopsis><command>yum</command>
<option>install</option> <replaceable>package_name</replaceable>
<replaceable>package_name</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>install</option> <replaceable>package_name</replaceable>
<replaceable>package_name</replaceable>…</synopsis>
<para>
If you are installing packages on a <firstterm>multilib</firstterm>
system, such as an AMD64 or Intel64 machine, you can specify the architecture of the
package (as long as it is available in an enabled repository) by appending
<replaceable>.arch</replaceable> to the package name. For example, to install
the <package>sqlite2</package> package for
<systemitem>i586</systemitem>, type:
</para>
- <screen>~]# <command>yum install
sqlite2.i586</command></screen>
+ <screen>~]# <command>dnf install
sqlite2.i586</command></screen>
<para>
You can use glob expressions to quickly install multiple similarly-named
packages:
</para>
- <screen>~]# <command>yum install
audacious-plugins-\*</command></screen>
+ <screen>~]# <command>dnf install
audacious-plugins-\*</command></screen>
<para>
- In addition to package names and glob expressions, you can also provide file
names to <command>yum install</command>. If you know the name of the binary
you want to install, but not its package name, you can give <command>yum
install</command> the path name:
+ In addition to package names and glob expressions, you can also provide file
names to <command>dnf install</command>. If you know the name of the binary
you want to install, but not its package name, you can give <command>dnf
install</command> the path name:
</para>
- <screen>~]# <command>yum install
/usr/sbin/named</command></screen>
+ <screen>~]# <command>dnf install
/usr/sbin/named</command></screen>
<para>
- <command>yum</command> then searches through its package lists, finds
the package which provides <filename>/usr/sbin/named</filename>, if any, and
prompts you as to whether you want to install it.
+ <command>dnf</command> then searches through its package lists, finds
the package which provides <filename>/usr/sbin/named</filename>, if any, and
prompts you as to whether you want to install it.
</para>
<note id="note-Finding_which_package_owns_a_file">
<title>Finding which package owns a file</title>
<para>
- If you know you want to install the package that contains the
<filename>named</filename> binary, but you do not know in which <filename
class="directory">bin</filename> or <filename
class="directory">sbin</filename> directory is the file installed, use
the <command>yum provides</command> command with a glob expression:
+ If you know you want to install the package that contains the
<filename>named</filename> binary, but you do not know in which <filename
class="directory">bin</filename> or <filename
class="directory">sbin</filename> directory is the file installed, use
the <command>dnf provides</command> command with a glob expression:
</para>
- <screen>~]# <command>yum provides
"*bin/named"</command>
+ <screen>~]# <command>dnf provides
"*bin/named"</command>
Loaded plugins: langpacks, presto, refresh-packagekit
32:bind-9.8.0-3.P1.fc15.i686 : The Berkeley Internet Name Domain (BIND) DNS
: (Domain Name System) server
@@ -633,7 +633,7 @@ Repo : fedora
Matched from:
Filename : /usr/sbin/named</screen>
<para>
- <command>yum provides
"*/<replaceable>file_name</replaceable>"</command> is a common
and useful trick to find the packages that contain
<replaceable>file_name</replaceable>.
+ <command>dnf provides
"*/<replaceable>file_name</replaceable>"</command> is a common
and useful trick to find the packages that contain
<replaceable>file_name</replaceable>.
</para>
</note>
<bridgehead id="bh-Installing_a_Package_Group">
@@ -648,9 +648,9 @@ Filename : /usr/sbin/named</screen>
<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:
+ 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>dnf
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:
</para>
- <screen>~]# <command>yum -v grouplist kde\*</command>
+ <screen>~]# <command>dnf -v grouplist kde\*</command>
Not loading "blacklist" plugin, as it is disabled
Loading "langpacks" plugin
Loading "presto" plugin
@@ -669,21 +669,21 @@ Done</screen>
<para>
You can install a package group by passing its full group name (without the
groupid part) to <command>groupinstall</command>:
</para>
- <synopsis><command>yum</command>
<option>groupinstall</option>
<replaceable>group_name</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>groupinstall</option>
<replaceable>group_name</replaceable></synopsis>
<para>
You can also install by groupid:
</para>
- <synopsis><command>yum</command>
<option>groupinstall</option>
<replaceable>groupid</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>groupinstall</option>
<replaceable>groupid</replaceable></synopsis>
<para>
- You can even pass the groupid (or quoted name) to the
<command>install</command> command if you prepend it with an
<keysym>@</keysym>-symbol (which tells <command>yum</command> that
you want to perform a <command>groupinstall</command>):
+ You can even pass the groupid (or quoted name) to the
<command>install</command> command if you prepend it with an
<keysym>@</keysym>-symbol (which tells <command>dnf</command> that
you want to perform a <command>groupinstall</command>):
</para>
- <synopsis><command>yum</command>
<option>install</option>
@<replaceable>group</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>install</option>
@<replaceable>group</replaceable></synopsis>
<para>
- For example, the following are alternative but equivalent ways of installing the
<literal>KDE Desktop</literal> group:
+ For example, the following are alternative but equivalent ways of installing the
<literal>KDE Desktop</literal> group:
</para>
- <screen>~]# <command>yum groupinstall "KDE
Desktop"</command>
-~]# <command>yum groupinstall kde-desktop</command>
-~]# <command>yum install @kde-desktop</command></screen>
+ <screen>~]# <command>dnf groupinstall "KDE
Desktop"</command>
+~]# <command>dnf groupinstall kde-desktop</command>
+~]# <command>dnf install @kde-desktop</command></screen>
</section>
<section id="sec-Removing">
<title>Removing Packages</title>
@@ -704,21 +704,21 @@ Done</screen>
<indexterm>
<primary>packages</primary>
<secondary>uninstalling packages with DNF</secondary>
- <tertiary>yum remove package_name</tertiary>
+ <tertiary>dnf remove package_name</tertiary>
</indexterm>
<indexterm>
<primary>DNF</primary>
<secondary>uninstalling packages with DNF</secondary>
- <tertiary>yum remove package_name</tertiary>
+ <tertiary>dnf remove package_name</tertiary>
</indexterm>
<para>
To uninstall a particular package, as well as any packages that depend on it,
run the following command as <systemitem
class="username">root</systemitem>:
- </para>
- <synopsis><command>yum</command>
<option>remove</option>
<replaceable>package_name</replaceable>…</synopsis>
+ </para>
+ <synopsis><command>dnf</command>
<option>remove</option>
<replaceable>package_name</replaceable>…</synopsis>
<para>
As when you install multiple packages, you can remove several at once by adding
more package names to the command. For example, to remove
<package>totem</package>, <package>rhythmbox</package>, and
<package>sound-juicer</package>, type the following at a shell prompt:
</para>
- <screen>~]# <command>yum remove totem rhythmbox
sound-juicer</command></screen>
+ <screen>~]# <command>dnf remove totem rhythmbox
sound-juicer</command></screen>
<para>
Similar to <command>install</command>,
<command>remove</command> can take these arguments:
</para>
@@ -756,14 +756,14 @@ Done</screen>
<para>
You can remove a package group using syntax congruent with the
<command>install</command> syntax:
</para>
- <synopsis><command>yum</command>
<option>groupremove</option>
<replaceable>group</replaceable></synopsis>
-<synopsis><command>yum</command> <option>remove</option>
@<replaceable>group</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>groupremove</option>
<replaceable>group</replaceable></synopsis>
+<synopsis><command>dnf</command> <option>remove</option>
@<replaceable>group</replaceable></synopsis>
<para>
The following are alternative but equivalent ways of removing the
<literal>KDE Desktop</literal> group:
</para>
- <screen>~]# <command>yum groupremove "KDE
Desktop"</command>
-~]# <command>yum groupremove kde-desktop</command>
-~]# <command>yum remove @kde-desktop</command></screen>
+ <screen>~]# <command>dnf groupremove "KDE
Desktop"</command>
+~]# <command>dnf groupremove kde-desktop</command>
+~]# <command>dnf remove @kde-desktop</command></screen>
<important id="important-Package_Group_Removal">
<title>Intelligent package group removal</title>
<indexterm>
@@ -775,38 +775,38 @@ Done</screen>
<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" />.
+ When you tell <application>dnf</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>dnf</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/dnf.conf</filename> configuration file. For more information on
this directive, refer to <xref linkend="sec-Setting_main_Options" />.
</para>
</important>
</section>
<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 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.
+ The <command>dnf 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-DNF-Transaction_History-Listing">
Listing Transactions
</bridgehead>
<para>
- To display a list of twenty most recent transactions, as <systemitem
class="username">root</systemitem>, either run <command>yum
history</command> with no additional arguments, or type the following at a shell
prompt:
+ To display a list of twenty most recent transactions, as <systemitem
class="username">root</systemitem>, either run <command>dnf
history</command> with no additional arguments, or type the following at a shell
prompt:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>list</option></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>list</option></synopsis>
<para>
To display all transactions, add the <literal>all</literal> keyword:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>list</option>
<option>all</option></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>list</option>
<option>all</option></synopsis>
<para>
To display only transactions in a given range, use the command in the following
form:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>list</option>
<replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>list</option>
<replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
<para>
You can also list only transactions regarding a particular package or packages.
To do so, use the command with a package name or a glob expression:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>list</option>
<replaceable>glob_expression</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>list</option>
<replaceable>glob_expression</replaceable>…</synopsis>
<para>
For example, the list of first five transactions may look as follows:
</para>
- <screen>~]# <command>yum history list 1..5</command>
+ <screen>~]# <command>dnf history list 1..5</command>
Loaded plugins: langpacks, presto, refresh-packagekit
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
@@ -817,7 +817,7 @@ ID | Login user | Date and time | Action(s)
| Altered
1 | System <unset> | 2011-07-16 14:38 | Install |
1106
history list</screen>
<para>
- All forms of the <command>yum history list</command> command produce
tabular output with each row consisting of the following columns:
+ All forms of the <command>dnf history list</command> command produce
tabular output with each row consisting of the following columns:
</para>
<itemizedlist>
<listitem>
@@ -980,7 +980,7 @@ history list</screen>
<literal>#</literal>
</entry>
<entry>
- The transaction finished successfully, but
<command>yum</command> returned a non-zero exit code.
+ The transaction finished successfully, but
<command>dnf</command> returned a non-zero exit code.
</entry>
</row>
<row>
@@ -1013,21 +1013,21 @@ history list</screen>
<para>
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>
+ <synopsis><command>dnf</command>
<option>history</option>
<option>summary</option></synopsis>
<para>
To display only transactions in a given range, type:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>summary</option>
<replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>summary</option>
<replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
<para>
- Similarly to the <command>yum history list</command> command, you can
also display a summary of transactions regarding a certain package or packages by
supplying a package name or a glob expression:
+ Similarly to the <command>dnf history list</command> command, you can
also display a summary of transactions regarding a certain package or packages by
supplying a package name or a glob expression:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>summary</option>
<replaceable>glob_expression</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>summary</option>
<replaceable>glob_expression</replaceable>…</synopsis>
<para>
For instance, a summary of the transaction history displayed above would look
like the following:
</para>
- <screen>~]# <command>yum history summary 1..5</command>
+ <screen>~]# <command>dnf history summary 1..5</command>
Loaded plugins: langpacks, presto, refresh-packagekit
-Login user | Time | Action(s) | Altered
+Login user | Time | Action(s) | Altered
-------------------------------------------------------------------------------
Jaromir ... <jhradilek> | Last day | Install |
1
Jaromir ... <jhradilek> | Last week | Install |
1
@@ -1035,16 +1035,16 @@ Jaromir ... <jhradilek> | Last 2 weeks |
I, U |
System <unset> | Last 2 weeks | I, U |
1107
history summary</screen>
<para>
- All forms of the <command>yum history summary</command> command
produce simplified tabular output similar to the output of <command>yum history
list</command>.
+ All forms of the <command>dnf history summary</command> command
produce simplified tabular output similar to the output of <command>dnf history
list</command>.
</para>
<para>
- As shown above, both <command>yum history list</command> and
<command>yum history summary</command> are oriented towards transactions, and
although they allow you to display only transactions related to a given package or
packages, they lack important details, such as package versions. To list transactions from
the perspective of a package, run the following command as <systemitem
class="username">root</systemitem>:
+ As shown above, both <command>dnf history list</command> and
<command>dnf history summary</command> are oriented towards transactions, and
although they allow you to display only transactions related to a given package or
packages, they lack important details, such as package versions. To list transactions from
the perspective of a package, run the following command as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>package-list</option>
<replaceable>glob_expression</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>package-list</option>
<replaceable>glob_expression</replaceable>…</synopsis>
<para>
For example, to trace the history of
<package>subscription-manager</package> and related packages, type the
following at a shell prompt:
</para>
- <screen>~]# <command>yum history package-list
subscription-manager\*</command>
+ <screen>~]# <command>dnf history package-list
subscription-manager\*</command>
Loaded plugins: langpacks, presto, refresh-packagekit
ID | Action(s) | Package
-------------------------------------------------------------------------------
@@ -1065,21 +1065,21 @@ history package-list</screen>
Examining Transactions
</bridgehead>
<para>
- To display the summary of a single transaction, as <systemitem
class="username">root</systemitem>, use the <command>yum history
summary</command> command in the following form:
+ To display the summary of a single transaction, as <systemitem
class="username">root</systemitem>, use the <command>dnf history
summary</command> command in the following form:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>summary</option>
<replaceable>id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>summary</option>
<replaceable>id</replaceable></synopsis>
<para>
To examine a particular transaction or transactions in more detail, run the
following command as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>info</option>
<replaceable>id</replaceable>…</synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>info</option>
<replaceable>id</replaceable>…</synopsis>
<para>
- The <replaceable>id</replaceable> argument is optional and when you
omit it, <command>yum</command> automatically uses the last transaction. Note
that when specifying more than one transaction, you can also use a range:
+ The <replaceable>id</replaceable> argument is optional and when you
omit it, <command>dnf</command> automatically uses the last transaction. Note
that when specifying more than one transaction, you can also use a range:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>info</option>
<replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>info</option>
<replaceable>start_id</replaceable>..<replaceable>end_id</replaceable></synopsis>
<para>
The following is sample output for two transactions, each installing one new
package:
</para>
- <screen>~]# <command>yum history info 4..5</command>
+ <screen>~]# <command>dnf history info 4..5</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Transaction ID : 4..5
Begin time : Thu Jul 21 15:10:46 2011
@@ -1101,15 +1101,15 @@ history info</screen>
<para>
You can also view additional information, such as what configuration options were
used at the time of the transaction, or from what repository and why were certain packages
installed. To determine what additional information is available for a certain
transaction, type the following at a shell prompt as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>addon-info</option>
<replaceable>id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>addon-info</option>
<replaceable>id</replaceable></synopsis>
<para>
- Similarly to <command>yum history info</command>, when no
<replaceable>id</replaceable> is provided, <command>yum</command>
automatically uses the latest transaction. Another way to refer to the latest transaction
is to use the <literal>last</literal> keyword:
+ Similarly to <command>dnf history info</command>, when no
<replaceable>id</replaceable> is provided, <command>dnf</command>
automatically uses the latest transaction. Another way to refer to the latest transaction
is to use the <literal>last</literal> keyword:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>addon-info</option>
<option>last</option></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>addon-info</option>
<option>last</option></synopsis>
<para>
- For instance, for the first transaction in the previous example, the
<command>yum history addon-info</command> command would provide the following
output:
+ For instance, for the first transaction in the previous example, the
<command>dnf history addon-info</command> command would provide the following
output:
</para>
- <screen>~]# <command>yum history addon-info 4</command>
+ <screen>~]# <command>dnf history addon-info 4</command>
Loaded plugins: langpacks, presto, refresh-packagekit
Transaction ID: 4
Available additional history information:
@@ -1134,41 +1134,41 @@ history addon-info</screen>
</listitem>
<listitem>
<para>
- <computeroutput>saved_tx</computeroutput> — the data
that can be used by the <command>yum load-transaction</command> command in
order to repeat the transaction on another machine (see below).
+ <computeroutput>saved_tx</computeroutput> — the data
that can be used by the <command>dnf load-transaction</command> command in
order to repeat the transaction on another machine (see below).
</para>
</listitem>
</itemizedlist>
<para>
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>
+ <synopsis><command>dnf</command>
<option>history</option> <option>addon-info</option>
<replaceable>id</replaceable>
<replaceable>information</replaceable></synopsis>
<bridgehead id="bh-DNF-Transaction_History-Reverting">
Reverting and Repeating Transactions
</bridgehead>
<para>
- Apart from reviewing the transaction history, the <command>yum
history</command> command provides means to revert or repeat a selected transaction.
To revert a transaction, type the following at a shell prompt as <systemitem
class="username">root</systemitem>:
+ Apart from reviewing the transaction history, the <command>dnf
history</command> command provides means to revert or repeat a selected transaction.
To revert a transaction, type the following at a shell prompt as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>undo</option>
<replaceable>id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>undo</option>
<replaceable>id</replaceable></synopsis>
<para>
To repeat a particular transaction, as <systemitem
class="username">root</systemitem>, run the following command:
</para>
- <synopsis><command>yum</command>
<option>history</option> <option>redo</option>
<replaceable>id</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>history</option> <option>redo</option>
<replaceable>id</replaceable></synopsis>
<para>
Both commands also accept the <literal>last</literal> keyword to undo
or repeat the latest transaction.
</para>
<para>
- 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" />.
+ Note that both <command>dnf history undo</command> and
<command>dnf 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>dnf 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, 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>
+ <synopsis><command>dnf</command> <option>-q</option>
<option>history</option> <option>addon-info</option>
<replaceable>id</replaceable> <option>saved_tx</option> >
<filename>file_name</filename></synopsis>
<para>
Once you copy this file to the target system, you can repeat the transaction by
using the following command as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>yum</command>
<option>load-transaction</option>
<replaceable>file_name</replaceable></synopsis>
+ <synopsis><command>dnf</command>
<option>load-transaction</option>
<replaceable>file_name</replaceable></synopsis>
<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.
+ 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>dnf version
nogroups</command> command.
</para>
<bridgehead id="bh-DNF-Transaction_History-New">
Starting New Transaction History
@@ -1176,9 +1176,9 @@ history addon-info</screen>
<para>
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>
+ <synopsis><command>dnf</command>
<option>history</option> <option>new</option></synopsis>
<para>
- This will create a new, empty database file in the <filename
class="directory">/var/lib/yum/history/</filename> directory. The old
transaction history will be kept, but will not be accessible as long as a newer database
file is present in the directory.
+ This will create a new, empty database file in the <filename
class="directory">/var/lib/dnf/history/</filename> directory. The old
transaction history will be kept, but will not be accessible as long as a newer database
file is present in the directory.
</para>
</section>
</section>
@@ -1194,7 +1194,7 @@ history addon-info</screen>
<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 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.
+ The configuration file for <command>dnf</command> and related utilities
is located at <filename>/etc/dnf.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/dnf.repos.d/</filename>directory. The values you
define in the <literal>[main]</literal> section of the
<filename>/etc/dnf.conf</filename> file may override values set in individual
<literal>[<replaceable>repository</replaceable>]</literal>
sections.
</para>
<para>
This section shows you how to:
@@ -1202,17 +1202,17 @@ history addon-info</screen>
<itemizedlist>
<listitem>
<para>
- set global DNF 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/dnf.conf</filename> configuration file;
</para>
</listitem>
<listitem>
<para>
- set options for individual repositories by editing the
<literal>[<replaceable>repository</replaceable>]</literal>
sections in <filename>/etc/yum.conf</filename> and <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/yum.repos.d/</filename> directory;
+ set options for individual repositories by editing the
<literal>[<replaceable>repository</replaceable>]</literal>
sections in <filename>/etc/dnf.conf</filename> and <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/dnf.repos.d/</filename> directory;
</para>
</listitem>
<listitem>
<para>
- 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;
+ use DNF variables in <filename>/etc/dnf.conf</filename> and files
in the <filename>/etc/dnf.repos.d/</filename> directory so that dynamic
version and architecture values are handled correctly;
</para>
</listitem>
<listitem>
@@ -1233,18 +1233,18 @@ history addon-info</screen>
<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 DNF treats repositories.
+ The <filename>/etc/dnf.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>dnf</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>.
+You can add many additional options under the <literal>[main]</literal>
section heading in <filename>/etc/dnf.conf</filename>.
</para>
<para>
- A sample <filename>/etc/yum.conf</filename> configuration file can
look like this:
+ A sample <filename>/etc/dnf.conf</filename> configuration file can
look like this:
</para>
<programlisting>[main]
-cachedir=/var/cache/yum/$basearch/$releasever
+cachedir=/var/cache/dnf/$basearch/$releasever
keepcache=0
debuglevel=2
-logfile=/var/log/yum.log
+logfile=/var/log/dnf.log
exactarch=1
obsoletes=1
gpgcheck=1
@@ -1254,7 +1254,7 @@ installonly_limit=3
<lineannotation>[comments abridged]</lineannotation>
# PUT YOUR REPOS HERE OR IN separate files named file.repo
-# in /etc/yum.repos.d</programlisting>
+# in /etc/dnf.repos.d</programlisting>
<para>
The following are the most commonly-used options in the
<literal>[main]</literal> section:
</para>
@@ -1266,10 +1266,10 @@ installonly_limit=3
…where <replaceable>value</replaceable> is one of:
</para>
<para>
- <literal>0</literal> — <command>yum</command>
should prompt for confirmation of critical actions it performs. This is the default.
+ <literal>0</literal> — <command>dnf</command>
should prompt for confirmation of critical actions it performs. This is the default.
</para>
<para>
- <literal>1</literal> — Do not prompt for confirmation of
critical <command>yum</command> actions. If
<option>assumeyes=1</option> is set, <command>yum</command>
behaves in the same way that the command line option <option>-y</option>
does.
+ <literal>1</literal> — Do not prompt for confirmation of
critical <command>dnf</command> actions. If
<option>assumeyes=1</option> is set, <command>dnf</command>
behaves in the same way that the command line option <option>-y</option>
does.
</para>
</listitem>
</varlistentry>
@@ -1277,7 +1277,7 @@ 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 DNF should store its cache and database files. By
default, DNF'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/dnf/$basearch/$releasever</filename>.
</para>
<para>
See <xref linkend="sec-Using_DNF_Variables" /> for
descriptions of the <varname>$basearch</varname> and
<varname>$releasever</varname> DNF variables.
@@ -1288,7 +1288,7 @@ installonly_limit=3
<term><option>debuglevel</option>=<replaceable>value</replaceable></term>
<listitem>
<para>
- …where <replaceable>value</replaceable> is an integer
between <literal>1</literal> and <literal>10</literal>. Setting a
higher <option>debuglevel</option> value causes
<command>yum</command> to display more detailed debugging output.
<option>debuglevel=0</option> disables debugging output, while
<option>debuglevel=2</option> is the default.
+ …where <replaceable>value</replaceable> is an integer
between <literal>1</literal> and <literal>10</literal>. Setting a
higher <option>debuglevel</option> value causes
<command>dnf</command> to display more detailed debugging output.
<option>debuglevel=0</option> disables debugging output, while
<option>debuglevel=2</option> is the default.
</para>
</listitem>
</varlistentry>
@@ -1302,7 +1302,7 @@ installonly_limit=3
<literal>0</literal> — Do not take into account the exact
architecture when updating packages.
</para>
<para>
- <literal>1</literal> — Consider the exact architecture when
updating packages. With this setting, <command>yum</command> will not install
an i686 package to update an i386 package already installed on the system. This is the
default.
+ <literal>1</literal> — Consider the exact architecture when
updating packages. With this setting, <command>dnf</command> will not install
an i686 package to update an i386 package already installed on the system. This is the
default.
</para>
</listitem>
</varlistentry>
@@ -1327,7 +1327,7 @@ installonly_limit=3
<literal>1</literal> — Enable GPG signature-checking on all
packages in all repositories, including local package installation.
<option>gpgcheck=1</option> is the default, and thus all packages'
signatures are checked.
</para>
<para>
- If this option is set in the <literal>[main]</literal> section
of the <filename>/etc/yum.conf</filename> file, it sets the GPG-checking rule
for all repositories. However, you can also set
<option>gpgcheck=<replaceable>value</replaceable></option> for
individual repositories instead; that is, you can enable GPG-checking on one repository
while disabling it on another. Setting
<option>gpgcheck=<replaceable>value</replaceable></option> for an
individual repository in its corresponding <filename
class="extension">.repo</filename> file overrides the default if it is
present in <filename>/etc/yum.conf</filename>.
+ If this option is set in the <literal>[main]</literal> section
of the <filename>/etc/dnf.conf</filename> file, it sets the GPG-checking rule
for all repositories. However, you can also set
<option>gpgcheck=<replaceable>value</replaceable></option> for
individual repositories instead; that is, you can enable GPG-checking on one repository
while disabling it on another. Setting
<option>gpgcheck=<replaceable>value</replaceable></option> for an
individual repository in its corresponding <filename
class="extension">.repo</filename> file overrides the default if it is
present in <filename>/etc/dnf.conf</filename>.
</para>
<para>
For more information on GPG signature-checking, refer to <xref
linkend="s1-check-rpm-sig" />.
@@ -1341,10 +1341,10 @@ installonly_limit=3
…where <replaceable>value</replaceable> is one of:
</para>
<para>
- <literal>0</literal> — <command>yum</command>
should <emphasis>not</emphasis> check the dependencies of each package when
removing a package group. With this setting, <command>yum</command> removes
all packages in a package group, regardless of whether those packages are required by
other packages or groups. <option>groupremove_leaf_only=0</option> is the
default.
+ <literal>0</literal> — <command>dnf</command>
should <emphasis>not</emphasis> check the dependencies of each package when
removing a package group. With this setting, <command>dnf</command> removes
all packages in a package group, regardless of whether those packages are required by
other packages or groups. <option>groupremove_leaf_only=0</option> is the
default.
</para>
<para>
- <literal>1</literal> — <command>yum</command>
should check the dependencies of each package when removing a package group, and remove
only those packages which are not not required by any other package or group.
+ <literal>1</literal> — <command>dnf</command>
should check the dependencies of each package when removing a package group, and remove
only those packages which are not not required by any other package or group.
</para>
<para>
For more information on removing packages, refer to <xref
linkend="important-Package_Group_Removal" />.
@@ -1355,10 +1355,10 @@ installonly_limit=3
<term><option>installonlypkgs</option>=<replaceable>space</replaceable> <replaceable>separated</replaceable> <replaceable>list</replaceable> <replaceable>of</replaceable> <replaceable>packages</replaceable></term>
<listitem>
<para>
- Here you can provide a space-separated list of packages which
<command>yum</command> can <emphasis>install</emphasis>, but will
never <emphasis>update</emphasis>. See the <emphasis
role="bold">yum.conf</emphasis>(5) manual page for the list of packages
which are install-only by default.
+ Here you can provide a space-separated list of packages which
<command>dnf</command> can <emphasis>install</emphasis>, but will
never <emphasis>update</emphasis>. See the <emphasis
role="bold">dnf.conf</emphasis>(5) manual page for the list of packages
which are install-only by default.
</para>
<para>
- If you add the <option>installonlypkgs</option> directive to
<filename>/etc/yum.conf</filename>, you should ensure that you list
<emphasis>all</emphasis> of the packages that should be install-only,
including any of those listed under the <literal>installonlypkgs</literal>
section of <emphasis role="bold">yum.conf</emphasis>(5). In
particular, kernel packages should always be listed in
<option>installonlypkgs</option> (as they are by default), and
<option>installonly_limit</option> should always be set to a value greater
than <literal>2</literal> so that a backup kernel is always available in case
the default one fails to boot.
+ If you add the <option>installonlypkgs</option> directive to
<filename>/etc/dnf.conf</filename>, you should ensure that you list
<emphasis>all</emphasis> of the packages that should be install-only,
including any of those listed under the <literal>installonlypkgs</literal>
section of <emphasis role="bold">dnf.conf</emphasis>(5). In
particular, kernel packages should always be listed in
<option>installonlypkgs</option> (as they are by default), and
<option>installonly_limit</option> should always be set to a value greater
than <literal>2</literal> so that a backup kernel is always available in case
the default one fails to boot.
</para>
</listitem>
</varlistentry>
@@ -1369,7 +1369,7 @@ installonly_limit=3
…where <replaceable>value</replaceable> is an integer
representing the maximum number of versions that can be installed simultaneously for any
single package listed in the <option>installonlypkgs</option> directive.
</para>
<para>
- The defaults for the <option>installonlypkgs</option> directive
include several different kernel packages, so be aware that changing the value of
<option>installonly_limit</option> will also affect the maximum number of
installed versions of any single kernel package. The default value listed in
<filename>/etc/yum.conf</filename> is
<option>installonly_limit=3</option>, and it is not recommended to decrease
this value, particularly below <literal>2</literal>.
+ The defaults for the <option>installonlypkgs</option> directive
include several different kernel packages, so be aware that changing the value of
<option>installonly_limit</option> will also affect the maximum number of
installed versions of any single kernel package. The default value listed in
<filename>/etc/dnf.conf</filename> is
<option>installonly_limit=3</option>, and it is not recommended to decrease
this value, particularly below <literal>2</literal>.
</para>
</listitem>
</varlistentry>
@@ -1391,7 +1391,7 @@ installonly_limit=3
<term><option>logfile</option>=<replaceable>file_name</replaceable></term>
<listitem>
<para>
- …where <replaceable>file_name</replaceable> is an
absolute path to the file in which <command>yum</command> should write its
logging output. By default, <command>yum</command> logs to
<filename>/var/log/yum.log</filename>.
+ …where <replaceable>file_name</replaceable> is an
absolute path to the file in which <command>dnf</command> should write its
logging output. By default, <command>dnf</command> logs to
<filename>/var/log/dnf.log</filename>.
</para>
</listitem>
</varlistentry>
@@ -1402,10 +1402,10 @@ installonly_limit=3
…where <replaceable>value</replaceable> is one of:
</para>
<para>
- <literal>best</literal> — install the best-choice architecture
for this system. For example, setting <option>multilib_policy=best</option> on
an AMD64 system causes <command>yum</command> to install 64-bit versions of
all packages.
+ <literal>best</literal> — install the best-choice architecture
for this system. For example, setting <option>multilib_policy=best</option> on
an AMD64 system causes <command>dnf</command> to install 64-bit versions of
all packages.
</para>
<para>
- <literal>all</literal> — always install every possible
architecture for every package. For example, with
<option>multilib_policy</option> set to <literal>all</literal> on
an AMD64 system, <command>yum</command> would install both the i586 and AMD64
versions of a package, if both were available.
+ <literal>all</literal> — always install every possible
architecture for every package. For example, with
<option>multilib_policy</option> set to <literal>all</literal> on
an AMD64 system, <command>dnf</command> would install both the i586 and AMD64
versions of a package, if both were available.
</para>
</listitem>
</varlistentry>
@@ -1416,10 +1416,10 @@ installonly_limit=3
…where <replaceable>value</replaceable> is one of:
</para>
<para>
- <literal>0</literal> — Disable
<command>yum</command>'s obsoletes processing logic when performing
updates.
+ <literal>0</literal> — Disable
<command>dnf</command>'s obsoletes processing logic when performing
updates.
</para>
<para>
- <literal>1</literal> — Enable
<command>yum</command>'s obsoletes processing logic when performing
updates. When one package declares in its spec file that it
<firstterm>obsoletes</firstterm> another package, the latter package will be
replaced by the former package when the former package is installed. Obsoletes are
declared, for example, when a package is renamed. <option>obsoletes=1</option>
the default.
+ <literal>1</literal> — Enable
<command>dnf</command>'s obsoletes processing logic when performing
updates. When one package declares in its spec file that it
<firstterm>obsoletes</firstterm> another package, the latter package will be
replaced by the former package when the former package is installed. Obsoletes are
declared, for example, when a package is renamed. <option>obsoletes=1</option>
the default.
</para>
</listitem>
</varlistentry>
@@ -1450,7 +1450,7 @@ installonly_limit=3
<term><option>reposdir</option>=<replaceable>directory</replaceable></term>
<listitem>
<para>
- …where <replaceable>directory</replaceable> is an
absolute path to the directory where <filename
class="extension">.repo</filename> files are located. All <filename
class="extension">.repo</filename> files contain repository information
(similar to the
<literal>[<replaceable>repository</replaceable>]</literal>
sections of <filename>/etc/yum.conf</filename>).
<command>yum</command> collects all repository information from <filename
class="extension">.repo</filename> files and the
<literal>[<replaceable>repository</replaceable>]</literal> section
of the <filename>/etc/yum.conf</filename> file to create a master list of
repositories to use for transactions. If <literal>reposdir</literal> is not
set, <command>yum</command> uses the default directory <filename
class="directory">/etc/yum.repos.d/</filename>.
+ …where <replaceable>directory</replaceable> is an
absolute path to the directory where <filename
class="extension">.repo</filename> files are located. All <filename
class="extension">.repo</filename> files contain repository information
(similar to the
<literal>[<replaceable>repository</replaceable>]</literal>
sections of <filename>/etc/dnf.conf</filename>).
<command>dnf</command> collects all repository information from <filename
class="extension">.repo</filename> files and the
<literal>[<replaceable>repository</replaceable>]</literal> section
of the <filename>/etc/dnf.conf</filename> file to create a master list of
repositories to use for transactions. If <literal>reposdir</literal> is not
set, <command>dnf</command> uses the default directory <filename
class="directory">/etc/dnf.repos.d/</filename>.
</para>
</listitem>
</varlistentry>
@@ -1458,13 +1458,13 @@ installonly_limit=3
<term><option>retries</option>=<replaceable>value</replaceable></term>
<listitem>
<para>
- …where <replaceable>value</replaceable> is an integer
<literal>0</literal> or greater. This value sets the number of times
<command>yum</command> should attempt to retrieve a file before returning an
error. Setting this to <literal>0</literal> makes
<command>yum</command> retry forever. The default value is
<literal>10</literal>.
+ …where <replaceable>value</replaceable> is an integer
<literal>0</literal> or greater. This value sets the number of times
<command>dnf</command> should attempt to retrieve a file before returning an
error. Setting this to <literal>0</literal> makes
<command>dnf</command> retry forever. The default value is
<literal>10</literal>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
- For a complete list of available <literal>[main]</literal> options,
refer to the <literal>[main] OPTIONS</literal> section of the <emphasis
role="bold">yum.conf</emphasis>(5) manual page.
+ For a complete list of available <literal>[main]</literal> options,
refer to the <literal>[main] OPTIONS</literal> section of the <emphasis
role="bold">dnf.conf</emphasis>(5) manual page.
</para>
</section>
<section id="sec-Setting_repository_Options">
@@ -1549,13 +1549,13 @@
baseurl=<replaceable>repository_url</replaceable></programlisting>
<literal>1</literal> — Include this repository as a package
source.
</para>
<para>
- Turning repositories on and off can also be performed by passing either the
<option>--enablerepo=<replaceable>repo_name</replaceable></option>
or
<option>--disablerepo=<replaceable>repo_name</replaceable></option>
option to <command>yum</command>, or through the <guilabel>Add/Remove
Software</guilabel> window of the <application>PackageKit</application>
utility.
+ Turning repositories on and off can also be performed by passing either the
<option>--enablerepo=<replaceable>repo_name</replaceable></option>
or
<option>--disablerepo=<replaceable>repo_name</replaceable></option>
option to <command>dnf</command>, or through the <guilabel>Add/Remove
Software</guilabel> window of the <application>PackageKit</application>
utility.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
- 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.
+ 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">dnf.conf</emphasis>(5) manual page.
</para>
</section>
<section id="sec-Using_DNF_Variables">
@@ -1565,14 +1565,14 @@
baseurl=<replaceable>repository_url</replaceable></programlisting>
<secondary>variables</secondary>
</indexterm>
<para>
- 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):
+ You can use and reference the following built-in variables in
<command>dnf</command> commands and in all DNF configuration files (that is,
<filename>/etc/dnf.conf</filename> and all <filename
class="extension">.repo</filename> files in the <filename
class="directory">/etc/dnf.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;. 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.
+ 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/dnf.conf</filename> configuration file. If there is
no such line in <filename>/etc/dnf.conf</filename>, then
<command>dnf</command> infers the correct value by deriving the version number
from the <package>redhat-release</package> package.
</para>
</listitem>
</varlistentry>
@@ -1596,18 +1596,18 @@
baseurl=<replaceable>repository_url</replaceable></programlisting>
<term><varname>$YUM0-9</varname></term>
<listitem>
<para>
- These ten variables are each replaced with the value of any shell
environment variables with the same name. If one of these variables is referenced (in
<filename>/etc/yum.conf</filename> for example) and a shell environment
variable with the same name does not exist, then the configuration file variable is not
replaced.
+ These ten variables are each replaced with the value of any shell
environment variables with the same name. If one of these variables is referenced (in
<filename>/etc/dnf.conf</filename> for example) and a shell environment
variable with the same name does not exist, then the configuration file variable is not
replaced.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
- To define a custom variable or to override the value of an existing one, create a
file with the same name as the variable (without the
<quote><literal>$</literal></quote> sign) in the <filename
class="directory">/etc/yum/vars/</filename> directory, and add the
desired value on its first line.
+ To define a custom variable or to override the value of an existing one, create a
file with the same name as the variable (without the
<quote><literal>$</literal></quote> sign) in the <filename
class="directory">/etc/dnf/vars/</filename> directory, and add the
desired value on its first line.
</para>
<para>
- For example, repository descriptions often include the operating system name. To
define a new variable called <varname>$osname</varname>, create a new file
with <quote>&MAJOROS;</quote> on the first line and save it as
<filename>/etc/yum/vars/osname</filename>:
+ For example, repository descriptions often include the operating system name. To
define a new variable called <varname>$osname</varname>, create a new file
with <quote>&MAJOROS;</quote> on the first line and save it as
<filename>/etc/dnf/vars/osname</filename>:
</para>
- <screen>~]# <command>echo "&MAJOROS;" >
/etc/yum/vars/osname</command></screen>
+ <screen>~]# <command>echo "&MAJOROS;" >
/etc/dnf/vars/osname</command></screen>
<para>
Instead of <quote>&MAJOROSVER;</quote>, you can now use the
following in the <filename class="extension">.repo</filename>
files:
</para>
@@ -1616,28 +1616,28 @@
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 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:
+ To display the current values of global DNF options (that is, the options
specified in the <literal>[main]</literal> section of the
<filename>/etc/dnf.conf</filename> file), run the
<command>dnf-config-manager</command> with no command line options:
</para>
- <synopsis><command>yum-config-manager</command></synopsis>
+ <synopsis><command>dnf-config-manager</command></synopsis>
<para>
To list the content of a different configuration section or sections, use the
command in the following form:
</para>
- <synopsis><command>yum-config-manager</command>
<replaceable>section</replaceable>…</synopsis>
+ <synopsis><command>dnf-config-manager</command>
<replaceable>section</replaceable>…</synopsis>
<para>
You can also use a glob expression to display the configuration of all matching
sections:
</para>
- <synopsis><command>yum-config-manager</command>
<replaceable>glob_expression</replaceable>…</synopsis>
+ <synopsis><command>dnf-config-manager</command>
<replaceable>glob_expression</replaceable>…</synopsis>
<para>
For example, to list all configuration options and their corresponding values,
type the following at a shell prompt:
</para>
- <screen>~]$ <command>yum-config-manager main \*</command>
+ <screen>~]$ <command>dnf-config-manager main \*</command>
Loaded plugins: langpacks, presto, refresh-packagekit
================================== main ===================================
[main]
alwaysprompt = True
assumeyes = False
bandwith = 0
-bugtracker_url =
https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%...
+bugtracker_url =
https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%...
cache = 0
<lineannotation>[output truncated]</lineannotation></screen>
</section>
@@ -1648,13 +1648,13 @@ cache = 0
<secondary>repository</secondary>
</indexterm>
<para>
- <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.
+ <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>dnf-config-manager</command> command.
</para>
<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>.
+ To define a new repository, you can either add a
<literal>[<replaceable>repository</replaceable>]</literal> section
to the <filename>/etc/dnf.conf</filename> file, or to a <filename
class="extension">.repo</filename> file in the <filename
class="directory">/etc/dnf.repos.d/</filename> directory. All files
with the <filename class="extension">.repo</filename> file extension
in this directory are read by <command>dnf</command>, and best practice is to
define your repositories here instead of in
<filename>/etc/dnf.conf</filename>.
</para>
<warning>
<title>Be careful when using untrusted software sources</title>
@@ -1665,42 +1665,42 @@ cache = 0
<para>
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>
+ <synopsis><command>dnf-config-manager</command>
<option>--add-repo</option>
<replaceable>repository_url</replaceable></synopsis>
<para>
…where <replaceable>repository_url</replaceable> is a link
to the <filename class="extension">.repo</filename> file. For
example, to add a repository located at
http://www.example.com/example.repo, type the
following at a shell prompt:
</para>
- <screen>~]# <command>yum-config-manager --add-repo
http://www.example.com/example.repo</command>
+ <screen>~]# <command>dnf-config-manager --add-repo
http://www.example.com/example.repo</command>
Loaded plugins: langpacks, presto, refresh-packagekit
adding repo from:
http://www.example.com/example.repo
-grabbing file
http://www.example.com/example.repo to /etc/yum.repos.d/example.repo
+grabbing file
http://www.example.com/example.repo to /etc/dnf.repos.d/example.repo
example.repo | 413 B 00:00
-repo saved to /etc/yum.repos.d/example.repo</screen>
+repo saved to /etc/dnf.repos.d/example.repo</screen>
<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>:
</para>
- <synopsis><command>yum-config-manager</command>
<option>--enable</option>
<replaceable>repository</replaceable>…</synopsis>
+ <synopsis><command>dnf-config-manager</command>
<option>--enable</option>
<replaceable>repository</replaceable>…</synopsis>
<para>
- …where <replaceable>repository</replaceable> is the unique
repository ID (use <command>yum repolist all</command> to list available
repository IDs). Alternatively, you can use a glob expression to enable all matching
repositories:
+ …where <replaceable>repository</replaceable> is the unique
repository ID (use <command>dnf repolist all</command> to list available
repository IDs). Alternatively, you can use a glob expression to enable all matching
repositories:
</para>
- <synopsis><command>yum-config-manager</command>
<option>--enable</option>
<replaceable>glob_expression</replaceable>…</synopsis>
+ <synopsis><command>dnf-config-manager</command>
<option>--enable</option>
<replaceable>glob_expression</replaceable>…</synopsis>
<para>
For example, to disable repositories defined in the
<literal>[example]</literal>,
<literal>[example-debuginfo]</literal>, and
<literal>[example-source]</literal>sections, type:
</para>
- <screen>~]# <command>yum-config-manager --enable
example\*</command>
+ <screen>~]# <command>dnf-config-manager --enable
example\*</command>
Loaded plugins: langpacks, presto, refresh-packagekit
============================== repo: example ==============================
[example]
bandwidth = 0
-base_persistdir = /var/lib/yum/repos/x86_64/6Server
+base_persistdir = /var/lib/dnf/repos/x86_64/6Server
baseurl =
http://www.example.com/repo/6Server/x86_64/
cache = 0
-cachedir = /var/cache/yum/x86_64/6Server/example
+cachedir = /var/cache/dnf/x86_64/6Server/example
<lineannotation>[output truncated]</lineannotation></screen>
<para>
- When successful, the <command>yum-config-manager --enable</command>
command displays the current repository configuration.
+ When successful, the <command>dnf-config-manager --enable</command>
command displays the current repository configuration.
</para>
<bridgehead id="bh-Managing_DNF_Repositories-Disabling">
Disabling a DNF Repository
@@ -1708,13 +1708,13 @@ cachedir = /var/cache/yum/x86_64/6Server/example
<para>
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>
+ <synopsis><command>dnf-config-manager</command>
<option>--disable</option>
<replaceable>repository</replaceable>…</synopsis>
<para>
- …where <replaceable>repository</replaceable> is the unique
repository ID (use <command>yum repolist all</command> to list available
repository IDs). Similarly to <command>yum-config-manager --enable</command>,
you can use a glob expression to disable all matching repositories at the same time:
+ …where <replaceable>repository</replaceable> is the unique
repository ID (use <command>dnf repolist all</command> to list available
repository IDs). Similarly to <command>dnf-config-manager --enable</command>,
you can use a glob expression to disable all matching repositories at the same time:
</para>
- <synopsis><command>yum-config-manager</command>
<option>--disable</option>
<replaceable>glob_expression</replaceable>…</synopsis>
+ <synopsis><command>dnf-config-manager</command>
<option>--disable</option>
<replaceable>glob_expression</replaceable>…</synopsis>
<para>
- When successful, the <command>yum-config-manager --disable</command>
command displays the current configuration.
+ When successful, the <command>dnf-config-manager --disable</command>
command displays the current configuration.
</para>
</section>
<section id="sec-Creating_a_DNF_Repository">
@@ -1731,7 +1731,7 @@ cachedir = /var/cache/yum/x86_64/6Server/example
<para>
Install the <package>createrepo</package> package:
</para>
- <screen>~]# <command>yum install
createrepo</command></screen>
+ <screen>~]# <command>dnf install
createrepo</command></screen>
</step>
<step>
<para>
@@ -1746,7 +1746,7 @@ cachedir = /var/cache/yum/x86_64/6Server/example
</step>
</procedure>
<para>
- This creates the necessary metadata for your DNF 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>dnf</command> operations.
</para>
</section>
</section>
@@ -1757,9 +1757,9 @@ cachedir = /var/cache/yum/x86_64/6Server/example
<secondary>DNF plug-ins</secondary>
</indexterm>
<para>
- 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:
+ 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>dnf</command> command. For example:
</para>
- <screen>~]# <command>yum info yum</command>
+ <screen>~]# <command>dnf info dnf</command>
Loaded plugins: langpacks, presto, refresh-packagekit
<lineannotation>[output truncated]</lineannotation></screen>
<para>
@@ -1780,7 +1780,7 @@ Loaded plugins: langpacks, presto, refresh-packagekit
<secondary>disabling plug-ins</secondary>
</indexterm>
<para>
- 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>:
+ 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/dnf.conf</filename>, and that its value is set to
<literal>1</literal>:
</para>
<programlisting>plugins=1</programlisting>
<para>
@@ -1793,34 +1793,34 @@ Loaded plugins: langpacks, presto, refresh-packagekit
</para>
</important>
<para>
- Every installed plug-in has its own configuration file in the <filename
class="directory">/etc/yum/pluginconf.d/</filename> directory. You can
set plug-in specific options in these files. For example, here is the
<application>refresh-packagekit</application> plug-in's
<filename>refresh-packagekit.conf</filename> configuration file:
+ Every installed plug-in has its own configuration file in the <filename
class="directory">/etc/dnf/pluginconf.d/</filename> directory. You can
set plug-in specific options in these files. For example, here is the
<application>refresh-packagekit</application> plug-in's
<filename>refresh-packagekit.conf</filename> configuration file:
</para>
<programlisting>[main]
enabled=1</programlisting>
<para>
- 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.
+ Plug-in configuration files always contain a
<literal>[main]</literal> section (similar to DNF's
<filename>/etc/dnf.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>dnf</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.
+ If you disable all plug-ins by setting <command>enabled=0</command>
in <filename>/etc/dnf.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 DNF 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>dnf</command> command, use the
<option>--noplugins</option> option.
</para>
<para>
- 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:
+ If you want to disable one or more DNF plug-ins for a single
<command>dnf</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>
+ <screen>~]# <command>dnf update
--disableplugin=presto</command></screen>
<para>
- The plug-in names you provide to the
<option>--disableplugin=</option> option are the same names listed after the
<command>Loaded plugins</command> line in the output of any
<command>yum</command> command. You can disable multiple plug-ins by
separating their names with commas. In addition, you can match multiple plug-in names or
shorten long ones by using glob expressions:
+ The plug-in names you provide to the
<option>--disableplugin=</option> option are the same names listed after the
<command>Loaded plugins</command> line in the output of any
<command>dnf</command> command. You can disable multiple plug-ins by
separating their names with commas. In addition, you can match multiple plug-in names or
shorten long ones by using glob expressions:
</para>
- <screen>~]# <command>yum update
--disableplugin=presto,refresh-pack*</command></screen>
+ <screen>~]# <command>dnf update
--disableplugin=presto,refresh-pack*</command></screen>
</section>
<section id="sec-Installing_More_DNF_Plugins">
<title>Installing Additional DNF Plug-ins</title>
<para>
- 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:
+ DNF plug-ins usually adhere to the
<filename>dnf-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>dnf-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>
+ <screen>~]# <command>dnf install
dnf-plugin-security</command></screen>
</section>
<section id="sec-Plugin_Descriptions">
<title>Plug-in Descriptions</title>
@@ -1835,7 +1835,7 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>fs-snapshot</application></tertiary>
</indexterm>
- <application>fs-snapshot</application>
(<package>yum-plugin-fs-snapshot</package>)
+ <application>fs-snapshot</application>
(<package>dnf-plugin-fs-snapshot</package>)
</term>
<listitem>
<para>
@@ -1879,7 +1879,7 @@ enabled=1</programlisting>
</step>
<step>
<para>
- Edit the configuration file located in
<filename>/etc/yum/pluginconf.d/fs-snapshot.conf</filename>, and make the
following changes to the <literal>[lvm]</literal> section:
+ Edit the configuration file located in
<filename>/etc/dnf/pluginconf.d/fs-snapshot.conf</filename>, and make the
following changes to the <literal>[lvm]</literal> section:
</para>
<substeps>
<step>
@@ -1901,9 +1901,9 @@ enabled=1</programlisting>
</step>
<step>
<para>
- Run the desired <command>yum</command> command, and make
sure <application>fs-snapshot</application> is included in the list of loaded
plug-ins (the <literal>Loaded plugins</literal> line) before you confirm the
changes and proceed with the transaction. The
<application>fs-snapshot</application> plug-in displays a line in the
following form for each affected logical volume:
+ Run the desired <command>dnf</command> command, and make
sure <application>fs-snapshot</application> is included in the list of loaded
plug-ins (the <literal>Loaded plugins</literal> line) before you confirm the
changes and proceed with the transaction. The
<application>fs-snapshot</application> plug-in displays a line in the
following form for each affected logical volume:
</para>
- <synopsis>fs-snapshot: snapshotting
<replaceable>file_system</replaceable>
(/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>):
<replaceable>logical_volume</replaceable>_yum_<replaceable>timestamp</replaceable></synopsis>
+ <synopsis>fs-snapshot: snapshotting
<replaceable>file_system</replaceable>
(/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>):
<replaceable>logical_volume</replaceable>_dnf_<replaceable>timestamp</replaceable></synopsis>
</step>
<step>
<para>
@@ -1914,7 +1914,7 @@ enabled=1</programlisting>
<para>
If you decide to keep the changes, remove the snapshot by running
the <command>lvremove</command> command as <systemitem
class="username">root</systemitem>:
</para>
- <synopsis><command>lvremove</command>
/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>_yum_<replaceable>timestamp</replaceable></synopsis>
+ <synopsis><command>lvremove</command>
/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>_dnf_<replaceable>timestamp</replaceable></synopsis>
</step>
<step>
<para>
@@ -1925,7 +1925,7 @@ enabled=1</programlisting>
<para>
As <systemitem
class="username">root</systemitem>, run the command in the following
form to merge a snapshot into its original logical volume:
</para>
- <synopsis><command>lvconvert</command>
<option>--merge</option>
/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>_yum_<replaceable>timestamp</replaceable></synopsis>
+ <synopsis><command>lvconvert</command>
<option>--merge</option>
/dev/<replaceable>volume_group</replaceable>/<replaceable>logical_volume</replaceable>_dnf_<replaceable>timestamp</replaceable></synopsis>
<para>
The <command>lvconvert</command> command will
inform you that a restart is required in order for the changes to take effect.
</para>
@@ -1947,9 +1947,9 @@ enabled=1</programlisting>
<procedure>
<step>
<para>
- Run the desired <command>yum</command> command, and make
sure <application>fs-snapshot</application> is included in the list of loaded
plug-ins (the <literal>Loaded plugins</literal> line) before you confirm the
changes and proceed with the transaction. The
<application>fs-snapshot</application> plug-in displays a line in the
following form for each affected file system:
+ Run the desired <command>dnf</command> command, and make
sure <application>fs-snapshot</application> is included in the list of loaded
plug-ins (the <literal>Loaded plugins</literal> line) before you confirm the
changes and proceed with the transaction. The
<application>fs-snapshot</application> plug-in displays a line in the
following form for each affected file system:
</para>
- <synopsis>fs-snapshot: snapshotting
<replaceable>file_system</replaceable>:
<replaceable>file_system</replaceable>/yum_<replaceable>timestamp</replaceable></synopsis>
+ <synopsis>fs-snapshot: snapshotting
<replaceable>file_system</replaceable>:
<replaceable>file_system</replaceable>/dnf_<replaceable>timestamp</replaceable></synopsis>
</step>
<step>
<para>
@@ -1960,7 +1960,7 @@ enabled=1</programlisting>
<para>
If you decide to keep the changes, you can optionally remove
unwanted snapshots. To remove a Btrfs snapshot, use the command in the following form as
<systemitem class="username">root</systemitem>:
</para>
- <synopsis><command>btrfs</command>
<option>subvolume</option> <option>delete</option>
<replaceable>file_system</replaceable>/yum_<replaceable>timestamp</replaceable></synopsis>
+ <synopsis><command>btrfs</command>
<option>subvolume</option> <option>delete</option>
<replaceable>file_system</replaceable>/dnf_<replaceable>timestamp</replaceable></synopsis>
</step>
<step>
<para>
@@ -1991,7 +1991,7 @@ enabled=1</programlisting>
</step>
</procedure>
<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.
+ 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">dnf-fs-snapshot</emphasis>(1) and <emphasis
role="bold">dnf-fs-snapshot.conf</emphasis>(5) manual pages.
</para>
<table id="tabl-DNF-Plugin_Descriptions-fs-snapshot">
<title>Supported <filename>fs-snapshot.conf</filename>
directives</title>
@@ -2064,14 +2064,14 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>kabi</application></tertiary>
</indexterm>
- <application>kabi</application>
(<package>kabi-yum-plugins</package>)
+ <application>kabi</application>
(<package>kabi-dnf-plugins</package>)
</term>
<listitem>
<para>
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-DNF-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/dnf/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-DNF-Plugin_Descriptions-kabi">
<title>Supported <filename>kabi.conf</filename>
directives</title>
@@ -2126,7 +2126,7 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>presto</application></tertiary>
</indexterm>
- <application>presto</application>
(<package>yum-presto</package>)
+ <application>presto</application>
(<package>dnf-presto</package>)
</term>
<listitem>
<para>
@@ -2145,14 +2145,14 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>protect-packages</application></tertiary>
</indexterm>
- <application>protect-packages</application>
(<package>yum-plugin-protect-packages</package>)
+ <application>protect-packages</application>
(<package>dnf-plugin-protect-packages</package>)
</term>
<listitem>
<para>
- The <application>protect-packages</application> plug-in
prevents the <package>yum</package> package and all packages it depends on
from being deliberately or accidentally removed. This prevents many of the most important
packages necessary for your system to run from being removed. In addition, you can list
more packages, one per line, in the
<filename>/etc/sysconfig/protected-packages</filename> file<footnote
id="footnote-Alternative_Locations_for_protect-packages_Lists"><para>You
can also place files with the extension <filename
class="extension">.list</filename> in the <filename
class="directory">/etc/sysconfig/protected-packages.d/</filename>
directory (which you should create if it does not exist), and list packages—one per
line—in these files. <application>protect-packages</application> will protect
these too.</para></footnote> (which you should create if it does not exist),
and <application>protect-packages</application> will extend protection-from-r
emoval to those packages as well.
+ The <application>protect-packages</application> plug-in
prevents the <package>dnf</package> package and all packages it depends on
from being deliberately or accidentally removed. This prevents many of the most important
packages necessary for your system to run from being removed. In addition, you can list
more packages, one per line, in the
<filename>/etc/sysconfig/protected-packages</filename> file<footnote
id="footnote-Alternative_Locations_for_protect-packages_Lists"><para>You
can also place files with the extension <filename
class="extension">.list</filename> in the <filename
class="directory">/etc/sysconfig/protected-packages.d/</filename>
directory (which you should create if it does not exist), and list packages—one per
line—in these files. <application>protect-packages</application> will protect
these too.</para></footnote> (which you should create if it does not exist),
and <application>protect-packages</application> will extend protection-from-r
emoval to those packages as well.
</para>
<para>
- To temporarily override package protection, use the <option>-
-override-protection</option> option with an applicable
<command>yum</command> command.
+ To temporarily override package protection, use the <option>-
-override-protection</option> option with an applicable
<command>dnf</command> command.
</para>
</listitem>
</varlistentry>
@@ -2164,11 +2164,11 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>refresh-packagekit</application></tertiary>
</indexterm>
- <application>refresh-packagekit</application>
(<package>PackageKit-yum-plugin</package>)
+ <application>refresh-packagekit</application>
(<package>PackageKit-dnf-plugin</package>)
</term>
<listitem>
<para>
- The <application>refresh-packagekit</application> plug-in
updates metadata for <application>PackageKit</application> whenever
<command>yum</command> is run. The
<application>refresh-packagekit</application> plug-in is installed by
default.
+ The <application>refresh-packagekit</application> plug-in
updates metadata for <application>PackageKit</application> whenever
<command>dnf</command> is run. The
<application>refresh-packagekit</application> plug-in is installed by
default.
</para>
</listitem>
</varlistentry>
@@ -2179,7 +2179,7 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>rhnplugin</application></tertiary>
</indexterm>
- <application>rhnplugin</application>
(<package>yum-rhn-plugin</package>)
+ <application>rhnplugin</application>
(<package>dnf-rhn-plugin</package>)
</term>
<listitem>
<para>
@@ -2197,16 +2197,16 @@ enabled=1</programlisting>
<secondary>plug-ins</secondary>
<tertiary><application>security</application></tertiary>
</indexterm>
- <application>security</application>
(<package>yum-plugin-security</package>)
+ <application>security</application>
(<package>dnf-plugin-security</package>)
</term>
<listitem>
<para>
- 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.
+ 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>dnf</command> with a set of highly-useful security-related commands,
subcommands and options.
</para>
<para>
You can check for security-related updates as follows:
</para>
- <screen>~]# <command>yum check-update --security</command>
+ <screen>~]# <command>dnf check-update --security</command>
Loaded plugins: langpacks, presto, refresh-packagekit, security
Limiting package lists to security relevant ones
updates-testing/updateinfo | 329 kB 00:00
@@ -2219,7 +2219,7 @@ NetworkManager.x86_64 1:0.8.999-2.git20110509.fc15
updates
NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
<lineannotation>[output truncated]</lineannotation></screen>
<para>
- You can then use either <command>yum update
--security</command> or <command>yum update-minimal --security</command>
to update those packages which are affected by security advisories. Both of these commands
update all packages on the system for which a security advisory has been issued.
<command>yum update-minimal --security</command> updates them to the latest
packages which were released as part of a security advisory, while <command>yum
update --security</command> will update all packages affected by a security advisory
<emphasis>to the latest version of that package available</emphasis>.
+ You can then use either <command>dnf update
--security</command> or <command>dnf update-minimal --security</command>
to update those packages which are affected by security advisories. Both of these commands
update all packages on the system for which a security advisory has been issued.
<command>dnf update-minimal --security</command> updates them to the latest
packages which were released as part of a security advisory, while <command>dnf
update --security</command> will update all packages affected by a security advisory
<emphasis>to the latest version of that package available</emphasis>.
</para>
<para>
In other words, if:
@@ -2242,10 +2242,10 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15
updates
</listitem>
</itemizedlist>
<para>
- ...then <command>yum update-minimal --security</command> will
update you to <package>kernel-2.6.38.6-22</package>, and <command>yum
update --security</command> will update you to
<package>kernel-2.6.38.6-26</package>. Conservative system administrators may
want to use <command>update-minimal</command> to reduce the risk incurred by
updating packages as much as possible.
+ ...then <command>dnf update-minimal --security</command> will
update you to <package>kernel-2.6.38.6-22</package>, and <command>dnf
update --security</command> will update you to
<package>kernel-2.6.38.6-26</package>. Conservative system administrators may
want to use <command>update-minimal</command> to reduce the risk incurred by
updating packages as much as possible.
</para>
<para>
- See the <emphasis
role="bold">yum-security</emphasis>(8) manual page for usage details
and further explanation of the enhancements the
<application>security</application> plug-in adds to
<command>yum</command>.
+ See the <emphasis
role="bold">dnf-security</emphasis>(8) manual page for usage details
and further explanation of the enhancements the
<application>security</application> plug-in adds to
<command>dnf</command>.
</para>
</listitem>
</varlistentry>
@@ -2261,7 +2261,7 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15
updates
<variablelist>
<varlistentry>
<term>
- <ulink
url="http://yum.baseurl.org/wiki/Guides" />
+ <ulink
url="http://dnf.baseurl.org/wiki/Guides" />
</term>
<listitem>
<para>