yum-software-management yum-software-management-en.xml,1.31,1.32
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Thu Jul 28 22:03:19 UTC 2005
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5817
Modified Files:
yum-software-management-en.xml
Log Message:
- Added note that package removal does not remove config and data files.
- Amended package operation description to hopefully clarify metadata download
- Added example of GPG key import.
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- yum-software-management-en.xml 28 Jul 2005 00:54:16 -0000 1.31
+++ yum-software-management-en.xml 28 Jul 2005 22:03:12 -0000 1.32
@@ -98,7 +98,7 @@
linkend="sn-software-management-concepts"/>
before using <command>yum</command> for the first time.
Experienced Linux users should start with
- <xref linkend="sn-updating-your-system"/>.
+ <xref linkend="sn-managing-packages"/>.
</para>
<para>
@@ -254,9 +254,7 @@
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. In each case the
- management utility connects to the configured repositories and
- checks their indexes to find the correct packages.
+ for new software by specifying criteria.
</para>
<para>
@@ -391,7 +389,7 @@
<filename>tsclient</filename> package supplied with &FC;:
</para>
<screen>
-<filename>tsclient-0.132-4.i386.rpm</filename>
+<filename>tsclient-0.132-6.i386.rpm</filename>
</screen>
<para>
Management utilities commonly refer to packages with one of
@@ -407,7 +405,7 @@
<listitem>
<para>
Package name with version and release numbers:
- <filename>tsclient-0.132-4</filename>
+ <filename>tsclient-0.132-6</filename>
</para>
<!-- In what instances is the release number not needed? For many -->
<!-- package updates, only the release number might change. Although it -->
@@ -624,11 +622,19 @@
</para>
<para>
- During operation, <command>yum</command> first determines the best
- set of actions to produce the required result, and displays the
- transaction for you to approve. The <command>yum</command> utility
- may prompt you to approve the installation, update, or removal of
- additional packages, in order to resolve software dependencies.
+ For each operation, <command>yum</command> downloads the latest
+ package information from the configured repositories. If your
+ system uses a slow network connection <command>yum</command> may
+ require several seconds to download the repository indexes and the
+ header files for each package.
+ </para>
+
+ <para>
+ The <command>yum</command> 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>
<example id="yum-transaction-format">
@@ -676,6 +682,41 @@
version.
</para>
</note>
+
+ <para>
+ The <command>yum</command> utility imports the repository public
+ key if it is not already installed on the <command>rpm</command>
+ keyring.
+ </para>
+
+ <example id="yum-publickey-import">
+ <title>Format of <command>yum</command> Public Key Import</title>
+
+ <para>
+ This is an example of the public key import:
+ </para>
+<screen>
+<computeroutput>
+<![CDATA[
+warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
+public key not available for tsclient-0.132-6.i386.rpm
+Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
+Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora at redhat.com>"
+Is this ok [y/N]:
+]]>
+</computeroutput>
+</screen>
+ </example>
+
+ <para>
+ Check the public key, and then press
+ <keycap>y</keycap>
+ to import the key and authorize the key for use. If you press
+ <keycap>N</keycap>
+ or
+ <keycap>Enter</keycap>
+ , <command>yum</command> stops without installing any packages.
+ </para>
<tip>
<title>Downloads are Cached</title>
<para>
@@ -766,8 +807,9 @@
<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 application or service is
+ restarted. Kernel updates take effect when you reboot the
+ system.
</para>
</important>
@@ -808,7 +850,8 @@
<para>
To remove software, <command>yum</command> examines your system
for both the specified software, and any software which claims
- it as a dependency.
+ it as a dependency. The transaction to remove the software
+ deletes both the software and the dependencies.
</para>
<para>
@@ -836,6 +879,16 @@
<systemitem class="username">root</systemitem> account when
prompted.
</para>
+
+ <note>
+ <title>Data and Settings are Retained</title>
+
+ <para>
+ The removal process leaves configuration files and data in
+ place. If you reinstall removed software the new installation
+ uses the original configuration files.
+ </para>
+ </note>
</section>
</section>
@@ -915,8 +968,9 @@
<para>
If you do not know the name of the package, use the
<option>search</option> or <option>provides</option> options.
- Alternatively, you may use wild cards and regular expressions
- with any <command>yum</command> search option.
+ Alternatively, use wild cards or regular expressions with any
+ <command>yum</command> search option to broaden the search
+ critieria.
</para>
<para>
@@ -1147,7 +1201,7 @@
<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
+ first time that 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>
More information about the docs-commits
mailing list