homepage/devel/po el.po,1.19,1.20
by fedora-docs-commits@redhat.com
Author: transif
Update of /cvs/docs/homepage/devel/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28058/po
Modified Files:
el.po
Log Message:
2008-01-25 Dimitris Glezos <dimitris(a)glezos.com> (via glezos(a)fedoraproject.org)
* po/el.po: Updated Greek translation
Index: el.po
===================================================================
RCS file: /cvs/docs/homepage/devel/po/el.po,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- el.po 6 Nov 2007 10:44:24 -0000 1.19
+++ el.po 25 Jan 2008 13:20:03 -0000 1.20
@@ -1,4 +1,4 @@
-# translation of el.po to Greek
+# translation of homepage-el.po to Greek
#
# Dimitris Glezos <dimitris(a)glezos.com>, 2006, 2007.
# Panagiota Bilianou <tetonio(a)gmail.com>, 2006.
@@ -353,8 +353,8 @@
"\"><placeholder-2/></ulink>."
msgstr ""
"�� ������������ ������������ �������������������� ���������������� ���������� �������� ���� ���������� �������������������� ���� "
-"<placeholder-1/> ������ <ulink url=\"http://fedoraproject.org/wiki/Docs/Drafts/DesktopUserGuide"
-"\"><placeholder-2/></ulink>."
+"<placeholder-1/> ������ <ulink url=\"http://fedoraproject.org/wiki/Docs/Drafts/"
+"DesktopUserGuide\"><placeholder-2/></ulink>."
#: en_US/homepage.xml:89(title)
msgid "Other Resources"
@@ -392,7 +392,9 @@
msgid ""
"<ulink url=\"http://fedoraproject.org/wiki/FAQ\"><placeholder-1/></ulink>: "
"Frequently asked questions about Fedora and their answers"
-msgstr "<ulink url=\"http://fedoraproject.org/wiki/FAQ\"><placeholder-1/></ulink>: ������������ ������������������ �������������� ���� ���� Fedora ������ ���� �������������������� ��������"
+msgstr ""
+"<ulink url=\"http://fedoraproject.org/wiki/FAQ\"><placeholder-1/></ulink>: "
+"������������ ������������������ �������������� ���� ���� Fedora ������ ���� �������������������� ��������"
#: en_US/homepage.xml:109(phrase)
msgid "Communicate"
@@ -405,8 +407,9 @@
"contributors that is ready to help you and listen to your feedback"
msgstr ""
"<ulink url=\"http://fedoraproject.org/wiki/Communicate\"><placeholder-1/></"
-"ulink>: ������������ ������ ���� ���������������������������� ���� ������ ������������ ������ ������������������ ������������������ �������������� "
-"������ ���������������������� ���� ������������ ���������� �������������� ���� ������ ������������������ ������ ���� ���������������� ���� ������������ ������"
+"ulink>: ������������ ������ ���� ���������������������������� ���� ������ ������������ ������ ������������������ ������������������ "
+"�������������� ������ ���������������������� ���� ������������ ���������� �������������� ���� ������ ������������������ ������ ���� "
+"���������������� ���� ������������ ������"
#: en_US/homepage.xml:117(phrase)
msgid "Participate"
@@ -418,7 +421,8 @@
"Ways you can make a change by helping with Fedora"
msgstr ""
"<ulink url=\"http://fedoraproject.org/wiki/Join\"><placeholder-1/></ulink>: "
-"������������ ���� �������� �������������� ���������������� ���� ������������ �������� ������������������ ������������������ ���� �������� Fedora"
+"������������ ���� �������� �������������� ���������������� ���� ������������ �������� ������������������ ������������������ ���� �������� "
+"Fedora"
#: en_US/homepage.xml:122(phrase)
msgid "Planet Fedora"
@@ -469,5 +473,6 @@
msgid ""
"<ulink url=\"http://fedoraforum.org\"><placeholder-1/></ulink>: The formally "
"endorsed forums of the Fedora Project"
-msgstr "<ulink url=\"http://fedoraforum.org\"><placeholder-1/></ulink>: ���� ���������������� ���������������������� forum ������ ���������� Fedora"
-
+msgstr ""
+"<ulink url=\"http://fedoraforum.org\"><placeholder-1/></ulink>: ���� ���������������� "
+"���������������������� forum ������ ���������� Fedora"
16 years, 3 months
install-guide/devel/po el.po,1.37,1.38
by fedora-docs-commits@redhat.com
Author: transif
Update of /cvs/docs/install-guide/devel/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27981/po
Modified Files:
el.po
Log Message:
2008-01-25 Dimitris Glezos <dimitris(a)glezos.com> (via glezos(a)fedoraproject.org)
* po/el.po: Updated Greek translation
Index: el.po
===================================================================
RCS file: /cvs/docs/install-guide/devel/po/el.po,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- el.po 8 Nov 2007 11:59:22 -0000 1.37
+++ el.po 25 Jan 2008 13:15:41 -0000 1.38
@@ -1,19 +1,17 @@
-# translation of el.po to Greek
-# translation of el.po to
# translation of fedora-install-guide to Greek
#
#
-# Dimitris Glezos <dimitris(a)glezos.com>, 2007.
+# Dimitris Glezos <dimitris(a)glezos.com>, 2007, 2008.
# Stavros Giannouris <stavrosg(a)hellug.gr>, 2007.
# Nikos Charonitakis <nikosx(a)gmail.com>, 2007.
# Dimitrios Typaldos <dtfedora(a)yahoo.com>, 2007.
msgid ""
msgstr ""
-"Project-Id-Version: el\n"
+"Project-Id-Version: install-guide.HEAD\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2007-11-08 10:40+0000\n"
-"PO-Revision-Date: 2007-11-08 10:55+0000\n"
-"Last-Translator: Dimitrios Typaldos <dtfedora(a)yahoo.com>\n"
+"POT-Creation-Date: 2007-11-07 23:05-0500\n"
+"PO-Revision-Date: 2008-01-25 15:10+0200\n"
+"Last-Translator: Dimitris Glezos <dimitris(a)glezos.com>\n"
"Language-Team: Greek <fedora-trans-el(a)redhat.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -980,8 +978,8 @@
#: en_US/pxe-server.xml:68(para)
msgid "If you are using a DVD disc or ISO image, Create a directory mount point:"
msgstr ""
-"���� ���������������������������� �������� ���������� DVD �� ������ ������������ ISO, ������������������������ ������ "
-"������������ ���������������������� ������������������:"
+"���� ���������������������������� �������� ���������� DVD �� ������ ������������ ISO, ������������������������ ������ ������������ "
+"���������������������� ������������������:"
#: en_US/pxe-server.xml:71(para)
msgid "To mount a physical DVD disc, use the following command:"
@@ -2549,19 +2547,19 @@
"The Fedora Project maintains a list of HTTP and FTP public mirrors, sorted "
"by region, at <ulink url=\"http://fedoraproject.org/wiki/Mirrors\"/>. To "
"determine the complete directory path for the installation files, add "
-"<filename>/7/Fedora/<replaceable>architecture</replaceable>/os/</filename> "
+"<filename>/8/Fedora/<replaceable>architecture</replaceable>/os/</filename> "
"to the path shown on the web page. A correct mirror location for an "
"<systemitem>i386</systemitem> system resembles the URL <literal>http://"
-"mirror.example.com/pub/fedora/linux/releases/7/Fedora/i386/os</literal>."
+"mirror.example.com/pub/fedora/linux/releases/8/Fedora/i386/os</literal>."
msgstr ""
-"���� �������� Fedora ���������������� ������ ���������� ���������������� �������������� HTTP ������ FTP, "
+"���� �������� Fedora ���������������� ������ ���������� ������������������������ �������������������� HTTP ������ FTP, "
"������������������������ ������ ��������������, ������ <ulink url=\"http://fedoraproject.org/wiki/"
"Mirrors\"/>. ������ ������ ������������������ ������������������ ������ ������������������ ������������������ ������ ���� "
-"������������ ������������������������, ������������������ <filename>/8//Fedora/<replaceable>architecture</"
-"replaceable>/os/</filename> ������ ���������������� ������ �������������������� �������� ��������������������. ������ "
-"���������� ������������������ �������������� ������ ������ �������������� <systemitem>i386</systemitem> ������������ "
-"���� �������������� ���� ���� URL <literal>http://mirror.example.com/pub/fedora/linux/"
-"releases/8/Fedora/i386/os</literal>."
+"������������ ������������������������, ������������������ <filename>/8/Fedora/"
+"<replaceable>architecture</replaceable>/os/</filename> ������ ���������������� ������ "
+"���������������������� �������� ��������������������. ������ ���������� ���������������������� ������������������ ������ ������ �������������� "
+"<systemitem>i386</systemitem> ������������ ���� �������������� ���� ���� URL <literal>http://"
+"mirror.example.com/pub/fedora/linux/releases/8/Fedora/i386/os</literal>."
#: en_US/other-instmethods.xml:243(para)
msgid ""
@@ -7840,7 +7838,7 @@
#: en_US/before-begin.xml:41(para)
msgid ""
-"The Release Notes specify the hardware requirements for Fedora 7. They also "
+"The Release Notes specify the hardware requirements for Fedora 8. They also "
"provide advice on any known problems with particular hardware and software "
"configurations."
msgstr ""
@@ -7978,18 +7976,18 @@
"The Fedora Project maintains a list of HTTP and FTP public mirrors, sorted "
"by region, at <ulink url=\"http://mirrors.fedoraproject.org/publiclist\"/>. "
"To determine the complete directory path for the installation files, add "
-"<filename>/7/<replaceable>architecture</replaceable>/os/</filename> to the "
+"<filename>/8/<replaceable>architecture</replaceable>/os/</filename> to the "
"path shown on the web page. If your computer uses the <systemitem>ppc</"
-"systemitem> architecture, for instance, add <filename class=\"directory\">/7/"
+"systemitem> architecture, for instance, add <filename class=\"directory\">/8/"
"ppc/os/</filename> to the path shown."
msgstr ""
"���� �������� Fedora ���������������� ������ ���������� ���������������� �������������� HTTP ������ FTP, "
"������������������������ ������ ��������������, ������ <ulink url=\"http://mirrors.fedoraproject.org/"
"publiclist\"/>. ������ ������ ������������������ ������������������ ������ ������������������ ������������������ ������ ���� "
-"������������ ������������������������, ������������������ <filename>/7/<replaceable>architecture</"
+"������������ ������������������������, ������������������ <filename>/8/<replaceable>architecture</"
"replaceable>/os/</filename> ������ ���������������� ������ �������������������� �������� ��������������������. ���� "
"�� ���������������������� ������ ������������������������ ������ �������������������������� <systemitem>ppc</"
-"systemitem>, ������ ��������������������, ������������������ <filename class=\"directory\">/7/ppc/"
+"systemitem>, ������ ��������������������, ������������������ <filename class=\"directory\">/8/ppc/"
"os/</filename> ������ ���������������� ������ ����������������������."
#: en_US/before-begin.xml:150(title)
16 years, 3 months
install-guide/F-8/po el.po,1.3,1.4
by fedora-docs-commits@redhat.com
Author: transif
Update of /cvs/docs/install-guide/F-8/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27560
Modified Files:
el.po
Log Message:
Dummy change to test Tx
Index: el.po
===================================================================
RCS file: /cvs/docs/install-guide/F-8/po/el.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- el.po 2 Jan 2008 22:25:04 -0000 1.3
+++ el.po 25 Jan 2008 13:05:04 -0000 1.4
@@ -1,5 +1,3 @@
-# translation of el.po to Greek
-# translation of el.po to
# translation of fedora-install-guide to Greek
#
#
16 years, 3 months
yum-software-management/en_US doc-entities.xml, 1.2, 1.3 rpm-info.xml, 1.1, 1.2
by fedora-docs-commits@redhat.com
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17181
Modified Files:
doc-entities.xml rpm-info.xml
Log Message:
Update document metadata
Index: doc-entities.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/doc-entities.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- doc-entities.xml 30 Apr 2006 15:17:04 -0000 1.2
+++ doc-entities.xml 24 Jan 2008 20:06:50 -0000 1.3
@@ -9,11 +9,11 @@
</entity>
<entity name="DOCVERSION">
<comment>Version number</comment>
- <text>1.31</text>
+ <text>2.01</text>
</entity>
<entity name="DOCDATE">
<comment>Date of last revision</comment>
- <text>2006-04-30</text>
+ <text>2008-01-24</text>
</entity>
<entity name="DOCID">
<comment>Document ID</comment>
@@ -23,8 +23,8 @@
</group>
<group name="Miscellaneous">
<entity name="FCLOCALVER">
- <comment>Local version of Fedora Core for this document</comment>
- <text>5</text>
+ <comment>Local version of Fedora for this document</comment>
+ <text>8</text>
</entity>
</group>
</entities>
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/rpm-info.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rpm-info.xml 6 Aug 2006 00:14:06 -0000 1.1
+++ rpm-info.xml 24 Jan 2008 20:06:50 -0000 1.2
@@ -7,9 +7,13 @@
<worker surname="Menezes" firstname="Rodrigo" othername="" id="RodrigoMenezes" email="menezes(a)projetofedora.org" wholename="Rodrigo Menezes" initials="RodrigoMenezes"/>
<worker surname="Cisneiros" firstname="Hugo" othername="" id="HugoCisneiros" email="hugo(a)devin.com.br" wholename="Hugo Cisneiros" initials="HugoCisneiros"/>
<worker surname="Pires" firstname="Jos��" othername="" id="JosePires" email="jncp(a)netcabo.pt" wholename="Jos�� Pires" initials="JP"/>
+ <worker surname="Christensen" firstname="Eric" othername="" id="EricChristensen" email="eric(a)christensenplace.us" wholename="Eric Christensen" initials="EricChristensen"/>
+ <worker surname="Smith" firstname="Jared" othername="K." id="JaredKSmith" email="jaredsmith(a)jaredsmith.net" wholename="Jared K. Smith" initials="JaredKSmith"/>
</colophon>
+ <author worker="EricChristensen"/>
<author worker="StuartEllis"/>
<editor worker="PaulWFrields"/>
+ <editor worker="JaredKSmith"/>
<translator worker="RodrigoMenezes"/>
<translator worker="HugoCisneiros"/>
<translator worker="JosePires"/>
@@ -18,12 +22,16 @@
<version>1.0</version>
</license>
<copyright>
- <year>2006</year>
- <holder>Stuart Ellis</holder>
+ <year>2008</year>
+ <holder>Red Hat, Inc. and others</holder>
</copyright>
<title>Managing Software with yum</title>
<desc>Documentation for the yum software management system.</desc>
<changelog order="newest-first">
+ <revision date="2008-01-24" number="2.01" role="doc">
+ <author worker="Jared Smith"/>
+ <details>Import new version from Wiki, convert to DocBook.</details>
+ </revision>
<revision date="2006-04-30" number="1.31" role="doc">
<author worker="StuartEllis"/>
</revision>
16 years, 3 months
yum-software-management/en_US customizing-yum.xml,1.3,1.4
by fedora-docs-commits@redhat.com
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6418
Modified Files:
customizing-yum.xml
Log Message:
Add the section for the yum-security plugin, and comment out the section for
the downloadonly plugin, as it's not currently documented
Index: customizing-yum.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/customizing-yum.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- customizing-yum.xml 24 Jan 2008 03:18:03 -0000 1.3
+++ customizing-yum.xml 24 Jan 2008 15:16:01 -0000 1.4
@@ -190,12 +190,66 @@
<para>You can configure various settings of this plugin in the file
<filename>/etc/yum/pluginconf.d/fastestmirror.conf</filename></para>
</section>
+ <section>
+ <title>Security Plugin</title>
+ <para>This plugin extends yum to allow lists and updates to be limited
+ using security relevant criteria. This may be important to you if you
+ are using Fedora in a production mode and you don't want to break your
+ software with an untested upgrade.</para>
+ <para>For installing it, use the following command
+ <command>su -c 'yum install yum-security'</command>
+ or from
+ the<guimenu>Applications</guimenu> menu select
+ <guimenuitem>Add/Remove Software</guimenuitem>
+ </para>
+ <para>There are two yum commands that are used with this plugin:</para>
+ <itemizedlist>
+ <listitem><para>info-sec</para></listitem>
+ <listitem><para>list-sec</para></listitem>
+ </itemizedlist>
+ <para>Both of these commands take these sub-commands:</para>
+ <itemizedlist>
+ <listitem>
+ <para><advisory> [advisory...]</para>
+ </listitem>
+ <listitem><para>bugzillas</para></listitem>
+ <listitem><para>cves</para></listitem>
+ <listitem><para>security</para></listitem>
+ </itemizedlist>
+ <section>
+ <title>Examples</title>
+ <para>To list all updates that are security relevant, and get a
+ return code on whether there are security updates use:</para>
+ <para>
+ <command>su -c 'yum --security check-update'</command>
+ </para>
+ <para>To apply updates that are security relevant use:</para>
+ <para>
+ <command>su -c 'yum --security update'</command>
+ </para>
+ <para>To get a list of all BZs that are fixed for packages you have
+ installed use:</para>
+ <para>
+ <command>su -c 'yum list-sec bugzillas'</command>
+ </para>
+ <para>To get the information on advisory FEDORA-2707-4567 use:</para>
+ <para>
+ <command>su -c 'yum info-sec FEDORA-2707-4567'</command>
+ </para>
+ <para>For additional information, view the man page:</para>
+ <para>
+ <command>man yum-security</command>
+ </para>
+ </section>
+ </section>
+ <!--
<section id="sn-YumPluginDownloadonly">
<title>Downloadonly Plugin</title>
<para>FIXME: Figure out how plugin works and document
that.</para>
<para />
</section>
+ -->
<section id="sn-YumPluginChangelog">
<title>Changelog Plugin</title>
<para>When Fedora developers provide a update to a existing
@@ -204,7 +258,7 @@
package changelog before doing a update. This plugin is not
installed by default. For installing it, use the following
command or from the <guimenu>Applications
- </guimenu>menu use<guimenuitem>Add/Remove
+ </guimenu> menu use <guimenuitem>Add/Remove
Software"</guimenuitem>.</para>
<para><command>su -c 'yum install
yum-changelog'</command></para>
16 years, 3 months
yum-software-management/en_US configuring-repositories.xml, 1.4, 1.5 customizing-yum.xml, 1.2, 1.3 isolated-install.xml, 1.2, 1.3 manage-with-yum.xml, 1.3, 1.4 pirut.xml, 1.2, 1.3 pup.xml, 1.2, 1.3 update-with-yum.xml, 1.2, 1.3 yum-caching.xml, 1.2, 1.3 yum-proxy.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5496
Modified Files:
configuring-repositories.xml customizing-yum.xml
isolated-install.xml manage-with-yum.xml pirut.xml pup.xml
update-with-yum.xml yum-caching.xml yum-proxy.xml
Log Message:
Finish up the tag cleanup started earlier... again, mostly replacing
<code> and <emphasis> tags with more meaningful tags.
Index: configuring-repositories.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/configuring-repositories.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- configuring-repositories.xml 22 Jan 2008 03:04:01 -0000 1.4
+++ configuring-repositories.xml 24 Jan 2008 03:18:03 -0000 1.5
@@ -17,31 +17,31 @@
repository. Members of the community also maintain repositories to
provide packages for Fedora systems. For example,
<ulink url="http://www.jpackage.org/">
- http://www.jpackage.org/</ulink>distributes popular Java software as
+ http://www.jpackage.org/</ulink> distributes popular Java software as
packages.</para>
<para />
<section id="sn-AddingRepository">
<title>Adding a Repository as a Package Source</title>
<para>To add an extra repository, place a definition file in the
- <code>/etc/yum.repos.d/</code>directory on your system. Package
+ <filename class="directory">/etc/yum.repos.d/</filename> directory on your system. Package
providers make the definition files for their repositories
available on their web sites.</para>
<note>
<title>Definition File Extension</title>
<para>The names of repository definition files end with
- <code>.repo</code>.</para>
+ <filename class="extension">.repo</filename>.</para>
</note>
<para>You must have
- <emphasis>root</emphasis>access to add a file to the definitions
+ <systemitem class="username">root</systemitem> access to add a file to the definitions
directory. To copy the definition file
- <code>example.repo</code>, type this command:</para>
+ <filename>example.repo</filename>, type this command:</para>
<para>
- <code>su -c 'cp example.repo /etc/yum.repos.d/'</code>
+ <command>su -c 'cp example.repo /etc/yum.repos.d/'</command>
</para>
<para>At the prompt, enter the password for the
- <emphasis>root</emphasis>account.</para>
+ <systemitem class="username">root</systemitem> account.</para>
<para>The configuration file for each repository should include a
- <code>gpgkey</code>setting. This setting specifies the location of
+ <literal>gpgkey</literal> 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 that you install software from the repository. If the
@@ -52,31 +52,31 @@
<section id="sn-ManuallyAuthorizing">
<title>Manually Authorizing Package Sources</title>
<para>To manually add a public key to your
- <code>rpm</code>keyring, use the import feature of the
- <code>rpm</code>utility. To import the file
- <code>GPG-PUB-KEY.asc</code>, type the following command:</para>
+ <application>rpm</application> keyring, use the import feature of the
+ <application>rpm</application> utility. To import the file
+ <filename>GPG-PUB-KEY.asc</filename>, type the following command:</para>
<para>
- <code>su -c 'rpm --import GPG-PUB-KEY.asc'</code>
+ <command>su -c 'rpm --import GPG-PUB-KEY.asc'</command>
</para>
<para>At the prompt, enter the password for the
- <emphasis>root</emphasis>account.</para>
+ <systemitem class="username">root</systemitem> account.</para>
<para>You may also import public keys directly from a web site. For
example, to import the file
- <code>GPG-PUB-KEY.asc</code>on the web site
- <emphasis>www.therepository.com</emphasis>, use this
+ <filename>GPG-PUB-KEY.asc</filename> on the web site
+ <replaceable>www.therepository.com</replaceable>, use this
command:</para>
<para>
- <code>su -c 'rpm --import
- http://www.therepository.com/GPG-PUB-KEY.asc'</code>
+ <command>su -c 'rpm --import
+ http://<replaceable>www.therepository.com</replaceable>/GPG-PUB-KEY.asc'</command>
</para>
<para>At the prompt, enter the
- <emphasis>root</emphasis>password.</para>
+ <systemitem class="username">root</systemitem> password.</para>
<important>
<title>Importing the Fedora Key</title>
<para>To add the Fedora public key to the
- <code>rpm</code>keyring on Fedora systems, run the command
- <code>su -c 'rpm --import
- /usr/share/rhn/RPM-GPG-KEY-fedora'</code>.</para>
+ <application>rpm</application> keyring on Fedora systems, run the command
+ <command>su -c 'rpm --import
+ /usr/share/rhn/RPM-GPG-KEY-fedora'</command>.</para>
</important>
<para />
</section>
@@ -110,31 +110,31 @@
<title>Old Versions of yum and Current Repositories</title>
<para>The data format for repository indexes changed with version
2.1 of
- <code>yum</code>. This was the version supplied with Fedora Core
+ <application>yum</application>. This was the version supplied with Fedora Core
3. Repository providers should specify the versions of Fedora
that they support. To confirm that an unlabeled repository is
compatible with current versions of
- <code>yum</code>, check that it has a sub-directory called
- <code>repodata/</code>.</para>
+ <application>yum</application>, check that it has a sub-directory called
+ <filename class="directory">repodata/</filename>.</para>
</note>
<para />
</section>
<section id="sn-DisablingSources">
<title>Disabling or Removing Package Sources</title>
<para>Set
- <code>enable=0</code>in a definition file to prevent
- <code>yum</code>from using that repository. The
- <code>yum</code>utility ignores any definition file with this
+ <literal>enable=0</literal> in a definition file to prevent
+ <application>yum</application> from using that repository. The
+ <application>yum</application> utility ignores any definition file with this
setting.</para>
<para>To completely remove access to a repository:</para>
<orderedlist numeration="arabic">
<listitem>
<para>Delete the relevant file from
- <code>/etc/yum.repos.d/</code>.</para>
+ <filename class="directory">/etc/yum.repos.d/</filename>.</para>
</listitem>
<listitem>
<para>Delete the cache directory from
- <code>/var/cache/yum/</code>.</para>
+ <filename class="directory">/var/cache/yum/</filename>.</para>
</listitem>
</orderedlist>
</section>
Index: customizing-yum.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/customizing-yum.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- customizing-yum.xml 22 Jan 2008 03:34:04 -0000 1.2
+++ customizing-yum.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -10,41 +10,41 @@
]>
<section id="sn-CustomizingYum">
<title>Customizing
- <code>yum</code></title>
+ <application>yum</application></title>
<para>To change the behavior of
- <code>yum</code>, you may either edit the configuration files, or
+ <application>yum</application>, you may either edit the configuration files, or
install
- <emphasis>plugins</emphasis>. Plugins enable developers to add new
+ <firstterm>plugins</firstterm>. Plugins enable developers to add new
features to
- <code>yum</code>.</para>
+ <application>yum</application>.</para>
<anchor id="editing_the_yum_configuration" />
<section id="sn-EditingYumConfig">
<title>Editing the yum Configuration</title>
<para>The file
- <code>/etc/yum.conf</code>provides the main configuration for
- <code>yum</code>. Settings in a repository definition file override
+ <filename>/etc/yum.conf</filename> provides the main configuration for
+ <application>yum</application>. Settings in a repository definition file override
the main configuration for those operations that use the defined
repository.</para>
<para>To edit
- <code>/etc/yum.conf</code>, run a text editor with
- <emphasis>root</emphasis>privileges. This command opens
- <code>/etc/yum.conf</code>with
- <emphasis role="strong">gedit</emphasis>, the default text editor
+ <filename>/etc/yum.conf</filename>, run a text editor with
+ <systemitem class="username">root</systemitem> privileges. This command opens
+ <filename>/etc/yum.conf</filename> with
+ <application>gedit</application>, the default text editor
for Fedora desktop systems:</para>
<para>
- <code>su -c 'gedit /etc/yum.conf'</code>
+ <command>su -c 'gedit /etc/yum.conf'</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 main configuration file provides the settings that apply
to all
- <code>yum</code>operations. These include caching options, and
+ <application>yum</application> operations. These include caching options, and
proxy server settings. The directory
- <code>/etc/yum.repos.d/</code>holds definition files for each
+ <filename class="directory">/etc/yum.repos.d/</filename> holds definition files for each
repository that
- <code>yum</code>uses. Plugins use the configuration files in the
+ <application>yum</application> uses. Plugins use the configuration files in the
directory
- <code>/etc/yum/pluginconf.d/</code>.</para>
+ <filename class="directory">/etc/yum/pluginconf.d/</filename>.</para>
<para>The following sections in this document provide further
information on configuring yum:</para>
<itemizedlist>
@@ -72,10 +72,10 @@
<note>
<title>Further Documentation</title>
<para>Refer to the
- <code>man</code>page for
- <code>yum.conf</code>for a complete list of the configuration
+ <application>man</application> page for
+ <filename>yum.conf</filename> for a complete list of the configuration
options supported by
- <code>yum</code>.</para>
+ <application>yum</application>.</para>
</note>
<para>
<anchor id="working_with_yum_plugins" />
@@ -92,42 +92,43 @@
<note>
<title role="strong">Plugin File Extension</title>
<para>The names of
- <code>yum</code>plugin files end with
- <code>.py</code>, the standard extension for Python
+ <application>yum</application> plugin files end with
+ <filename class="extension">.py</filename>, the standard extension for Python
scripts.</para>
</note>
<para>To install a plugin, copy it to the directory
- <code>/usr/lib/yum-plugins/</code>. Create a configuration file for
+ <filename class="directory">/usr/lib/yum-plugins/</filename>. Create a configuration file for
the plugin in the directory
- <code>/etc/yum/pluginconf.d/</code>. Save the configuration file
+ <filename class="directory">/etc/yum/pluginconf.d/</filename>. Save the configuration file
with the same name as the plugin, but with the extension
- <code>.conf</code>.</para>
+ <filename class="extension">.conf</filename>.</para>
<note>
<title>
- <emphasis role="strong">root</emphasis>Privileges
+ <systemitem class="username">root</systemitem> Privileges
Required</title>
<para>You must have
- <emphasis>root</emphasis>access to add files to the directories
- <code>/usr/lib/yum-plugins/</code>and
- <code>/etc/yum/pluginconf.d/</code>.</para>
+ <systemitem class="username">root</systemitem> access to add files to the directories
+ <filename class="directory">/usr/lib/yum-plugins/</filename> and
+ <filename class="directory">/etc/yum/pluginconf.d/</filename>.</para>
</note>
<para>For example, to copy the plugin
- <code>exampleplugin.py</code>, enter the command:</para>
+ <filename>exampleplugin.py</filename>, enter the command:</para>
<para>
- <code>su -c 'cp exampleplugin.py /usr/lib/yum-plugins/'</code>
+ <command>su -c 'cp exampleplugin.py
+ /usr/lib/yum-plugins/'</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>You may then create a configuration file for the plugin with
a text editor. This example uses
- <emphasis role="strong">gedit</emphasis>, the default text editor
+ <application>gedit</application>, the default text editor
for Fedora desktop systems:</para>
<para>
- <code>su -c 'gedit
- /etc/yum/pluginconf.d/exampleplugin.conf'</code>
+ <command>su -c 'gedit
+ /etc/yum/pluginconf.d/exampleplugin.conf'</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>Each plugin configuration file includes the enabled setting.
Some plugins also require additional settings. To determine the
correct settings, either refer to the documentation supplied with
@@ -140,10 +141,6 @@
anotheroption=0
]]>
</screen>
- <para>Example 3. Example Plugin Configuration File</para>
- <para>
- <anchor id="useful_plugins_for_fedora_users" />
- </para>
</section>
<section id="sn-UsefulYumPlugins">
<title>Useful Plugins for Fedora Users</title>
@@ -175,7 +172,7 @@
<title>Fastest Mirror Plugin</title>
<para>Yum in Fedora uses a dynamic server side
<ulink url="http://fedoraproject.org/wiki/Infrastructure/MirrorManagement">
- mirror management infrastructure</ulink>that distributes the
+ mirror management infrastructure</ulink> that distributes the
bandwidth consumptions on each of these mirrors by automatically
directing the update to one of the geographically closest
mirrors. This mirror is automatically checked against the master
@@ -186,14 +183,12 @@
faster ones for package downloads. This plugin is not installed
by default. For installing it, use the following command or from
the
- <emphasis>Applications</emphasis>menu use
- <emphasis>Add/Remove Software".</emphasis></para>
- <screen>
- <![CDATA[su -c 'yum install yum-fastestmirror'
- ]]>
- </screen>
- <para>You can configure various settings of this plugin in the
- file /etc/yum/pluginconf.d/fastestmirror.conf</para>
+ <guimenu>Applications</guimenu> menu use
+ <guimenuitem>Add/Remove Software"</guimenuitem>.</para>
+ <para><command>su -c 'yum install
+ yum-fastestmirror'</command></para>
+ <para>You can configure various settings of this plugin in the file
+ <filename>/etc/yum/pluginconf.d/fastestmirror.conf</filename></para>
</section>
<section id="sn-YumPluginDownloadonly">
<title>Downloadonly Plugin</title>
@@ -208,12 +203,11 @@
software package change log. This plugin helps you see the
package changelog before doing a update. This plugin is not
installed by default. For installing it, use the following
- command or from the Applications
- <emphasis>menu use</emphasis>Add/Remove Software".</para>
- <screen>
- <![CDATA[su -c 'yum install yum-changelog'
- ]]>
- </screen>
+ command or from the <guimenu>Applications
+ </guimenu>menu use<guimenuitem>Add/Remove
+ Software"</guimenuitem>.</para>
+ <para><command>su -c 'yum install
+ yum-changelog'</command></para>
<para>Sample output:</para>
<screen>
<![CDATA[su -c 'yum update frysk --changelog'
@@ -331,20 +325,15 @@
configuration file. The skip-broken plugin helps do that. This
plugin is not installed by default. For installing it, use the
following command or from the
- <emphasis>Applications</emphasis>menu use
- <emphasis>Add/Remove Software".</emphasis></para>
- <screen>
- <![CDATA[su -c 'yum install yum-skip-broken'
- ]]>
- </screen>
+ <guimenu>Applications</guimenu> menu use
+ <guimenuitem>Add/Remove Software".</guimenuitem></para>
+ <para><command>su -c 'yum install
+ yum-skip-broken'</command></para>
<para>You can use this plugin doing a update by specifying the
following command line argument.</para>
- <screen>
- <![CDATA[su -c 'yum update --skip-broken'
- ]]>
- </screen>
+ <para><command>su -c 'yum update --skip-broken'</command></para>
<para>You can disable this plugin by changing the option in the
- file /etc/yum/pluginconf.d/skip-broken.conf</para>
+ file <filename>/etc/yum/pluginconf.d/skip-broken.conf</filename></para>
</section>
<section id="sn-YumPluginAllowdowngrade">
<title>Allowdowngrade Plugin</title>
@@ -357,31 +346,22 @@
update. This plugin adds the ability to perform downgrades of
packages in Fedora. This plugin is not installed by default. For
installing it, use the following command or from the
- <emphasis>Applications</emphasis>menu use
- <emphasis>Add/Remove Software</emphasis>.</para>
- <screen>
- <![CDATA[su -c 'yum install yum-allowdowngrade'
- ]]>
- </screen>
+ <guimenu>Applications</guimenu> menu use
+ <guimenuitem>Add/Remove Software</guimenuitem>.</para>
+ <para><command>su -c 'yum install
+ yum-allowdowngrade'</command></para>
<para>You can use this plugin doing a update by specifying the
following command line argument.</para>
- <screen>
- <![CDATA[su -c 'yum update -allow-downgrade'
- ]]>
- </screen>
+ <para><command>su -c 'yum update
+ -allow-downgrade'</command></para>
<para>You can disable this plugin by changing the option in the
- file /etc/yum/pluginconf.d/allowdowngrade.conf</para>
+ file <filename>/etc/yum/pluginconf.d/allowdowngrade.conf</filename></para>
</section>
<section id="sn-DisablingPlugins">
<title>Disabling All Plugins</title>
<para>If you would like to disable all the plugins while running
Yum, you can use the following command line argument</para>
- <para />
- <screen>
- <![CDATA[su -c 'yum update --noplugins'
- ]]>
- </screen>
- <para />
+ <para><command>su -c 'yum update --noplugins'</command></para>
</section>
<section id="sn-DevelopingPlugins">
<title>Developing New Plugins</title>
@@ -392,7 +372,7 @@
http://wiki.linux.duke.edu/WritingYumPlugins</ulink>. Join the
yum development list at
<ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum-devel">
- https://lists.dulug.duke.edu/mailman/listinfo/yum-devel</ulink>to
+ https://lists.dulug.duke.edu/mailman/listinfo/yum-devel</ulink> to
collaborate with Yum developers.</para>
</section>
</section>
Index: isolated-install.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/isolated-install.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- isolated-install.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ isolated-install.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -12,10 +12,10 @@
<section id="sn-IsolatedInstall">
<title>Installing Software from an Isolated Package</title>
<para>Use repositories and the standard
- <code>yum</code>commands to locate and install new software, unless
+ <application>yum</application> commands to locate and install new software, unless
the software package is not available from any repository. In these
cases, use the
- <code>localinstall</code>function to install the software from the
+ <literal>localinstall</literal> function to install the software from the
package file.</para>
<important>
<title>Public Key is Required</title>
@@ -25,21 +25,22 @@
<xref linkend="sn-ManuallyAuthorizing" />.</para>
</important>
<para>Enter this command to install the package
- <code>tsclient-0.132-4.i386.rpm</code>:</para>
+ <package>tsclient-0.132-4.i386.rpm</package>:</para>
<para>
- <code>su -c 'yum localinstall tsclient-0.132-4.i386.rpm'</code>
+ <command>su -c 'yum localinstall
+ tsclient-0.132-4.i386.rpm'</command>
</para>
<para>At the prompt, enter the
- <emphasis>root</emphasis>password.</para>
+ <systemitem class="username">root</systemitem> password.</para>
<note>
<title>Previously Installed Software is Updated</title>
<para>If the package provides a later version of software that is
already installed on your system,
- <code>yum</code>updates the installed software.</para>
+ <application>yum</application> updates the installed software.</para>
</note>
<para>If the package requires software that is not installed on your
system,
- <code>yum</code>attempts to meet the dependencies with packages from
+ <application>yum</application> attempts to meet the dependencies with packages from
the configured repositories. You may need to manually download and
install additional packages in order to satisfy all of the
dependencies.</para>
@@ -47,7 +48,7 @@
<title>Maintaining Manually Installed Software</title>
<para>If you install software that is not provided by a repository,
- <code>yum update</code>cannot automatically upgrade it as new
+ <command>yum update</command> cannot automatically upgrade it as new
versions become available. To ensure that you have the latest
packages, subscribe to e-mail or RSS services that notify you when
new versions are released.</para>
Index: manage-with-yum.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/manage-with-yum.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- manage-with-yum.xml 24 Jan 2008 01:48:01 -0000 1.3
+++ manage-with-yum.xml 24 Jan 2008 03:18:03 -0000 1.4
@@ -71,8 +71,6 @@
Total download size: 355 k
Is this ok [y/N]:]]>
</screen>
- <para>Example 1. Format of
- <application>yum</application> Transaction Reports</para>
<para>Review the list of changes, and then press
<keycap>Y</keycap> to accept and begin the
process. If you press
@@ -97,8 +95,6 @@
Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora(a)redhat.com>"
Is this ok [y/N]:]]>
</screen>
- <para>Example 2. Format of
- <application>yum</application> Public Key Import</para>
<para>Check the public key, and then press
<keycap>Y</keycap> to import the key and authorize
the key for use. If you press
Index: pirut.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/pirut.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pirut.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ pirut.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -12,55 +12,55 @@
<section id="sn-Pirut">
<title>Managing Software with Pirut</title>
<para>This section explains
- <emphasis role="strong">Pirut</emphasis>, Fedora's graphical package
+ <application>Pirut</application>, Fedora's graphical package
management program. It demonstrates the different search facilities
within
- <emphasis role="strong">Pirut</emphasis>and how to install a package.
+ <application>Pirut</application> and how to install a package.
The
- <emphasis role="strong">Banshee</emphasis>music management package is
+ <application>Banshee</application> music management package is
used as an example.</para>
<para />
<section id="sn-BrowseSoftware">
<title>Browse Software</title>
<para>Start
- <emphasis role="strong">Pirut</emphasis>by selecting the
- <emphasis>Add/Remove Programs</emphasis>entry in the
- <emphasis>Applications</emphasis>menu, entering your
- <code>root</code>password when prompted.</para>
+ <application>Pirut</application> by selecting the
+ <guimenuitem>Add/Remove Programs</guimenuitem> entry in the
+ <guimenu>Applications</guimenu> menu, entering your
+ <systemitem class="username">root</systemitem> password when prompted.</para>
<para>The program starts in
- <emphasis>Browse</emphasis>view by default. This view organizes
+ <literal>Browse</literal> view by default. This view organizes
packages into related groups, displaying top level groups on the
left and sub-categories on the right. When a tick is present next
to a sub-category, it indicates applications from that group are
installed.</para>
<para>To install
- <emphasis role="strong">Banshee</emphasis>, select the
- <emphasis>Sound and Video</emphasis>sub-category and press the
- <emphasis>Optional Packages</emphasis>button. Locate
- <emphasis role="strong">Banshee</emphasis>in the list and queue it
+ <application>Banshee</application>, select the
+ <literal>Sound and Video</literal> sub-category and press the
+ <guibutton>Optional Packages</guibutton> button. Locate
+ <application>Banshee</application> in the list and queue it
for installation by ticking its box with a left-click. As many
packages as desired can be queued for installation by ticking the
appropriate boxes.</para>
<para>To add packages from other groups or sub-categories to the
queue, browse to the desired group or sub-category and proceed as
before. The
- <emphasis>Optional Packages</emphasis>button is only available when
+ <guibutton>Optional Packages</guibutton> button is only available when
the desired sub-category is ticked. Ticking a previously un-ticked
sub-category automatically queues for installation any packages
required for that sub-category.</para>
<para>To install the queued packages press the
- <emphasis>Apply</emphasis>button.</para>
+ <guibutton>Apply</guibutton> button.</para>
<note>
<title>Removing packages</title>
<para>Remove packages by un-ticking the appropriate boxes and
pressing the
- <emphasis>Apply</emphasis>button.</para>
+ <guibutton>Apply</guibutton> button.</para>
</note>
</section>
<section id="sn-Dependencies">
<title>Dependencies</title>
<para>After applying changes,
- <emphasis role="strong">Pirut</emphasis>prompts to confirm the
+ <application>Pirut</application> prompts to confirm the
packages you have selected. Proceed if the list is correct,
otherwise cancel and refine the selection.</para>
<note>
@@ -69,7 +69,7 @@
package to function correctly.</para>
</note>
<para>
- <emphasis role="strong">Pirut</emphasis>now resolves any
+ <application>Pirut</application> now resolves any
dependencies. A dialog informs you which dependencies have been
found, and are automatically marked for installation. Confirm this
list to proceed.</para>
@@ -77,7 +77,7 @@
<title>Dependencies can be removed</title>
<para>When a package is removed it is possible other packages may
have relied on it to function correctly. If this is the case
- <emphasis role="strong">Pirut</emphasis>also removes these other
+ <application>Pirut</application> also removes these other
applications. Check the dependency dialog and cancel if any of
the packages marked for removal are still needed. This can be
corrected by refining your package selection.</para>
@@ -86,19 +86,19 @@
<section id="sn-SearchSoftware">
<title>Search Software</title>
<para>When the desired application's name is known, the
- <emphasis>Search</emphasis>tab is more efficient.</para>
+ <literal>Search</literal> tab is more efficient.</para>
<para>Select the
- <emphasis>Search</emphasis>tab from the top of the window and enter
+ <literal>Search</literal> tab from the top of the window and enter
- <emphasis role="strong">Banshee</emphasis>into the search box.
+ <literal>Banshee</literal> into the search box.
Press enter to begin the search. Results, including related
packages, are shown in the box below. To find more information
about a package before installation, highlight it with a left-click
and press the
- <emphasis>Package Details</emphasis>text below.</para>
+ <literal>Package Details</literal> text below.</para>
<para>To queue a package for installation or removal, toggle its
box as appropriate. Once all the packages have been selected press
- <emphasis>Apply</emphasis>.</para>
+ <guibutton>Apply</guibutton>.</para>
<para />
</section>
<section id="sn-ListSoftware">
@@ -106,7 +106,7 @@
<para>The list tab displays all available packages. Packages can be
queued for installation or removal in the same manner as before.
Once satisfied with the selections, press the
- <emphasis>Apply</emphasis>button to commit the changes.</para>
+ <guibutton>Apply</guibutton> button to commit the changes.</para>
</section>
</section>
<!--
Index: pup.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/pup.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pup.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ pup.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -12,15 +12,15 @@
<section id="sn-Pup">
<title>Updating Software With Pup</title>
<para>This chapter explains how to use the
- <emphasis role="strong">Pup</emphasis>graphical update program, and
+ <application>Pup</application> graphical update program, and
how
- <emphasis role="strong">Puplet</emphasis>works to provide
+ <application>Puplet</application> works to provide
notifications of available updates.</para>
<para />
<section id="sn-UpdateNotifications">
<title>Update Notifications</title>
<para>
- <emphasis role="strong">Puplet</emphasis>works constantly in the
+ <application>Puplet</application> works constantly in the
background, checking for available software updates from the
enabled repositories. When updates become available a package icon
appears in the notification area, along with an alert which appears
@@ -31,24 +31,24 @@
<itemizedlist>
<listitem>
<para>
- <emphasis>Refresh</emphasis>will check for new updates</para>
+ <literal>Refresh</literal> will check for new updates</para>
</listitem>
<listitem>
<para>
- <emphasis>View Updates</emphasis>launches
- <emphasis role="strong">Pup</emphasis>and allows you to find
+ <literal>View Updates</literal> launches
+ <application>Pup</application> and allows you to find
more details about the packages to be updated, to de-select
some updates, and to start the update process</para>
</listitem>
<listitem>
<para>
- <emphasis>Apply Updates</emphasis>
+ <literal>Apply Updates</literal>
</para>
</listitem>
<listitem>
<para>
- <emphasis>Quit</emphasis>closes
- <emphasis role="strong">Puplet</emphasis>until the next time
+ <literal>Quit</literal> closes
+ <application>Puplet</application> until the next time
the system starts</para>
</listitem>
</itemizedlist>
@@ -58,7 +58,7 @@
<title>The Package Updater</title>
<para>This program features a scrollable text window under the
heading
- <emphasis>Updates available</emphasis>. In this text window all of
+ <literal>Updates available</literal>. In this text window all of
the available updates are listed, and all are selected by default.
If you want to remove any of the packages queued for update, left
click the ticked box next to the relevant package.</para>
@@ -67,14 +67,14 @@
system reboot.</para>
<para>Further information about the updates can be found by
selecting the desired package, then left clicking the
- <emphasis>Update Details</emphasis>text.</para>
+ <literal>Update Details</literal> text.</para>
<para>Once satisfied with the package selection left click the
- <emphasis>Apply Updates</emphasis>button. Pup checks for
+ <guibutton>Apply Updates</guibutton> button. Pup checks for
dependencies, ensuring that the updated packages will have
everything required to function correctly. If dependencies are
added a dialogue will be displayed informing you which new packages
are set to be installed. Review this dialog and click
- <emphasis>Continue</emphasis>if it is OK.</para>
+ <guibutton>Continue</guibutton> if it is OK.</para>
<para>The packages will then be downloaded and installed. If a
reboot is needed for some of the changes to take place, you will be
informed of this at the end of the updates.</para>
Index: update-with-yum.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/update-with-yum.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- update-with-yum.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ update-with-yum.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -11,7 +11,7 @@
]>
<section id="sn-UpdateWithYum">
<title>Updating Your System with
- <code>yum</code></title>
+ <application>yum</application></title>
<para>Use the update option to upgrade all of your Fedora system
software to the latest version with one operation.</para>
<para>To perform a full system update, type this command:</para>
@@ -19,7 +19,7 @@
<command>su -c 'yum update'</command>
</para>
<para>At the prompt, enter the
- <emphasis>root</emphasis>password.</para>
+ <systemitem class="username">root</systemitem> password.</para>
<para />
<section id="sn-AutoUpdates">
<title>Automatically Updating Your System</title>
@@ -32,7 +32,7 @@
/sbin/service yum-updatesd start'</command>
</para>
<para>At the prompt, enter the password for the
- <emphasis>root</emphasis>account.</para>
+ <systemitem class="username">root</systemitem> account.</para>
</section>
</section>
<!--
Index: yum-caching.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-caching.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- yum-caching.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ yum-caching.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -12,21 +12,21 @@
<section id="sn-YumCaching">
<title>Working with yum Caching</title>
<para>By default, current versions of
- <code>yum</code>delete the data files and packages that they
+ <application>yum</application> delete the data files and packages that they
download, after these have been successfully used for an operation.
This minimizes the amount of storage space that
- <code>yum</code>uses. You may enable caching, so that
- <code>yum</code>retains the files that it downloads in cache
+ <application>yum</application> uses. You may enable caching, so that
+ <application>yum</application> retains the files that it downloads in cache
directories.</para>
<para>Caches provide three advantages:</para>
<itemizedlist>
<listitem>
<para>The performance of
- <code>yum</code>increases</para>
+ <application>yum</application> increases</para>
</listitem>
<listitem>
<para>You may carry out
- <code>yum</code>operations without a network connection, by using
+ <application>yum</application> operations without a network connection, by using
only the caches</para>
</listitem>
<listitem>
@@ -35,19 +35,20 @@
</listitem>
</itemizedlist>
<para>By default,
- <code>yum</code>stores temporary files under the directory
- <code>/var/cache/yum/</code>, with one subdirectory for each
+ <application>yum</application> stores temporary files under the directory
+ <filename class="directory">/var/cache/yum/</filename>, with one subdirectory for each
configured repository. The
- <code>packages/</code>directory within each repository directory
+ <filename class="directory">packages/</filename> directory within each repository directory
holds the cached packages. For example, the directory
- <code>/var/cache/yum/development/packages/</code>holds packages
+ <filename
+ class="directory">/var/cache/yum/development/packages/</filename> holds packages
downloaded from the development repository.</para>
<note>
<title role="strong">Clearing the
- <code>yum</code>Caches</title>
+ <application>yum</application> Caches</title>
<para>Cached files use disk space until removed. You may wish to
periodically clear the
- <code>yum</code>caches to recover capacity. Refer to
+ <application>yum</application> caches to recover capacity. Refer to
<xref linkend="sn-YumCaching" />for information on clearing the
caches.</para>
</note>
@@ -56,20 +57,21 @@
<section id="sn-EnablingCaches">
<title>Enabling the Caches</title>
<para>To configure
- <code>yum</code>to retain downloaded files rather than discarding
+ <application>yum</application> to retain downloaded files rather than discarding
them, set the
- <code>keepcache</code>option in
- <code>/etc/yum.conf</code>to
- <code>1</code>:</para>
- <para>
- <code>keepcache=1</code>
- </para>
+ <literal>keepcache</literal> option in
+ <filename>/etc/yum.conf</filename> to
+ <literal>1</literal>:</para>
+ <screen>
+ <![CDATA[keepcache=1
+ ]]>
+ </screen>
<para>Refer to
<xref linkend="sn-CustomizingYum" />for more information on editing
the
- <code>yum</code>configuration file.</para>
+ <application>yum</application> configuration file.</para>
<para>Once you enable caching, every
- <code>yum</code>operation may download package data from the
+ <application>yum</application> operation may download package data from the
configured repositories. To ensure that the caches have a set of
package data, carry out an operation after you enable caching. Use
a list or search query to download package data without modifying
@@ -79,46 +81,46 @@
<section id="sn-CacheOnlyMode">
<title>Using yum in Cache-only Mode</title>
<para>To carry out a
- <code>yum</code>command without a network connection, add the
- <code>-C</code>option. This causes
- <code>yum</code>to proceed without checking any network
+ <application>yum</application> command without a network connection, add the
+ <literal>-C</literal> option. This causes
+ <application>yum</application> to proceed without checking any network
repositories, and use only cached files. In this mode, yum may only
install packages that have been downloaded and cached by a previous
operation.</para>
<para>To search for the package
- <code>tsclient</code>without using a network connection, enter the
+ <package>tsclient</package> without using a network connection, enter the
command:</para>
<para>
- <code>su -c 'yum -C list tsclient'</code>
+ <command>su -c 'yum -C 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>
<note>
<title>Cache-only Mode Requires Cached Data</title>
<para>Cache-only mode requires package data to exist in the
caches. If you enable caching, every
- <code>yum</code>operation may update the data files, unless
+ <application>yum</application> operation may update the data files, unless
cache-only mode is specified for the operation.</para>
</note>
</section>
<section id="sn-ClearingCaches">
<title>Clearing the yum Caches</title>
<para>If you configure it to do so,
- <code>yum</code>retains the packages and package data files that it
+ <application>yum</application> retains the packages and package data files that it
downloads, so that they may be reused in future operations without
being downloaded again. To purge the package data files, use this
command:</para>
<para>
- <code>su -c 'yum clean headers'</code>
+ <command>su -c 'yum clean headers'</command>
</para>
<para>Run this command to remove all of the packages held in the
caches:</para>
<para>
- <code>su -c 'yum clean packages'</code>
+ <command>su -c 'yum clean packages'</command>
</para>
<para>When using these commands, at the prompt, enter the password
for the
- <emphasis>root</emphasis>account.</para>
+ <systemitem class="username">root</systemitem> account.</para>
<para>Purging cached files causes those files to downloaded again
the next time that they are required. This increases the amount of
time required to complete the operation.</para>
Index: yum-proxy.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-proxy.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- yum-proxy.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ yum-proxy.xml 24 Jan 2008 03:18:03 -0000 1.3
@@ -12,42 +12,42 @@
<section id="sn-YumProxy">
<title>Using yum with a Proxy Server</title>
<para>By default,
- <code>yum</code>accesses network repositories with HTTP. All
- <code>yum</code>HTTP operations use HTTP/1.1, and are compatible with
+ <application>yum</application> accesses network repositories with HTTP. All
+ <application>yum</application> HTTP operations use HTTP/1.1, and are compatible with
web proxy servers that support this standard. You may also access FTP
repositories, and configure
- <code>yum</code>to use an FTP proxy server. The
- <code>squid</code>package provides a proxy service for both HTTP/1.1
+ <application>yum</application> to use an FTP proxy server. The
+ <package>squid</package> package provides a proxy service for both HTTP/1.1
and FTP connections.</para>
<note>
<title>Modifying
- <code>yum</code>for Network Compatibility</title>
+ <application>yum</application> for Network Compatibility</title>
<para>Refer to the
- <code>man</code>page for
- <code>yum.conf</code>for information on HTTP settings that may be
+ <application>man</application> page for
+ <filename>yum.conf</filename> for information on HTTP settings that may be
modified for compatibility with nonstandard web proxy servers.
Alternatively, configure
- <code>yum</code>to use an FTP proxy server, and access repositories
+ <application>yum</application> to use an FTP proxy server, and access repositories
that support FTP. The Fedora repositories support both HTTP and
FTP.</para>
</note>
<section id="sn-ConfiguringProxy">
<title>Configuring Proxy Server Access</title>
<para>To enable all
- <code>yum</code>operations to use a proxy server, specify the proxy
+ <application>yum</application> operations to use a proxy server, specify the proxy
server details in
- <code>/etc/yum.conf</code>. The proxy setting must specify the
+ <filename>/etc/yum.conf</filename>. The proxy 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
- <code>proxy_username</code>and
- <code>proxy_password</code>settings.</para>
+ <literal>proxy_username</literal> and
+ <literal>proxy_password</literal> settings.</para>
<para>The settings below enable yum to use the proxy server
- <code>mycache.mydomain.com</code>, connecting to port 3128, with
+ <replaceable>mycache.mydomain.com</replaceable>, connecting to
+ port <replaceable>3128</replaceable>, with
the username
- <code>yum-user</code>and the password
- <code>qwerty</code>.</para>
- <para />
+ <replaceable>yum-user</replaceable> and the password
+ <replaceable>qwerty</replaceable>.</para>
<screen>
<![CDATA[# The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
@@ -56,19 +56,17 @@
proxy_password=qwerty
]]>
</screen>
- <para>Example 4. Configuration File Settings for Using A Proxy
- Server</para>
<note>
<para>Older versions of yum may require a "/" after the port
number:
- <code>proxy=http://mycache.mydomain.com:3128/</code></para>
+ <literal>proxy=http://mycache.mydomain.com:3128/</literal></para>
</note>
<note>
<title>Global Settings</title>
<para>If you define a proxy server in
- <code>/etc/yum.conf</code>, all users connect to the proxy server
+ <filename>/etc/yum.conf</filename>, all users connect to the proxy server
with those details when using
- <code>yum</code>.</para>
+ <application>yum</application>.</para>
</note>
<para />
</section>
@@ -76,10 +74,11 @@
<title>Configuring Proxy Server Access for a Single User</title>
<para>To enable proxy access for a specific user, add the lines in
the example box below to the user's shell profile. For the default
- <code>bash shell</code>, the profile is the file
- <code>~/.bash_profile</code>. The settings below enable
- <code>yum</code>to use the proxy server
- <code>mycache.mydomain.com</code>, connecting to port 3128.</para>
+ <application>bash shell</application>, the profile is the file
+ <filename>~/.bash_profile</filename>. The settings below enable
+ <application>yum</application> to use the proxy server
+ <replaceable>mycache.mydomain.com</replaceable>, connecting to
+ port <replaceable>3128</replaceable>.</para>
<para />
<screen>
<![CDATA[# The Web proxy server used by this account
@@ -87,27 +86,25 @@
export http_proxy
]]>
</screen>
- <para>Example 5. Profile Settings for Using a Proxy Server</para>
<para>If the proxy server requires a username and password, add
these to the URL. To include the username
- <code>yum-user</code>and the password
- <code>qwerty</code>, add these settings:</para>
+ <replaceable>yum-user</replaceable> and the password
+ <replaceable>qwerty</replaceable>, add these settings:</para>
<para />
<screen>
<![CDATA[# The Web proxy server, with the username and password for this account
http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
export http_proxy ]]>
</screen>
- <para>Example 6. Profile Settings for a Secured Proxy Server</para>
<note>
<title>The
- <code>http_proxy</code>Environment Variable</title>
+ <literal>http_proxy</literal> Environment Variable</title>
<para>The
- <code>http_proxy</code>environment variable is also used by
- <code>curl</code>and other utilities. Although
- <code>yum</code>itself may use
- <code>http_proxy</code>in either upper-case or lower-case,
- <code>curl</code>requires the name of the variable to be in
+ <literal>http_proxy</literal> environment variable is also used by
+ <application>curl</application> and other utilities. Although
+ <application>yum</application> itself may use
+ <literal>http_proxy</literal> in either upper-case or lower-case,
+ <application>curl</application> requires the name of the variable to be in
lower-case.</para>
</note>
</section>
16 years, 3 months
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
by fedora-docs-commits@redhat.com
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>
<!--
16 years, 3 months
yum-software-management/en_US concepts.xml, 1.6, 1.7 introduction.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1317
Modified Files:
concepts.xml introduction.xml
Log Message:
Start fixing up more of the tags from the wiki import, specifically things marked with emphasis and code tags
Index: concepts.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/concepts.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- concepts.xml 22 Jan 2008 03:04:01 -0000 1.6
+++ concepts.xml 23 Jan 2008 19:06:48 -0000 1.7
@@ -38,9 +38,9 @@
</section>
<section id="sn-AboutRepositories">
<title>About Repositories</title>
- <para>A <emphasis>repository</emphasis> is a prepared directory or
+ <para>A <firstterm>repository</firstterm> is a prepared directory or
Web site that contains software packages and index files. Software
- management utilities such as <code>yum</code> automatically locate
+ 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
Index: introduction.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/introduction.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- introduction.xml 22 Jan 2008 03:34:05 -0000 1.2
+++ introduction.xml 23 Jan 2008 19:06:48 -0000 1.3
@@ -13,23 +13,23 @@
<section id="sn-AboutDocument">
<title>About this Document</title>
<para>
- <emphasis>Purpose</emphasis>: How to install and update software
+ <emphasis role="strong">Purpose</emphasis>: How to install and update software
packages from the desktop and the CLI.</para>
<para>
- <emphasis>Audience</emphasis>: Individuals who are unfamiliar with
+ <emphasis role="strong">Audience</emphasis>: Individuals who are unfamiliar with
software package management in Fedora.</para>
<para>
- <emphasis>Approach</emphasis>: Explain basic principles; explain
+ <emphasis role="strong">Approach</emphasis>: Explain basic principles; explain
one principle at a time; do not assume familiarity with any
Linux/UNIX-specific terminology or concepts; compare functionality
where appropriate to what the reader may know from other operating
systems, particularly Microsoft Windows.</para>
<para>
- <emphasis>Assumptions:</emphasis>The reader has a default
+ <emphasis role="strong">Assumptions</emphasis>: The reader has a default
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
+ <emphasis role="strong">does</emphasis> have access to the
+ <emphasis>root</emphasis> password. The user does not have a degree
in Computer Science.</para>
</section>
<section id="sn-UsingDocument">
@@ -62,48 +62,48 @@
<tip>
<title>Previous Versions of Fedora</title>
<para>This document describes the configuration of
- <code>yum</code>on current versions of Fedora. You must perform
+ <application>yum</application> on current versions of Fedora. You must perform
the additional step noted in
<xref linkend="sn-ManuallyAuthorizing" />to enable
- <code>yum</code>on earlier versions Fedora.</para>
+ <application>yum</application> on earlier versions Fedora.</para>
</tip>
<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.
+ <code>root</code> 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
- <code>su -c</code>to provide this facility. Graphical
+ <code>root</code> access will prompt you for the
+ <code>root</code> 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>
</warning>
<para>Most of the examples in this document use the package
- <code>tsclient</code>, which is included with Fedora. The
- <code>tsclient</code>package provides an application for remote
+ <package>tsclient</package>, which is included with Fedora. The
+ <package>tsclient</package> package provides an application for remote
desktop access. The example commands for Fedora package groups use
the
- <code>MySQL Database</code>group. To use the examples, substitute
+ <application>MySQL Database</application> group. To use the examples, substitute
the name of the relevant package for
- <code>tsclient</code>.</para>
+ <package>tsclient</package>.</para>
<para>Fedora includes a
- <code>yum</code>configuration that is suitable for independent
+ <application>yum</application> configuration that is suitable for independent
systems with Internet access. You may use
- <code>yum</code>and related software on such systems without any
+ <application>yum</application> and related software on such systems without any
additional configuration.</para>
<para>If your system is part of a managed network, consult your
network administrators for advice. You may need to configure
- <code>yum</code>to use a network proxy server.
+ <application>yum</application> to use a network proxy server.
<xref linkend="sn-YumProxy" />explains how to configure
- <code>yum</code>to use a proxy server. Administrators may also
+ <application>yum</application> to use a proxy server. Administrators may also
suggest or require that
- <code>yum</code>clients use specific package repositories. Refer to
+ <application>yum</application> clients use specific package repositories. Refer to
<xref linkend="sn-ConfiguringRepositories" />for instructions on
how to configure access to repositories.</para>
<para>To improve performance and enable disconnected operations,
activate the
- <code>yum</code>caches on your system. Refer to
+ <application>yum</application> caches on your system. Refer to
<xref linkend="sn-YumCaching" />for more information on the caching
option.</para>
<para />
@@ -111,20 +111,20 @@
<section id="sn-AdditionalResources">
<title>Additional Resources</title>
<para>The
- <code>yum</code>utility has features and options not discussed in
+ <application>yum</application> utility has features and options not discussed in
this document. Read the
- <code>man</code>pages for
- <code>yum(8)</code>and
- <code>yum.conf(5)</code>to learn more, using the following
+ <application>man</application> pages for
+ <application>yum(8)</application> and
+ <filename>yum.conf(5)</filename> to learn more, using the following
commands:</para>
<para>
- <code>man yum</code>
+ <command>man yum</command>
</para>
<para>
- <code>man yum.conf</code>
+ <command>man yum.conf</command>
</para>
<para>Other useful
- <code>yum</code>resources on the Internet include:</para>
+ <application>yum</application> resources on the Internet include:</para>
<para>Project Web site</para>
<itemizedlist>
<listitem>
@@ -157,12 +157,12 @@
<para>If you encounter a persistent error with a specific
operation, visit
<ulink url="https://bugzilla.redhat.com">
- https://bugzilla.redhat.com</ulink>and review the bug reports for
+ https://bugzilla.redhat.com</ulink> and review the bug reports for
the package or packages involved. An error in a package may cause
all
- <code>yum</code>operations that rely on that package to fail.
+ <application>yum</application> operations that rely on that package to fail.
Please file bug reports for Fedora packages, including
- <code>yum</code>, on this Bugzilla web site.</para>
+ <application>yum</application>, on this Bugzilla web site.</para>
</important>
</section>
</section>
16 years, 3 months