yum-software-management yum-software-management-en.xml,1.17,1.18

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Wed Jul 20 00:55:59 UTC 2005


Author: elliss

Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22498

Modified Files:
	yum-software-management-en.xml 
Log Message:

- Add su to search/list commands: these may not work as an unprivileged user unless previously run as root to fetch current indices.
- Style fixes.



Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- yum-software-management-en.xml	19 Jul 2005 21:07:42 -0000	1.17
+++ yum-software-management-en.xml	20 Jul 2005 00:55:56 -0000	1.18
@@ -563,7 +563,7 @@
       Review the list of changes before pressing
       <userinput>y</userinput> to accept and begin the process. No
       packages are downloaded or changed if you press
-      <userinput>n</userinput>.
+      <userinput>N</userinput>.
     </para>
 
     <note>
@@ -773,15 +773,21 @@
         package <filename>tsclient</filename> the command would be:
       </para>
 <screen>
-<userinput>yum list <replaceable>tsclient</replaceable></userinput>
+<userinput>su -c 'yum list <replaceable>tsclient</replaceable>'</userinput>
 </screen>
       <para>
+        Enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
+      </para>
+
+      <para>
         To make your queries more specific, add other package
         attributes. For example, to search for version 0.132 of the
         application the command would be:
       </para>
 <screen>
-<userinput>yum list <replaceable>tsclient-0.132</replaceable></userinput>
+<userinput>su -c 'yum list <replaceable>tsclient-0.132</replaceable>'</userinput>
 </screen>
     </section>
 
@@ -800,9 +806,15 @@
         all packages that relate to PalmPilots, type:
       </para>
 <screen>
-<userinput>yum search <replaceable>PalmPilot</replaceable></userinput>
+<userinput>su -c 'yum search <replaceable>PalmPilot</replaceable>'</userinput>
 </screen>
       <para>
+        Enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
+      </para>
+
+      <para>
         The <option>provides</option> function checks both the files
         included in the packages and the functions that the software
         provides. This option requires <command>yum</command> to
@@ -815,7 +827,7 @@
         <filename>libneon</filename>, type:
       </para>
 <screen>
-<userinput>yum provides <replaceable>libneon</replaceable></userinput>
+<userinput>su -c 'yum provides <replaceable>libneon</replaceable>'</userinput>
 </screen>
       <para>
         To search for all packages that either provide an MTA (Mail
@@ -823,8 +835,13 @@
         <filename>mta</filename> in their name:
       </para>
 <screen>
-<userinput>yum provides <replaceable>MTA</replaceable></userinput>
+<userinput>su -c 'yum provides <replaceable>MTA</replaceable>'</userinput>
 </screen>
+      <para>
+        For each command, enter the password for the
+        <systemitem class="username">root</systemitem> account when
+        prompted.
+      </para>
       <tip>
         <title>Wildcards and Regular Expressions</title>
         <para>
@@ -941,8 +958,8 @@
         You must manually configure &FED; 3 systems to use &FEX;, using
         the instructions at:
         <ulink url="http://fedora.redhat.com/projects/extras/">http://fedora.redhat.com/projects/extras/</ulink>.
-        Refer to this Website for additional packages for &FC; 1 and
-        &FC; 2:
+        Refer to this Website for additional packages for &FED; 1 and
+        &FED; 2:
         <ulink url="http://www.fedora.us/">http://www.fedora.us/</ulink>.
       </para>
     </note>
@@ -992,12 +1009,13 @@
       </para>
 
       <para>
-        The configuration file for each repository should include the
-        location of the public key that verifies the packages provided
-        by that repository. This public key is automatically imported
-        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"/>.
+        The configuration file for each repository should include a
+        <command>gpgkey</command> setting to specify the location of the
+        public key that verifies the packages it provides. This public
+        key is automatically imported 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>
 
       <note>
@@ -1060,13 +1078,14 @@
       </para>
 
       <para>
-        Before attempting to use a repository, read the Website for
-        information on package compatibility. Repositories often provide
-        packages that are specifically intended for use with packages
-        that are supplied by other repositories. In some cases separate
-        third-party repository providers may each offer different
-        versions of the same software, preventing those repositories
-        from being safely used together by your &FED; system.
+        Refer to the Website of the repository for information on
+        package compatibility before adding it as a package source.
+        Repositories often provide packages that are specifically
+        intended for use with packages that are supplied by other
+        repositories. In some cases separate third-party repository
+        providers may each offer different versions of the same
+        software, preventing those repositories from being safely used
+        together by your &FED; system.
       </para>
 
       <para>
@@ -1095,11 +1114,11 @@
 
     <para>
       The <command>yum</command> system does not require any routine
-      maintenance. It is useful to disable or remove repository
-      definitions that are no longer required, as each repository that
-      is defined and enabled is checked for every operation. You may
-      also clear the files from the <command>yum</command> caches in
-      order to recover disk space.
+      maintenance. To ensure that <command>yum</command> operations are
+      carried out at the best possible speed, disable or remove
+      repository definitions are no longer required. You may also clear
+      the files from the <command>yum</command> caches in order to
+      recover disk space.
     </para>
 
     <section id="sn-removing-sources">
@@ -1231,16 +1250,20 @@
 <userinput>su -c 'yum clean packages'</userinput>
 </screen>
       <para>
-        In both cases, enter the password for the
+        When using these commands, enter the password for the
         <systemitem class="username">root</systemitem> account when
         prompted.
       </para>
 
-      <para>
-        Package management operations download header files and packages
-        as required, automatically replacing any purged files needed for
-        the operation.
-      </para>
+      <note>
+        <title>Purged Files</title>
+
+        <para>
+          Package management operations download header files and
+          packages as required, automatically replacing any deleted
+          files needed for the operation.
+        </para>
+      </note>
     </section>
   </section>
 




More information about the Fedora-docs-commits mailing list