yum-software-management yum-software-management-en.xml,1.27,1.28
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Mon Jul 25 21:58:01 UTC 2005
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29204
Modified Files:
yum-software-management-en.xml
Log Message:
- Restructured "Understanding Package Names"
- Style fixes
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- yum-software-management-en.xml 25 Jul 2005 19:51:19 -0000 1.27
+++ yum-software-management-en.xml 25 Jul 2005 21:57:58 -0000 1.28
@@ -17,8 +17,8 @@
<article id="yum-software-management" lang="en">
<articleinfo>
- <title>Software Management with <command>yum</command> -
- <emphasis>BETA DOCUMENT</emphasis></title>
+ <title>Software Management with <command>yum</command> - <emphasis>BETA
+ DOCUMENT</emphasis></title>
<copyright>
<year>2005</year>
<holder>Stuart Ellis</holder>
@@ -52,14 +52,14 @@
</revdescription>
</revision>
<revision>
- <revnumber>0.6</revnumber>
- <date>2005-07-25</date>
- <authorinitials>PaulWFrields</authorinitials>
- <revdescription>
- <para>
- Edited for style and usage; BETA publication.
- </para>
- </revdescription>
+ <revnumber>0.6</revnumber>
+ <date>2005-07-25</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Edited for style and usage; BETA publication.
+ </para>
+ </revdescription>
</revision>
</revhistory>
</articleinfo>
@@ -166,6 +166,7 @@
<!-- use sentences, but rather headings, in the term area. Alternately, -->
<!-- if you like sentences, just use a para instead for the whole -->
<!-- collection of links. [PWF] -->
+<!-- SE: Multiple links in a paragraph is pretty ugly. Not that I like this layout either :) -->
<para>
Other useful <command>yum</command> resources on the Internet
include:
@@ -174,7 +175,7 @@
<variablelist>
<varlistentry>
<term>
- Web home page
+ Project web site
</term>
<listitem>
<para>
@@ -215,27 +216,27 @@
<title>About Packages</title>
<indexterm>
<primary>packages</primary>
- <secondary>defined</secondary>
+ <secondary>defined</secondary>
</indexterm>
<para>
&FED; software and documentation is supplied in the form of
- files called RPM <firstterm>packages</firstterm>. Each package
- is a compressed archive containing product information, program
- files, icons, documentation and management scripts. Management
- applications use these files to safely locate, install, update
- and remove software. For example, the &FED; installation process
- uses the packages supplied with &FC; to build or upgrade a
- system to your requirements.
+ files called RPM <firstterm>packages</firstterm>. Each package
+ is a compressed archive containing product information, program
+ files, icons, documentation and management scripts. Management
+ applications use these files to safely locate, install, update
+ and remove software. For example, the &FED; installation process
+ uses the packages supplied with &FC; to build or upgrade a
+ system to your requirements.
</para>
<para>
Packages also include a digital signature to prove their source.
- Software management utilities verify this digital signature by
- using a GPG <firstterm>public key</firstterm>. The
- <command>yum</command> and <command>rpm</command> utilities
- share a common <firstterm>keyring</firstterm> that stores all of
- the public keys for approved package sources. The system
- administrator configures these approved package sources.
+ Software management utilities verify this digital signature by
+ using a GPG <firstterm>public key</firstterm>. The
+ <command>yum</command> and <command>rpm</command> utilities
+ share a common <firstterm>keyring</firstterm> that stores all of
+ the public keys for approved package sources. The system
+ administrator configures these approved package sources.
</para>
</section>
@@ -243,7 +244,7 @@
<title>About Repositories</title>
<indexterm>
<primary>repositories</primary>
- <secondary>defined</secondary>
+ <secondary>defined</secondary>
</indexterm>
<para>
A <firstterm>repository</firstterm> is a prepared directory or
@@ -251,7 +252,7 @@
Software management utilities such as <command>yum</command>
automatically locate and obtain the correct RPM packages from
these repositories. This method frees you from having to
- manually find and install new applications or updates. You may
+ manually find and install new applications or updates. You may
use a single command to update all system software, or search
for new software by specifying criteria. In each case the
management utility connects to the configured repositories and
@@ -260,11 +261,11 @@
<para>
The package management utilities in &FC; are already configured
- to use the network of repositories maintained by the &FP;. These
- repositories contain the software included with &FC; and a large
- selection of additional software known as &FEX;. Third-party
- software developers also provide repositories for their &FED;
- compatible packages.
+ to use the network of repositories maintained by the &FP;. These
+ repositories contain the software included with &FC; and a large
+ selection of additional software known as &FEX;. Third-party
+ software developers also provide repositories for their &FED;
+ compatible packages.
</para>
<note>
@@ -272,19 +273,19 @@
<para>
All of the software provided by the &FP; is open source
- software. You may download and install software from the &FP;
- network of repositories on as many systems as desired.
+ software. You may download and install software from the &FP;
+ network of repositories on as many systems as desired.
</para>
</note>
<indexterm>
<primary>package groups</primary>
- <secondary>defined</secondary>
+ <secondary>defined</secondary>
</indexterm>
<para>
You may also use the <firstterm>package groups</firstterm>
- provided by the &FED; repositories to manage related packages as
- sets. Some third-party repositories add packages to these
- groups, or provide their packages as additional groups.
+ provided by the &FED; repositories to manage related packages as
+ sets. Some third-party repositories add packages to these
+ groups, or provide their packages as additional groups.
</para>
<!-- SE: Some repositories use groups and some don't: I've tried to put this nicely. -->
<!-- SE: Using the admonition for this is not optimal, it just doesn't fit anywhere else. -->
@@ -293,34 +294,34 @@
<para>
To view a list of all of the available package groups for your
- &FED; system, run the command <command>yum
- grouplist</command>.
+ &FED; system, run the command <command>su -c 'yum
+ grouplist'</command>.
</para>
</note>
-<!-- I removed the extra option tag above. I used to do the same thing -->
-<!-- and Karsten and Tammy both cautioned me against overtagging -->
-<!-- commands. [PWF] -->
+
<para>
Use repositories to ensure that you always receive current
- versions of software. If several versions of the same package
- are available, your management utility automatically selects the
- latest version.
+ versions of software. If several versions of the same package
+ are available, your management utility automatically selects the
+ latest version.
</para>
<caution>
- <title>Installing Software not from a Repository</title>
- <para>
- Install software using manual methods only when you are
- confident there is no repository which can currently provide
- it. You may have to manage that software with manual methods,
- instead of with &FED; software management utilities.
- </para>
+ <title>Installing Software not from a Repository</title>
+
+ <para>
+ Install software using manual methods only when you are
+ confident there is no repository which can currently provide
+ it. You may have to manage that software with manual methods,
+ instead of with &FED; software management utilities.
+ </para>
+
<para>
The <command>yum</command> commands shown in this document use
- repositories as package sources. Refer to
+ repositories as package sources. Refer to
<xref linkend="sn-yum-installing-frompackage"/> for details of
- using <command>yum</command> to install software from a
- package file.
+ using <command>yum</command> to install software from a
+ package file.
</para>
</caution>
</section>
@@ -329,60 +330,51 @@
<title>About Dependencies</title>
<indexterm>
<primary>dependencies</primary>
- <secondary>defined</secondary>
+ <secondary>defined</secondary>
</indexterm>
<para>
- Some of the files installed on a &FED; distribution are
- <firstterm>libraries</firstterm> which may provide functions to
- multiple applications. When an application requires a specific
- library, the package which contains that library is a
- <firstterm>dependency</firstterm>. To properly install a
- package, &FED; must first satisfy its dependencies. The
- dependency information for a RPM package is stored within the
- RPM file.
+ Some of the files installed on a &FED; distribution are
+ <firstterm>libraries</firstterm> which may provide functions to
+ multiple applications. When an application requires a specific
+ library, the package which contains that library is a
+ <firstterm>dependency</firstterm>. To properly install a
+ package, &FED; must first satisfy its dependencies. The
+ dependency information for a RPM package is stored within the
+ RPM file.
</para>
<para>
The <command>yum</command> utility uses package dependency data
- to ensure all its requirements are met during installation. The
- <command>yum</command> utility automatically installs packages
- for any required software not already present on your system. If
- a new application has requirements that conflict with existing
- software, <command>yum</command> aborts without making any
- changes to your system.
- </para>
-<!-- SE: Note that this is a generality: the behaviour described is -->
-<!-- standard for rpm, up2date etc.-->
-
-<!-- I totally understand; however, I've used yum specifically for two -->
-<!-- reasons: (1) Even though this is a section about concepts, the -->
-<!-- tutorial is still about yum; and more importantly, (2) the -->
-<!-- continual use of "Software management tools such as yum" was -->
-<!-- becoming redundant and unwieldy, and would force us to use very -->
-<!-- awkward sentence structures. -->
-
+ to ensure that all of requirements for an application are met
+ during installation. It automatically installs the packages for
+ any dependencies not already present on your system. If a new
+ application has requirements that conflict with existing
+ software, <command>yum</command> aborts without making any
+ changes to your system.
+ </para>
</section>
<section id="sn-package-names">
<title>Understanding Package Names</title>
<indexterm>
<primary>packages</primary>
- <secondary>hardware compatibility</secondary>
+ <secondary>hardware compatibility</secondary>
</indexterm>
<indexterm>
<primary>packages</primary>
- <secondary>naming</secondary>
+ <secondary>naming</secondary>
</indexterm>
<para>
Each package file has a long name that indicates several key
- pieces of information. This is the full name of the
- <filename>tsclient</filename> package supplied with &FC;:
+ pieces of information. This is the full name of the
+ <filename>tsclient</filename> package supplied with &FC;:
</para>
<screen>
<filename>tsclient-0.132-4.i386.rpm</filename>
</screen>
<para>
- These naming conventions are valid for the file shown above:
+ Management utilities refer to packages with one of three
+ formats:
</para>
<itemizedlist>
@@ -394,7 +386,7 @@
<listitem>
<para>
Package name with version and release numbers:
- <filename>tsclient-0.132-4</filename>
+ <filename>tsclient-0.132-4</filename>
</para>
<!-- In what instances is the release number not needed? For many -->
<!-- package updates, only the release number might change. Although it -->
@@ -403,50 +395,111 @@
<listitem>
<para>
Package name with hardware architecture:
- <filename>tsclient.i386</filename>
+ <filename>tsclient.i386</filename>
</para>
</listitem>
</itemizedlist>
-
- <para>
- Use only the name of the package with <command>yum</command>,
- except when the exact version or type is necessary. <remark
- role="fixme">When exactly is that required? I fixed the
- sentence structure but the meaning is obscure here. Tell the
- reader the full story here. [PWF]</remark> For example, use
- <filename>name-version</filename> to specify the exact version
- of the application. The package listings provided by
- <command>yum</command> use the format
- <filename>name.architecture</filename> to specify the type of
- computer for which the package is intended.
- </para>
-
<!-- I'm not sure we need any of this information on architecture. How -->
<!-- exactly does this help a yum user? Note that I'm not being snide, -->
<!-- I'm pointing out that unless this is hooked to a specific -->
<!-- procedure, it's out of place in a tutorial. [PWF] -->
-
<para>
- The hardware architecture is the <emphasis>minimum</emphasis>
- type of machine required for that specific package. Packages
- with architecture <option>i386</option> run on any current
- Intel-compatible computer. Packages for PowerPC systems, such as
- Apple Power Macintosh, are indicated with <option>ppc</option>.
- Packages for systems with 64-bit processors such as Opterons are
- indicated with <option>x86_64</option>. Packages specified as
- <option>noarch</option> have no architecture requirement.
+ For clarity, <command>yum</command> itself lists packages in the
+ format <filename>name.architecture</filename>. Repositories also
+ commonly store packages in separate directories by architecture.
+ In each case, the hardware architecture specified for the
+ package is the <emphasis>minimum</emphasis> type of machine
+ required to use the package.
</para>
+ <variablelist>
+ <varlistentry>
+ <term>
+ i386
+ </term>
+ <listitem>
+ <para>
+ Suitable for any current Intel-compatible computer
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ noarch
+ </term>
+ <listitem>
+ <para>
+ Compatible with all computer architectures
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ ppc
+ </term>
+ <listitem>
+ <para>
+ Suitable for PowerPC systems, such as Apple Power
+ Macintosh
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ x86_64
+ </term>
+ <listitem>
+ <para>
+ Suitable for 64-bit Intel-compatible processors, such as
+ Opterons
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
<para>
Some software may be optimized for particular types of
- Intel-compatible machine. Separate packages may be provided for
- <option>i386</option>, <option>i586</option>,
- <option>i686</option> and <option>x86_64</option> computers. A
- machine with at least an Intel Pentium, VIA C3 or compatible CPU
- may use <option>i586</option> packages. Computers with an Intel
- Pentium Pro and above, or a current model of AMD chip, may use
- <option>i686</option> packages.
+ Intel-compatible machine. Separate packages may be provided for
+ <option>i386</option>, <option>i586</option>,
+ <option>i686</option> and <option>x86_64</option> computers. A
+ machine with at least an Intel Pentium, VIA C3 or compatible CPU
+ may use <option>i586</option> packages. Computers with an Intel
+ Pentium Pro and above, or a current model of AMD chip, may use
+ <option>i686</option> packages.
</para>
+
+ <para>
+ Use the short name of the package for <command>yum</command>
+ commands. This causes <command>yum</command> to automatically
+ select the most recent package in the repositories that matches
+ the hardware architecture of your computer.
+ </para>
+
+ <para>
+ Specify a package with other name formats to override the
+ default behavior and force <command>yum</command> to use the
+ package that matches that version or architecture. Only override
+ <command>yum</command> when you know that the default package
+ selection has a bug or other fault that makes it unsuitable for
+ installation.
+ </para>
+ <tip>
+ <title>Package Names</title>
+ <para>
+ You may use any of the following formats to specify a package
+ in a <command>yum</command> operation:
+ <replaceable>name</replaceable>,
+ <replaceable>name.architecture</replaceable>,
+ <replaceable>name-version</replaceable>,
+ <replaceable>name-version-release</replaceable>,
+ <replaceable>name-version-release.architecture</replaceable>,
+ and
+ <replaceable>epoch:name-version-release.architecture</replaceable>.
+ </para>
+ </tip>
</section>
</section>
@@ -479,13 +532,11 @@
<para>
&FC; also includes
<application>system-config-packages</application>. To run this
- application from the graphical interface, select
- <menuchoice>
- <guimenu>Desktop</guimenu>
- <guisubmenu>System Settings</guisubmenu>
- <guimenuitem>Add/Remove Applications</guimenuitem>
- </menuchoice>. Unlike <application>up2date</application> and
- <command>yum</command>,
+ application from the graphical interface, select <menuchoice>
+ <guimenu>Desktop</guimenu> <guisubmenu>System
+ Settings</guisubmenu> <guimenuitem>Add/Remove
+ Applications</guimenuitem> </menuchoice>. Unlike
+ <application>up2date</application> and <command>yum</command>,
<application>system-config-packages</application> installs
software packages from your &FC; installation discs only, and does
not use repositories. This application is used on systems that do
@@ -507,9 +558,9 @@
<para>
The <application>up2date</application> and
- <command>yum</command> utilities ensure that you have the most
- recent version of software packages. Other methods do not
- guarantee that the packages are current.
+ <command>yum</command> utilities ensure that you have the most
+ recent version of software packages. Other methods do not
+ guarantee that the packages are current.
</para>
</caution>
</section>
@@ -521,26 +572,25 @@
<secondary>software management</secondary>
</indexterm>
<para>
- The <command>yum</command> utility may modify the software on your
- system in three ways:
+ Use the <command>yum</command> utility to modify the software on
+ your system in three ways:
</para>
<para>
<itemizedlist>
<listitem>
<para>
- It may install new software from repositories or a package
- file.
+ To install new software from repositories or a package file
</para>
</listitem>
<listitem>
<para>
- It may update existing software on your system.
+ To update existing software on your system
</para>
</listitem>
<listitem>
<para>
- It may remove unwanted software from your system.
+ To remove unwanted software from your system
</para>
</listitem>
</itemizedlist>
@@ -551,23 +601,11 @@
packages or package groups. Each section below gives some
examples.
</para>
- <tip>
- <title>Package Names</title>
- <para>
- You may use any of the following formats to specify a package in
- a <command>yum</command> operation: <replaceable>name</replaceable>,
- <replaceable>name.architecture</replaceable>,
- <replaceable>name-version</replaceable>,
- <replaceable>name-version-release</replaceable>,
- <replaceable>name-version-release.architecture</replaceable>, and
- <replaceable>epoch:name-version-release.architecture</replaceable>.
- </para>
- </tip>
+
<para>
- To use the repositories <command>yum</command> downloads data
- files from each of the configured repositories. On a slow
- connection, it may take several seconds to download the required
- files for each package.
+ <command>yum</command> downloads data files from each of the
+ configured repositories. On a slow connection, it may take several
+ seconds to download the required files for each package.
</para>
<para>
@@ -581,9 +619,10 @@
<example id="yum-transaction-format">
<title>Format of <command>yum</command> Transaction Reports</title>
+
<para>
- This is an example of the transaction for installing
- <filename>tsclient</filename>:
+ This is an example of the transaction for installing
+ <filename>tsclient</filename>:
</para>
<screen>
<computeroutput>=============================================================================
@@ -605,10 +644,13 @@
</example>
<para>
- Review the list of changes, and then press <keycap>y</keycap> to
- accept and begin the process. If you press <keycap>N</keycap> or
- <keycap>Enter</keycap>, <command>yum</command> does not download
- or change any packages.
+ Review the list of changes, and then press
+ <keycap>y</keycap>
+ to accept and begin the process. If you press
+ <keycap>N</keycap>
+ or
+ <keycap>Enter</keycap>
+ , <command>yum</command> does not download or change any packages.
</para>
<note>
@@ -616,34 +658,34 @@
<para>
The <command>yum</command> utility only displays and uses the
- newest version of each package, unless you specify an older
- version.
+ newest version of each package, unless you specify an older
+ version.
</para>
</note>
<tip>
<title>Downloads are Cached</title>
<para>
The <command>yum</command> utility keeps Downloaded data files
- and packages for reuse. You may copy packages from the
- repository cache directories under
- <filename>/var/cache/yum/</filename>, and use them elsewhere if
- you wish. If you remove a package from the cache, you do not
- affect the copy of the software installed on your system.
+ and packages for reuse. You may copy packages from the
+ repository cache directories under
+ <filename>/var/cache/yum/</filename>, and use them elsewhere if
+ you wish. If you remove a package from the cache, you do not
+ affect the copy of the software installed on your system.
</para>
</tip>
<section id="sn-yum-installing-withrepositories">
<title>Installing New Software with <command>yum</command></title>
<indexterm>
- <primary>installing software</primary>
- <see>software, installing</see>
+ <primary>installing software</primary>
+ <see>software, installing</see>
</indexterm>
<indexterm>
<primary>software</primary>
- <secondary>installing</secondary>
+ <secondary>installing</secondary>
</indexterm>
<para>
To install the package <filename>tsclient</filename>, enter the
- command:
+ command:
</para>
<screen>
<userinput>su -c 'yum install <replaceable>tsclient</replaceable>'</userinput>
@@ -672,14 +714,12 @@
<para>
When you install a service, &FED; does not activate or start
- it. To configure a new service to run on bootup, choose
- <menuchoice>
- <guimenu>Desktop</guimenu>
- <guisubmenu>System Settings</guisubmenu>
- <guisubmenu>Server Settings</guisubmenu>
- <guimenuitem>Services</guimenuitem>
- </menuchoice>, or use the <command>chkconfig</command>
- and <command>service</command> command-line utilities.
+ it. To configure a new service to run on bootup, choose
+ <menuchoice> <guimenu>Desktop</guimenu> <guisubmenu>System
+ Settings</guisubmenu> <guisubmenu>Server Settings</guisubmenu>
+ <guimenuitem>Services</guimenuitem> </menuchoice>, or use the
+ <command>chkconfig</command> and <command>service</command>
+ command-line utilities.
</para>
</important>
</section>
@@ -687,12 +727,12 @@
<section id="sn-yum-updating-withrepositories">
<title>Updating Software with <command>yum</command></title>
<indexterm>
- <primary>updating</primary>
- <secondary>software packages</secondary>
+ <primary>updating</primary>
+ <secondary>software packages</secondary>
</indexterm>
<indexterm>
<primary>software</primary>
- <secondary>updating</secondary>
+ <secondary>updating</secondary>
</indexterm>
<para>
To update the <filename>tsclient</filename> package to the
@@ -712,8 +752,8 @@
<para>
If a piece of software is in use when you update it, the old
- version remains active until the software is restarted. Kernel
- updates take effect when you reboot the system.
+ version remains active until the software is restarted. Kernel
+ updates take effect when you reboot the system.
</para>
</important>
@@ -735,7 +775,7 @@
<para>
To update all of the packages on your &FED; system, use the
- commands described in
+ commands described in
<xref
linkend="sn-updating-your-system"/>.
</para>
@@ -749,7 +789,7 @@
</indexterm>
<indexterm>
<primary>software</primary>
- <secondary>removing</secondary>
+ <secondary>removing</secondary>
</indexterm>
<para>
To remove software, <command>yum</command> examines your system
@@ -807,9 +847,9 @@
<para>
The <option>search</option> and <option>list</option> options of
- <command>yum</command> are not case-sensitive. A query for
- <filename>palmpilot</filename> automatically finds
- <filename>PalmPilot</filename> packages.
+ <command>yum</command> are not case-sensitive. A query for
+ <filename>palmpilot</filename> automatically finds
+ <filename>PalmPilot</filename> packages.
</para>
</note>
@@ -824,8 +864,8 @@
<para>
To search for a specific package by name, use the
- <option>list</option> function. To search for the package
- <filename>tsclient</filename>, use the command:
+ <option>list</option> function. To search for the package
+ <filename>tsclient</filename>, use the command:
</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsclient</replaceable>'</userinput>
@@ -838,8 +878,8 @@
<para>
To make your queries more specific, add other package
- attributes. To search for version 0.132 of the application, use
- the command:
+ attributes. To search for version 0.132 of the application, use
+ the command:
</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsclient-0.132</replaceable>'</userinput>
@@ -856,9 +896,9 @@
<para>
The <option>search</option> option checks the names,
- descriptions, summaries and listed package maintainers of all of
- the available packages to find those that match. For example, to
- search for all packages that relate to PalmPilots, type:
+ descriptions, summaries and listed package maintainers of all of
+ the available packages to find those that match. For example, to
+ search for all packages that relate to PalmPilots, type:
</para>
<screen>
<userinput>su -c 'yum search <replaceable>PalmPilot</replaceable>'</userinput>
@@ -886,8 +926,8 @@
</screen>
<para>
To search for all packages that either provide a MTA (Mail
- Transport Agent) service, or include files with
- <filename>mta</filename> in their name:
+ Transport Agent) service, or include files with
+ <filename>mta</filename> in their name:
</para>
<screen>
<userinput>su -c 'yum provides <replaceable>MTA</replaceable>'</userinput>
@@ -900,10 +940,10 @@
<title>Wildcards and Regular Expressions</title>
<para>
You may use the standard wildcard characters in search
- criteria: <option>?</option> to represent any one character,
- and <option>*</option> to mean zero or more characters. Use
- Perl or Python regular expressions to carry out more complex
- queries.
+ criteria: <option>?</option> to represent any one character,
+ and <option>*</option> to mean zero or more characters. Use
+ Perl or Python regular expressions to carry out more complex
+ queries.
</para>
</tip>
</section>
@@ -913,18 +953,18 @@
<para>
Searches with <command>yum</command> show all of the packages
- that match your criteria. Packages must meet the terms of the
- search exactly to be considered matches, unless you use
- wildcards or a regular expression.
+ that match your criteria. Packages must meet the terms of the
+ search exactly to be considered matches, unless you use
+ wildcards or a regular expression.
</para>
<para>
For example, a search query for <filename>shadowutils</filename>
- or <filename>shadow-util</filename> would not produce the
- package <filename>shadow-utils</filename>. This package would
- match and be shown if the query was either
- <filename>shadow-util?</filename> or
- <filename>Shadow*</filename>.
+ or <filename>shadow-util</filename> would not produce the
+ package <filename>shadow-utils</filename>. This package would
+ match and be shown if the query was either
+ <filename>shadow-util?</filename> or
+ <filename>Shadow*</filename>.
</para>
</section>
</section>
@@ -951,7 +991,8 @@
<userinput>su -c 'yum update'</userinput>
</screen>
<para>
- At the prompt, enter the <systemitem
+ At the prompt, enter the
+ <systemitem
class="username">root</systemitem> password.
</para>
@@ -962,8 +1003,8 @@
</indexterm>
<para>
The <filename>yum</filename> package supplied with &FC; includes
- scripts to perform full system updates every day. To activate
- automatic daily updates, enter this command:
+ scripts to perform full system updates every day. To activate
+ automatic daily updates, enter this command:
</para>
<screen>
<userinput>su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'</userinput>
@@ -978,12 +1019,12 @@
<para>
There is no separate <command>yum</command> service that runs
- on your system. The command given above enables the control
- script <filename>/etc/rc.d/init.d/yum</filename>. This control
- script activates the script
- <filename>/etc/cron.daily/yum.cron</filename>, which causes
- the <command>cron</command> service to perform the system
- update automatically each day.
+ on your system. The command given above enables the control
+ script <filename>/etc/rc.d/init.d/yum</filename>. This control
+ script activates the script
+ <filename>/etc/cron.daily/yum.cron</filename>, which causes
+ the <command>cron</command> service to perform the system
+ update automatically each day.
</para>
</note>
</section>
@@ -1013,9 +1054,11 @@
<para>
You must manually configure &FED; 3 systems to use &FEX;, using
- the instructions at <ulink
+ the instructions at
+ <ulink
url="http://fedora.redhat.com/projects/extras/"/>. For
- additional packages for &FED; 1 and &FED; 2, refer to <ulink
+ additional packages for &FED; 1 and &FED; 2, refer to
+ <ulink
url="http://www.fedora.us/"/>.
</para>
</note>
@@ -1032,7 +1075,7 @@
<title>Adding a Repository as a Package Source</title>
<indexterm>
<primary>repositories</primary>
- <secondary>adding to yum</secondary>
+ <secondary>adding to yum</secondary>
</indexterm>
<para>
To add an extra repository, place a definition file in the
@@ -1049,9 +1092,9 @@
</tip>
<para>
You must have <systemitem class="username">root</systemitem>
- access to add a file to the definitions directory. To copy the
- definition file <filename>example.repo</filename>, type this
- command:
+ access to add a file to the definitions directory. To copy the
+ definition file <filename>example.repo</filename>, type this
+ command:
</para>
<screen>
<userinput>su -c 'cp example.repo /etc/yum.repos.d/'</userinput>
@@ -1063,12 +1106,12 @@
<para>
The configuration file for each repository should include a
- <command>gpgkey</command> setting. This setting specifies the
- location of a public key that verifies the packages provided by
- that repository. This public key is automatically imported the
- first time you install software from the repository. If the
- configuration file provided does not include this setting, refer
- to <xref linkend="sn-authorizing-package-sources"/>.
+ <command>gpgkey</command> setting. This setting specifies the
+ location of a public key that verifies the packages provided by
+ that repository. This public key is automatically imported the
+ first time you install software from the repository. If the
+ configuration file provided does not include this setting, refer
+ to <xref linkend="sn-authorizing-package-sources"/>.
</para>
<note>
@@ -1076,11 +1119,11 @@
<para>
Starting with &FED; 4, <command>yum</command> repositories are
- automatically used as <application>up2date</application>
- channels. On &FED; 3 and earlier systems, you must manually
- configure <application>up2date</application> to use these
- channels. To do so, edit the
- <filename>/etc/sysconfig/rhn/sources</filename> file.
+ automatically used as <application>up2date</application>
+ channels. On &FED; 3 and earlier systems, you must manually
+ configure <application>up2date</application> to use these
+ channels. To do so, edit the
+ <filename>/etc/sysconfig/rhn/sources</filename> file.
</para>
</note>
</section>
@@ -1089,14 +1132,14 @@
<title>Manually Authorizing Package Sources</title>
<indexterm>
<primary>public keys</primary>
- <secondary>adding</secondary>
+ <secondary>adding</secondary>
</indexterm>
<para>
To manually add a public key to your <command>rpm</command>
- keyring, use the <option>import</option> feature of the
- <command>rpm</command> utility. To import the file
- <filename>GPG-PUB-KEY.asc</filename>, type the following
- command:
+ keyring, use the <option>import</option> feature of the
+ <command>rpm</command> utility. To import the file
+ <filename>GPG-PUB-KEY.asc</filename>, type the following
+ command:
</para>
<screen>
<userinput>su -c 'rpm --import <replaceable>GPG-PUB-KEY.asc</replaceable>'</userinput>
@@ -1121,46 +1164,46 @@
<title>Understanding Repository Compatibility</title>
<indexterm>
<primary>packages</primary>
- <secondary>software compatibility</secondary>
+ <secondary>software compatibility</secondary>
</indexterm>
<indexterm>
<primary>repositories</primary>
- <secondary>compatibility</secondary>
+ <secondary>compatibility</secondary>
</indexterm>
<para>
The &FEX; project provides packages which are built to the same
- standards as &FC; packages. Third-party packages should be
- compatible with these official packages, unless the provider
- specifically states otherwise.
+ standards as &FC; packages. Third-party packages should be
+ compatible with these official packages, unless the provider
+ specifically states otherwise.
</para>
<para>
Refer to the web site of the repository for information on
- package compatibility before you add it as a package source.
- Repositories often provide packages specifically intended for
- use with packages supplied by other repositories. In some cases,
- separate third-party repository providers may each offer
- different versions of the same software. This situation may
- prevent you from safely using those repositories together on
- your &FED; system.
+ package compatibility before you add it as a package source.
+ Repositories often provide packages specifically intended for
+ use with packages supplied by other repositories. In some cases,
+ separate third-party repository providers may each offer
+ different versions of the same software. This situation may
+ prevent you from safely using those repositories together on
+ your &FED; system.
</para>
<para>
Packages built for one version of &FED; are usually not
- compatible with other versions of &FED;. The web site of the
- provider should specifically state which versions of &FED; they
- support.
+ compatible with other versions of &FED;. The web site of the
+ provider should specifically state which versions of &FED; they
+ support.
</para>
<tip>
<title>Old Versions of <command>yum</command> and Current Repositories</title>
<para>
The data format for repository indexes changed with version
- 2.1 of <command>yum</command>. This was the version supplied
- with &FED; 3. Repository providers should specify the versions
- of &FED; that they support. To confirm that an unlabeled
- repository is compatible with current versions of
- <command>yum</command>, check that it has a sub-directory
- called <filename>repodata/</filename>.
+ 2.1 of <command>yum</command>. This was the version supplied
+ with &FED; 3. Repository providers should specify the versions
+ of &FED; that they support. To confirm that an unlabeled
+ repository is compatible with current versions of
+ <command>yum</command>, check that it has a sub-directory
+ called <filename>repodata/</filename>.
</para>
</tip>
</section>
@@ -1182,17 +1225,17 @@
<title>Disabling or Removing Package Sources</title>
<indexterm>
<primary>repositories</primary>
- <secondary>disabling in yum</secondary>
+ <secondary>disabling in yum</secondary>
</indexterm>
<indexterm>
<primary>repositories</primary>
- <secondary>removing from yum</secondary>
+ <secondary>removing from yum</secondary>
</indexterm>
<para>
Set <command>enable=0</command> in a definition file to prevent
- <command>yum</command> from using that repository. The
- <command>yum</command> utility ignores any definition file with
- this setting.
+ <command>yum</command> from using that repository. The
+ <command>yum</command> utility ignores any definition file with
+ this setting.
</para>
<para>
@@ -1202,17 +1245,16 @@
<step>
<para>
Delete the relevant file from
- <filename>/etc/yum.repos.d/</filename>.
+ <filename>/etc/yum.repos.d/</filename>.
</para>
</step>
<step>
<para>
Delete the cache directory from
- <filename>/var/cache/yum/</filename>.
+ <filename>/var/cache/yum/</filename>.
</para>
</step>
</procedure>
-
<!-- What with the "web of trust," removing GPG keys is not really -->
<!-- something we should encourage. Having an extra GPG key in the RPM -->
<!-- database is not a vulnerability, nor does it hamper the system in -->
@@ -1221,7 +1263,6 @@
<!-- we just had several admonitions against people running the rpm -->
<!-- command on its own anyway, I would just omit this part -->
<!-- completely. [PWF] -->
-
<!--
<important>
@@ -1295,20 +1336,19 @@
</para>
-->
-
</section>
<section id="sn-yum-clearance">
<title>Clearing the <command>yum</command> Caches</title>
<indexterm>
<primary>yum</primary>
- <secondary>cleaning caches</secondary>
+ <secondary>cleaning caches</secondary>
</indexterm>
<para>
By design, <command>yum</command> does not automatically delete
- any of the packages or package data files it downloads, so they
- may be reused in future operations. To purge the header files,
- use this command:
+ any of the packages or package data files it downloads, so they
+ may be reused in future operations. To purge the header files,
+ use this command:
</para>
<screen>
<userinput>su -c 'yum clean headers'</userinput>
@@ -1322,7 +1362,7 @@
</screen>
<para>
When using these commands, at the prompt, enter the password for
- the <systemitem class="username">root</systemitem> account.
+ the <systemitem class="username">root</systemitem> account.
</para>
<note>
@@ -1330,8 +1370,8 @@
<para>
Package management operations download header files and
- packages as required, and automatically replace any deleted
- files needed for the operation.
+ packages as required, and automatically replace any deleted
+ files needed for the operation.
</para>
</note>
</section>
@@ -1377,7 +1417,8 @@
<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
</screen>
<para>
- At the prompt, enter the <systemitem
+ At the prompt, enter the
+ <systemitem
class="username">root</systemitem> password.
</para>
@@ -1409,18 +1450,19 @@
<filename>/etc/yum.conf</filename>. The <option>proxy</option>
setting must specify the proxy server as a complete URL, including
the TCP port number. If your proxy server requires a username and
- password, specify these by adding
- <option>proxy_username</option> and
- <option>proxy_password</option> settings.
+ password, specify these by adding <option>proxy_username</option>
+ and <option>proxy_password</option> settings.
</para>
<para>
The settings below enable <command>yum</command> to use the proxy
- server <systemitem
- class="systemname">mycache.mydomain.com</systemitem>, connecting
- to port 3128, with the username <systemitem
- class="username">yum-user</systemitem> and the password
- <systemitem>qwerty</systemitem>.
+ server
+ <systemitem
+ class="systemname">mycache.mydomain.com</systemitem>,
+ connecting to port 3128, with the username
+ <systemitem
+ class="username">yum-user</systemitem> and the
+ password <systemitem>qwerty</systemitem>.
</para>
<example id="config-file-httpproxy">
@@ -1439,9 +1481,9 @@
<para>
If you define a proxy server in
- <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis>
- users connect to the proxy server with those details when using
- <command>yum</command>.
+ <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis>
+ users connect to the proxy server with those details when using
+ <command>yum</command>.
</para>
</note>
@@ -1450,9 +1492,10 @@
example box below to the user's shell profile. For the default
<command>bash</command> shell, the profile is the file
<filename>~/.bash_profile</filename>. The settings below enable
- <command>yum</command> to use the proxy server <systemitem
- class="systemname">mycache.mydomain.com</systemitem>, connecting
- to port 3128.
+ <command>yum</command> to use the proxy server
+ <systemitem
+ class="systemname">mycache.mydomain.com</systemitem>,
+ connecting to port 3128.
</para>
<example id="profile-script-httpproxy">
@@ -1467,8 +1510,8 @@
<para>
If the proxy server requires a username and password, add these to
the URL. To include the username
- <systemitem class="username">yum-user</systemitem> and the password
- <systemitem>qwerty</systemitem>, add these settings:
+ <systemitem class="username">yum-user</systemitem> and the
+ password <systemitem>qwerty</systemitem>, add these settings:
</para>
<example id="profile-script-httpproxy-withpassword">
@@ -1481,16 +1524,15 @@
</example>
<note>
- <title>The <option>http_proxy</option> Environment
- Variable</title>
+ <title>The <option>http_proxy</option> Environment Variable</title>
<para>
The <command>http_proxy</command> environment variable is also
- used by <command>curl</command> and other utilities. Although
- <command>yum</command> itself may use
- <command>http_proxy</command> in either upper-case or
- lower-case, <command>curl</command> requires the name of the
- variable to be in lower-case.
+ used by <command>curl</command> and other utilities. Although
+ <command>yum</command> itself may use
+ <command>http_proxy</command> in either upper-case or
+ lower-case, <command>curl</command> requires the name of the
+ variable to be in lower-case.
</para>
</note>
</section>
More information about the Fedora-docs-commits
mailing list