yum-software-management/en_US introduction.xml, 1.3, 1.4 concepts.xml, 1.7, 1.8 tools.xml, 1.2, 1.3 manage-with-yum.xml, 1.2, 1.3 search-with-yum.xml, 1.2, 1.3
Jared Smith (jsmith)
fedora-docs-commits at redhat.com
Thu Jan 24 01:48:03 UTC 2008
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22777
Modified Files:
introduction.xml concepts.xml tools.xml manage-with-yum.xml
search-with-yum.xml
Log Message:
Checking in another round of changes, mostly replacing <code> and <emphasis> tags
with their proper (more precise!) replacements.
Index: introduction.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/introduction.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- introduction.xml 23 Jan 2008 19:06:48 -0000 1.3
+++ introduction.xml 24 Jan 2008 01:48:01 -0000 1.4
@@ -29,7 +29,7 @@
installation of Fedora which includes the desktop components. The
reader has a user account with the default settings. The reader
<emphasis role="strong">does</emphasis> have access to the
- <emphasis>root</emphasis> password. The user does not have a degree
+ <systemitem class="username">root</systemitem> password. The user does not have a degree
in Computer Science.</para>
</section>
<section id="sn-UsingDocument">
@@ -70,10 +70,10 @@
<warning>
<title>Warning: Avoid Logging in with the Root Account</title>
<para>You do not need to log in with the
- <code>root</code> account in order to manage your Fedora system.
+ <systemitem class="username">root</systemitem> account in order to manage your Fedora system.
All of the commands shown in this tutorial that require
- <code>root</code> access will prompt you for the
- <code>root</code> password. The example terminal commands use
+ <systemitem class="username">root</systemitem> access will prompt you for the
+ <systemitem class="username">root</systemitem> password. The example terminal commands use
<command>su -c</command> to provide this facility. Graphical
applications that require root access will automatically prompt
for the root password when launched.</para>
Index: concepts.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/concepts.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- concepts.xml 23 Jan 2008 19:06:48 -0000 1.7
+++ concepts.xml 24 Jan 2008 01:48:01 -0000 1.8
@@ -1,197 +1,228 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
+<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: -->
-
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
+[
<!-- *************** COMMON FDP entities *************** -->
<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
%FDP-ENTITIES;
]>
- <section id="sn-Concepts">
- <title>Software Management Concepts</title>
+<section id="sn-Concepts">
+ <title>Software Management Concepts</title>
<section id="sn-AboutPackages">
<title>About Packages</title>
<para>Fedora 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 Fedora installation process uses
- the packages supplied with Fedora to build or upgrade a system to
- your requirements. </para>
+ 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 Fedora installation process uses the packages
+ supplied with Fedora 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. </para>
+ 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.</para>
<note>
<title>All Fedora Packages are Free and Open Source
- Software</title>
- <para> All of the software provided by the Fedora Project is Free
- and open source software. You may download and install Fedora
- packages on as many systems as desired. </para>
+ Software</title>
+ <para>All of the software provided by the Fedora Project is Free
+ and open source software. You may download and install Fedora
+ packages on as many systems as desired.</para>
</note>
</section>
<section id="sn-AboutRepositories">
<title>About Repositories</title>
- <para>A <firstterm>repository</firstterm> is a prepared directory or
- Web site that contains software packages and index files. Software
- management utilities such as <package>yum</package> 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 use a single command to update
- all system software, or search for new software by specifying
- criteria. </para>
+ <para>A
+ <firstterm>repository</firstterm>is a prepared directory or Web
+ site that contains software packages and index files. Software
+ management utilities such as
+ <package>yum</package>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 use a single command to update all system software, or
+ search for new software by specifying criteria.</para>
<para>A network of servers provide several repositories for each
- version of Fedora. The package management utilities in Fedora are
- already configured to use three of these repositories: </para>
- <para>Base </para>
+ version of Fedora. The package management utilities in Fedora are
+ already configured to use three of these repositories:</para>
+ <para>Base</para>
<itemizedlist>
- <listitem><para>The packages that make up a Fedora release, as it
- is on disc </para></listitem>
+ <listitem>
+ <para>The packages that make up a Fedora release, as it is on
+ disc</para>
+ </listitem>
</itemizedlist>
- <para>Updates </para>
+ <para>Updates</para>
<itemizedlist>
- <listitem><para>Updated versions of packages that are provided in
- Base </para></listitem>
+ <listitem>
+ <para>Updated versions of packages that are provided in
+ Base</para>
+ </listitem>
</itemizedlist>
- <para>Extras </para>
+ <para>Extras</para>
<itemizedlist>
- <listitem><para>Packages for a large selection of additional
- software </para></listitem>
+ <listitem>
+ <para>Packages for a large selection of additional
+ software</para>
+ </listitem>
</itemizedlist>
<warning>
<title>Fedora Development Repositories</title>
- <para> Fedora also includes settings for several alternative
- repositories. These provide packages for various types of test
- system, and replace one or more of the standard repositories.
- Only enable support for one of the following repositories if you
- test or develop Fedora software: <systemitem>fedora-devel</systemitem>
- (Rawhide), <systemitem>fedora-extras-devel</systemitem>, and
- <systemitem>updates-testing</systemitem>. </para>
+ <para>Fedora also includes settings for several alternative
+ repositories. These provide packages for various types of test
+ system, and replace one or more of the standard repositories.
+ Only enable support for one of the following repositories if you
+ test or develop Fedora software:
+ <systemitem>fedora-devel</systemitem>(Rawhide),
+ <systemitem>fedora-extras-devel</systemitem>, and
+ <systemitem>updates-testing</systemitem>.</para>
</warning>
<para>Third-party software developers also provide repositories for
- their Fedora compatible packages. To learn how to configure your
- Fedora system to use third-party repositories, read <xref
- linkend="sn-ConfiguringRepositories"/>. </para>
- <para>You may also use the <firstterm>package groups</firstterm>
- provided by the Fedora repositories to manage related packages as
- sets. Some third-party repositories add packages to these groups,
- or provide their packages as additional groups. </para>
+ their Fedora compatible packages. To learn how to configure your
+ Fedora system to use third-party repositories, read
+ <xref linkend="sn-ConfiguringRepositories" />.</para>
+ <para>You may also use the
+ <firstterm>package groups</firstterm>provided by the Fedora
+ repositories to manage related packages as sets. Some third-party
+ repositories add packages to these groups, or provide their
+ packages as additional groups.</para>
<important>
<title>Available Package Groups</title>
- <para> To view a list of all of the available package groups for
- your Fedora system, run the command <command>su -c 'yum
- grouplist'</command>. </para>
+ <para>To view a list of all of the available package groups for
+ your Fedora system, run the command
+ <command>su -c 'yum grouplist'</command>.</para>
</important>
<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. </para>
+ versions of software. If several versions of the same package are
+ available, your management utility automatically selects the latest
+ version.</para>
<warning>
<title>Manually Installing Software</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 Fedora software management utilities. </para>
+ <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 Fedora software management utilities.</para>
</warning>
- <para>The <command>yum</command> commands shown in this document use
- repositories as package sources. Refer to <xref
- linkend="sn-IsolatedInstall"/> for details of using
- <command>yum</command> to install software from a package file. </para>
- <para/>
+ <para>The
+ <command>yum</command>commands shown in this document use
+ repositories as package sources. Refer to
+ <xref linkend="sn-IsolatedInstall" />for details of using
+ <command>yum</command>to install software from a package
+ file.</para>
+ <para />
</section>
<section id="sn-AboutDependencies">
<title>About Dependencies</title>
- <para>Some of the files installed on a Fedora distribution are <emphasis>libraries</emphasis> which may provide functions to multiple applications. When an application requires a specific library, the package which contains that library is a <emphasis>dependency</emphasis>. To properly install a package, Fedora must first satisfy its dependencies. The dependency information for a RPM package is stored within the RPM file. </para>
- <para>The <code>yum</code> utility uses package dependency data 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, <code>yum</code> aborts without making any changes to your system. </para>
+ <para>Some of the files installed on a Fedora 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,
+ Fedora must first satisfy its dependencies. The dependency
+ information for a RPM package is stored within the RPM file.</para>
+ <para>The
+ <application>yum</application>utility uses package dependency data
+ 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,
+ <application>yum</application>aborts without making any changes to
+ your system.</para>
</section>
<section id="sn-UnderstandingPackageNames">
<title>Understanding Package Names</title>
<para>Each package file has a long name that indicates several key
- pieces of information. For example, this is the full name of a
- <package>tsclient</package> package: </para>
+ pieces of information. For example, this is the full name of a
+ <package>tsclient</package>package:</para>
<para>
<filename>tsclient-0.132-6.i386.rpm</filename>
</para>
<para>Management utilities commonly refer to packages with one of
- three formats: </para>
+ three formats:</para>
<itemizedlist>
<listitem>
- <para>Package name: <package>tsclient</package> </para>
+ <para>Package name:
+ <package>tsclient</package></para>
</listitem>
<listitem>
- <para>Package name with version and release numbers:
- <package>tsclient-0.132-6</package> </para>
+ <para>Package name with version and release numbers:
+ <package>tsclient-0.132-6</package></para>
</listitem>
<listitem>
- <para>Package name with hardware architecture:
- <package>tsclient.i386</package> </para>
+ <para>Package name with hardware architecture:
+ <package>tsclient.i386</package></para>
</listitem>
</itemizedlist>
- <para>For clarity, <command>yum</command> lists packages in the
- format <package>name.architecture</package>. 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>
+ <para>For clarity,
+ <command>yum</command>lists packages in the format
+ <package>name.architecture</package>. 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>
<segmentedlist>
<segtitle>Architecture</segtitle>
<segtitle>Compatibility</segtitle>
<seglistitem>
- <seg>i386</seg>
- <seg>Suitable for any current Intel-compatible computer</seg>
+ <seg>i386</seg>
+ <seg>Suitable for any current Intel-compatible computer</seg>
</seglistitem>
<seglistitem>
- <seg>noarch </seg>
- <seg>Compatible with all computer architectures
- </seg>
+ <seg>noarch</seg>
+ <seg>Compatible with all computer architectures</seg>
</seglistitem>
<seglistitem>
- <seg>ppc </seg>
- <seg>Suitable for PowerPC systems, such as Apple Power Macintosh
- </seg>
+ <seg>ppc</seg>
+ <seg>Suitable for PowerPC systems, such as Apple Power
+ Macintosh</seg>
</seglistitem>
<seglistitem>
- <seg>x86_64 </seg>
- <seg>Suitable for 64-bit Intel-compatible processors, such as
- Opterons </seg>
+ <seg>x86_64</seg>
+ <seg>Suitable for 64-bit Intel-compatible processors, such as
+ Opterons</seg>
</seglistitem>
</segmentedlist>
<para>Some software may be optimized for particular types of
- Intel-compatible machine. Separate packages may be provided for
- <systemitem>i386</systemitem>, <systemitem>i586</systemitem>,
- <systemitem>i686</systemitem> and
- <systemitem>x86_64</systemitem> computers. A machine with at
- least an Intel Pentium, VIA C3 or compatible CPU may use
- <systemitem>i586</systemitem> packages. Computers with an Intel
- Pentium Pro and above, or a current model of AMD chip, may use
- <systemitem>i686</systemitem> 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>
+ Intel-compatible machine. Separate packages may be provided for
+ <systemitem>i386</systemitem>,
+ <systemitem>i586</systemitem>,
+ <systemitem>i686</systemitem>and
+ <systemitem>x86_64</systemitem>computers. A machine with at least
+ an Intel Pentium, VIA C3 or compatible CPU may use
+ <systemitem>i586</systemitem>packages. Computers with an Intel
+ Pentium Pro and above, or a current model of AMD chip, may use
+ <systemitem>i686</systemitem>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>
+ 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>
<important>
<title>Package Names</title>
- <para> You may use any of the following formats to specify a
- package in a <command>yum</command> operation:
- <package>name</package>, <package>name.architecture</package>,
- <package>name-version</package>,
- <package>name-version-release</package>,
- <package>name-version-release.architecture</package>, and
- <package>epoch:name-version-release.architecture</package>.
- </para>
+ <para>You may use any of the following formats to specify a
+ package in a
+ <command>yum</command>operation:
+ <package>name</package>,
+ <package>name.architecture</package>,
+ <package>name-version</package>,
+ <package>name-version-release</package>,
+ <package>name-version-release.architecture</package>, and
+ <package>
+ epoch:name-version-release.architecture</package>.</para>
</important>
</section>
</section>
Index: tools.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/tools.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tools.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ tools.xml 24 Jan 2008 01:48:01 -0000 1.3
@@ -13,49 +13,49 @@
<section id="sn-Tools">
<title>Software Management Tools in Fedora</title>
<para>The
- <code>yum</code>command-line utility is a complete software
+ <application>yum</application> command-line utility is a complete software
management system. Fedora also includes two graphical applications
for software management that use
- <code>yum</code>. The
- <emphasis role="strong">pup</emphasis>utility provides an interface
+ <application>yum</application>. The
+ <application>pup</application> utility provides an interface
for updating software, and the
- <emphasis role="strong">pirut</emphasis>application enables you to
+ <application>pirut</application> application enables you to
add or remove software.</para>
<para>Both graphical tools appear in the
- <emphasis>Applications</emphasis>desktop menu. To update your system
+ <guimenu>Applications</guimenu> desktop menu. To update your system
with
- <emphasis role="strong">pup</emphasis>, select
- <emphasis>Applications → System Tools → Software
- Updater</emphasis>. To add or remove software with
- <emphasis role="strong">pirut</emphasis>, select
- <emphasis>Applications → Add/Remove Software</emphasis>.</para>
+ <application>pup</application>, select
+ <guimenu>Applications</guimenu> <guisubmenu>System Tools</guisubmenu>
+ <guimenuitem>Software Updater</guimenuitem>. To add or remove software with
+ <application>pirut</application>, select <guimenu>Applications</guimenu>
+ <guimenuitem>Add/Remove Software</guimenuitem>.</para>
<warning>
<title>Root Access Needed</title>
<para>When using
- <emphasis role="strong">pup</emphasis>or
- <emphasis role="strong">pirut</emphasis>you will be asked for the
- root password when starting these programs.</para>
+ <application>pup</application> or
+ <application>pirut</application> you will be asked for the
+ <systemitem class="username">root</systemitem> password when starting these programs.</para>
</warning>
<para>There is also
- <emphasis role="strong">puplet</emphasis>which automatically checks
+ <application>puplet</application> which automatically checks
for, and alerts you to, updates for your system. It appears as an
icon in the notification area when new updates are available. Click
this icon to launch
- <emphasis role="strong">pup</emphasis>and update your system.</para>
+ <application>pup</application> and update your system.</para>
<para>The
- <code>rpm</code>command-line utility has many functions for working
+ <application>rpm</application> command-line utility has many functions for working
with individual RPM packages. You may use it to manually install and
remove packages from your system. If you install software with the
- <code>rpm</code>utility, you must manually check and install any
+ <application>rpm</application> utility, you must manually check and install any
dependencies. For this reason,
- <emphasis role="strong">pirut</emphasis>and
- <code>yum</code>are the recommended methods for installing
+ <application>pirut</application> and
+ <application>yum</application> are the recommended methods for installing
software.</para>
<warning>
<title>Current Package Versions</title>
<para>The
- <emphasis role="strong">pirut</emphasis>and
- <code>yum</code>utilities ensure that you have the most recent
+ <application>pirut</application> and
+ <application>yum</application> utilities ensure that you have the most recent
version of software packages. Other methods do not guarantee that
the packages are current.</para>
</warning>
Index: manage-with-yum.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/manage-with-yum.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- manage-with-yum.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ manage-with-yum.xml 24 Jan 2008 01:48:01 -0000 1.3
@@ -12,7 +12,7 @@
<section id="sn-ManageWithYum">
<title>Managing Software with yum</title>
<para>Use the
- <code>yum</code>utility to modify the software on your system in four
+ <application>yum</application> utility to modify the software on your system in four
ways:</para>
<itemizedlist>
<listitem>
@@ -31,28 +31,28 @@
<note>
<title>Installing Software from a Package File</title>
<para>The
- <code>yum</code>commands shown in this section use repositories as
+ <application>yum</application> commands shown in this section use repositories as
package sources. Refer to
<xref linkend="sn-IsolatedInstall" />for details of using
- <code>yum</code>to install software from an individual package
+ <application>yum</application> to install software from an individual package
file.</para>
</note>
<para>To use
- <code>yum</code>, specify a function and one or more packages or
+ <application>yum</application>, specify a function and one or more packages or
package groups. Each section below gives some examples.</para>
<para>For each operation,
- <code>yum</code>downloads the latest package information from the
+ <application>yum</application> downloads the latest package information from the
configured repositories. If your system uses a slow network
connection yum may require several seconds to download the repository
indexes and the header files for each package.</para>
<para>The
- <code>yum</code>utility searches these data files to determine the
+ <application>yum</application> utility searches these data files to determine the
best set of actions to produce the required result, and displays the
transaction for you to approve. The transaction may include the
installation, update, or removal of additional packages, in order to
resolve software dependencies.</para>
<para>This is an example of the transaction for installing
- <code>tsclient</code>:</para>
+ <package>tsclient</package>:</para>
<para />
<screen>
<![CDATA[=============================================================================
@@ -72,21 +72,21 @@
Is this ok [y/N]:]]>
</screen>
<para>Example 1. Format of
- <code>yum</code>Transaction Reports</para>
+ <application>yum</application> Transaction Reports</para>
<para>Review the list of changes, and then press
- <emphasis role="strong">[y]</emphasis>to accept and begin the
+ <keycap>Y</keycap> to accept and begin the
process. If you press
- <emphasis role="strong">[N]</emphasis>or
- <emphasis role="strong">[Enter]</emphasis>,
- <code>yum</code>does not download or change any packages.</para>
+ <keycap>N</keycap> or
+ <keycap>Enter</keycap>,
+ <application>yum</application> does not download or change any packages.</para>
<note>
<title>Package Versions</title>
<para>The
- <code>yum</code>utility only displays and uses the newest version
+ <application>yum</application> utility only displays and uses the newest version
of each package, unless you specify an older version.</para>
</note>
<para>The
- <code>yum</code>utility also imports the repository public key if it
+ <application>yum</application> utility also imports the repository public key if it
is not already installed on the rpm keyring.</para>
<para>This is an example of the public key import:</para>
<para />
@@ -98,63 +98,64 @@
Is this ok [y/N]:]]>
</screen>
<para>Example 2. Format of
- <code>yum</code>Public Key Import</para>
+ <application>yum</application> Public Key Import</para>
<para>Check the public key, and then press
- <emphasis role="strong">[y]</emphasis>to import the key and authorize
+ <keycap>Y</keycap> to import the key and authorize
the key for use. If you press
- <emphasis role="strong">[N]</emphasis>or
- <emphasis role="strong">[Enter]</emphasis>,
- <code>yum</code>stops without installing any packages.</para>
+ <keycap>N</keycap> or
+ <keycap>Enter</keycap>,
+ <application>yum</application> stops without installing any packages.</para>
<para>To ensure that downloaded packages are genuine,
- <code>yum</code>verifies the digital signature of each package
+ <application>yum</application> verifies the digital signature of each package
against the public key of the provider. Once all of the packages
required for the transaction are successfully downloaded and
verified,
- <code>yum</code>applies them to your system.</para>
+ <application>yum</application> applies them to your system.</para>
<note>
<title>Transaction Log</title>
<para>Every completed transaction records the affected packages in
the log file
- <code>/var/log/yum.log</code>. You may only read this file with
- <emphasis>root</emphasis>access.</para>
+ <filename>/var/log/yum.log</filename>. You may only read this file with
+ <systemitem class="username">root</systemitem> access.</para>
</note>
<para />
<section id="sn-InstallingNewSoftware">
<title>Installing New Software with yum</title>
<para>To install the package
- <code>tsclient</code>, enter the command:</para>
+ <package>tsclient</package>, enter the command:</para>
<para>
- <code>su -c 'yum install tsclient'</code>
+ <command>su -c 'yum install tsclient'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<para>To install the package group
- <code>MySQL Database</code>, enter the command:</para>
+ <package>MySQL Database</package>, enter the command:</para>
<para>
- <code>su -c 'yum groupinstall "MySQL Database"'</code>
+ <command>su -c 'yum groupinstall "MySQL Database"'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<important>
<title>New Services Require Activation</title>
<para>When you install a service, Fedora does not activate or
start it. To configure a new service to run on bootup, choose
- <emphasis>System → Administration →
- Services</emphasis>from the top desktop panel, or use the
- <code>chkconfig</code>and
- <code>service</code>command-line utilities.</para>
+ <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu> <guimenuitem>
+ Services</guimenuitem> from the top desktop panel, or use the
+ <application>chkconfig</application> and
+ <application>service</application> command-line utilities.</para>
</important>
<anchor id="updating_software" />
</section>
<section id="UpdatingSoftware">
<title>Updating Software with yum</title>
<para>To update the
- <code>tsclient package</code>to the latest version, type:</para>
+ <package>tsclient</package> package to the latest version, type:</para>
<para>
- <code>su -c 'yum update tsclient'</code>
+ <command>su -c 'yum update tsclient'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<important>
<title>New Software Versions Require Reloading</title>
<para>If a piece of software is in use when you update it, the
@@ -172,12 +173,12 @@
current kernel and the previous version.</para>
</note>
<para>To update all of the packages in the package group
- <code>MySQL Database</code>, enter the command:</para>
+ <package>MySQL Database</package>, enter the command:</para>
<para>
- <code>su -c 'yum groupupdate "MySQL Database"'</code>
+ <command>su -c 'yum groupupdate "MySQL Database"'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<note>
<title>Updating the Entire System</title>
<para>To update all of the packages on your Fedora system, use
@@ -189,25 +190,25 @@
<section id="sn-RemovingSoftware">
<title>Removing Software with yum</title>
<para>To remove software,
- <code>yum</code>examines your system for both the specified
+ <application>yum</application> examines your system for both the specified
software, and any software which claims it as a dependency. The
transaction to remove the software deletes both the software and
the dependencies.</para>
<para>To remove the
- <code>tsclient</code>package from your system, use the
+ <package>tsclient</package> package from your system, use the
command:</para>
<para>
- <code>su -c 'yum remove tsclient'</code>
+ <command>su -c 'yum remove tsclient'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<para>To remove all of the packages in the package group
- <code>MySQL Database</code>, enter the command:</para>
+ <package>MySQL Database</package>, enter the command:</para>
<para>
- <code>su -c 'yum groupremove "MySQL Database"'</code>
+ <command>su -c 'yum groupremove "MySQL Database"'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<note>
<title>Data and Configuration File Retention</title>
<para>The removal process leaves user data in place but may
Index: search-with-yum.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/search-with-yum.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- search-with-yum.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ search-with-yum.xml 24 Jan 2008 01:48:01 -0000 1.3
@@ -11,11 +11,11 @@
]>
<section id="sn-SearchingForPackagesWithYum">
<title>Searching for Packages with
- <code>yum</code></title>
+ <application>yum</application></title>
<section id="sn-SearchingForPackages">
<title>Searching for Packages with yum</title>
<para>Use the search features of
- <code>yum</code>to find software that is available from the
+ <application>yum</application> to find software that is available from the
configured repositories, or already installed on your system.
Searches automatically include both installed and available
packages.</para>
@@ -28,18 +28,18 @@
<title>Searching by Package Name and Attributes</title>
<para>To search for a specific package by name, use the list
function. To search for the package
- <code>tsclient</code>, use the command:</para>
+ <package>tsclient</package>, use the command:</para>
<para>
- <code>su -c 'yum list tsclient'</code>
+ <command>su -c 'yum list tsclient'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<para>To make your queries more precise, specify packages with a
name that include other attributes, such as version or hardware
architecture. To search for version 0.132 of the application, use
the command:</para>
<para>
- <code>su -c 'yum list tsclient-0.132'</code>
+ <command>su -c 'yum list tsclient-0.132'</command>
</para>
<note>
<title>Valid Package Attributes</title>
@@ -53,61 +53,61 @@
<title>Advanced Searches</title>
<para>If you do not know the name of the package, use the search or
provides options. Alternatively, use wild cards with any
- <code>yum</code>search option to broaden the search
+ <application>yum</application> search option to broaden the search
criteria.</para>
<para>The search 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 Palm Pilots, type:</para>
<para>
- <code>su -c 'yum search PalmPilot'</code>
+ <command>su -c 'yum search PalmPilot'</command>
</para>
<para>Enter the password for the
- <emphasis>root</emphasis>account when prompted.</para>
+ <systemitem class="username">root</systemitem> account when prompted.</para>
<para>The provides function checks both the files included in the
packages and the functions that the software provides. This option
requires
- <code>yum</code>to download and read much larger index files than
+ <application>yum</application> to download and read much larger index files than
with the search option.</para>
<para>To search for all packages that include files called
- <code>libneon</code>, type:</para>
+ <literal>libneon</literal>, type:</para>
<para>
- <code>su -c 'yum provides libneon'</code>
+ <command>su -c 'yum provides libneon'</command>
</para>
<para>To search for all packages that either provide a MTA (Mail
Transport Agent) service, or include files with
- <code>mta</code>in their name:</para>
+ <literal>mta</literal> in their name:</para>
<para>
- <code>su -c 'yum provides MTA'</code>
+ <command>su -c 'yum provides MTA'</command>
</para>
<para>For each command, at the prompt enter the password for the
- <emphasis>root</emphasis>account.</para>
+ <systemitem class="username">root</systemitem> account.</para>
<para>Use the standard wild-card characters to run any search
option with a partial word or name:
- <code>?</code>to represent any one character, and
- <code>*</code>to mean zero or more characters. Always add the
+ <literal>?</literal> to represent any one character, and
+ <literal>*</literal> to mean zero or more characters. Always add the
escape character
- <code>\</code>before wild-cards.</para>
+ <literal>\</literal> before wild-cards.</para>
<para>To list all packages with names that begin with
- <code>tsc</code>, type:</para>
+ <literal>tsc</literal>, type:</para>
<para>
- <code>su -c 'yum list tsc\*'</code>
+ <command>su -c 'yum list tsc\*'</command>
</para>
<para />
</section>
<section id="sn-UnderstandingMatches">
<title>Understanding Matches</title>
<para>Searches with
- <code>yum</code>show all of the packages that match your criteria.
+ <application>yum</application> 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 wild-cards.</para>
<para>For example, a search query for
- <code>shadowutils</code>or
- <code>shadow-util</code>would not produce the package
- <code>shadow-utils</code>. This package would match and be shown if
+ <literal>shadowutils</literal> or
+ <literal>shadow-util</literal> would not produce the package
+ <package>shadow-utils</package>. This package would match and be shown if
the query was
- <code>shadow-util\?</code>, or
- <code>shadow\*</code>.</para>
+ <literal>shadow-util\?</literal>, or
+ <literal>shadow\*</literal>.</para>
</section>
</section>
<!--
More information about the Fedora-docs-commits
mailing list