yum-software-management yum-software-management-en.xml,1.21,1.22
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24534
Modified Files:
yum-software-management-en.xml
Log Message:
More editing for style and clarity
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- yum-software-management-en.xml 23 Jul 2005 00:18:43 -0000 1.21
+++ yum-software-management-en.xml 23 Jul 2005 20:47:23 -0000 1.22
@@ -402,8 +402,8 @@
Use only the name of the package with <command>yum</command>,
except when the exact version or type is necessary. <remark
role="fixme">When exactly is that required? I fixed the
- sentence structure but the meaning is obscure here.
- [PWF]</remark> For example, use
+ sentence structure but the meaning is obscure here. Tell the
+ reader the full story here. [PWF]</remark> For example, use
<filename>name-version</filename> to specify the exact version
of the application. The package listings provided by
<command>yum</command> use the format
@@ -455,42 +455,46 @@
<para>
On your desktop is an <application>Alert Icon</application> that
keeps you informed about package updates. Until your system is
- updated this appears as a red circle with a flashing exclamation
- mark. The alert icon is integrated with
- <application>up2date</application>, which enables you to easily
- install updates for your system.
+ updated the icon appears as a red circle with a flashing
+ exclamation mark. The Alert Icon is part of the
+ <application>up2date</application> application, which enables you
+ to easily install system updates.
</para>
<para>
- Also included in &FC; is
- <application>system-config-packages</application>. From the main
- menu, this is <menuchoice><guimenu>System
- Settings</guimenu><guimenuitem>Add/Remove
- Applications</guimenuitem></menuchoice>. Unlike
- <application>up2date</application> and <command>yum</command>, it
- installs software packages from your &FC; installation discs, and
- does not use repositories. This application is used on systems
- that do not have a network connection.
+ &FC; also includes
+ <application>system-config-packages</application>. To run this
+ application from the graphical interface, select
+ <menuchoice>
+ <guimenu>Desktop</guimenu>
+ <guisubmenu>System Settings</guisubmenu>
+ <guimenuitem>Add/Remove Applications</guimenuitem>
+ </menuchoice>. Unlike <application>up2date</application> and
+ <command>yum</command>,
+ <application>system-config-packages</application> installs
+ software packages from your &FC; installation discs only, and does
+ not use repositories. This application is used on systems that do
+ not have a network connection.
</para>
<para>
The <command>rpm</command> command-line utility has many functions
- for working with individual RPM packages. It may also be used to
- manually install and remove packages from your system. Installing
- software with the <command>rpm</command> utility requires you to
- manually check and install the dependencies of the software. For
- this reason, using the <command>rpm</command> utility to manage
- software is not recommended.
+ 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 <command>rpm</command> utility, you must
+ manually check and install any dependencies. For this reason,
+ <command>yum</command> is the recommended method for installing
+ software.
</para>
<caution>
<title>Current Package Versions</title>
<para>
- Using <application>up2date</application> and
- <command>yum</command> ensures that you have the most recent
- version of the packages that are being installed. Other methods
- do not guarantee that the packages are current.
+ The <application>up2date</application> and
+ <command>yum</command> utilities ensure that you have the most
+ recent version of software packages. Other methods do not
+ guarantee that the packages are current.
</para>
</caution>
</section>
@@ -498,7 +502,8 @@
<section id="sn-managing-packages">
<title>Managing Software with <command>yum</command></title>
<indexterm>
- <primary>yum, package management</primary>
+ <primary>yum</primary>
+ <secondary>software management</secondary>
</indexterm>
<para>
The <command>yum</command> utility may modify the software on your
@@ -509,68 +514,64 @@
<itemizedlist>
<listitem>
<para>
- By installing new software from repositories or a package
+ It may install new software from repositories or a package
file.
</para>
</listitem>
<listitem>
<para>
- By updating existing software on your system.
+ It may update existing software on your system.
</para>
</listitem>
<listitem>
<para>
- By removing unwanted software from your system.
+ It may remove unwanted software from your system.
</para>
</listitem>
</itemizedlist>
</para>
<para>
- In each case you must specify the function and the criteria, such
- as the name of the package or package group. Simple examples are
- given in each section.
+ To use <command>yum</command>, specify a function and one or more
+ packages or package groups. Each section below gives some
+ examples.
</para>
<tip>
<title>Package Names</title>
<para>
- You may use any of the following formats for specifying a
- package in a <command>yum</command> operation:
- <filename>name</filename>,
- <filename>name.architecture</filename>,
- <filename>name-version</filename>,
- <filename>name-version-release</filename>,
- <filename>name-version-release.architecture</filename>, and
- <filename>epoch:name-version-release.architecture</filename>.
+ You may use any of the following formats to specify a package in
+ a <command>yum</command> operation: <replaceable>name</replaceable>,
+ <replaceable>name.architecture</replaceable>,
+ <replaceable>name-version</replaceable>,
+ <replaceable>name-version-release</replaceable>,
+ <replaceable>name-version-release.architecture</replaceable>, and
+ <replaceable>epoch:name-version-release.architecture</replaceable>.
</para>
</tip>
<para>
To use the repositories <command>yum</command> downloads data
- files from each of the repositories that it is configured to use.
- On a slow connection downloading the repository index files and
- the <firstterm>header</firstterm> file for each package may take
- several seconds to complete.
+ 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>
- When installing, updating or removing software,
- <command>yum</command> first determines the best set of actions to
- produce the required result, and displays the transaction for you
- to approve. This may include installing, updating or removing
- other packages in addition to the package that you specified, in
- order to resolve the dependencies of the software.
- </para>
-
- <para>
- As an example, this is the transaction for installing
- <filename>tsclient</filename>:
+ 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.
</para>
<example id="yum-transaction-format">
<title>Format of <command>yum</command> Transaction Reports</title>
-<programlisting>
- <![CDATA[
-=============================================================================
+ <para>
+ This is an example of the transaction for installing
+ <filename>tsclient</filename>:
+ </para>
+<screen>
+<computeroutput>=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
@@ -584,16 +585,15 @@
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 355 k
-Is this ok [y/N]:
- ]]>
- </programlisting>
+Is this ok [y/N]:</computeroutput>
+</screen>
</example>
<para>
- Review the list of changes before pressing
- <userinput>y</userinput> to accept and begin the process. No
- packages are downloaded or changed if you press
- <userinput>N</userinput>.
+ Review the list of changes, and then press <keycap>y</keycap> to
+ accept and begin the process. If you press <keycap>N</keycap> or
+ <keycap>Enter</keycap>, <command>yum</command> does not download
+ or change any packages.
</para>
<note>
18 years, 11 months
- 1
- 0
release-notes/FC4 RELEASE-NOTES-en.xml, 1.11, 1.12 splash.xml, 1.10, 1.11
by fedora-docs-commits＠redhat.com
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1494
Modified Files:
RELEASE-NOTES-en.xml splash.xml
Log Message:
New section on patented software and the like. Forgot to commit this when I did all the updates to the posted version of the release notes.
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-en.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- RELEASE-NOTES-en.xml 19 Jul 2005 20:41:03 -0000 1.11
+++ RELEASE-NOTES-en.xml 23 Jul 2005 03:31:13 -0000 1.12
@@ -37,7 +37,7 @@
<!-- *************** Local entities *************** -->
-<!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-19-T16:20-0700)"> <!-- version of manual and date -->
+<!ENTITY BOOKID "RELEASE-NOTES-&FCX;&DISTROVER; (2005-07-22-T04:20-0700)"> <!-- version of manual and date -->
<!ENTITY LOCALVER "4"> <!-- Set value to your choice, when guide version is out -->
<!-- of sync with FC release, use instead of FEDVER or FEDTESTVER -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
Index: splash.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/splash.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- splash.xml 7 Jun 2005 19:55:45 -0000 1.10
+++ splash.xml 23 Jul 2005 03:31:13 -0000 1.11
@@ -177,6 +177,176 @@
</listitem>
</itemizedlist>
</section>
+ <section id="sn-why-no-mp3">
+ <title>MP3 Codecs and Other Patented or Closed Source Software</title>
+ <para>
+ This section is a brief explanation of why certain software is not
+ included in &FC; or &FEX;. This information was drawn directly
+ from the canonical wiki page:
+ </para>
+ <para>
+ <ulink
+ url="http://fedoraproject.org/wiki/ForbiddenItems">http://fedoraproject.org/wiki/ForbiddenItems</ulink>
+ </para>
+ <para>
+ A frequent question of the &FP; is why certain items are not
+ included in &FC; or &FEX;. This briefly explains some of the
+ reasons.
+ </para>
+ <para>
+ Other items, such as file systems support, requires community
+ participation. For more information, refer to <ulink
+ url="http://fedoraproject.org/wiki/Wishlist">http://fedoraproject.org/wiki/Wishlist</ulink>
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>NTFS</term>
+ <listitem>
+ <para>
+ NTFS Support is not included in the &FC; kernel because of
+ patent concerns. Using a file system natively supported by
+ Linux such as ext3 is a better option. If you must share
+ files between Windows and Linux on a single system, use
+ FAT/FAT32 (vfat) instead. For sharing across a network,
+ Samba is a good option.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>MP3 encode/decode functionality</term>
+ <listitem>
+ <para>
+ MP3 support is not included in any &FC; application because
+ MP3 is heavily patented in several regions including the
+ United States. The patent holder is unwilling to give an
+ unrestricted patent grant, as required by the GPL. Other
+ platforms might have paid the royalty and/or included
+ proprietary software. Other Linux distributions not based in
+ a region affected by the patent might ship MP3
+ decoders/encoders. However, &FC; cannot and does not ship
+ MP3 decoders/encoders in order to serve the goal of shipping
+ only free and open source software. Using other open source
+ formats such as Ogg Vorbis (a lossy codec that has better
+ quality than MP3) or FLAC (a lossless codec) is highly
+ recommended.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>NVIDIA 3D drivers</term>
+ <listitem>
+ <para>
+ The NVIDIA 3D drivers are closed source. &FC; does not
+ include proprietary binaries. Consider using an Intel or any
+ other manufacturer that supports open source cards with full
+ specifications and/or source code.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>ATI 3D drivers</term>
+ <listitem>
+ <para>
+ The ATI 3D drivers are closed source. &FC; does not include
+ proprietary binaries. Consider using an Intel or any other
+ manufacturer that supports open source cards with full
+ specifications and/or source code.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>RealPlayer</term>
+ <listitem>
+ <para>
+ RealPlayer is a closed source application. &FC; does not
+ include proprietary binaries. Consider using open source
+ codecs that do not have patent restrictions.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>DVD video playback</term>
+ <listitem>
+ <para>
+ DVD video playback (of CSS encrypted DVDs) may violate the
+ US DMCA (refer to <ulink
+ url="http://en.wikipedia.org/wiki/DMCA">http://en.wikipedia.org/wiki/DMCA</ulink>)
+ because it may be considered circumventing an encryption
+ mechanism. Additionally, MPEG2 is a patented codec, so even
+ DVDs without encryption cannot be played. Consider using
+ open source unencrypted mediums such as Ogg Theora formats.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Mono</term>
+ <listitem>
+ <para>
+ Mono packages are not currently included due to potential
+ legal issues. (Pending more input.) Applications can be
+ written in other languages that are open source, such as
+ Python, Perl, or Ruby. Java is cross-platform and GCJ is a
+ relatively mature open source implementation of it. These
+ are not direct one-to-one equivalents with .NET but might
+ serve your purpose.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Cryptology (mcrypt)</term>
+ <listitem>
+ <para>
+ Some cryptology related packages such as mcrypt are not
+ included within &FC; due to US export restrictions. Consider
+ using non-restricted cryptographical methods instead.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>szip</term>
+ <listitem>
+ <para>
+ The szip license is too restrictive for inclusion in &FEX;.
+ Use other open source alternatives.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ In conclusion:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para> If it is proprietary, it cannot be included in &FED;.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If it is legally encumbered, it cannot be included in &FED;.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If it violates US Federal law, it cannot be included in &FED;.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Of course, the logical followup is: "But I want to get foo and do
+ bar, how can I do one of the items listed above?"
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ The binary only drivers can be acquired from the vendors. You can
+ find many interesting things with Google.
+ </para>
+ </section>
</section>
<!--
Local variables:
18 years, 11 months
- 1
- 0
securing-filesystems setfacl-en.xml,1.1,NONE
by fedora-docs-commits＠redhat.com
Author: trjones
Update of /cvs/docs/securing-filesystems
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28930/securing-filesystems
Removed Files:
setfacl-en.xml
Log Message:
--- setfacl-en.xml DELETED ---
18 years, 11 months
- 1
- 0
yum-software-management yum-software-management-en.xml,1.20,1.21
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27952
Modified Files:
yum-software-management-en.xml
Log Message:
More style editing, through package arch section
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- yum-software-management-en.xml 22 Jul 2005 22:31:08 -0000 1.20
+++ yum-software-management-en.xml 23 Jul 2005 00:18:43 -0000 1.21
@@ -261,19 +261,20 @@
<para>
All of the software provided by the &FP; is Open Source
- software, or and can therefore be downloaded and installed
+ software, and can therefore be downloaded and installed
from the network of &FED; repositories without restrictions.
</para>
</note>
<!-- SE: The key point here is that users can install Fedora packages as many times as they like on as many systems as they like, as opposed to widely prevalent no-cost but not freely redistributable software -->
<indexterm>
- <primary>package groups, defined</primary>
+ <primary>package groups</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
- You may also manage related packages as sets by using the
- <firstterm>package groups</firstterm> provided by the &FED;
- repositories. Some third-party repositories add packages to
- these groups, or provide their packages as additional groups.
+ You may also use the <firstterm>package groups</firstterm>
+ provided by the &FED; repositories to manage related packages as
+ sets. Some third-party repositories add packages to these
+ groups, or provide their packages as additional groups.
</para>
<!-- SE: Some repositories use groups and some don't: I've tried to put this nicely. -->
<!-- SE: Using the admonition for this is not optimal, it just doesn't fit anywhere else. -->
@@ -282,74 +283,86 @@
<para>
To view a list of all of the available package groups for your
- &FED; system, run the command <command>yum
- <option>grouplist</option></command>.
+ &FED; system, run the command <command>yum
+ grouplist</command>.
</para>
</note>
-
- <para>
- Using repositories ensures that you always receive the current
- version of the software. If several versions of the same package
- are available then your management utility automatically selects
- the latest version.
- </para>
-
- <para>
- For all of these reasons you should only manually install
- software when you are confident that there is no repository that
- can currently provide it. If a piece of software on your system
- is not available from a repository then you cannot automatically
- find or install newer versions. You must keep that product
- updated yourself.
- </para>
-
- <note>
- <title>Manual Package Installation</title>
-
+<!-- I removed the extra option tag above. I used to do the same thing -->
+<!-- and Karsten and Tammy both cautioned me against overtagging -->
+<!-- commands. [PWF] -->
+ <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>
+
+ <caution>
+ <title>Installing Software not from a Repository</title>
+ <para>
+ Install software using manual methods only when you are
+ confident there is no repository which can currently provide
+ it. You may not be able to manage such software using &FED;
+ software management utilities. You may need to update that
+ software with manual methods.
+ </para>
<para>
The <command>yum</command> commands shown in this document use
- repositories as package sources. Refer to
+ repositories as package sources. Refer to
<xref linkend="sn-yum-installing-frompackage"/> for details of
- using <command>yum</command> to manually install software from
- a package file.
+ using <command>yum</command> to install software from a
+ package file.
</para>
- </note>
+ </caution>
</section>
<section id="sn-about-dependencies">
<title>About Dependencies</title>
<indexterm>
- <primary>dependencies, defined</primary>
+ <primary>dependencies</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
- You must consider package <firstterm>dependencies</firstterm>
- when manually installing software. To avoid conflicts and
- inconsistencies Linux distributions supply program library files
- as separate packages to the applications that use their
- functions. Many libraries and command-line utilities are used by
- multiple applications.
+ Some of the files installed on a &FED; 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, &FED; must first satisfy its dependencies. The
+ dependency information for a RPM package is stored within the
+ RPM file.
</para>
<para>
- Management tools like <command>yum</command> use the information
- on dependencies stored within packages to ensure that all of the
- requirements are met when you install an application. The
- packages for any supporting software are automatically be
- installed first, if they are not already present on your system.
- If a new application has requirements that conflict with
- existing software then the installation process safely aborts
- without making any changes to your system.
- </para>
-<!-- SE: Note that this is a generality: the behaviour described is standard for rpm, up2date etc.-->
+ The <command>yum</command> utility uses package dependency data
+ to ensure all its requirements are met during installation. The
+ <command>yum</command> utility automatically installs packages
+ for any required software not already present on your system. If
+ a new application has requirements that conflict with existing
+ software, <command>yum</command> aborts without making any
+ changes to your system.
+ </para>
+<!-- SE: Note that this is a generality: the behaviour described is -->
+<!-- standard for rpm, up2date etc.-->
+
+<!-- I totally understand; however, I've used yum specifically for two -->
+<!-- reasons: (1) Even though this is a section about concepts, the -->
+<!-- tutorial is still about yum; and more importantly, (2) the -->
+<!-- continual use of "Software management tools such as yum" was -->
+<!-- becoming redundant and unwieldy, and would force us to use very -->
+<!-- awkward sentence structures. -->
+
</section>
<section id="sn-package-names">
<title>Understanding Package Names</title>
<indexterm>
- <primary>packages, hardware compatibility</primary>
+ <primary>packages</primary>
+ <secondary>hardware compatibility</secondary>
</indexterm>
<indexterm>
- <primary>packages, naming</primary>
+ <primary>packages</primary>
+ <secondary>naming</secondary>
</indexterm>
<para>
Each package file has a long name that indicates several key
@@ -360,17 +373,6 @@
<filename>tsclient-0.132-4.i386.rpm</filename>
</screen>
<para>
- Use just the name of the package itself with
- <command>yum</command>, except when it is necessary to specify
- the exact version or type. For example, use
- <filename>name-version</filename> to specify the exact version
- of the application. The package listings provided by
- <command>yum</command> itself use the format
- <filename>name.architecture</filename>, to specify the type of
- computer that the package is intended for.
- </para>
-
- <para>
These naming conventions are valid for the file shown above:
</para>
@@ -383,8 +385,10 @@
<listitem>
<para>
Package name with version number:
- <filename>tsclient-0.132</filename>
+ <filename>tsclient-0.132-4</filename>
</para>
+<!-- I'm pretty sure the release number is needed; feel free to check -->
+<!-- this. [PWF] -->
</listitem>
<listitem>
<para>
@@ -395,25 +399,38 @@
</itemizedlist>
<para>
+ Use only the name of the package with <command>yum</command>,
+ except when the exact version or type is necessary. <remark
+ role="fixme">When exactly is that required? I fixed the
+ sentence structure but the meaning is obscure here.
+ [PWF]</remark> For example, use
+ <filename>name-version</filename> to specify the exact version
+ of the application. The package listings provided by
+ <command>yum</command> use the format
+ <filename>name.architecture</filename> to specify the type of
+ computer for which the package is intended.
+ </para>
+
+ <para>
The hardware architecture is the <emphasis>minimum</emphasis>
- type of machine required for that specific package. Packages for
- <option>i386</option> run on any current Intel-compatible
- computer. Packages for PowerPC machines, such as Apple Macs, are
- indicated with <option>ppc</option>. Packages specified as
- <option>noarch</option> have no architecture requirement.
+ type of machine required for that specific package. Packages
+ with architecture <option>i386</option> run on any current
+ Intel-compatible computer. Packages for PowerPC systems, such as
+ Apple Power Macintosh, are indicated with <option>ppc</option>.
+ Packages for systems with 64-bit processors such as Opterons are
+ indicated with <option>x86_64</option>. Packages specified as
+ <option>noarch</option> have no architecture requirement.
</para>
<para>
Some software may be optimized for particular types of
- Intel-compatible machine. For these products, separate packages
- may be provided for <option>i386</option>,
- <option>i586</option>, <option>i686</option> and
- <option>x86_64</option> computers. A machine with at least an
- Intel Pentium, VIA C3 or compatible CPU is an
- <option>i586</option>. Computers with an Intel Pentium II and
- above, or a current model of AMD chip, are <option>i686</option>
- machines. 64-bit PCs use <option>x86_64</option> packages for
- full 64-bit support.
+ Intel-compatible machine. Separate packages may be provided for
+ <option>i386</option>, <option>i586</option>,
+ <option>i686</option> and <option>x86_64</option> computers. A
+ machine with at least an Intel Pentium, VIA C3 or compatible CPU
+ may use <option>i586</option> packages. Computers with an Intel
+ Pentium Pro and above, or a current model of AMD chip, may use
+ <option>i686</option> packages.
</para>
</section>
</section>
18 years, 11 months
- 1
- 0
yum-software-management yum-software-management-en.xml,1.19,1.20
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25413/yum-software-management
Modified Files:
yum-software-management-en.xml
Log Message:
All the changes I could make in the 90 seconds of editing time I had... :-)
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- yum-software-management-en.xml 21 Jul 2005 16:54:45 -0000 1.19
+++ yum-software-management-en.xml 22 Jul 2005 22:31:08 -0000 1.20
@@ -140,8 +140,7 @@
</para>
<screen>
<userinput>man yum
-man yum.conf
-</userinput>
+man yum.conf</userinput>
</screen>
<indexterm>
<primary>yum</primary>
@@ -238,24 +237,23 @@
<para>
A <firstterm>repository</firstterm> is a prepared directory or
Website that contains software packages and index files.
- Software management utilities like <command>yum</command>
+ Software management utilities such as <command>yum</command>
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 of the software that makes up
- your system, or to search for new software by specifying
- criteria. In each case the management utility connects to the
- repositories that it is configured to use, and checks the
- indexes that they provide to find the correct packages.
+ 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.
</para>
<para>
The package management utilities in &FC; are automatically
- configured to use the network of repository servers maintained
- by the &FP;. These repositories hold both 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.
+ 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.
</para>
<note>
18 years, 11 months
- 1
- 0
mirror-tutorial mirror-tutorial-en.xml,1.6,1.7
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11507
Modified Files:
mirror-tutorial-en.xml
Log Message:
Bump to 0.29, fix entities and note yum versioning for repodata change
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- mirror-tutorial-en.xml 22 Jul 2005 12:34:43 -0000 1.6
+++ mirror-tutorial-en.xml 22 Jul 2005 12:43:58 -0000 1.7
@@ -2,10 +2,10 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "mirror-tutorial-0.27 (2004-12-01)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "mirror-tutorial-0.29 (2005-07-22)"> <!-- change version of manual and date here -->
]>
@@ -126,6 +126,16 @@
</para>
</revdescription>
</revision>
+ <revision>
+ <revnumber>0.29</revnumber>
+ <date>2005-07-22</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Minor note on yum versioning for repodata; fixed entities ref.
+ </para>
+ </revdescription>
+ </revision>
</revhistory>
</articleinfo>
@@ -1082,10 +1092,10 @@
<section id="sn-yum-arch">
<title><command>yum-arch</command></title>
<para>
- A directory which supports older versions of <command>yum</command> is
- named <filename>headers</filename>. It is created by using the command
- <command>yum-arch</command>, which is run against the directory
- <emphasis>under which</emphasis> you want the
+ A directory which supports older versions of <command>yum</command>
+ (before 2.2) is named <filename>headers</filename>. It is created by
+ using the command <command>yum-arch</command>, which is run against
+ the directory <emphasis>under which</emphasis> you want the
<filename>headers</filename> directory to appear. The
<command>yum-arch</command> program searches recursively through that
directory and any subdirectories for RPM packages, and includes them
18 years, 11 months
- 1
- 0
mirror-tutorial mirror-tutorial-en.xml,1.5,1.6
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11455
Modified Files:
mirror-tutorial-en.xml
Log Message:
Rolled in newest mirror-tutorial (#163912)
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- mirror-tutorial-en.xml 22 Jul 2005 11:39:45 -0000 1.5
+++ mirror-tutorial-en.xml 22 Jul 2005 12:34:43 -0000 1.6
@@ -1,11 +1,11 @@
- <!-- $Id: -->
+<!-- $Id: -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.xml">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "mirror-tutorial-0.24 (2005-07-22)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "mirror-tutorial-0.27 (2004-12-01)"> <!-- change version of manual and date here -->
]>
@@ -78,12 +78,51 @@
</revision>
<revision>
<revnumber>0.24</revnumber>
- <date>2005-07-22</date>
+ <date>2004-09-09</date>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
<para>
- Removed references to <command>yum-arch</command> and replaced with
- <command>createrepo</command>.
+ Brought introduction section in line with &FDP; standards.
+ </para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>0.25</revnumber>
+ <date>2004-10-13</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Incorporated all suggested changes by KWade.
+ </para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>0.26</revnumber>
+ <date>2004-12-01</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Updated repository setup to include createrepo.
+ </para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>0.27</revnumber>
+ <date>2004-12-01</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Minor corrections.
+ </para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>0.28</revnumber>
+ <date>2005-01-30</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Minor corrections.
</para>
</revdescription>
</revision>
@@ -95,19 +134,19 @@
<section id="sn-purpose">
<title>Purpose</title>
<para>
- This tutorial presents a number of related topics that allow an
- administrator to seamlessly integrate mirroring and update services for
- &FC;. These services are used to provision a classroom, laboratory, or
- office. These service provisions also increase ease of use and enhance
- user experience, adding to the perceived value of non-proprietary
- operating systems and software.
+ This tutorial presents a number of related topics that allow an
+ administrator to seamlessly integrate mirroring and update services for
+ &FC;. You can use these services to provision a classroom, laboratory,
+ or office. These service provisions also increase ease of use and
+ enhance user experience, adding to the perceived value of
+ non-proprietary operating systems and software.
</para>
<note>
<title>A note about &FC; and this document</title>
<para>
This document applies to &FC; &FCVER;, which may not be the newest
- release of &FC;. Find more information about the newest version at
- &FP-URL;.
+ release of &FC;. You can find more information about the newest
+ version at &FP-URL;.
</para>
</note>
</section>
@@ -151,11 +190,13 @@
<para>
The site from which you retrieve files to build your mirror is called an
<emphasis>upstream mirror</emphasis><indexterm>
- <primary>mirror</primary> <secondary>upstream</secondary>
+ <primary>mirror</primary> <secondary>upstream</secondary>
</indexterm>. If possible, choose an upstream mirror that is located
close to you geographically. This reduces unnecessary traffic across
transcontinental sections of the Internet, where bandwidth is limited
- and expensive.
+ and expensive. Use only upstream mirrors that are intended for public
+ access, unless you have permission from the upstream mirror site
+ administrator.
</para>
</section>
<section id="sn-additional-resources">
@@ -164,11 +205,11 @@
For more information on installing &FC; see the &FC; &IG;<!-- at
&IG-URL; -->. For more information on basic Internet protocols, see
<ulink
- url="http://library.albany.edu/internet/internet.html">http://library.albany.edu/internet/internet.html</ulink>,
+ url="http://library.albany.edu/internet/internet.html">http://library.albany.edu/internet/internet.html</ulink>,
or search Google at <ulink
- url="http://www.google.com/">http://www.google.com/</ulink>. For more
+ url="http://www.google.com/">http://www.google.com/</ulink>. For more
general information about mirrors, see <ulink
- url="http://en.wikipedia.org/wiki/Mirror_(computing)">http://en.wikipedia.org/wiki/Mirror_(computing)</ulink>.
+ url="http://en.wikipedia.org/wiki/Mirror_(computing)">http://en.wikipedia.org/wiki/Mirror_(computing)</ulink>.
</para>
</section>
<section id="sn-acknowledgements">
@@ -179,45 +220,23 @@
</para>
</section>
</section>
-
+
<section id="sn-planning-and-setup">
<title>Planning and Setup</title>
-
- <!-- I see you removed the following to <para>s in an edit, was this -->
- <!-- intentional? -->
-
- <para>
- A <firstterm>mirror</firstterm>
- <indexterm><primary>mirror</primary></indexterm> is a server that provides
- a copy of one or more collections of files. Mirroring a site reduces
- traffic to the original source site, thus spreading the stress and
- bandwidth costs of many users across many sites. Side benefits of running
- a local mirror include very fast access through the local network,
- providing custom services to local users, and increasing your skills in
- managing Internet services.
- </para>
- <para>
- The <firstterm>upstream mirror</firstterm><indexterm>
- <primary>mirror</primary>
- <secondary>upstream</secondary> </indexterm> is the site you retrieve
- files from to build your mirror. If possible, choose an upstream mirror
- that is located close to you geographically. This reduces unnecessary
- traffic across transcontinental sections of the Internet, where bandwidth
- is limited and expensive.
- </para>
-
+
<section id="sn-hierarchy">
<title>The Distribution Structure</title>
<para>
- The &FED; <firstterm>distribution</firstterm><indexterm>
+ The &FED; <emphasis>distribution</emphasis><indexterm>
<primary>distribution</primary>
</indexterm>, which is the collection of all &FED;-related files, uses
the directory tree in <xref linkend="ex-fedora-dir-tree"/>. It may
- include multiple versions of &FC;. The tree design makes trimming of
+ include multiple versions of &FC;. The tree design makes "trimming" of
unnecessary or undesired files easier. When setting up a mirror,
duplicate this tree exactly, or as closely as possible. Doing so makes
automating nightly updates easier.
</para>
+
<example id="ex-fedora-dir-tree">
<title>Fedora directory tree</title>
<screen>
@@ -257,6 +276,7 @@
+-- x86_64</computeroutput>
</screen>
</example>
+
<note>
<title>Naming conventions</title>
<para>
@@ -322,7 +342,7 @@
Installation Disc 1 into the
<filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/os</filename>
folder. Then copy all files from the <filename>&FED;</filename> folder
- of each of the remaining installation discs into the
+ of each of the remaining Installation discs into the
<filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/os/&FED;</filename>
folder on the server.
</para>
@@ -395,22 +415,22 @@
</para>
<variablelist>
<varlistentry>
- <term>Older versions of &FC; (any numbered directory).</term>
+ <term>Older versions of &FC; (any numbered directory).</term>
<listitem>
<para>
- Before you exclude an old version, ensure this does not adversely
- affect any of your users. These adverse affects can come in many
- forms. For example, the level of support for certain hardware
- sometimes changes between releases of &FC;. Users who cannot
- install a previous version may not be able to use &FC;. Your users
- might need to perform software-related tasks such as building
- packages for different &FC; releases. Always remain aware of the
- needs of your users during the planning stage.
+ Before you exclude an old version, ensure
+ this does not adversely affect any of your users. These adverse
+ affects can come in many forms. For example, the level of support
+ for certain hardware sometimes changes between releases of &FC;.
+ Users who cannot install a previous version may not be able to use
+ &FC;. Your users might need to perform software-related tasks such
+ as building packages for different &FC; releases. Always remain
+ aware of the needs of your users during the planning stage.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>Folders for architectures your site does not support.</term>
+ <term>Folders for architectures your site does not support.</term>
<listitem>
<para>
If you do not have any x86-64 hosts to support, trimming these
@@ -422,16 +442,16 @@
</varlistentry>
<varlistentry>
<term>The <filename>development</filename> folder (formerly
- <filename>rawhide</filename>).</term>
+ <quote>Rawhide</quote>).</term>
<listitem>
<para>
- This folder contains all the latest bleeding-edge packages from
- the &FP;. If you participate in active &FED; development, you
- should not trim this branch. &FED; development moves at a rapid
- pace and requires frequent updates to the latest development
- package versions. However, the frequent updates cause your mirror
- to download significant amounts of material during the regular
- update cycle.
+ This folder contains all the latest <quote>bleeding-edge</quote>
+ packages from the &FP;. If you participate in active &FED;
+ development, you should not trim this branch. &FED; development
+ moves at a rapid pace and requires frequent updates to the latest
+ development package versions. However, the frequent updates cause
+ your mirror to download significant amounts of material during the
+ regular update cycle.
</para>
</listitem>
</varlistentry>
@@ -441,9 +461,9 @@
<para>
These branches contain updates that are being subjected to quality
assurance through public testing, as well as the test or
- <firstterm>pre-release</firstterm> versions of the &FC;
- distribution. The <filename>testing</filename> folder under the
- main <filename>core</filename> tree is where test versions of the
+ <quote>pre-release</quote> versions of the &FC; distribution. The
+ <filename>testing</filename> folder under the main
+ <filename>core</filename> tree is where test versions of the
distribution, such as &FC; &FCTESTVER;, are kept. (Users of &FC;
test distributions are often directed to use the
<filename>development</filename> branch to update packages.) The
@@ -454,21 +474,16 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>The <filename>debug</filename> folders.</term>
+ <term>The <filename>debug</filename> folders.</term>
<listitem>
<para>
These folders contain packages that enable developers and skilled
users to interpret data created when a program crashes or
encounters a bug. If you participate actively in &FED;
development, you should not trim these folders. If you trim this
- branch, you may still download individual packages on an ad hoc
- basis from a nearby public mirror site. <!-- removed
- <foreignphrase> mainly because the stylesheet italicized it, yet
- the term is neither new nor noteworthy enough to make it stand out
- like that ... the usage is correct and may not even be overboard,
- but the format outcome is jarring for the reader, and I'd prefer
- not to have to hack the XSL to make this bigger. Maybe next time?
- -->
+ branch, you may still download individual packages on an
+ <foreignphrase>ad hoc</foreignphrase> basis from a nearby public
+ mirror site.
</para>
</listitem>
</varlistentry>
@@ -479,7 +494,8 @@
<para>
These folders contain the original source for all the binary RPM
packages in the distribution. You may download these packages on
- an ad hoc basis if you need to save space on your local mirror.
+ an <foreignphrase>ad hoc</foreignphrase> basis if you need to save
+ space on your local mirror.
</para>
</listitem>
</varlistentry>
@@ -526,26 +542,26 @@
<itemizedlist>
<listitem>
<para>
- <option>--mirror</option> turns on recursion (descends into all
+ <command>--mirror</command> turns on recursion (descends into all
subdirectories), and duplicates file timestamps;
</para>
</listitem>
<listitem>
<para>
- <option>-np</option> prevents <command>wget</command> from
+ <command>-np</command> prevents <command>wget</command> from
ascending into the parent directory;
</para>
</listitem>
<listitem>
<para>
- <option>-nH</option> prevents <command>wget</command> from
+ <command>-nH</command> prevents <command>wget</command> from
writing a directory named after the host (in this case,
<filename><replaceable>mirror.example.com</replaceable></filename>);
</para>
</listitem>
<listitem>
<para>
- <option>--cut-dirs=<replaceable>n</replaceable></option>
+ <command>--cut-dirs=<replaceable>n</replaceable></command>
truncates the first <replaceable>n</replaceable> directories in
the path. In the example above, <command>--cut-dirs=2</command>
prevents <command>wget</command> from writing the
@@ -576,11 +592,10 @@
</para>
<para>
Begin by identifying the modules available on the upstream mirror site
- you have chosen. Note that the double colon
- <computeroutput>::</computeroutput> is always used after the host name
- to separate it from the rest of the <command>rsync</command> path. The
- following command generates a list of <firstterm>modules</firstterm>
- on the upstream mirror.
+ you have chosen. Note that the double colon <quote>::</quote> is
+ always used after the host name to separate it from the rest of the
+ <command>rsync</command> path. The following command generates a list
+ of <quote>modules</quote> on the upstream mirror.
</para>
<screen>
@@ -595,10 +610,9 @@
equivalent to the <filename>fedora/linux/core</filename> path found at
the &FP; main download server. To list the contents of the &FC;
&FCVER; distribution folder on the upstream server, issue the
- following command. Do not forget the trailing slash
- <computeroutput>/</computeroutput>. Without it, you only receive a
- listing of a folder name that matches the last component of the remote
- path.
+ following command. Do not forget the trailing slash <quote>/</quote>.
+ Without it, you only receive a listing of a folder name that matches
+ the last component of the remote path.
</para>
<screen>
@@ -614,8 +628,8 @@
your system to the end of the command line. The resulting tree of
files from the listing you perform are downloaded to the local path
you specify. Remember, if you leave off the trailing slash on the
- remote path, then the last component of that path is created as a new
- folder inside the target directory, and its contents are copied.
+ remote path, then the last component of that path is created as a
+ folder, and its contents are copied.
</para>
<screen>
@@ -625,7 +639,7 @@
<para>
When downloading using <command>rsync</command> for mirror purposes,
use some of the command line switches to improve performance and
- feedback. The switches <option>-PHav</option> enable the following
+ feedback. The switches <command>-PHav</command> enable the following
<command>rsync</command> features:
</para>
<itemizedlist>
@@ -669,6 +683,7 @@
understand the consequences.
</para>
</caution>
+
<screen>
<userinput>rsync -PHav mirror.example.org::fedora-linux-core/&FCVER;/ /var/ftp/pub/mirror/fedora/core/&FCVER;</userinput>
</screen>
@@ -738,7 +753,7 @@
Use the <command>--exclude</command> switch, along with a simple
pattern, to disallow download of certain files and/or folders. For
instance, <command>--exclude "*.iso"</command> excludes the download
- of any file that has the string <quote>x86_64</quote> in its filename.
+ of any file whose name ends with the string ".iso".
</para>
<para>
Use the <command>--delete</command> switch, again with a pattern, to
@@ -1058,40 +1073,105 @@
<para>
To set up a <command>yum</command> repository, you must write a
- directory of header information from which the clients extract the data that
- they require. The directory is named <filename>repodata/</filename>. It is
- created by using the command <command>createrepo</command>, which is run
- against the directory <emphasis>under which</emphasis> you want the
- <filename>repodata/</filename> directory to appear. The
- <command>createrepo</command> program searches recursively through that
- directory and any subdirectories for RPM packages, and includes them in
- the header data.
+ directory that contains information which the clients require to resolve
+ RPM dependencies. The directory's name depends on the version of
+ <command>yum</command> it supports. It is permissible to have both kinds
+ of repository information in a single repository.
</para>
+ <section id="sn-yum-arch">
+ <title><command>yum-arch</command></title>
+ <para>
+ A directory which supports older versions of <command>yum</command> is
+ named <filename>headers</filename>. It is created by using the command
+ <command>yum-arch</command>, which is run against the directory
+ <emphasis>under which</emphasis> you want the
+ <filename>headers</filename> directory to appear. The
+ <command>yum-arch</command> program searches recursively through that
+ directory and any subdirectories for RPM packages, and includes them
+ in the header data.
+ </para>
+
+<screen>
+<userinput>yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
+</screen>
+
+ <para>
+ The <command>-l</command> switch follows symbolic links. The
+ <command>-s</command> switch includes SRPMS (source RPM packages) in
+ the header list. The command above creates the <command>yum</command>
+ header cache in the directory
+ <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers</filename>.
+ </para>
+ </section>
+
+ <section id="sn-createrepo">
+ <title><command>createrepo</command></title>
+ <para>
+ The <command>createrepo</command> command creates repository
+ information to support newer versions of <command>yum</command> (and
+ possibly other repository client programs). The
+ <command>createrepo</command> command stores this data in a folder
+ named <filename>repodata</filename>. Just as with
+ <command>yum-arch</command>, run <command>createrepo</command> against
+ the directory <emphasis>under which</emphasis> you want the
+ <filename>repodata</filename> directory to appear. The
+ <command>createrepo</command> program also searches recursively for
+ RPM packages to include in the repository data.
+ </para>
+
<screen>
<userinput>createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
</screen>
- <para>
- The command above creates the <command>yum</command> header cache in the directory
- <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers</filename>.
- Typically <command>createrepo</command> is run against at least the
- following locations:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- The stock distribution; for example,
- <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>.
- </para>
- </listitem>
- <listitem>
+ <para>
+ The command above creates the repository data in the directory
+ <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/repodata</filename>.
+ </para>
+ <important>
+ <title>Supporting &FC; 3 and beyond</title>
<para>
- Official updates to the distribution; for example,
- <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>.
+ &FC; 3 ships with a newer version of <command>yum</command>. To
+ support &FC; 3 <command>yum</command> clients, you
+ <emphasis>must</emphasis> use <command>createrepo</command> on your
+ server's repositories.
</para>
- </listitem>
- </itemizedlist>
+ </important>
+ <para>
+ You may not be able to foresee all the possible uses for your server's
+ repositories. To minimize problems for your clients, create both kinds
+ of repository data for any repositories.
+ </para>
+
+ </section>
+
+ <section id="sn-repository-locations">
+ <title>Repository Locations</title>
+ <para>
+ Typically <command>yum-arch</command> or <command>createrepo</command>
+ is run against at least the following locations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The stock distribution; for example,
+ <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>.
+ For <command>yum-arch</command> use the <command>-l</command> and
+ <command>-s</command> options to follow the linked directory
+ <filename>SRPMS</filename> and include the source packages
+ therein.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Official updates to the distribution; for example,
+ <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>.
+ Once again, for <command>yum-arch</command> use
+ <command>-l</command> and/or <command>-s</command> if appropriate.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
@@ -1473,18 +1553,16 @@
</screen>
<para>
- If a user forgets the <command>--aid</command> switch, they
- still receive hints. Normally <command>rpm</command>
- displays a slightly cryptic list of capability requirements,
- instead of straightforward package names. If you edit
- <filename>/etc/rpm/macros.solve</filename> as shown,
- <command>rpm</command> displays a list of required package
+ If a user forgets the <command>--aid</command> switch, they still
+ receive hints. Normally <command>rpm</command> displays a slightly
+ cryptic list of capability requirements, instead of straightforward
+ package names. If you edit <filename>/etc/rpm/macros.solve</filename>
+ as shown, <command>rpm</command> displays a list of required package
names instead.
</para>
<para>
- Package dependency solutions using <command>--aid</command>
- are also restricted as shown above in <xref
- linkend="tp-s-c-p-stock-only"/>.
+ Package dependency solutions using <command>--aid</command> are also
+ restricted as shown above in <xref linkend="tp-s-c-p-stock-only"/>.
</para>
</section>
@@ -1503,51 +1581,46 @@
<section id="sn-up2date-config">
<title><filename>/etc/sysconfig/rhn/up2date</filename></title>
<para>
- The <filename>/etc/sysconfig/rhn/up2date</filename> file
- controls the global configuration of the
- <application>up2date</application> application. This file is
- well commented and is not explained in great detail
- here. Here are some points to keep in mind, however:
+ The <filename>/etc/sysconfig/rhn/up2date</filename> file controls the
+ global configuration of the <application>up2date</application>
+ application. This file is well commented and is not explained in great
+ detail here. Here are some points to keep in mind, however:
</para>
<itemizedlist>
<listitem>
<para>
By default, the user must intervene to update
<command>kernel</command> packages. See the
- <command>pkgSkipList</command> variable. At the command
- line, use the <command>-f</command> option to force an
- override. At the GUI interface,
- <application>up2date</application> allows the user to
+ <command>pkgSkipList</command> variable. At the command line, use
+ the <command>-f</command> option to force an override. At the GUI
+ interface, <application>up2date</application> allows the user to
override.
</para>
</listitem>
<listitem>
<para>
- By default, <command>up2date</command> does not remove
- old <command>kernel</command> packages. See the
+ By default, <command>up2date</command> does not remove old
+ <command>kernel</command> packages. See the
<command>pkgsToInstallNotUpdate</command> variable. When
- <command>up2date</command> installs a new kernel
- package, the old version remains in place until removed
- explicitly.
+ <command>up2date</command> installs a new kernel package, the old
+ version remains in place until removed explicitly.
</para>
</listitem>
<listitem>
<para>
- The configuration file also allows use of an HTTP proxy
- if desired. A number of variables pertain to this
- function.
+ The configuration file also allows use of an HTTP proxy if
+ desired. A number of variables pertain to this function.
</para>
</listitem>
<listitem>
<para>
- By default, <application>up2date</application> sends
- mail to <email>root@localhost</email> when packages are
- updated in batch mode. (Running <command>up2date
- -u</command> starts <application>up2date</application>
- in batch mode.) See the <command>adminAddress</command>
- option. If you support multiple clients and intend to
- use batch mode at your site, you should set a new
- address here.
+ By default, <application>up2date</application> sends mail to
+ <email>root@localhost</email> when packages are updated in batch
+ mode. (Running <command>up2date -u</command> starts
+ <application>up2date</application> in batch mode.) See the
+ <command>adminAddress</command> option. If you support multiple
+ clients and intend to use batch mode at your site, you should set
+ a new address here.
</para>
</listitem>
</itemizedlist>
@@ -1592,7 +1665,7 @@
Edit <filename>/etc/sysconfig/rhn/sources</filename> for the clients
at your site to point to your repository. For any repository, point to
the URL for the directory containing the <filename>headers</filename>
- folder. You created this folder using <command>createrepo</command> in
+ folder. You created this folder using <command>yum-arch</command> in
<xref linkend="sn-repositories"/>. You will likely have two
repositories, one for the stock distribution and one for updates.
Examples are shown below; you may wish to point to an internal address
@@ -1601,8 +1674,8 @@
</para>
<screen>
-<userinput>yum fedora-core-2 http://www.mydomain.org/pub/linux/fedora/core/2/i386/os
-yum fc2-updates http://www.mydomain.org/pub/linux/fedora/core/updates/2/i386</userinput>
+<userinput>yum fedora-core-&FCVER; http://www.mydomain.org/pub/linux/fedora/core/&FCVER;/i386/os
+yum fc&FCVER;-updates http://www.mydomain.org/pub/linux/fedora/core/updates/&FCVER;/i386</userinput>
</screen>
</section>
@@ -1611,7 +1684,7 @@
</section>
-<!--
+<!--
FIXME:
@@ -1634,9 +1707,3 @@
</index>
</article>
-
-<!--
-Local variables:
-mode: xml
-End:
--->
18 years, 11 months
- 1
- 0
mirror-tutorial mirror-tutorial-en.xml,1.4,1.5
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10180
Modified Files:
mirror-tutorial-en.xml
Log Message:
Removed references to yum-arch and replaced with createrepo; bump to 0.24
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- mirror-tutorial-en.xml 18 Jun 2005 13:51:02 -0000 1.4
+++ mirror-tutorial-en.xml 22 Jul 2005 11:39:45 -0000 1.5
@@ -5,7 +5,7 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "mirror-tutorial-0.23 (2004-09-08)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "mirror-tutorial-0.24 (2005-07-22)"> <!-- change version of manual and date here -->
]>
@@ -76,6 +76,17 @@
</para>
</revdescription>
</revision>
+ <revision>
+ <revnumber>0.24</revnumber>
+ <date>2005-07-22</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Removed references to <command>yum-arch</command> and replaced with
+ <command>createrepo</command>.
+ </para>
+ </revdescription>
+ </revision>
</revhistory>
</articleinfo>
@@ -1047,45 +1058,37 @@
<para>
To set up a <command>yum</command> repository, you must write a
- directory of header information from which the clients pull the data
- they require. The directory is named <filename>headers</filename>. It is
- created by using the command <command>yum-arch</command>, which is run
+ directory of header information from which the clients extract the data that
+ they require. The directory is named <filename>repodata/</filename>. It is
+ created by using the command <command>createrepo</command>, which is run
against the directory <emphasis>under which</emphasis> you want the
- <filename>headers</filename> directory to appear. The
- <command>yum-arch</command> program searches recursively through that
+ <filename>repodata/</filename> directory to appear. The
+ <command>createrepo</command> program searches recursively through that
directory and any subdirectories for RPM packages, and includes them in
the header data.
</para>
<screen>
-<userinput>yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
+<userinput>createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
</screen>
<para>
- The <command>-l</command> switch follows symbolic links. This is useful
- in the first case below. The <command>-s</command> switch includes SRPMS
- (source RPM packages) in the header list. The command above creates the
- <command>yum</command> header cache in the directory
+ The command above creates the <command>yum</command> header cache in the directory
<filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers</filename>.
- Typically <command>yum-arch</command> is run against at least the
+ Typically <command>createrepo</command> is run against at least the
following locations:
</para>
<itemizedlist>
<listitem>
<para>
The stock distribution; for example,
- <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>.
- Use the <command>-l</command> and <command>-s</command> options to
- follow the linked directory <filename>SRPMS</filename> and include
- the source packages therein.
+ <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>.
</para>
</listitem>
<listitem>
<para>
Official updates to the distribution; for example,
- <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>.
- Once again use <command>-l</command> and/or <command>-s</command> if
- appropriate.
+ <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>.
</para>
</listitem>
</itemizedlist>
@@ -1589,7 +1592,7 @@
Edit <filename>/etc/sysconfig/rhn/sources</filename> for the clients
at your site to point to your repository. For any repository, point to
the URL for the directory containing the <filename>headers</filename>
- folder. You created this folder using <command>yum-arch</command> in
+ folder. You created this folder using <command>createrepo</command> in
<xref linkend="sn-repositories"/>. You will likely have two
repositories, one for the stock distribution and one for updates.
Examples are shown below; you may wish to point to an internal address
@@ -1631,3 +1634,9 @@
</index>
</article>
+
+<!--
+Local variables:
+mode: xml
+End:
+-->
18 years, 11 months
- 1
- 0
yum-software-management yum-software-management-en.xml,1.18,1.19
by fedora-docs-commits＠redhat.com
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16729/yum-software-management
Modified Files:
yum-software-management-en.xml
Log Message:
Some style edits, still working on this...
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- yum-software-management-en.xml 20 Jul 2005 00:55:56 -0000 1.18
+++ yum-software-management-en.xml 21 Jul 2005 16:54:45 -0000 1.19
@@ -124,59 +124,73 @@
<section id="sn-yum-additional-resources">
<title>Additional Resources</title>
<indexterm>
- <primary>yum, documentation</primary>
+ <primary>yum</primary>
+ <secondary>documentation</secondary>
</indexterm>
<indexterm>
- <primary>yum, man pages</primary>
+ <primary>yum</primary>
+ <secondary>man pages</secondary>
</indexterm>
<para>
- The <command>yum</command> utility has features and options that
- are not discussed in this document. Read the
- <command>man</command> pages for <command>yum(8)</command> and
+ The <command>yum</command> utility has features and options not
+ discussed in this document. Read the <command>man</command>
+ pages for <command>yum(8)</command> and
<filename>yum.conf(5)</filename> to learn more, using the
following commands:
</para>
<screen>
-<userinput>
-man yum man yum.conf
+<userinput>man yum
+man yum.conf
</userinput>
</screen>
<indexterm>
- <primary>yum, Websites</primary>
+ <primary>yum</primary>
+ <secondary>web sites</secondary>
</indexterm>
<indexterm>
- <primary>yum, mailing lists</primary>
+ <primary>yum</primary>
+ <secondary>mailing lists</secondary>
</indexterm>
+<!-- Hopefully this is not too confusing below. This is sort of a -->
+<!-- grammar/usage issue. If you use a variablelist, you don't want to -->
+<!-- use sentences, but rather headings, in the term area. Alternately, -->
+<!-- if you like sentences, just use a para instead for the whole -->
+<!-- collection of links. [PWF] -->
+ <para>
+ Other useful <command>yum</command> resources on the Internet
+ include:
+ </para>
+
<variablelist>
<varlistentry>
<term>
- The Website for <command>yum</command> is:
+ Web home page
</term>
<listitem>
<para>
- <ulink url="http://linux.duke.edu/projects/yum/">http://linux.duke.edu/projects/yum/</ulink>
+ <ulink url="http://linux.duke.edu/projects/yum/"/>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
- The mailing list for <command>yum</command> users is:
- </term>
+ Users mailing list
+ </term>
<listitem>
<para>
- <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum/">https://lists.dulug.duke.edu/mailman/listinfo/yum/</ulink>
+ <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum/"/>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
-The archive for the <command>yum</command> development mailing list is:
-</term>
+ Development mailing list
+ </term>
<listitem>
<para>
- <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/">https://lists.dulug.duke.edu/pipermail/yum-devel/</ulink>
+ <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/"/>
</para>
</listitem>
</varlistentry>
@@ -190,7 +204,8 @@
<section id="sn-about-packages">
<title>About Packages</title>
<indexterm>
- <primary>packages, defined</primary>
+ <primary>packages</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
All of the software and documentation prepared for use with
@@ -206,12 +221,12 @@
<para>
Packages also include a digital signature to prove their source.
- This digital signature is verified by software management
- utilities 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 the package sources approved by the system
- administrator.
+ 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>
</section>
18 years, 11 months
- 1
- 0
owners pr-owners,NONE,1.1
by fedora-docs-commits＠redhat.com
Author: jtr
Update of /cvs/docs/owners
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16183
Added Files:
pr-owners
Log Message:
The "pr-owners" script makes it easy to see what is in that machine-readable
"owners.list" script.
--- NEW FILE pr-owners ---
#!/bin/sh
########################################################################
# This "pr-owners" script displays the content of the "owners.list"
# file in a human readable format. Use it like this:
#
# $ ./pr-owners owners.list | less
#
########################################################################
awk '
function trim( s, v ) {
v = s
sub( /^[ \t]*/, "", v )
sub( /[ \t]*$/, "", v )
return( v )
}
BEGIN {
FS = "|"
}
{ sub( /#.*$/, "" ) }
NF == 6 {
product = trim( $1 )
component = trim( $2 )
description = trim( $3 )
initialowner = trim( $4 )
qacontact = trim( $5 )
initialcclist = trim( $6 )
if( others ) {
printf "\n"
}
others = 1
printf "%s/%s\n\n", product, component
printf "\tOwner:\t%s\n", initialowner
printf "\tQA:\t%s\n", qacontact
printf "\tCC:\t%s\n", initialcclist
printf "\n"
# printf "\t%s\n", description
nwords = split( description, words, /[ \t]/ )
# printf "%d words\n", nwords
leadin = ""
sep = ""
line = ""
for( i = 1; i <= nwords; ++i ) {
word = words[ i ]
if( (length(word)+length(sep)+length(line)) >= 64 ) {
printf "\t%s\n", line
line = ""
sep = ""
}
line = line sep word
sep = " "
}
if( length( line ) > 0 ) {
printf "\t%s\n", line
}
}
' $@
18 years, 11 months
- 1
- 0