[system-administrators-guide] Refer to >> See {bulk change}
stephenw
stephenw at fedoraproject.org
Thu Jul 31 10:39:05 UTC 2014
commit df14e589198d2d792696d7e4633c6cb5f54aaa69
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Thu Jul 31 12:29:44 2014 +0200
Refer to >> See {bulk change}
en-US/Automatic_Bug_Reporting_Tool_ABRT.xml | 10 ++++----
en-US/Automating_System_Tasks.xml | 8 +++---
en-US/Configuring_NTP_Using_ntpd.xml | 2 +-
en-US/FTP.xml | 16 +++++++-------
en-US/Mail_Servers.xml | 14 ++++++------
en-US/Managing_Users_and_Groups.xml | 6 ++--
en-US/Manually_Upgrading_the_Kernel.xml | 16 +++++++-------
en-US/OProfile.xml | 14 ++++++------
en-US/OpenLDAP.xml | 6 ++--
en-US/OpenSSH.xml | 12 +++++-----
en-US/PackageKit.xml | 6 ++--
en-US/Printer_Configuration.xml | 10 ++++----
en-US/RPM.xml | 10 ++++----
en-US/Samba.xml | 6 ++--
en-US/System_Monitoring_Tools.xml | 2 +-
en-US/The_Apache_HTTP_Server.xml | 18 ++++++++--------
en-US/The_X_Window_System.xml | 12 +++++-----
en-US/The_kdump_Crash_Recovery_Service.xml | 6 ++--
en-US/Working_with_Kernel_Modules.xml | 2 +-
en-US/Yum.xml | 30 +++++++++++++-------------
20 files changed, 103 insertions(+), 103 deletions(-)
---
diff --git a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
index 1093dc8..4d580a5 100644
--- a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+++ b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
@@ -366,7 +366,7 @@ kernel.panic = 0</screen>
</mediaobject>
</figure>
<para>
- Here, you need to provide your Red Hat login information (Refer to <xref linkend="sect-abrt-configuration-event_configuration_in_gui"/> for more information on how to acquire it and how to set this event.), otherwise you will fail to report the problem.
+ Here, you need to provide your Red Hat login information (See <xref linkend="sect-abrt-configuration-event_configuration_in_gui"/> for more information on how to acquire it and how to set this event.), otherwise you will fail to report the problem.
</para>
<figure
id="fig-abrt-gui_rhtsupport_configuration.png">
@@ -828,7 +828,7 @@ rm '/var/spool/abrt/ccpp-2011-09-12-18:37:24-4413'</screen>
When a problem is detected and its defining data is stored, the problem is processed by running events on the
problem's data directory. For more information on events and how to define one, refer to <xref
linkend="sect-abrt-configuration-events"/>. Standard <application>ABRT</application> installation currently
- supports several default events that can be selected and used during problem reporting process. Refer to <xref
+ supports several default events that can be selected and used during problem reporting process. See <xref
linkend="sect-abrt-configuration-events-default_events"/> to see the list of these events.
</para>
<para>
@@ -1515,7 +1515,7 @@ ftp> <command>quit</command></screen>
</listitem>
<listitem>
<para>
- Decide whether you want to collect package information (the <option>package</option> and the <option>component</option> elements) in the problem data. Refer to <xref
+ Decide whether you want to collect package information (the <option>package</option> and the <option>component</option> elements) in the problem data. See <xref
linkend="sect-abrt-centralized_crash_collection-saving_package_information"/> to find out whether you need to collect package information in your centralized crash collection configuration and how to configure it properly.
</para>
</listitem>
@@ -1530,13 +1530,13 @@ ftp> <command>quit</command></screen>
<orderedlist>
<listitem>
<para>
- If you do not wish to generate a backtrace, or if you decided to generate it on a server system, you need to delete or comment out the corresponding rules in the <filename>/etc/libreport/events.d/ccpp_events.conf</filename> file. Refer to <xref
+ If you do not wish to generate a backtrace, or if you decided to generate it on a server system, you need to delete or comment out the corresponding rules in the <filename>/etc/libreport/events.d/ccpp_events.conf</filename> file. See <xref
linkend="sect-abrt-centralized_crash_collection-server"/> for an example of such a example.
</para>
</listitem>
<listitem>
<para>
- If you decided to not collect package information on client machines, delete, comment out or modify the rule which runs abrt-action-save-package-data in the <filename>/etc/libreport/events.d/abrt_event.conf</filename> file. Refer to <xref
+ If you decided to not collect package information on client machines, delete, comment out or modify the rule which runs abrt-action-save-package-data in the <filename>/etc/libreport/events.d/abrt_event.conf</filename> file. See <xref
linkend="sect-abrt-centralized_crash_collection-saving_package_information"/> to find out whether you need to collect package information in your centralized crash collection configuration and how to configure it properly.
</para>
</listitem>
diff --git a/en-US/Automating_System_Tasks.xml b/en-US/Automating_System_Tasks.xml
index 7b603f1..4a9a2ea 100644
--- a/en-US/Automating_System_Tasks.xml
+++ b/en-US/Automating_System_Tasks.xml
@@ -36,7 +36,7 @@
<para>It is recommended that you start the service at boot time. To do so, use the following command as <systemitem class="username">root</systemitem>:</para>
<screen><command>systemctl enable crond.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s2-configuring-anacron-jobs">
@@ -306,7 +306,7 @@ HOME=/
<keycap>D</keycap>
</keycombo> on a blank line to exit. If a script is entered, the shell used is the shell set in the user's <envar>SHELL</envar> environment, the user's login shell, or <command>/bin/sh</command> (whichever is found first).</para>
<para>If the set of commands or script tries to display information to standard output, the output is emailed to the user.</para>
- <para>Use the command <command>atq</command> to view pending jobs. Refer to <xref linkend="s2-autotasks-at-batch-viewing"/> for more information.</para>
+ <para>Use the command <command>atq</command> to view pending jobs. See <xref linkend="s2-autotasks-at-batch-viewing"/> for more information.</para>
<para>Usage of the <command>at</command> command can be restricted. For more information, refer to <xref linkend="s2-autotasks-at-batch-controlling-access"/> for details.</para>
</section>
<section id="s2-autotasks-batch-configuring">
@@ -320,7 +320,7 @@ HOME=/
<keycap>D</keycap>
</keycombo> on a blank line to exit. If a script is entered, the shell used is the shell set in the user's <envar>SHELL</envar> environment, the user's login shell, or <command>/bin/sh</command> (whichever is found first). As soon as the load average is below 0.8, the set of commands or script is executed.</para>
<para>If the set of commands or script tries to display information to standard out, the output is emailed to the user.</para>
- <para>Use the command <command>atq</command> to view pending jobs. Refer to <xref linkend="s2-autotasks-at-batch-viewing"/> for more information.</para>
+ <para>Use the command <command>atq</command> to view pending jobs. See <xref linkend="s2-autotasks-at-batch-viewing"/> for more information.</para>
<para>Usage of the <command>batch</command> command can be restricted. For more information, refer to <xref linkend="s2-autotasks-at-batch-controlling-access"/> for details.</para>
</section>
<section id="s2-autotasks-at-batch-viewing">
@@ -391,7 +391,7 @@ HOME=/
<para>It is recommended that you start the service at boot time. To do so, run the following command as <systemitem class="username">root</systemitem>:</para>
<screen><command>systemctl enable atd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
</section>
diff --git a/en-US/Configuring_NTP_Using_ntpd.xml b/en-US/Configuring_NTP_Using_ntpd.xml
index eced2f9..c956c70 100644
--- a/en-US/Configuring_NTP_Using_ntpd.xml
+++ b/en-US/Configuring_NTP_Using_ntpd.xml
@@ -257,7 +257,7 @@ server 3.fedora.pool.ntp.org iburst</screen>
<term>The broadcast multicast servers entry</term>
<listitem>
<para>
- By default, the <filename>ntp.conf</filename> file contains some commented out examples. These are largely self explanatory. Refer to the explanation of the specific commands <xref linkend="s1-Configure_NTP" />. If required, add your commands just below the examples.</para>
+ By default, the <filename>ntp.conf</filename> file contains some commented out examples. These are largely self explanatory. See the explanation of the specific commands <xref linkend="s1-Configure_NTP" />. If required, add your commands just below the examples.</para>
</listitem>
</varlistentry>
diff --git a/en-US/FTP.xml b/en-US/FTP.xml
index 3f4dd47..5f943c9 100644
--- a/en-US/FTP.xml
+++ b/en-US/FTP.xml
@@ -73,7 +73,7 @@
<term>passive mode</term>
<listitem>
<para>Passive mode, like active mode, is initiated by the <systemitem class="protocol">FTP</systemitem> client application. When requesting data from the server, the <systemitem class="protocol">FTP</systemitem> client indicates it wants to access the data in passive mode and the server provides the <systemitem class="protocol">IP</systemitem> address and a random, unprivileged port (greater than <constant>1024</constant>) on the server. The client then connects to that port on the server to download the requested information.</para>
- <para>While passive mode resolves issues for client-side firewall interference with data connections, it can complicate administration of the server-side firewall. You can reduce the number of open ports on a server by limiting the range of unprivileged ports on the <systemitem class="protocol">FTP</systemitem> server. This also simplifies the process of configuring firewall rules for the server. Refer to <xref
+ <para>While passive mode resolves issues for client-side firewall interference with data connections, it can complicate administration of the server-side firewall. You can reduce the number of open ports on a server by limiting the range of unprivileged ports on the <systemitem class="protocol">FTP</systemitem> server. This also simplifies the process of configuring firewall rules for the server. See <xref
linkend="s3-ftp-vsftpd-conf-opt-net"/> for more information about limiting passive ports.</para>
</listitem>
</varlistentry>
@@ -188,7 +188,7 @@
<itemizedlist>
<listitem>
<para>
- <filename>/etc/rc.d/init.d/vsftpd</filename> — The <emphasis>initialization script</emphasis> (<firstterm>initscript</firstterm>) used by the <command>systemctl</command> command to start, stop, or reload <command>vsftpd</command>. Refer to <xref
+ <filename>/etc/rc.d/init.d/vsftpd</filename> — The <emphasis>initialization script</emphasis> (<firstterm>initscript</firstterm>) used by the <command>systemctl</command> command to start, stop, or reload <command>vsftpd</command>. See <xref
linkend="s2-ftp-vsftpd-start"/> for more information about using this script.</para>
</listitem>
<listitem>
@@ -197,7 +197,7 @@
</listitem>
<listitem>
<para>
- <filename>/etc/vsftpd/vsftpd.conf</filename> — The configuration file for <command>vsftpd</command>. Refer to <xref
+ <filename>/etc/vsftpd/vsftpd.conf</filename> — The configuration file for <command>vsftpd</command>. See <xref
linkend="s2-ftp-vsftpd-conf"/> for a list of important options contained within this file.</para>
</listitem>
<listitem>
@@ -265,7 +265,7 @@
<para>To conditionally restart the server, as <systemitem class="username">root</systemitem> type:</para>
<screen><command>systemctl condrestart vsftpd.service</command></screen>
<para>
- By default, the <command>vsftpd</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure the <command>vsftpd</command> service to start at boot time, use a service manager such as <command>systemctl</command>. Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.</para>
+ By default, the <command>vsftpd</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure the <command>vsftpd</command> service to start at boot time, use a service manager such as <command>systemctl</command>. See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.</para>
<section
id="s3-ftp-vsftpd-start-multi">
<title>Starting Multiple Copies of <command>vsftpd</command>
@@ -424,7 +424,7 @@
<para>
<command>anonymous_enable</command> — When enabled, anonymous users are allowed to log in. The usernames <computeroutput>anonymous</computeroutput> and <computeroutput>ftp</computeroutput> are accepted.</para>
<para>The default value is <command>YES</command>.</para>
- <para>Refer to <xref
+ <para>See <xref
linkend="s3-ftp-vsftpd-conf-opt-anon"/> for a list of directives affecting anonymous users.</para>
</listitem>
<listitem>
@@ -456,7 +456,7 @@
<para>
<command>local_enable</command> — When enabled, local users are allowed to log into the system.</para>
<para>The default value is <command>YES</command>.</para>
- <para>Refer to <xref
+ <para>See <xref
linkend="s3-ftp-vsftpd-conf-opt-usr"/> for a list of directives affecting local users.</para>
</listitem>
<listitem>
@@ -817,7 +817,7 @@
<para>There is no default value for this directive.</para>
<note>
<title>Running multiple copies of vsftpd</title>
- <para>If running multiple copies of <command>vsftpd</command> serving different <systemitem class="protocol">IP</systemitem> addresses, the configuration file for each copy of the <command>vsftpd</command> daemon must have a different value for this directive. Refer to <xref
+ <para>If running multiple copies of <command>vsftpd</command> serving different <systemitem class="protocol">IP</systemitem> addresses, the configuration file for each copy of the <command>vsftpd</command> daemon must have a different value for this directive. See <xref
linkend="s3-ftp-vsftpd-start-multi"/> for more information about multihomed <systemitem class="protocol">FTP</systemitem> servers.</para>
</note>
</listitem>
@@ -827,7 +827,7 @@
<para>There is no default value for this directive.</para>
<note>
<title>Running multiple copies of vsftpd</title>
- <para>If running multiple copies of <command>vsftpd</command> serving different <systemitem class="protocol">IP</systemitem> addresses, the configuration file for each copy of the <command>vsftpd</command> daemon must have a different value for this directive. Refer to <xref
+ <para>If running multiple copies of <command>vsftpd</command> serving different <systemitem class="protocol">IP</systemitem> addresses, the configuration file for each copy of the <command>vsftpd</command> daemon must have a different value for this directive. See <xref
linkend="s3-ftp-vsftpd-start-multi"/> for more information about multihomed <systemitem class="protocol">FTP</systemitem> servers.</para>
</note>
</listitem>
diff --git a/en-US/Mail_Servers.xml b/en-US/Mail_Servers.xml
index dc03e0b..23406f6 100644
--- a/en-US/Mail_Servers.xml
+++ b/en-US/Mail_Servers.xml
@@ -97,7 +97,7 @@
<secondary>protocols</secondary>
<tertiary>IMAP</tertiary>
</indexterm>
- <para>The default <systemitem class="protocol">IMAP</systemitem> server under &MAJOROS; is <application>Dovecot</application> and is provided by the <package>dovecot</package> package. Refer to <xref linkend="s3-email-protocols-pop"/> for information on how to install <application>Dovecot</application>.</para>
+ <para>The default <systemitem class="protocol">IMAP</systemitem> server under &MAJOROS; is <application>Dovecot</application> and is provided by the <package>dovecot</package> package. See <xref linkend="s3-email-protocols-pop"/> for information on how to install <application>Dovecot</application>.</para>
<para>When using an <systemitem class="protocol">IMAP</systemitem> mail server, email messages remain on the server where users can read or delete them. <systemitem class="protocol">IMAP</systemitem> also allows client applications to create, rename, or delete mail directories on the server to organize and store email.</para>
<para><systemitem class="protocol">IMAP</systemitem> is particularly useful for users who access their email using multiple machines. The protocol is also convenient for users connecting to the mail server via a slow connection, because only the email header information is downloaded for messages until opened, saving bandwidth. The user also has the ability to delete messages without viewing or downloading them.</para>
<para>For convenience, <systemitem class="protocol">IMAP</systemitem> client applications are capable of caching copies of messages locally, so the user can browse previously read messages when not directly connected to the <systemitem class="protocol">IMAP</systemitem> server.</para>
@@ -404,7 +404,7 @@ search_base = dc=<replaceable>example</replaceable>, dc=<replaceable>com</replac
<secondary>limitations</secondary>
</indexterm>
<para>It is important to be aware of what Sendmail is and what it can do, as opposed to what it is not. In these days of monolithic applications that fulfill multiple roles, Sendmail may seem like the only application needed to run an email server within an organization. Technically, this is true, as Sendmail can spool mail to each users' directory and deliver outbound mail for users. However, most users actually require much more than simple email delivery. Users usually want to interact with their email using an MUA, that uses <systemitem class="protocol">POP</systemitem> or <systemitem class="protocol">IMAP</systemitem>, to download their messages to their local machine. Or, they may prefer a Web interface to gain access to their mailbox. These other applications can work in conjunction with Sendmail, but they actually exist for different reasons and can operate separately from one another.</para>
- <para>It is beyond the scope of this section to go into all that Sendmail should or could be configured to do. With literally hundreds of different options and rule sets, entire volumes have been dedicated to helping explain everything that can be done and how to fix things that go wrong. Refer to the <xref
+ <para>It is beyond the scope of this section to go into all that Sendmail should or could be configured to do. With literally hundreds of different options and rule sets, entire volumes have been dedicated to helping explain everything that can be done and how to fix things that go wrong. See the <xref
linkend="s1-email-additional-resources"/> for a list of Sendmail resources.</para>
<para>This section reviews the files installed with Sendmail by default and reviews basic configuration changes, including how to stop unwanted email (spam) and how to extend Sendmail with the <firstterm>Lightweight Directory Access Protocol (LDAP)</firstterm>.</para>
</section>
@@ -555,8 +555,8 @@ MASQUERADE_AS(bigcorp.com)dnl</programlisting>
<para>Because the <filename>/etc/mail/access.db</filename> file is a database, use the <command>makemap</command> command to update any changes. Do this using the following command as <systemitem class="username">root</systemitem>:</para>
<screen><command>makemap hash /etc/mail/access < /etc/mail/access</command></screen>
<para>Message header analysis allows you to reject mail based on header contents. <systemitem class="protocol">SMTP</systemitem> servers store information about an email's journey in the message header. As the message travels from one MTA to another, each puts in a <literal>Received</literal> header above all the other <literal>Received</literal> headers. It is important to note that this information may be altered by spammers.</para>
- <para>The above examples only represent a small part of what Sendmail can do in terms of allowing or blocking access. Refer to the <filename>/usr/share/sendmail-cf/README</filename> for more information and examples.</para>
- <para>Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to use a spam filtering program, such as SpamAssassin, to identify and file spam for users. Refer to <xref
+ <para>The above examples only represent a small part of what Sendmail can do in terms of allowing or blocking access. See the <filename>/usr/share/sendmail-cf/README</filename> for more information and examples.</para>
+ <para>Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to use a spam filtering program, such as SpamAssassin, to identify and file spam for users. See <xref
linkend="s3-email-mda-spam"/> for more information about using SpamAssassin.</para>
</section>
<section
@@ -577,7 +577,7 @@ FEATURE('ldap_routing')dnl</programlisting>
<para>This is only for a very basic configuration of Sendmail with <systemitem class="protocol">LDAP</systemitem>. The configuration can differ greatly from this depending on the implementation of <systemitem class="protocol">LDAP</systemitem>, especially when configuring several Sendmail machines to use a common <systemitem class="protocol">LDAP</systemitem> server.</para>
<para>Consult <filename>/usr/share/sendmail-cf/README</filename> for detailed <systemitem class="protocol">LDAP</systemitem> routing configuration instructions and examples.</para>
</note>
- <para>Next, recreate the <filename>/etc/mail/sendmail.cf</filename> file by running the <command>m4</command> macro processor and again restarting Sendmail. Refer to <xref
+ <para>Next, recreate the <filename>/etc/mail/sendmail.cf</filename> file by running the <command>m4</command> macro processor and again restarting Sendmail. See <xref
linkend="s3-email-mta-sendmail-changes"/> for instructions.</para>
<para>For more information on <systemitem class="protocol">LDAP</systemitem>, refer to <xref
linkend="s1-OpenLDAP" />.</para>
@@ -1072,7 +1072,7 @@ poll mail.domain2.com
</command> section specifies that a lockfile is created for this message. If a lockfile is created, the name can be specified by replacing <command><replaceable>lockfile-name</replaceable>
</command>.</para>
<para>A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the asterisk character (<command>*</command>) can further control the condition.</para>
- <para>The <command><replaceable>action-to-perform</replaceable></command> argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. Refer to <xref
+ <para>The <command><replaceable>action-to-perform</replaceable></command> argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. See <xref
linkend="s3-email-procmail-recipes-special"/> for more information.</para>
<section
id="s2-email-procmail-recipes-delivering">
@@ -1297,7 +1297,7 @@ poll mail.domain2.com
<para>To start the SpamAssassin daemon when the system is booted, run:</para>
<screen><command>systemctl enable spamassassin.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
<para>To configure Procmail to use the SpamAssassin client application instead of the Perl script, place the following line near the top of the <filename>~/.procmailrc</filename> file. For a system-wide configuration, place it in <filename>/etc/procmailrc</filename>:</para>
<programlisting>INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</programlisting>
diff --git a/en-US/Managing_Users_and_Groups.xml b/en-US/Managing_Users_and_Groups.xml
index de6fe53..cfafab9 100644
--- a/en-US/Managing_Users_and_Groups.xml
+++ b/en-US/Managing_Users_and_Groups.xml
@@ -31,7 +31,7 @@
Each user is associated with a unique numerical identification number called a <firstterm>user ID</firstterm> (<acronym>UID</acronym>). Likewise, each group is associated with a <firstterm>group ID</firstterm> (<acronym>GID</acronym>). A user who creates a file is also the owner and group owner of that file. The file is assigned separate read, write, and execute permissions for the owner, the group, and everyone else. The file owner can be changed only by <systemitem class="username">root</systemitem>, and access permissions can be changed by both the <systemitem class="username">root</systemitem> user and file owner.
</para>
<para>
- Additionally, &MAJOROS; supports <firstterm>access control lists</firstterm> (<acronym>ACLs</acronym>) for files and directories which allow permissions for specific users outside of the owner to be set. Refer to For more information about this feature, refer to the <ulink url="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-acls.html"><citetitle pubwork="chapter">Access Control Lists</citetitle></ulink> chapter of the <ulink url="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html"><citetitle pubwork="book">Storage Administration Guide</citetitle></ulink>.
+ Additionally, &MAJOROS; supports <firstterm>access control lists</firstterm> (<acronym>ACLs</acronym>) for files and directories which allow permissions for specific users outside of the owner to be set. See For more information about this feature, refer to the <ulink url="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-acls.html"><citetitle pubwork="chapter">Access Control Lists</citetitle></ulink> chapter of the <ulink url="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html"><citetitle pubwork="book">Storage Administration Guide</citetitle></ulink>.
</para>
<section id="s2-users-groups-private-groups">
<title>User Private Groups</title>
@@ -627,7 +627,7 @@
</para>
<synopsis><command>passwd</command> <replaceable>username</replaceable></synopsis>
<para>
- Optionally, you can set password aging policy. Refer to <xref linkend="s2-users-tools-password-aging" /> for information on how to enable password aging.
+ Optionally, you can set password aging policy. See <xref linkend="s2-users-tools-password-aging" /> for information on how to enable password aging.
</para>
<table id="table-useradd-options">
<title>useradd command line options</title>
@@ -1282,7 +1282,7 @@ drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 myproject</screen>
<secondary>additional resources</secondary>
</indexterm>
<para>
- Refer to the following resources for more information about managing users and groups.
+ See the following resources for more information about managing users and groups.
</para>
<section id="s2-users-groups-documentation">
<title>Installed Documentation</title>
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index 03863cd..d836b85 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -251,7 +251,7 @@
</step>
</procedure>
<para>
- Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the <package>mkbootdisk</package> package and running the <command>mkbootdisk</command> command as <systemitem class="username">root</systemitem>. Refer to <command>man mkbootdisk</command> man page after installing the package for usage information.
+ Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the <package>mkbootdisk</package> package and running the <command>mkbootdisk</command> command as <systemitem class="username">root</systemitem>. See <command>man mkbootdisk</command> man page after installing the package for usage information.
</para>
<para>
To determine which kernel packages are installed, execute the command <command>yum list installed "kernel-*"</command> at a shell prompt. The output will comprise some or all of the following packages, depending on the system's architecture, and the version numbers may differ:
@@ -266,7 +266,7 @@ kernel-doc.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing
kernel-headers.x86_64 3.1.0-0.rc6.git0.3.fc16 @updates-testing
kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing</screen>
<para>
- From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <package>kernel</package> package. Refer to <xref linkend="s1-kernel-packages" /> for descriptions of the different packages.
+ From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <package>kernel</package> package. See <xref linkend="s1-kernel-packages" /> for descriptions of the different packages.
</para>
<!-- RHEL6: the following info is probably unnecessary
<para>In the file name, each kernel package contains the architecture for which the package was built. The format is kernel-<replaceable><variant></replaceable>-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm, where <replaceable><variant></replaceable> is one of either <package>PAE</package>, <package>xen</package>, and so forth. The <replaceable><arch></replaceable> is one of the following:</para>
@@ -336,7 +336,7 @@ kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing</screen
<itemizedlist>
<listitem>
<para>
- Security Advisories — Refer to <ulink url="http://fedoraproject.org/wiki/FSA" /> for information on Security Advisories, including kernel upgrades that fix security issues.
+ Security Advisories — See <ulink url="http://fedoraproject.org/wiki/FSA" /> for information on Security Advisories, including kernel upgrades that fix security issues.
</para>
</listitem>
<listitem>
@@ -369,7 +369,7 @@ kernel-headers.x86_64 3.1.0-0.rc9.git0.0.fc16 @updates-testing</screen
</para>
<screen><command>rpm -ivh kernel-<replaceable>kernel_version</replaceable>.<replaceable>arch</replaceable>.rpm </command></screen>
<para>
- The next step is to verify that the initial RAM disk image has been created. Refer to <xref linkend="sec-Verifying_the_Initial_RAM_Disk_Image" /> for details.
+ The next step is to verify that the initial RAM disk image has been created. See <xref linkend="sec-Verifying_the_Initial_RAM_Disk_Image" /> for details.
</para>
</section>
<section id="sec-Verifying_the_Initial_RAM_Disk_Image">
@@ -465,7 +465,7 @@ drwxr-xr-x 2 root root 0 Oct 11 20:36 proc
lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
<lineannotation>[output truncated]</lineannotation></screen>
<para>
- Refer to <command>man dracut</command> and <command>man dracut.conf</command> for more information on options and usage.
+ See <command>man dracut</command> and <command>man dracut.conf</command> for more information on options and usage.
</para>
</step>
<step>
@@ -476,7 +476,7 @@ lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
initrd /initramfs-3.1.0-0.rc6.git0.3.fc16.x86_64.img
initrd /initramfs-3.1.0-0.rc9.git0.0.fc16.x86_64.img</screen>
<para>
- Refer to <xref linkend="s1-kernel-boot-loader" /> for more information on how to read and update the <filename>/boot/grub2/grub.cfg</filename> file.
+ See <xref linkend="s1-kernel-boot-loader" /> for more information on how to read and update the <filename>/boot/grub2/grub.cfg</filename> file.
</para>
</step>
</procedure>
@@ -510,7 +510,7 @@ lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
It is always recommended to double-check the boot loader configuration file after installing a new kernel with <command>rpm</command> to ensure that the configuration is correct. Otherwise, the system may not be able to boot into &MAJOROS; properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.
</para>
<para>
- In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "Refer to" link to jump to the correct instructions for your system.
+ In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "See" link to jump to the correct instructions for your system.
</para>
<!--silas: the following table adapted from the RHEL6 Installation Guide, Grub.xml, "Boot Loaders and System Architecture"-->
<table id="tb-grub-arch-loaders">
@@ -528,7 +528,7 @@ lrwxrwxrwx 1 root root 17 Oct 11 20:36 etc -> run/initramfs/etc
Boot Loader
</entry>
<entry>
- Refer to
+ See
</entry>
</row>
</thead>
diff --git a/en-US/OProfile.xml b/en-US/OProfile.xml
index 47bc0e9..5e293ed 100644
--- a/en-US/OProfile.xml
+++ b/en-US/OProfile.xml
@@ -101,7 +101,7 @@
<command>opannotate</command>
</entry>
<entry>
- Creates annotated source for an executable if the application was compiled with debugging symbols. Refer to <xref
+ Creates annotated source for an executable if the application was compiled with debugging symbols. See <xref
linkend="s2-oprofile-reading-opannotate"/> for details.
</entry>
</row>
@@ -110,7 +110,7 @@
<command>opcontrol</command>
</entry>
<entry>
- <para>Configures what data is collected. Refer to <xref
+ <para>Configures what data is collected. See <xref
linkend="s1-oprofile-configuring"/> for details.</para>
</entry>
</row>
@@ -119,7 +119,7 @@
<command>opreport</command>
</entry>
<entry>
- <para>Retrieves profile data. Refer to <xref
+ <para>Retrieves profile data. See <xref
linkend="s2-oprofile-reading-opreport"/> for details.</para>
</entry>
</row>
@@ -196,7 +196,7 @@
</tertiary>
</indexterm>
<screen>~]# <command>opcontrol --setup --no-vmlinux</command></screen>
- <para>This command also loads the <computeroutput>oprofile</computeroutput> kernel module, if it is not already loaded, and creates the <filename>/dev/oprofile/</filename> directory, if it does not already exist. Refer to <xref
+ <para>This command also loads the <computeroutput>oprofile</computeroutput> kernel module, if it is not already loaded, and creates the <filename>/dev/oprofile/</filename> directory, if it does not already exist. See <xref
linkend="s1-oprofile-dev-oprofile"/> for details about this directory.</para>
<para>Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, refer to <xref
linkend="s2-oprofile-starting-separate"/>.</para>
@@ -807,7 +807,7 @@
<title>Back up the executable and the sample files</title>
<para>The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, back up the executable used to create the samples as well as the sample files. Please note that the sample file and the binary have to agree. Making a backup is not going to work if they do not match. <command>oparchive</command> can be used to address this problem.</para>
</warning>
- <para>Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The OProfile analysis tools use the executable file that created the samples during analysis. If the executable changes the analysis tools will be unable to analyze the associated samples. Refer to <xref
+ <para>Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The OProfile analysis tools use the executable file that created the samples during analysis. If the executable changes the analysis tools will be unable to analyze the associated samples. See <xref
linkend="s1-oprofile-saving-data"/> for details on how to back up the sample file.</para>
<section
id="s2-oprofile-reading-opreport">
@@ -856,7 +856,7 @@ samples| %|
1 0.0038 libgthread-2.0.so.0.400.7
1 0.0038 libwnck-1.so.4.9.0</screen>
<para>Each executable is listed on its own line. The first column is the number of samples recorded for the executable. The second column is the percentage of samples relative to the total number of samples. The third column is the name of the executable.</para>
- <para>Refer to the <command>opreport</command> man page for a list of available command line options, such as the <option>-r</option> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples.</para>
+ <para>See the <command>opreport</command> man page for a list of available command line options, such as the <option>-r</option> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples.</para>
</section>
<section
id="s2-oprofile-reading-opreport-single">
@@ -1035,7 +1035,7 @@ samples % symbol name
<para>For this utility to work, the appropriate <package>debuginfo</package> package for the executable must be installed on the system. By default, &MAJOROS; <package>debuginfo</package> packages are not installed together with their corresponding packages, which contain the executable, so that you have to obtain and install the <package>debuginfo</package> packages separately.</para>
<para>The general syntax for <command>opannotate</command> is as follows:</para>
<screen>~]# <command>opannotate --search-dirs <replaceable>src-dir</replaceable> --source <replaceable>executable</replaceable></command></screen>
- <para>The directory containing the source code and the executable to be analyzed must be specified. Refer to the <command>opannotate</command> man page for a list of additional command line options.</para>
+ <para>The directory containing the source code and the executable to be analyzed must be specified. See the <command>opannotate</command> man page for a list of additional command line options.</para>
</section>
</section>
<section
diff --git a/en-US/OpenLDAP.xml b/en-US/OpenLDAP.xml
index 2c15e47..942dcb3 100644
--- a/en-US/OpenLDAP.xml
+++ b/en-US/OpenLDAP.xml
@@ -168,7 +168,7 @@
<procedure>
<step>
<para>
- Install the OpenLDAP suite. Refer to <xref linkend="s2-ldap-installation" /> for more information on required packages.
+ Install the OpenLDAP suite. See <xref linkend="s2-ldap-installation" /> for more information on required packages.
</para>
</step>
<step>
@@ -1092,7 +1092,7 @@ Re-enter new password:
</para>
<screen><command>systemctl enable slapd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s3-ldap-running-stopping">
@@ -1110,7 +1110,7 @@ Re-enter new password:
</para>
<screen><command>systemctl disable slapd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s3-ldap-running-restarting">
diff --git a/en-US/OpenSSH.xml b/en-US/OpenSSH.xml
index 3184132..7239f8e 100644
--- a/en-US/OpenSSH.xml
+++ b/en-US/OpenSSH.xml
@@ -467,7 +467,7 @@
</tgroup>
</table>
<para>
- Refer to the <command>ssh_config</command> and <command>sshd_config</command> man pages for information concerning the various directives available in the SSH configuration files.
+ See the <command>ssh_config</command> and <command>sshd_config</command> man pages for information concerning the various directives available in the SSH configuration files.
</para>
</section>
<section id="s2-ssh-configuration-sshd">
@@ -479,7 +479,7 @@
<note>
<title>Make sure you have relevant packages installed</title>
<para>
- To run an OpenSSH server, you must have the <package>openssh-server</package> and <package>openssh</package> packages installed. Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+ To run an OpenSSH server, you must have the <package>openssh-server</package> and <package>openssh</package> packages installed. See <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
</para>
</note>
<indexterm>
@@ -505,7 +505,7 @@
</para>
<screen><command>systemctl enable sshd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
<para>
Note that if you reinstall the system, a new set of identification keys will be created. As a result, clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message:
@@ -548,7 +548,7 @@ It is also possible that the RSA host key has just been changed.</screen>
<command>systemctl disable rlogin.service</command>
<command>systemctl disable vsftpd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s2-ssh-configuration-keypairs">
@@ -801,7 +801,7 @@ The key's randomart image is:
</step>
</procedure>
<para>
- Refer to <xref linkend="s3-ssh-configuration-keypairs-agent" /> for information on how to set up your system to remember the passphrase.
+ See <xref linkend="s3-ssh-configuration-keypairs-agent" /> for information on how to set up your system to remember the passphrase.
</para>
<important>
<title>Never share your private key</title>
@@ -945,7 +945,7 @@ Enter passphrase for /home/john/.ssh/id_rsa:</screen>
<note>
<title>Make sure you have relevant packages installed</title>
<para>
- To connect to an OpenSSH server from a client machine, you must have the <package>openssh-clients</package> and <package>openssh</package> packages installed. Refer to <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
+ To connect to an OpenSSH server from a client machine, you must have the <package>openssh-clients</package> and <package>openssh</package> packages installed. See <xref linkend="sec-Installing" /> for more information on how to install new packages in &MAJOROS;.
</para>
</note>
diff --git a/en-US/PackageKit.xml b/en-US/PackageKit.xml
index 54137a5..77c3e99 100644
--- a/en-US/PackageKit.xml
+++ b/en-US/PackageKit.xml
@@ -179,7 +179,7 @@
<section
id="sec-Refreshing_Software_Sources_Yum_Repositories">
<title>Refreshing Software Sources (Yum Repositories)</title>
- <para>To enable or disable a <application>Yum</application> repository, open a dialog box by sclicking <menuchoice><guimenu>System</guimenu><guimenuitem>Software Sources</guimenuitem></menuchoice>, and select the <guilabel>Software Sources</guilabel> tab. Refer to <xref linkend="sec-Setting_preferences_for_software_sources" /> for more information on available configuration options.</para>
+ <para>To enable or disable a <application>Yum</application> repository, open a dialog box by sclicking <menuchoice><guimenu>System</guimenu><guimenuitem>Software Sources</guimenuitem></menuchoice>, and select the <guilabel>Software Sources</guilabel> tab. See <xref linkend="sec-Setting_preferences_for_software_sources" /> for more information on available configuration options.</para>
<para>After enabling and/or disabling the correct <application>Yum</application> repositories, make sure that you have the latest list of available packages. Click on <menuchoice><guimenu>System</guimenu><guimenuitem>Refresh Package Lists</guimenuitem></menuchoice> and <application>PackageKit</application> will obtain the latest lists of packages from all enabled software sources, that is, <application>Yum</application> repositories.</para>
</section>
<section
@@ -283,7 +283,7 @@
</indexterm>
</term>
<listitem>
- <para>Search for packages which are considered to be free software Refer to the <ulink
+ <para>Search for packages which are considered to be free software See the <ulink
url="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses">Fedora Licensing List</ulink> for details on approved licenses.</para>
</listitem>
</varlistentry>
@@ -588,7 +588,7 @@
</tbody>
</tgroup>
</table>
- <para>The <command>packagekitd</command> daemon runs outside the user session and communicates with the various graphical front ends. The <command>packagekitd</command> daemon<footnote id="footnote-Daemons"><para>System daemons are typically long-running processes that provide services to the user or to other programs, and which are started, often at boot time. Daemons respond to the <command>systemctl</command> command and can be turned on or off permanently by using the <command>systemctl enable</command> or <command>systemctl disable</command>commands. They can typically be recognized by a <quote><emphasis>d</emphasis></quote> appended to their name, such as the <command>packagekitd</command> daemon. Refer to <xref linkend="ch-Services_and_Daemons"/> for information about system services.</para>
+ <para>The <command>packagekitd</command> daemon runs outside the user session and communicates with the various graphical front ends. The <command>packagekitd</command> daemon<footnote id="footnote-Daemons"><para>System daemons are typically long-running processes that provide services to the user or to other programs, and which are started, often at boot time. Daemons respond to the <command>systemctl</command> command and can be turned on or off permanently by using the <command>systemctl enable</command> or <command>systemctl disable</command>commands. They can typically be recognized by a <quote><emphasis>d</emphasis></quote> appended to their name, such as the <command>packagekitd</command> daemon. See <xref linkend="ch-Services_and_Daemons"/> for information about system services.</para>
</footnote>
communicates via the <application>DBus</application> system message bus with another back end, which utilizes <application>Yum</application>'s Python API to perform queries and make changes to the system. On Linux systems other than Red Hat Enterprise Linux and Fedora, <command>packagekitd</command> can communicate with other back ends that are able to utilize the native package manager for that system. This modular architecture provides the abstraction necessary for the graphical interfaces to work with many different package managers to perform essentially the same types of package management tasks. Learning how to use the <application>PackageKit</application> front ends means that you can use the same familiar graphical interface across many different Linux distributions, even when they utilize a native package manager other than <application>Yum</application>.</para>
<para>In addition, <application>PackageKit</application>'s separation of concerns provides reliability in that a crash of one of the GUI windows—or even the user's X Window session—will not affect any package management tasks being supervised by the <command>packagekitd</command> daemon, which runs outside of the user session.</para>
diff --git a/en-US/Printer_Configuration.xml b/en-US/Printer_Configuration.xml
index 688eec8..5557c3b 100644
--- a/en-US/Printer_Configuration.xml
+++ b/en-US/Printer_Configuration.xml
@@ -162,7 +162,7 @@
</step>
<step>
<para>
- Select the printer model. Refer to <xref linkend="s1-printing-select-model" /> for details.
+ Select the printer model. See <xref linkend="s1-printing-select-model" /> for details.
</para>
</step>
</procedure>
@@ -226,7 +226,7 @@
</step>
<step>
<para>
- Select the printer model. Refer to <xref linkend="s1-printing-select-model" /> for details.
+ Select the printer model. See <xref linkend="s1-printing-select-model" /> for details.
</para>
</step>
</procedure>
@@ -303,7 +303,7 @@
</step>
<step>
<para>
- Select the printer model. Refer to <xref linkend="s1-printing-select-model" /> for details.
+ Select the printer model. See <xref linkend="s1-printing-select-model" /> for details.
</para>
</step>
</procedure>
@@ -374,7 +374,7 @@
</step>
<step>
<para>
- Select the printer model. Refer to <xref linkend="s1-printing-select-model" /> for details.
+ Select the printer model. See <xref linkend="s1-printing-select-model" /> for details.
</para>
</step>
</procedure>
@@ -482,7 +482,7 @@
</step>
<step>
<para>
- Select the printer model. Refer to <xref linkend="s1-printing-select-model" /> for details.
+ Select the printer model. See <xref linkend="s1-printing-select-model" /> for details.
</para>
</step>
</procedure>
diff --git a/en-US/RPM.xml b/en-US/RPM.xml
index dfd3b1f..20ef0b4 100644
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@ -21,9 +21,9 @@
<title>Use Yum Instead of RPM Whenever Possible</title>
<para>For most package management tasks, the <application>Yum</application> package manager offers equal and often greater capabilities and utility than RPM<indexterm><primary>packages</primary>
<secondary>Yum instead of RPM</secondary>
- </indexterm>. <application>Yum</application> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <application>Yum</application> instead of RPM whenever possible to perform package management tasks. Refer to <xref
+ </indexterm>. <application>Yum</application> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <application>Yum</application> instead of RPM whenever possible to perform package management tasks. See <xref
linkend="ch-yum"/>.</para>
- <para>If you prefer a graphical interface, you can use the <application>PackageKit</application> GUI application, which uses <application>Yum</application> as its back end, to manage your system's packages. Refer to <xref
+ <para>If you prefer a graphical interface, you can use the <application>PackageKit</application> GUI application, which uses <application>Yum</application> as its back end, to manage your system's packages. See <xref
linkend="ch-PackageKit"/> for details.</para>
</warning>
<important>
@@ -128,7 +128,7 @@
<indexterm>
<primary> packages</primary>
<secondary>initial RPM repositories</secondary>
- </indexterm>. Refer to <xref
+ </indexterm>. See <xref
linkend="ch-yum"/> for details on how to use the official &MAJOROS; package repositories.</para>
</listitem>
<listitem>
@@ -209,7 +209,7 @@ d22e77f2</screen>
key ID d22e77f2</screen>
<para>If you do not have the appropriate key installed to verify the signature, the message contains the word <computeroutput>NOKEY</computeroutput>:</para>
<screen>warning: tree-1.5.2.2-4.&PKGOS;.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</screen>
- <para>Refer to <xref
+ <para>See <xref
linkend="s1-check-rpm-sig"/> for more information on checking a package's signature.</para>
<section
id="s3-rpm-errors">
@@ -738,7 +738,7 @@ your system.</screen>
<primary>RPM</primary>
<secondary>additional resources</secondary>
</indexterm>
- <para>RPM is an extremely complex utility with many options and methods for querying, installing, upgrading, and removing packages. Refer to the following resources to learn more about RPM.</para>
+ <para>RPM is an extremely complex utility with many options and methods for querying, installing, upgrading, and removing packages. See the following resources to learn more about RPM.</para>
<section
id="s2-rpm-installed-docs">
<title>Installed Documentation</title>
diff --git a/en-US/Samba.xml b/en-US/Samba.xml
index fb6c81f..c0879a2 100644
--- a/en-US/Samba.xml
+++ b/en-US/Samba.xml
@@ -410,7 +410,7 @@ create mask = 0765</programlisting>
<screen><command>systemctl condrestart smb.service</command></screen>
<para>A manual reload of the <filename>/etc/samba/smb.conf</filename> file can be useful in case of a failed automatic reload by the <command>smb</command> service. To ensure that the Samba server configuration file is reloaded without restarting the service, type the following command, as <systemitem class="username">root</systemitem>:</para>
<screen><command>systemctl reload smb.service</command></screen>
- <para>By default, the <command>smb</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure Samba to start at boot time, use a service manager such as <command>systemctl</command>. Refer to <xref linkend="ch-Services_and_Daemons" /> for more information regarding this tool.</para>
+ <para>By default, the <command>smb</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure Samba to start at boot time, use a service manager such as <command>systemctl</command>. See <xref linkend="ch-Services_and_Daemons" /> for more information regarding this tool.</para>
</section>
<section
id="s2-samba-servers">
@@ -1107,7 +1107,7 @@ security = share
<listitem>
<para>The <command>ldapsam</command> back end provides an optimal distributed account installation method for Samba. LDAP is optimal because of its ability to replicate its database to any number of servers such as an <application>OpenLDAP Server</application>. LDAP databases are light-weight and scalable, and as such are preferred by large enterprises. For more information on LDAP, refer to <xref linkend="s1-OpenLDAP" />.</para>
<para>If you are upgrading from a previous version of Samba to 3.0, note that the OpenLDAP schema file (<filename>/usr/share/doc/samba-<replaceable>version</replaceable>/LDAP/samba.schema</filename>) has changed. These files contain the <firstterm>attribute syntax definitions</firstterm> and <firstterm>objectclass definitions</firstterm> that the <command>ldapsam</command> back end needs in order to function properly.</para>
- <para>As such, if you are using the <command>ldapsam</command> back end for your Samba server, you will need to configure <command>slapd</command> to include one of these schema file. Refer to <xref
+ <para>As such, if you are using the <command>ldapsam</command> back end for your Samba server, you will need to configure <command>slapd</command> to include one of these schema file. See <xref
linkend="s3-ldap-configuration-schema"/> for directions on how to do this.</para>
<note>
<title>Make sure the openldap-server package is installed</title>
@@ -1767,7 +1767,7 @@ Press enter to see a dump of your service definitions
</listitem>
</itemizedlist>
<para>
- Refer to the following manual pages for detailed information specific <application>Samba</application> features:
+ See the following manual pages for detailed information specific <application>Samba</application> features:
</para>
<itemizedlist>
<listitem>
diff --git a/en-US/System_Monitoring_Tools.xml b/en-US/System_Monitoring_Tools.xml
index d762f56..54578a7 100644
--- a/en-US/System_Monitoring_Tools.xml
+++ b/en-US/System_Monitoring_Tools.xml
@@ -1451,7 +1451,7 @@ IF-MIB::ifInOctets.3 = Counter32: 0</screen>
<note>
<title>Using the proc directive</title>
<para>
- The Net-SNMP Agent also provides a built-in mechanism for checking the process table via the <option>proc</option> directive. Refer to the <emphasis role="bold">snmpd.conf</emphasis>(5) manual page for more information.
+ The Net-SNMP Agent also provides a built-in mechanism for checking the process table via the <option>proc</option> directive. See the <emphasis role="bold">snmpd.conf</emphasis>(5) manual page for more information.
</para>
</note>
<para>
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index d64c8e9..f70321f 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -168,7 +168,7 @@
</para>
<screen><command>systemctl enable httpd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
<note>
<title>Using the secure server</title>
@@ -192,7 +192,7 @@
</para>
<screen><command>systemctl disable httpd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s3-apache-running-restarting">
@@ -234,7 +234,7 @@
</listitem>
</orderedlist>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
<section id="s3-apache-running-status">
@@ -248,7 +248,7 @@
</para>
<screen><command>systemctl is-active httpd.service</command></screen>
<para>
- Refer to <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
+ See <xref linkend="ch-Services_and_Daemons" /> for more information on how to configure services in &MAJOROS;.
</para>
</section>
</section>
@@ -303,7 +303,7 @@
</tgroup>
</table>
<para>
- Although the default configuration should be suitable for most situations, it is a good idea to become at least familiar with some of the more important configuration options. Note that for any changes to take effect, the web server has to be restarted first. Refer to <xref linkend="s3-apache-running-restarting" /> for more information on how to restart the <systemitem class="service">httpd</systemitem> service.
+ Although the default configuration should be suitable for most situations, it is a good idea to become at least familiar with some of the more important configuration options. Note that for any changes to take effect, the web server has to be restarted first. See <xref linkend="s3-apache-running-restarting" /> for more information on how to restart the <systemitem class="service">httpd</systemitem> service.
</para>
<indexterm>
<primary><application>Apache HTTP Server</application></primary>
@@ -2108,7 +2108,7 @@ ErrorDocument 404 /404-not_found.html</programlisting>
The <replaceable>name</replaceable> has to be a valid identifier of the required module. The <replaceable>path</replaceable> refers to an existing module file, and must be relative to the directory in which the libraries are placed (that is, <filename class="directory">/usr/lib/httpd/</filename> on 32-bit and <filename class="directory">/usr/lib64/httpd/</filename> on 64-bit systems by default).
</para>
<para>
- Refer to <xref linkend="s2-apache-dso" /> for more information on the Apache HTTP Server's DSO support.
+ See <xref linkend="s2-apache-dso" /> for more information on the Apache HTTP Server's DSO support.
</para>
<example id="example-apache-httpdconf-loadmodule">
<title>Using the LoadModule directive</title>
@@ -3385,7 +3385,7 @@ ErrorDocument 404 /404-not_found.html</programlisting>
</varlistentry>
</variablelist>
<para>
- Note that for the <filename>/etc/httpd/conf.d/ssl.conf</filename> file to be present, the <package>mod_ssl</package> needs to be installed. Refer to <xref linkend="s2-apache-mod_ssl" /> for more information on how to install and configure an SSL server.
+ Note that for the <filename>/etc/httpd/conf.d/ssl.conf</filename> file to be present, the <package>mod_ssl</package> needs to be installed. See <xref linkend="s2-apache-mod_ssl" /> for more information on how to install and configure an SSL server.
</para>
</section>
<section id="s3-apache-mpm-common">
@@ -3622,7 +3622,7 @@ ErrorDocument 404 /404-not_found.html</programlisting>
<programlisting>LoadModule ssl_module modules/mod_ssl.so</programlisting>
</example>
<para>
- Once you are finished, restart the web server to reload the configuration. Refer to <xref linkend="s3-apache-running-restarting" /> for more information on how to restart the <systemitem class="service">httpd</systemitem> service.
+ Once you are finished, restart the web server to reload the configuration. See <xref linkend="s3-apache-running-restarting" /> for more information on how to restart the <systemitem class="service">httpd</systemitem> service.
</para>
</section>
<section id="s3-apache-dso-writing">
@@ -3686,7 +3686,7 @@ ErrorDocument 404 /404-not_found.html</programlisting>
</para>
</note>
<para>
- To activate a newly created virtual host, the web server has to be restarted first. Refer to <xref linkend="s3-apache-running-restarting" /> for more information on how to restart the <systemitem class="service">httpd</systemitem> service.
+ To activate a newly created virtual host, the web server has to be restarted first. See <xref linkend="s3-apache-running-restarting" /> for more information on how to restart the <systemitem class="service">httpd</systemitem> service.
</para>
</section>
<section id="s2-apache-mod_ssl">
diff --git a/en-US/The_X_Window_System.xml b/en-US/The_X_Window_System.xml
index a103169..8cef913 100644
--- a/en-US/The_X_Window_System.xml
+++ b/en-US/The_X_Window_System.xml
@@ -306,7 +306,7 @@
<!-- <para>To load optional modules, they must be specified in the X server configuration file, <filename>/etc/X11/xorg.conf</filename>. For more information about loading modules, refer to <xref linkend="s3-x-server-config-xorg.conf-modules"/>.</para> -->
- <para>When &MAJOROSVER; is installed, the configuration files for X are created using information gathered about the system hardware during the installation process by the HAL (Hardware Abstraction Layer) configuration back end. Whenever the X server is started, it asks HAL for the list of input devices and adds each of them with their respective driver. Whenever a new input device is plugged in, or an existing input device is removed, HAL notifies the X server about the change. Because of this notification system, devices using the <systemitem>mouse</systemitem>, <systemitem>kbd</systemitem>, or <systemitem>vmmouse</systemitem> driver configured in the <filename>xorg.conf</filename> file are, by default, ignored by the X server. Refer to <xref linkend="s3-x-server-config-xorg.conf-serverf"/> for further details. Additional configuration is provided in the <filename class="directory">/etc/X11/xorg.conf.d/</filename> directory and it can override or augment any configurat
ion that has been obtained through HAL.</para>
+ <para>When &MAJOROSVER; is installed, the configuration files for X are created using information gathered about the system hardware during the installation process by the HAL (Hardware Abstraction Layer) configuration back end. Whenever the X server is started, it asks HAL for the list of input devices and adds each of them with their respective driver. Whenever a new input device is plugged in, or an existing input device is removed, HAL notifies the X server about the change. Because of this notification system, devices using the <systemitem>mouse</systemitem>, <systemitem>kbd</systemitem>, or <systemitem>vmmouse</systemitem> driver configured in the <filename>xorg.conf</filename> file are, by default, ignored by the X server. See <xref linkend="s3-x-server-config-xorg.conf-serverf"/> for further details. Additional configuration is provided in the <filename class="directory">/etc/X11/xorg.conf.d/</filename> directory and it can override or augment any configuration t
hat has been obtained through HAL.</para>
<section id="s2-x-server-config-xorg.conf-struct">
@@ -475,7 +475,7 @@ EndSection</screen>
<para><option>MatchVendor "<replaceable>vendor_name</replaceable>"</option> — this option matches if the <replaceable>vendor_name</replaceable> substring occurs in the vendor name of the device.</para>
</listitem>
<listitem>
- <para><option>MatchDevicePath "<replaceable>/path/to/device</replaceable>"</option> — this option matches any device if its device path corresponds to the patterns given in the "<replaceable>/path/to/device</replaceable>" template, for example <literal>/dev/input/event*</literal>. Refer to the <command>fnmatch(3)</command> man page for further details.</para>
+ <para><option>MatchDevicePath "<replaceable>/path/to/device</replaceable>"</option> — this option matches any device if its device path corresponds to the patterns given in the "<replaceable>/path/to/device</replaceable>" template, for example <literal>/dev/input/event*</literal>. See the <command>fnmatch(3)</command> man page for further details.</para>
</listitem>
<listitem>
<para><option>MatchTag "<replaceable>tag_pattern</replaceable>"</option> — this option matches if at least one tag assigned by the HAL configuration back end matches the <replaceable>tag_pattern</replaceable> pattern.</para>
@@ -608,7 +608,7 @@ EndSection</screen>
</listitem>
<listitem>
- <para><option>"AutoAddDevices" "<replaceable>boolean</replaceable>"</option> — When the value of <replaceable><boolean></replaceable> is set to <literal>false</literal>, the server will not hot plug input devices and instead rely solely on devices configured in the <filename>xorg.conf</filename> file. Refer to <xref linkend="s3-x-server-config-xorg.conf-inputd"/> for more information concerning input devices. This option is enabled by default and HAL (hardware abstraction layer) is used as a back end for device discovery.</para>
+ <para><option>"AutoAddDevices" "<replaceable>boolean</replaceable>"</option> — When the value of <replaceable><boolean></replaceable> is set to <literal>false</literal>, the server will not hot plug input devices and instead rely solely on devices configured in the <filename>xorg.conf</filename> file. See <xref linkend="s3-x-server-config-xorg.conf-inputd"/> for more information concerning input devices. This option is enabled by default and HAL (hardware abstraction layer) is used as a back end for device discovery.</para>
</listitem>
</itemizedlist>
@@ -721,7 +721,7 @@ EndSection</screen>
<listitem>
<para><option>FontPath</option> — Specifies where the X server must connect to obtain fonts from the <command>xfs</command> font server.</para>
- <para>By default, the <option>FontPath</option> is <literal>unix/:7100</literal>. This tells the X server to obtain font information using UNIX-domain sockets for inter-process communication (IPC) on port 7100. Refer to <xref linkend="s1-x-fonts"/> for more information concerning X and fonts.</para>
+ <para>By default, the <option>FontPath</option> is <literal>unix/:7100</literal>. This tells the X server to obtain font information using UNIX-domain sockets for inter-process communication (IPC) on port 7100. See <xref linkend="s1-x-fonts"/> for more information concerning X and fonts.</para>
</listitem> -->
<listitem>
@@ -793,7 +793,7 @@ EndSection</screen>
</listitem>
<listitem>
- <para><option>Modeline</option> — An optional parameter which specifies additional video modes for the monitor at particular resolutions, with certain horizontal sync and vertical refresh resolutions. Refer to the <filename>xorg.conf(5)</filename> man page for a more detailed explanation of <option>Modeline</option> entries.</para>
+ <para><option>Modeline</option> — An optional parameter which specifies additional video modes for the monitor at particular resolutions, with certain horizontal sync and vertical refresh resolutions. See the <filename>xorg.conf(5)</filename> man page for a more detailed explanation of <option>Modeline</option> entries.</para>
</listitem>
<listitem>
@@ -1118,7 +1118,7 @@ EndSection</screen>
<see>X</see>
</indexterm>
- <para>When in runlevel 3, the best way to start an X session is to log in and type <command>startx</command>. The <command>startx</command> command is a front-end to the <command>xinit</command> command, which launches the X server (<filename>Xorg</filename>) and connects X client applications to it. Because the user is already logged into the system at runlevel 3, <command>startx</command> does not launch a display manager or authenticate users. Refer to <xref linkend="s2-x-runlevels-5"/> for more information about display managers.</para>
+ <para>When in runlevel 3, the best way to start an X session is to log in and type <command>startx</command>. The <command>startx</command> command is a front-end to the <command>xinit</command> command, which launches the X server (<filename>Xorg</filename>) and connects X client applications to it. Because the user is already logged into the system at runlevel 3, <command>startx</command> does not launch a display manager or authenticate users. See <xref linkend="s2-x-runlevels-5"/> for more information about display managers.</para>
<procedure>
<step>
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 32f02a6..8b39cde 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -160,7 +160,7 @@
To write the dump directly to a device, select the <guilabel>Raw device</guilabel> radio button, and choose the desired target device from the pulldown list next to it.
</para>
<para>
- To store the dump to a remote machine, select the <guilabel>Network</guilabel> radio button. To use the NFS protocol, select the <guilabel>NFS</guilabel> radio button, and fill the <guilabel>Server name</guilabel> and <guilabel>Path to directory</guilabel> fields. To use the SSH protocol, select the <guilabel>SSH</guilabel> radio button, and fill the <guilabel>Server name</guilabel>, <guilabel>Path to directory</guilabel>, and <guilabel>User name</guilabel> fields with the remote server address, target directory, and a valid remote user name respectively. Refer to <xref linkend="ch-OpenSSH" /> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ To store the dump to a remote machine, select the <guilabel>Network</guilabel> radio button. To use the NFS protocol, select the <guilabel>NFS</guilabel> radio button, and fill the <guilabel>Server name</guilabel> and <guilabel>Path to directory</guilabel> fields. To use the SSH protocol, select the <guilabel>SSH</guilabel> radio button, and fill the <guilabel>Server name</guilabel>, <guilabel>Path to directory</guilabel>, and <guilabel>User name</guilabel> fields with the remote server address, target directory, and a valid remote user name respectively. See <xref linkend="ch-OpenSSH" /> for information on how to configure an SSH server, and how to set up a key-based authentication.
</para>
<indexterm>
<primary><systemitem class="service">kdump</systemitem></primary>
@@ -423,7 +423,7 @@ path /usr/local/cores</programlisting>
</para>
<programlisting>net john at penguin.example.com</programlisting>
<para>
- Refer to <xref linkend="ch-OpenSSH" /> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ See <xref linkend="ch-OpenSSH" /> for information on how to configure an SSH server, and how to set up a key-based authentication.
</para>
<indexterm>
<primary><systemitem class="service">kdump</systemitem></primary>
@@ -461,7 +461,7 @@ path /usr/local/cores</programlisting>
</para>
<programlisting>core_collector makedumpfile -d 17 -c</programlisting>
<para>
- Refer to the manual page for <command>makedumpfile</command> for a complete list of available options.
+ See the manual page for <command>makedumpfile</command> for a complete list of available options.
</para>
<table id="table-kdump-configuration-cli-filtering-makedumpfile">
<title>Supported filtering levels</title>
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index 6151f7f..b89ae9e 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -425,7 +425,7 @@ rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</screen>
<para>First, ensure the module is not already loaded into the kernel. For example:</para>
<screen>~]# <command>lsmod | grep e1000e</command>
~]# </screen>
- <para>Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. Refer to <xref
+ <para>Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <xref
linkend="sec-Unloading_a_Module"/> for instructions on safely unloading it.</para>
</step>
<step
diff --git a/en-US/Yum.xml b/en-US/Yum.xml
index c242db7..3aa3d1d 100644
--- a/en-US/Yum.xml
+++ b/en-US/Yum.xml
@@ -9,14 +9,14 @@
<important id="important-Secure_Package_Management_with_GPG-Signed_Packages">
<title>Secure package management with GPG-signed packages</title>
<para>
- Yum provides secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed packages to be turned on for all package repositories (i.e. package sources), or for individual repositories. When signature verification is enabled, Yum will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <application>RPM</application> packages you download and install on your system are from a trusted source, such as &OSORG;, and were not modified during transfer. Refer to <xref linkend="sec-Configuring_Yum_and_Yum_Repositories" /> for details on enabling signature-checking with Yum, or <xref linkend="s1-check-rpm-sig" /> for information on working with and verifying GPG-signed <application>RPM</application> packages in general.
+ Yum provides secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed packages to be turned on for all package repositories (i.e. package sources), or for individual repositories. When signature verification is enabled, Yum will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <application>RPM</application> packages you download and install on your system are from a trusted source, such as &OSORG;, and were not modified during transfer. See <xref linkend="sec-Configuring_Yum_and_Yum_Repositories" /> for details on enabling signature-checking with Yum, or <xref linkend="s1-check-rpm-sig" /> for information on working with and verifying GPG-signed <application>RPM</application> packages in general.
</para>
</important>
<para>
Yum also enables you to easily set up your own repositories of <application>RPM</application> packages for download and installation on other machines.
</para>
<para>
- Learning Yum is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <application>PackageKit</application> graphical package management tools. Refer to <xref linkend="ch-PackageKit" /> for details on using <application>PackageKit</application>.
+ Learning Yum is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <application>PackageKit</application> graphical package management tools. See <xref linkend="ch-PackageKit" /> for details on using <application>PackageKit</application>.
</para>
<note id="note-Note_Yum_and_Superuser_Privileges">
<title>Yum and superuser privileges</title>
@@ -140,7 +140,7 @@ Is this ok [y/N]:</screen>
<orderedlist>
<listitem>
<para>
- <computeroutput>Loaded plugins:</computeroutput> — <command>yum</command> always informs you which <application>Yum</application> plug-ins are installed and enabled. Here, <command>yum</command> is using the <application>langpacks</application>, <application>presto</application>, and <application>refresh-packagekit</application> plug-ins. Refer to <xref linkend="sec-Yum_Plugins" /> for general information on <application>Yum</application> plug-ins, or to <xref linkend="sec-Plugin_Descriptions" /> for descriptions of specific plug-ins.
+ <computeroutput>Loaded plugins:</computeroutput> — <command>yum</command> always informs you which <application>Yum</application> plug-ins are installed and enabled. Here, <command>yum</command> is using the <application>langpacks</application>, <application>presto</application>, and <application>refresh-packagekit</application> plug-ins. See <xref linkend="sec-Yum_Plugins" /> for general information on <application>Yum</application> plug-ins, or to <xref linkend="sec-Plugin_Descriptions" /> for descriptions of specific plug-ins.
</para>
</listitem>
<listitem>
@@ -163,7 +163,7 @@ Is this ok [y/N]:</screen>
<command>yum</command> always <emphasis>installs</emphasis> a new kernel in the same sense that <application>RPM</application> installs a new kernel when you use the command <command>rpm -i kernel</command>. Therefore, you do not need to worry about the distinction between <emphasis>installing</emphasis> and <emphasis>upgrading</emphasis> a kernel package when you use <command>yum</command>: it will do the right thing, regardless of whether you are using the <command>yum update</command> or <command>yum install</command> command.
</para>
<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). Refer to <xref linkend="sec-Installing_and_Upgrading" /> for more information on installing/updating kernels with <application>RPM</application>.
+ 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>.
</para>
</important>
<bridgehead id="bh-Updating_All_Packages_and_Their_Dependencies">
@@ -195,7 +195,7 @@ Is this ok [y/N]:</screen>
<see>Security</see>
</indexterm>
<para>
- Discovering which packages have security updates available and then updating those packages quickly and easily is important. Yum provides the plug-in for this purpose. The <application>security</application> plug-in extends the <command>yum</command> command with a set of highly-useful security-centric commands, subcommands and options. Refer to <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. Yum provides the plug-in for this purpose. The <application>security</application> plug-in extends the <command>yum</command> command with a set of highly-useful security-centric commands, subcommands and options. See <xref linkend="sec-Plugin_Descriptions" /> for specific information.
</para>
</section>
<section id="sec-Preserving_Configuration_File_Changes">
@@ -204,7 +204,7 @@ Is this ok [y/N]:</screen>
<primary>Configuration File Changes</primary>
</indexterm>
<para>
- You will inevitably make changes to the configuration files installed by packages as you use your &MAJOROS; system. <application>RPM</application>, which Yum uses to perform changes to the system, provides a mechanism for ensuring their integrity. Refer to <xref linkend="sec-Installing_and_Upgrading" /> for details on how to manage changes to configuration files across package upgrades.
+ You will inevitably make changes to the configuration files installed by packages as you use your &MAJOROS; system. <application>RPM</application>, which Yum uses to perform changes to the system, provides a mechanism for ensuring their integrity. See <xref linkend="sec-Installing_and_Upgrading" /> for details on how to manage changes to configuration files across package upgrades.
</para>
</section>
</section>
@@ -307,7 +307,7 @@ komparator.x86_64 : Kompare and merge two folders
</listitem>
</itemizedlist>
<para>
- Refer to <xref linkend="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions" /> and <xref linkend="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards" /> for an example usage of both these methods.
+ See <xref linkend="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions" /> and <xref linkend="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards" /> for an example usage of both these methods.
</para>
</note>
<variablelist>
@@ -1125,12 +1125,12 @@ history addon-info</screen>
<itemizedlist>
<listitem>
<para>
- <computeroutput>config-main</computeroutput> — global Yum options that were in use during the transaction. Refer to <xref linkend="sec-Setting_main_Options" /> for information on how to change global options.
+ <computeroutput>config-main</computeroutput> — global Yum options that were in use during the transaction. See <xref linkend="sec-Setting_main_Options" /> for information on how to change global options.
</para>
</listitem>
<listitem>
<para>
- <computeroutput>config-repos</computeroutput> — options for individual Yum repositories. Refer to <xref linkend="sec-Setting_repository_Options" /> for information on how to change options for individual repositories.
+ <computeroutput>config-repos</computeroutput> — options for individual Yum repositories. See <xref linkend="sec-Setting_repository_Options" /> for information on how to change options for individual repositories.
</para>
</listitem>
<listitem>
@@ -1281,7 +1281,7 @@ installonly_limit=3
…where <replaceable>directory</replaceable> is an absolute path to the directory where Yum should store its cache and database files. By default, Yum's cache directory is <filename class="directory">/var/cache/yum/$basearch/$releasever</filename>.
</para>
<para>
- Refer to <xref linkend="sec-Using_Yum_Variables" /> for descriptions of the <varname>$basearch</varname> and <varname>$releasever</varname> Yum variables.
+ See <xref linkend="sec-Using_Yum_Variables" /> for descriptions of the <varname>$basearch</varname> and <varname>$releasever</varname> Yum variables.
</para>
</listitem>
</varlistentry>
@@ -1356,7 +1356,7 @@ 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>. Refer to 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>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.
</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.
@@ -1897,7 +1897,7 @@ enabled=1</programlisting>
</step>
</substeps>
<para>
- Refer to <xref linkend="tabl-Yum-Plugin_Descriptions-fs-snapshot" /> for a complete list of available configuration options.
+ See <xref linkend="tabl-Yum-Plugin_Descriptions-fs-snapshot" /> for a complete list of available configuration options.
</para>
</step>
<step>
@@ -2072,7 +2072,7 @@ enabled=1</programlisting>
The <application>kabi</application> plug-in checks whether a driver update package conforms with official &OSORG; <firstterm>kernel Application Binary Interface</firstterm> (<acronym>kABI</acronym>). With this plug-in enabled, when a user attempts to install a package that uses kernel symbols which are not on a whitelist, a warning message is written to the system log. Additionally, configuring the plug-in to run in enforcing mode prevents such packages from being installed at all.
</para>
<para>
- To configure the <application>kabi</application> plug-in, edit the configuration file located in <filename>/etc/yum/pluginconf.d/kabi.conf</filename>. Refer to <xref linkend="tabl-Yum-Plugin_Descriptions-kabi" /> for a list of directives that can be used in the <option>[main]</option> section.
+ To configure the <application>kabi</application> plug-in, edit the configuration file located in <filename>/etc/yum/pluginconf.d/kabi.conf</filename>. See <xref linkend="tabl-Yum-Plugin_Descriptions-kabi" /> for a list of directives that can be used in the <option>[main]</option> section.
</para>
<table id="tabl-Yum-Plugin_Descriptions-kabi">
<title>Supported <filename>kabi.conf</filename> directives</title>
@@ -2187,7 +2187,7 @@ enabled=1</programlisting>
The <application>rhnplugin</application> provides support for connecting to <systemitem class="systemname">RHN Classic</systemitem>. This allows systems registered with <systemitem class="systemname">RHN Classic</systemitem> to update and install packages from this system.
</para>
<para>
- Refer to the <emphasis role="bold">rhnplugin</emphasis>(8) manual page for more information about the plug-in.
+ See the <emphasis role="bold">rhnplugin</emphasis>(8) manual page for more information about the plug-in.
</para>
</listitem>
</varlistentry>
@@ -2246,7 +2246,7 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
...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.
</para>
<para>
- Refer to 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">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>.
</para>
</listitem>
</varlistentry>
More information about the docs-commits
mailing list