docs-commits July 2005

docs-commits@lists.fedoraproject.org

1 participants
71 discussions

docs-common/css fedora.css,1.6,1.7
by fedora-docs-commits＠redhat.com 30 Jul '05

30 Jul '05

Author: pfrields Update of /cvs/docs/docs-common/css In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11316 Modified Files: fedora.css Log Message: Better agreement with the official web site color scheme Index: fedora.css =================================================================== RCS file: /cvs/docs/docs-common/css/fedora.css,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- fedora.css 29 Jul 2005 17:47:45 -0000 1.6 +++ fedora.css 30 Jul 2005 01:44:15 -0000 1.7 @@ -72,21 +72,31 @@ h1, h2, h3, h4 { font-family: luxi sans,sans-serif; - color: #172e56; + color: #22437f; font-weight: bold; } h1 { font-size: 1.75em; } - + h2 { font-size: 1.25em; } - + h3 { font-size: 1.1em; } +a:link { + color: #900; +} +a:visited { + color: #48468f; +} +a:hover { + color: #f20; +} + code.screen, pre.screen { font-family: monospace; font-size: 1em;

1 0

docs-common/css fedora.css,1.5,1.6
by fedora-docs-commits＠redhat.com 29 Jul '05

29 Jul '05

Author: pfrields Update of /cvs/docs/docs-common/css In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4191 Modified Files: fedora.css Log Message: Heading and admonition color changes to provide new Fedora branded feel Index: fedora.css =================================================================== RCS file: /cvs/docs/docs-common/css/fedora.css,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- fedora.css 18 May 2005 02:05:51 -0000 1.5 +++ fedora.css 29 Jul 2005 17:47:45 -0000 1.6 @@ -39,8 +39,8 @@ div.note table, div.tip table, div.important table, div.caution table, div.warning table { width: 95%; - border: 2px solid #B0C4DE; - background-color: #F0F8FF; + border: 2px solid #D0D0B0; + background-color: #FAF9E0; color: #000000; /* padding inside table area */ padding: 0.5em; @@ -72,7 +72,7 @@ h1, h2, h3, h4 { font-family: luxi sans,sans-serif; - color: #990000; + color: #172e56; font-weight: bold; } h1 {

1 0

securing-filesystems securing-filesystems-en.xml,1.1,1.2
by fedora-docs-commits＠redhat.com 29 Jul '05

29 Jul '05

Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32351/securing-filesystems Modified Files: securing-filesystems-en.xml Log Message: Structural changes of the document model. Index: securing-filesystems-en.xml =================================================================== RCS file: /cvs/docs/securing-filesystems/securing-filesystems-en.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- securing-filesystems-en.xml 24 Jul 2005 00:08:23 -0000 1.1 +++ securing-filesystems-en.xml 29 Jul 2005 15:02:56 -0000 1.2 @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="US-ASCII"?>   - + @@ -12,52 +12,51 @@    - + <!ENTITY doccvs "$Id$"> <!ENTITY docpubid "Securing Filesystems"> <!ENTITY docsyspath "/home/thomas/projects/docs/cvsroot/securing-filesystems"> <!ENTITY docsysid "&docsyspath;/securing-filesystems-en.xml"> - - + +  - - <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.xml"> + + <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent"> %FEDORA-ENTITIES-EN; - + <!ENTITY REVID "0.3"> <!ENTITY BOOKID "securing-filesystems-&REVID; (2005-07-23-T18:49-0500)"> <!ENTITY BUG-NUM "157559"> - <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml"> - - +  - + <!ENTITY acl "<emphasis>Access Control List</emphasis>"> <!ENTITY acll "<acronym>acl</acronym>"> <!ENTITY aclu "<acronym>ACL</acronym>"> <!ENTITY author "<firstname>Thomas</firstname><othername>R.</othername> <surname>Jones</surname>"> - <!ENTITY author.mail "<address><email>thomasjones&commat;computer.org</email></address>"> + <!ENTITY author.mail "<address><email>thomasjones(a)computer.org</email></address>"> <!ENTITY ea "<emphasis>Extended Attributes</emphasis>"> <!ENTITY eau "<abbrev>EA</abbrev>"> + <!ENTITY fhs "<emphasis>Filesystem Hierarchy Standard</emphasis>"> + <!ENTITY fhsu "<abbrev>FHS</abbrev>"> <!ENTITY posix "<acronym>POSIX</acronym>"> - - + +  - - <!ENTITY pr-introduction SYSTEM "pr-introduction.xml"> - <!ENTITY ch-standards_compliance SYSTEM "ch-standards_compliance.xml"> - <!ENTITY ch-basic_characteristics SYSTEM "ch-basic_characteristics.xml"> - <!ENTITY ch-laying_foundation SYSTEM "ch-laying_foundation.xml"> - <!ENTITY ch-understanding_access_control SYSTEM "ch-understanding_access_control.xml"> - <!ENTITY ch-introducing_access_control SYSTEM "ch-introducing_access_control.xml"> - <!ENTITY ch-introducing_extended_attributes SYSTEM "ch-introducing_extended_attributes.xml"> - <!ENTITY ch-supplemental_packages SYSTEM "ch-supplemental_packages.xml"> - <!ENTITY ch-case_studies SYSTEM "ch-case_studies.xml"> - <!ENTITY ap-annotated_filesystem SYSTEM "ap-annotated_filesystem.xml"> - <!ENTITY ap-glossary_of_terminology SYSTEM "ap-glossary_of_terminology.xml"> - <!ENTITY ap-bibliography SYSTEM "ap-bibliography.xml"> - + + <!ENTITY sn-introduction SYSTEM "sn-introduction.xml"> + <!ENTITY ch-constitutes_filesystem SYSTEM "ch-constitutes_filesystem.xml"> + <!ENTITY ch-permissions SYSTEM "ch-permissions.xml"> + <!ENTITY ch-access_control SYSTEM "ch-access_control.xml"> + <!ENTITY ch-extended_attributes SYSTEM "ch-extended_attributes.xml"> + <!ENTITY ch-access_control_lists SYSTEM "ch-access_control_lists.xml"> + <!ENTITY ch-administration SYSTEM "ch-administration.xml"> + <!ENTITY ch-case_studies SYSTEM "ch-case_studies.xml"> + <!ENTITY ap-annotated_filesystem SYSTEM "ap-annotated_filesystem.xml"> + <!ENTITY ap-glossary_of_terminology SYSTEM "ap-glossary_of_terminology.xml"> + <!ENTITY ap-bibliography SYSTEM "ap-bibliography.xml"> +  ]> @@ -65,93 +64,90 @@ <book> <bookinfo> <title>&docpubid;</title> - <subtitle>Implementing effective filesystem permissions and access controls in Fedora</subtitle> + <subtitle> + Implementing effective filesystem permissions and access controls in Fedora + </subtitle> <authorgroup> <author>&author;<affiliation>&author.mail;</affiliation></author> </authorgroup> - + <abstract> <para> - This document provides a review of the concept and implementation of traditional - permissions, various access control methodologies, techniques and models to develop - effective safeguards to secure the filesystems of Fedora. + This document provides a review of the concept and implementation of + traditional permissions, various access control methodologies, techniques + and models to develop effective safeguards to secure the filesystems of + Fedora. &DRAFTNOTICE; - </para> + </para> </abstract> </bookinfo> - - + +  - - &pr-introduction; - - - -  - - &ch-standards_compliance; - - - + + &sn-introduction; + + +  - - &ch-basic_characteristics; - - - -  - - &ch-laying_foundation; - - - -  - - &ch-understanding_access_control; - - - -  - - &ch-introducing_access_control; - - - + + &ch-constitutes_filesystem; + + + +  + + &ch-permissions; + + + +  + + &ch-access_control; + + +  - - &ch-introducing_extended_attributes; - - - -  - - &ch-supplemental_packages; - - - + + &ch-extended_attributes; + + + +  + + &ch-access_control_lists; + + + +  + + +  - - &ch-case_studies; - - - + + &ch-case_studies; + + +  - + &ap-annotated_filesystem; - - - + + +  - + &ap-glossary_of_terminology; - - + +  - - &ap-bibliography; + + &ap-bibliography; </book> - + \ No newline at end of file

1 0

securing-filesystems sn-introduction.xml,NONE,1.1
by fedora-docs-commits＠redhat.com 29 Jul '05

29 Jul '05

Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31227/securing-filesystems Added Files: sn-introduction.xml Log Message: Initial commit to the Fedora Docs repository. --- NEW FILE sn-introduction.xml --- <?xml version="1.0" encoding="US-ASCII"?>     <preface id="sn-introduction"> <title>Introduction</title> <section id="sn-introduction-audience"> <title>Intended Audience</title> <para> This document is intended for all end-users of the fedora distribution. However it is my intention to present, as effectively as possible, this topic so that the following experienced audience can readily acquire valuable relevant information from this document as well: </para> <itemizedlist> <listitem><para>System Administrators</para></listitem> <listitem><para>Security Practitioners</para></listitem> <listitem><para>Power Users</para></listitem> </itemizedlist> </section> <section id="sn-introduction-current"> <title>Current Version</title> <para> The most current version of this document can be accessed at the following location: <ulink url="http://www.domain.com/docs/current/something.html"> http://www.domain.com/docs/current/something.html</ulink> </para> <para>This document is built from the following sources:</para> <variablelist> <varlistentry> <term><emphasis>Remote Development Versioning</emphasis></term> <listitem><para>&doccvs;</para></listitem> </varlistentry> <varlistentry> <term><emphasis>Local Development Identification</emphasis></term> <listitem><para>&docsysid;</para></listitem> </varlistentry> </variablelist> </section> <section id="sn-introduction-revision"> <title>Revision History</title> <para> <revhistory> <revision> <revnumber>&REVID;</revnumber> <date>2005-07-18</date> <authorinitials>TRJ</authorinitials> <revremark> Imported into fedora-docs CVS. Altered document outline. Added the character device content. </revremark> </revision> <revision> <revnumber>0.2</revnumber> <date>2005-05-13</date> <authorinitials>TRJ</authorinitials> <revremark> Bugzilla submission. Received bugid: &BUG-NUM;. Altered inclusive nature of the document title. </revremark> </revision> <revision> <revnumber>0.1</revnumber> <date>2005-05-04</date> <authorinitials>TRJ</authorinitials> <revremark> Initial draft for <emphasis>fedora-docs</emphasis> </revremark> </revision> </revhistory> </para> </section> <section id="sn-introduction-feedback"> <title>Feedback</title> <para> Have you found some missing information, missing links, or missing characters? Maybe you just have some comments and/or suggestions about this document? </para> <para> Mail it to the author of this document at the following address: &author.mail; </para> <para> Whenever possible please utilize the authors GnuPG key for these communications: </para> <para> KeyID: <computeroutput>1024D/57BF9042 2004-12-26 Thomas R. Jones ( IEEE Computer Society Account) <thomasjones&commat;computer.org></computeroutput> </para> <para> Fingerprint: <computeroutput>5264 BCA1 6059 57A8 58E5 7F04 A11E 5C13 57BF 9042</computeroutput> </para> </section> <section id="sn-introduction-copyright"> <title>Copyright Information</title> <para>Copyright 2005 Thomas R. Jones &author.mail;</para> </section> <section id="sn-introduction-legalnotice"> <title>Legal Information</title> &LEGALNOTICE-CONTENT; </section> <section id="sn-introduction-requirements"> <title>System Requirements</title> <para>List requirements&colon; materials, knowledge.</para> </section> <section id="sn-introduction-conventions"> <title>Document Conventions</title> <para> The following typographic and usage conventions occur in this document: </para> <table id="conventions-table" frame="all"> <title>Typographic and usage conventions</title> <tgroup cols="2" align="left" colsep="0" rowsep="0"> <thead> <row><entry>Text type</entry><entry>Meaning</entry></row> </thead> <tbody> <row> <entry><quote>Quoted text</quote></entry> <entry>Quotes from people, quoted computer output.</entry> </row> <row> <entry><screen>terminal view</screen></entry> <entry> Literal computer input and output captured from the terminal, usually rendered with a light grey background. </entry> </row> <row> <entry><command>command</command></entry> <entry> Name of a command that can be entered on the command line. </entry> </row> <row> <entry><varname>VARIABLE</varname></entry> <entry> Name of a variable or pointer to content of a variable, as in <varname>$VARNAME</varname>. </entry> </row> <row> <entry><option>option</option></entry> <entry> Option to a command, as in <quote>the <option>-a</option> option to the <command>ls</command> command</quote>. </entry> </row> <row> <entry><parameter>argument</parameter></entry> <entry> Argument to a command, as in <quote>read <command>man <parameter>ls</parameter></command></quote>. </entry> </row> <row> <entry> <cmdsynopsis> <command>command <option>options</option> <parameter>arguments</parameter></command> </cmdsynopsis> </entry> <entry> Command synopsis or general usage, on a separated line. </entry> </row> <row> <entry><filename>filename</filename></entry> <entry> Name of a file or directory, for example <quote>Change to the <filename>/usr/bin</filename> directory.</quote> </entry> </row> <row> <entry><keycap>Key</keycap></entry> <entry> Keys to hit on the keyboard, such as <quote>type <keycap>Q</keycap> to quit</quote>. </entry> </row> <row> <entry><guibutton>Button</guibutton></entry> <entry> Graphical button to click, like the <guibutton>OK</guibutton> button. </entry> </row> <row> <entry> <menuchoice> <guimenu>Menu</guimenu> <guimenuitem>Choice</guimenuitem> </menuchoice> </entry> <entry> Choice to select from a graphical menu, for instance&colon; <quote>Select <menuchoice> <guimenu>Help</guimenu> <guimenuitem>About Mozilla</guimenuitem> </menuchoice> in your browser.</quote> </entry> </row> <row> <entry><emphasis>Terminology</emphasis></entry> <entry> Important term or concept: <quote>The Linux <emphasis>kernel</emphasis> is the heart of the system.</quote> </entry> </row> <row> <entry>See ?????</entry> <entry>link to related subject within this guide.</entry> </row> <row> <entry> <ulink url="http://www.buddhalinux.com">The authors site</ulink> </entry> <entry>Clickable link to an external web resource.</entry> </row> </tbody> </tgroup> </table> </section> </preface>

1 0

yum-software-management yum-software-management-en.xml,1.31,1.32
by fedora-docs-commits＠redhat.com 28 Jul '05

28 Jul '05

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

1 0

yum-software-management yum-software-management-en.xml,1.30,1.31
by fedora-docs-commits＠redhat.com 28 Jul '05

28 Jul '05

Author: kwade Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7990 Modified Files: yum-software-management-en.xml Log Message: Bumping date for beta publication. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- yum-software-management-en.xml 27 Jul 2005 21:27:32 -0000 1.30 +++ yum-software-management-en.xml 28 Jul 2005 00:54:16 -0000 1.31 @@ -4,7 +4,7 @@ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent"> %FEDORA-ENTITIES-EN; -<!ENTITY BOOKID "yum-software-management-0.6 (2005-07-25)">  +<!ENTITY BOOKID "yum-software-management-0.6.1 (2005-07-27)">  <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">

1 0

yum-software-management yum-software-management-en.xml,1.29,1.30
by fedora-docs-commits＠redhat.com 27 Jul '05

27 Jul '05

Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2737 Modified Files: yum-software-management-en.xml Log Message: - Revised section on Repository Compatibility. - Style fix in Advanced Search section. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- yum-software-management-en.xml 26 Jul 2005 23:29:18 -0000 1.29 +++ yum-software-management-en.xml 27 Jul 2005 21:27:32 -0000 1.30 @@ -679,7 +679,7 @@ <tip> <title>Downloads are Cached</title> <para> - The <command>yum</command> utility keeps Downloaded data files + The <command>yum</command> utility keeps downloaded data files and packages for reuse. You may copy packages from the repository cache directories under <filename>/var/cache/yum/</filename>, and use them elsewhere if @@ -915,6 +915,8 @@ <para> If you do not know the name of the package, use the <option>search</option> or <option>provides</option> options. + Alternatively, you may use wild cards and regular expressions + with any <command>yum</command> search option. </para> <para> @@ -962,8 +964,8 @@ <para> Use the standard wildcard characters to run any search option - without a complete name: <option>?</option> to represent any one - character, and <option>*</option> to mean zero or more + with a partial word or name: <option>?</option> to represent any + one character, and <option>*</option> to mean zero or more characters. Always add the escape character (<option>\</option>) before wildcards. </para> @@ -1207,23 +1209,31 @@ <secondary>compatibility</secondary> </indexterm> <para> - The &FEX; project provides packages which are built to the same - standards as &FC; packages. Third-party packages should be - compatible with these official packages, unless the provider + The &FEX; repository provides packages which are built to the + same standards as &FC; packages. Third-party packages should be + compatible with these &FP; packages, unless the provider specifically states otherwise. </para> <para> - Refer to the web site of the repository for information on + Always read the web site of the repository for information on package compatibility before you add it as a package source. - Repositories often provide packages specifically intended for - use with packages supplied by other repositories. In some cases, - separate third-party repository providers may each offer - different versions of the same software. This situation may - prevent you from safely using those repositories together on - your &FED; system. + Separate repository providers may offer different and + incompatible versions of the same software. In some cases, + third-party repositories may also include alternative packages + for software provided by &FP; repositories that are not + compatible with other &FED; packages. </para> + <caution> + <title>Incompatible Repositories</title> + + <para> + If you use incompatible repositories <command>yum</command> + operations may fail. + </para> + </caution> + <para> Packages built for one version of &FED; are usually not compatible with other versions of &FED;. The web site of the @@ -1381,10 +1391,10 @@ <secondary>cleaning caches</secondary> </indexterm> <para> - By default, <command>yum</command> retains the packages or + By default, <command>yum</command> retains the packages and package data files that it downloads, so they may be reused in future operations without being downloaded again. To purge the - header files, use this command: + package data files, use this command: </para> <screen> <userinput>su -c 'yum clean headers'</userinput>

1 0

yum-software-management yum-software-management-en.xml,1.28,1.29
by fedora-docs-commits＠redhat.com 27 Jul '05

27 Jul '05

Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2765 Modified Files: yum-software-management-en.xml Log Message: - Clarify wording on effect of purging caches - Explicitly list Fedora repositories - Amended explanation of use of wildcards in searches Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- yum-software-management-en.xml 25 Jul 2005 21:57:58 -0000 1.28 +++ yum-software-management-en.xml 26 Jul 2005 23:29:18 -0000 1.29 @@ -261,13 +261,27 @@ <para> The package management utilities in &FC; are already configured - to use the network of repositories maintained by the &FP;. These - repositories contain the software included with &FC; and a large - selection of additional software known as &FEX;. Third-party - software developers also provide repositories for their &FED; - compatible packages. + to use a network of servers that provide three repositories: </para> + <itemizedlist> + <listitem> + <para> + The packages that make up &FC;, as it is released on disc + </para> + </listitem> + <listitem> + <para> + Updated versions of &FC; software + </para> + </listitem> + <listitem> + <para> + A large selection of additional software, known as &FEX; + </para> + </listitem> + </itemizedlist> + <note> <title>All &FED; Packages are Open Source Software</title> @@ -277,6 +291,13 @@ network of repositories on as many systems as desired. </para> </note> + + <para> + Third-party software developers also provide repositories for + their &FED; compatible packages. To learn how to configure your + &FED; system to use third-party repositories, read + <xref linkend="sn-using-repositories"/>. + </para> <indexterm> <primary>package groups</primary> <secondary>defined</secondary> @@ -373,8 +394,8 @@ <filename>tsclient-0.132-4.i386.rpm</filename> </screen> <para> - Management utilities refer to packages with one of three - formats: + Management utilities commonly refer to packages with one of + three formats: </para> <itemizedlist> @@ -603,18 +624,11 @@ </para> <para> - <command>yum</command> downloads data files from each of the - configured repositories. On a slow connection, it may take several - seconds to download the required files for each package. - </para> - - <para> During operation, <command>yum</command> first determines the best set of actions to produce the required result, and displays the transaction for you to approve. The <command>yum</command> utility - may prompt you to approve installation, update, or removal of - additional packages in addition to the package that you specified. - These actions may be necessary to resolve software dependencies. + may prompt you to approve the installation, update, or removal of + additional packages, in order to resolve software dependencies. </para> <example id="yum-transaction-format"> @@ -877,20 +891,29 @@ </para> <para> - To make your queries more specific, add other package - attributes. To search for version 0.132 of the application, use - the command: + 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> <screen> <userinput>su -c 'yum list <replaceable>tsclient-0.132</replaceable>'</userinput> </screen> + <note> + <title>Valid Package Attributes</title> + + <para> + Refer to <xref linkend="sn-package-names" /> for information + on package name formats and the attributes that they include. + </para> + </note> </section> <section id="sn-searching-packages-advanced"> <title>Advanced Searches</title> <para> - If you do not know the name of the package, use either the + If you do not know the name of the package, use the <option>search</option> or <option>provides</option> options. </para> @@ -936,14 +959,27 @@ For each command, at the prompt enter the password for the <systemitem class="username">root</systemitem> account. </para> + + <para> + Use the standard wildcard characters to run any search option + without a complete name: <option>?</option> to represent any one + character, and <option>*</option> to mean zero or more + characters. Always add the escape character (<option>\</option>) + before wildcards. + </para> + + <para> + To <option>list</option> all packages with names that begin with + <filename>tsc</filename>, type: + </para> +<screen> +<userinput>su -c 'yum list <replaceable>tsc\*</replaceable>'</userinput> +</screen> <tip> - <title>Wildcards and Regular Expressions</title> + <title>Regular Expressions</title> <para> - You may use the standard wildcard characters in search - criteria: <option>?</option> to represent any one character, - and <option>*</option> to mean zero or more characters. Use - Perl or Python regular expressions to carry out more complex - queries. + Use Perl or Python regular expressions to carry out more + complex queries. </para> </tip> </section> @@ -963,8 +999,8 @@ or <filename>shadow-util</filename> would not produce the package <filename>shadow-utils</filename>. This package would match and be shown if the query was either - <filename>shadow-util?</filename> or - <filename>Shadow*</filename>. + <filename>shadow-util\?</filename> or + <filename>Shadow\*</filename>. </para> </section> </section> @@ -1345,10 +1381,10 @@ <secondary>cleaning caches</secondary> </indexterm> <para> - By design, <command>yum</command> does not automatically delete - any of the packages or package data files it downloads, so they - may be reused in future operations. To purge the header files, - use this command: + By default, <command>yum</command> retains the packages or + package data files that it downloads, so they may be reused in + future operations without being downloaded again. To purge the + header files, use this command: </para> <screen> <userinput>su -c 'yum clean headers'</userinput> @@ -1365,15 +1401,11 @@ the <systemitem class="username">root</systemitem> account. </para> - <note> - <title>Purged Files</title> - - <para> - Package management operations download header files and - packages as required, and automatically replace any deleted - files needed for the operation. - </para> - </note> + <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> </section> </section>

1 0

release-notes/FC4 splash.xml,1.12,1.13
by fedora-docs-commits＠redhat.com 26 Jul '05

26 Jul '05

Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32731 Modified Files: splash.xml Log Message: What's a period more or less. Index: splash.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/splash.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- splash.xml 26 Jul 2005 21:07:06 -0000 1.12 +++ splash.xml 26 Jul 2005 21:27:23 -0000 1.13 @@ -340,7 +340,7 @@ url="http://fedorafaq.org">http://fedorafaq.org</ulink> provides useful answers on commonly asked questions. However, these are completely unsupported by the &FP;. The &FP; encourages using free - and open source software.. + and open source software. </para> <para> The binary only drivers can be acquired from the vendors. You can

1 0

release-notes/FC4 RELEASE-NOTES-en.xml, 1.12, 1.13 splash.xml, 1.11, 1.12
by fedora-docs-commits＠redhat.com 26 Jul '05

26 Jul '05

Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32540 Modified Files: RELEASE-NOTES-en.xml splash.xml Log Message: Better wording, close to project goal. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-en.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- RELEASE-NOTES-en.xml 23 Jul 2005 03:31:13 -0000 1.12 +++ RELEASE-NOTES-en.xml 26 Jul 2005 21:07:06 -0000 1.13 @@ -37,7 +37,7 @@  -<!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-22-T04:20-0700)">  +<!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-26-T16:20-0700)">  <!ENTITY LOCALVER "4">   <!ENTITY NAME "Fedora">  Index: splash.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/splash.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- splash.xml 23 Jul 2005 03:31:13 -0000 1.11 +++ splash.xml 26 Jul 2005 21:07:06 -0000 1.12 @@ -339,8 +339,8 @@ The unofficial <ulink url="http://fedorafaq.org">http://fedorafaq.org</ulink> provides useful answers on commonly asked questions. However, these are - completely unsupported by the &FP;. The &FP; recommends using free - and open source software alternatives whenever possible. + completely unsupported by the &FP;. The &FP; encourages using free + and open source software.. </para> <para> The binary only drivers can be acquired from the vendors. You can

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits July 2005