[install-guide/f22-branch] Update references to reflect DNF as the default package manager
Ben Cotton
bcotton at fedoraproject.org
Sun Jan 25 20:23:52 UTC 2015
commit 150a09b88a374bba126480602772a9655231d735
Author: Ben Cotton <bcotton at fedoraproject.org>
Date: Sun Jan 25 15:23:38 2015 -0500
Update references to reflect DNF as the default package manager
en-US/After_Installation.xml | 12 ++++++------
en-US/CustomSpoke_PartitioningAdvice.xml | 2 +-
en-US/Kickstart_Installations.xml | 2 +-
en-US/Kickstart_Syntax_Reference.xml | 12 ++++++------
en-US/Network_based_Installations.xml | 8 ++++----
en-US/Troubleshooting.xml | 4 ++--
en-US/VNC_Installations.xml | 2 +-
7 files changed, 21 insertions(+), 21 deletions(-)
---
diff --git a/en-US/After_Installation.xml b/en-US/After_Installation.xml
index ffe2164..24ceff0 100644
--- a/en-US/After_Installation.xml
+++ b/en-US/After_Installation.xml
@@ -72,7 +72,7 @@
If you installed &PRODUCT; from a full installation ISO image (such as the Workstation live image or full Server DVD), it is recommended to perform an initial system update, because your installation media likely contained older versions of software packages. During the initial update, all installed packages are updated to their latest available versions. Updates to packages provide security fixes, bug fixes and enhancements.
</para>
<para>
- The <application>Yum</application> package manager is used for updating installed packages. For more information about updating your system with <application>Yum</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
+ The <application>DNF</application> package manager is used for updating installed packages. For more information about updating your system with <application>DNF</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
</listitem>
</varlistentry>
@@ -83,7 +83,7 @@
Usually, drivers for system devices are already supported in the kernel provided by Red Hat Enterprise Linux. However, occasionally, support for devices that have been released recently could be missing. In these cases, a driver update enabling your device may be available.
</para>
<para>
- Devices necessary to complete the installation can have driver updates provided before the installation begins. If a device is missing a driver, but it is not essential during the installation, it is recommended to wait until after the installation completes, and install additional drivers afterwards. For instructions on installing and enabling additional drivers on the installed system using <application>RPM</application> and <application>Yum</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
+ Devices necessary to complete the installation can have driver updates provided before the installation begins. If a device is missing a driver, but it is not essential during the installation, it is recommended to wait until after the installation completes, and install additional drivers afterwards. For instructions on installing and enabling additional drivers on the installed system using <application>RPM</application> and <application>DNF</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
</para>
</listitem>
</varlistentry>
@@ -91,7 +91,7 @@
<term>Configure additional repositories</term>
<listitem>
<para>
- New software is installed from <firstterm>package repositories</firstterm>. Package repositories are organized sets of software and metadata that can be accessed by the <application>Yum</application> package manager. By default, several update repositories provided by &PRODUCT; are configured automatically and you can install updates and additional software from those. However, if you want to set up additional repositories, for example ones containing your own software, some extra steps are needed.
+ New software is installed from <firstterm>package repositories</firstterm>. Package repositories are organized sets of software and metadata that can be accessed by the <application>DNF</application> package manager. By default, several update repositories provided by &PRODUCT; are configured automatically and you can install updates and additional software from those. However, if you want to set up additional repositories, for example ones containing your own software, some extra steps are needed.
</para>
<para>
For information about configuring additional software repositories, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />.
@@ -102,7 +102,7 @@
<term>Install additional packages</term>
<listitem>
<para>
- You can control which packages will be installed by selecting an environment in the <systemitem>Software Selection</systemitem> dialog in the graphical installation (see <xref linkend="sect-installation-gui-software-selection" />). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the <application>Yum</application> packages manager to install additional packages after the installation. See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for more information.
+ You can control which packages will be installed by selecting an environment in the <systemitem>Software Selection</systemitem> dialog in the graphical installation (see <xref linkend="sect-installation-gui-software-selection" />). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the <application>DNF</application> package manager to install additional packages after the installation. See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for more information.
</para>
</listitem>
</varlistentry>
@@ -113,11 +113,11 @@
Depending on the options you chose during the installation process, it is possible that your system does not have a graphical interface, instead offering only a text-based prompt. If this is the case and you wish to enable a graphical desktop after the installation, you must install the <application>X Window System</application> and your preferred desktop environment (either <application>GNOME</application> or <application>KDE</application>).
</para>
<para>
- As with all other software, these packages can be installed using the <application>Yum</application> package manager. For information about using <application>Yum</application> to install new packages, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. For information on how to enable graphical login by default, see <xref linkend="sect-trouble-after-graphical-login" />.
+ As with all other software, these packages can be installed using the <application>DNF</application> package manager. For information about using <application>DNF</application> to install new packages, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />. For information on how to enable graphical login by default, see <xref linkend="sect-trouble-after-graphical-login" />.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml
index f49c322..ace2774 100644
--- a/en-US/CustomSpoke_PartitioningAdvice.xml
+++ b/en-US/CustomSpoke_PartitioningAdvice.xml
@@ -36,7 +36,7 @@
</listitem>
<listitem>
<para>
- The <filename class="directory">/var</filename> directory holds content for a number of applications, including the <application>Apache</application> web server, and is used by the <application>Yum</application> package manager to temporarily store downloaded package updates. Make sure that the partition or volume containing <filename class="directory">/var</filename> has at least 3 GB.
+ The <filename class="directory">/var</filename> directory holds content for a number of applications, including the <application>Apache</application> web server, and is used by the <application>DNF</application> package manager to temporarily store downloaded package updates. Make sure that the partition or volume containing <filename class="directory">/var</filename> has at least 3 GB.
</para>
</listitem>
<listitem>
diff --git a/en-US/Kickstart_Installations.xml b/en-US/Kickstart_Installations.xml
index 89ddc9f..e7d7e5c 100644
--- a/en-US/Kickstart_Installations.xml
+++ b/en-US/Kickstart_Installations.xml
@@ -104,7 +104,7 @@
When creating or customizing your kickstart file, it is useful to verify that it is valid before attempting to use it in an installation. &PRODUCT; includes the <application>ksvalidator</application> command line utility which can be used to do this. This tool is a part of the <package>pykickstart</package> package. To install this package, execute the following command:
</para>
<screen>
-<prompt>#</prompt> <command>yum install pykickstart</command>
+<prompt>#</prompt> <command>dnf install pykickstart</command>
</screen>
<para>
After installing the package, you can validate a Kickstart file using the following command:
diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml
index 2e07479..93a9b4f 100644
--- a/en-US/Kickstart_Syntax_Reference.xml
+++ b/en-US/Kickstart_Syntax_Reference.xml
@@ -333,15 +333,15 @@
</section>
<section id="sect-kickstart-commands-repo">
- <title>repo (optional) - Configure Additional Yum Repositories</title>
+ <title>repo (optional) - Configure Additional Repositories</title>
<para>
- Configures additional <application>Yum</application> repositories that may be used as sources for package installation. This command can be used multiple times in a single Kickstart file.
+ Configures additional <application>DNF</application> repositories that may be used as sources for package installation. This command can be used multiple times in a single Kickstart file.
</para>
<programlisting>
<command>repo --name=<replaceable>repoid</replaceable> [--baseurl=<replaceable><url></replaceable>|--mirrorlist=<replaceable>url</replaceable>] [<replaceable>options</replaceable>]</command>
</programlisting>
<para>
- See the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about the <application>Yum</application> package manager.
+ See the <citetitle>Fedora System Administrator's Guide</citetitle>, available at <ulink url="http://docs.fedoraproject.org/" />, for information about the <application>DNF</application> package manager.
</para>
<important>
<para>
@@ -361,7 +361,7 @@
<term><option>--baseurl=</option></term>
<listitem>
<para>
- The repository URL. The variables that may be used in <application>Yum</application> repo configuration files are <emphasis>not</emphasis> supported. You may use one of either this option or <option>--mirrorlist</option>, not both.
+ The repository URL. The variables that may be used in <application>DNF</application> repo configuration files are <emphasis>not</emphasis> supported. You may use one of either this option or <option>--mirrorlist</option>, not both.
</para>
</listitem>
</varlistentry>
@@ -369,7 +369,7 @@
<term><option>--mirrorlist=</option></term>
<listitem>
<para>
- The URL pointing at a list of mirrors for the repository. The variables that may normally be used in yum repository configuration files are not supported here. You may use one of either this option or --baseurl, not both.
+ The URL pointing at a list of mirrors for the repository. The variables that may normally be used in dnf repository configuration files are not supported here. You may use one of either this option or --baseurl, not both.
</para>
</listitem>
</varlistentry>
@@ -3890,4 +3890,4 @@ umount /mnt/temp
</section>
-</appendix>
\ No newline at end of file
+</appendix>
diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml
index 272d77c..e957683 100644
--- a/en-US/Network_based_Installations.xml
+++ b/en-US/Network_based_Installations.xml
@@ -73,7 +73,7 @@
<para>
Install the dhcp server package.
</para>
- <screen><command>yum install dhcp</command></screen>
+ <screen><prompt>#</prompt> <command>dnf install dhcp</command></screen>
</step>
<step>
<para>
@@ -138,7 +138,7 @@ subnet 192.168.1.0 netmask 255.255.255.0 {
Install the tftp server package.
</para>
<screen>
-<command>yum install tftp-server</command>
+<command><prompt>#</prompt> dnf install tftp-server</command>
</screen>
</step>
<step>
@@ -166,7 +166,7 @@ subnet 192.168.1.0 netmask 255.255.255.0 {
Install the <package>syslinux</package> package.
</para>
<screen>
-<command>yum install syslinux</command>
+<command><prompt>#</prompt> dnf install syslinux</command>
</screen>
</step>
<step>
@@ -188,7 +188,7 @@ subnet 192.168.1.0 netmask 255.255.255.0 {
Install the <package>shim</package> and <package>grub2-efi</package> packages. If your server is a BIOS system, you <emphasis>must install the packages to a temporary install root</emphasis>. Installing them directly on a BIOS machine will attempt to configure the system for UEFI booting and cause problems.
</para>
<screen>
-<command>yum install shim grub2-efi --installroot=/tmp/fedora --releasever &PRODVER;</command>
+<command><prompt>#</prompt> dnf install shim grub2-efi --installroot=/tmp/fedora --releasever &PRODVER;</command>
</screen>
</step>
<step>
diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml
index c1cd611..15aeabe 100644
--- a/en-US/Troubleshooting.xml
+++ b/en-US/Troubleshooting.xml
@@ -99,7 +99,7 @@
<filename>/tmp/packaging.log</filename>
</entry>
<entry>
- <application>yum</application> and <application>rpm</application> package installation messages
+ <application>dnf</application> and <application>rpm</application> package installation messages
</entry>
</row>
<row>
@@ -709,7 +709,7 @@ GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -
If you are having trouble getting <application>X</application> (the <application>X Window System</application>) to start, it is possible that it has not been installed. Some of the pre-set base environments you can select during the installation, such as <guilabel>Minimal install</guilabel> or <guilabel>Web Server</guilabel>, do not include a graphical interface - it has to be installed manually.
</para>
<para>
- If you want <application>X</application>, you can install the necessary packages after the installation using the <application>Yum</application> package manager. For example, to install <application>GNOME</application>, use <command>yum install gnome-shell</command> as <systemitem class="username">root</systemitem>.
+ If you want <application>X</application>, you can install the necessary packages after the installation using the <application>DNF</application> package manager. For example, to install <application>GNOME</application>, use <command>dnf install gnome-shell</command> as <systemitem class="username">root</systemitem>.
</para>
</section>
diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml
index 1dadb28..c862316 100644
--- a/en-US/VNC_Installations.xml
+++ b/en-US/VNC_Installations.xml
@@ -44,7 +44,7 @@
To install any of the viewers listed above, execute the following command as <systemitem>root</systemitem>:
</para>
<screen>
-<prompt>#</prompt> <command>yum install <replaceable>package</replaceable></command>
+<prompt>#</prompt> <command>dnf install <replaceable>package</replaceable></command>
</screen>
<para>
Replace <replaceable>package</replaceable> with the package name of the viewer you want to use (for example, <package>tigervnc</package>).
More information about the docs-commits
mailing list