web/html/docs/beta/mirror-tutorial generated-index.php, 1.6, 1.7 index.php, 1.6, 1.7 ln-legalnotice.php, 1.6, 1.7 rv-revhistory.php, 1.6, 1.7 sn-client-config.php, 1.5, 1.6 sn-planning-and-setup.php, 1.6, 1.7 sn-server-config.php, 1.6, 1.7
Paul W. Frields (pfrields)
fedora-extras-commits at redhat.com
Thu Nov 17 12:42:59 UTC 2005
Author: pfrields
Update of /cvs/fedora/web/html/docs/beta/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6386
Modified Files:
generated-index.php index.php ln-legalnotice.php
rv-revhistory.php sn-client-config.php
sn-planning-and-setup.php sn-server-config.php
Log Message:
Update to 0.37 and push
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/index.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.php 11 Nov 2005 16:59:59 -0000 1.6
+++ index.php 17 Nov 2005 12:42:57 -0000 1.7
@@ -20,7 +20,7 @@
at <a href="http://bugzilla.redhat.com/" target="_top">http://bugzilla.redhat.com/</a>. When you file your bug, select "Fedora Documentation" as the
<code class="systemitem">Product</code>, and select the title of this document as
the <code class="systemitem">Component</code>. The version of this document is
- mirror-tutorial-0.36 (2005-11-11).
+ mirror-tutorial-0.37 (2005-11-17).
</p><p>
The maintainers of this document will automatically receive your bug report.
On behalf of the entire Fedora community, thank you for helping us make
@@ -37,7 +37,7 @@
Using a command line interface
</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-mirrors"></a>1.3. About Mirrors</h3></div></div></div><p>
A <span class="emphasis"><em>mirror</em></span>
- <a class="indexterm" name="id2544878"></a> is a server
+ <a class="indexterm" name="id2784732"></a> 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
@@ -47,7 +47,7 @@
managing Internet services.
</p><p>
The site from which you retrieve files to build your mirror is
- called an <span class="emphasis"><em>upstream mirror</em></span><a class="indexterm" name="id2544899"></a>. If possible, choose an upstream mirror that is
+ called an <span class="emphasis"><em>upstream mirror</em></span><a class="indexterm" name="id2784752"></a>. 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. Use only upstream mirrors
Index: ln-legalnotice.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/ln-legalnotice.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- ln-legalnotice.php 11 Nov 2005 16:59:59 -0000 1.6
+++ ln-legalnotice.php 17 Nov 2005 12:42:57 -0000 1.7
@@ -26,7 +26,7 @@
They all may be freely redistributed with documentation
produced for the Fedora Project.
</p><p>
- mirror-tutorial-0.36 (2005-11-11)
+ mirror-tutorial-0.37 (2005-11-17)
</p><p>
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of
Red Hat, Inc. in the United States and other countries.
Index: rv-revhistory.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/rv-revhistory.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rv-revhistory.php 11 Nov 2005 16:59:59 -0000 1.6
+++ rv-revhistory.php 17 Nov 2005 12:42:57 -0000 1.7
@@ -77,6 +77,10 @@
Added some additional information about repository
configuration (#172815, #172819).
</p>
+ </td></tr><tr><td align="left">Revision 0.37</td><td align="left">2005-11-17</td><td align="left">PaulWFrields</td></tr><tr><td align="left" colspan="3">
+ <p>
+ Fixed createrepo and yum-arch command issues (#172819).
+ </p>
</td></tr></table></div></div>
<?
Index: sn-client-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/sn-client-config.php,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- sn-client-config.php 11 Nov 2005 16:59:59 -0000 1.5
+++ sn-client-config.php 17 Nov 2005 12:42:57 -0000 1.6
@@ -14,7 +14,7 @@
<code class="filename">/etc/yum.repos.d</code> and end with the suffix
<code class="filename">.repo</code>. Below is an example configuration
file.
- </p><div class="example"><a name="id2595476"></a><pre class="screen">
+ </p><div class="example"><a name="id2835464"></a><pre class="screen">
<code class="computeroutput">[mirror]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://server.mydomain.net/mirror/fedora/linux/core/$releasever/$basearch
Index: sn-planning-and-setup.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/sn-planning-and-setup.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- sn-planning-and-setup.php 11 Nov 2005 16:59:59 -0000 1.6
+++ sn-planning-and-setup.php 17 Nov 2005 12:42:57 -0000 1.7
@@ -8,7 +8,7 @@
?>
<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2. Planning and Setup</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-server-config.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-planning-and-setup"></a>2. Planning and Setup</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-hierarchy"></a>2.1. The Distribution Structure</h3></div></div></div><p>
- The Fedora <span class="emphasis"><em>distribution</em></span><a class="indexterm" name="id2544966"></a>, which is the collection of all Fedora-related
+ The Fedora <span class="emphasis"><em>distribution</em></span><a class="indexterm" name="id2784352"></a>, which is the collection of all Fedora-related
files, uses the directory tree in <a href="sn-planning-and-setup.php#ex-fedora-dir-tree" title="Example 1. Fedora directory tree">Example 1, “Fedora directory tree”</a>. It may include multiple
versions of Fedora Core. The tree design makes it easier to "trim"
unnecessary or undesired files. When you set up a mirror,
@@ -73,7 +73,7 @@
folder contains images of the CD-ROM version of the
distribution.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: RPM packages"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">RPM packages</th></tr><tr><td align="left" valign="top"><p>
- <em class="firstterm">RPM</em><a class="indexterm" name="id2592878"></a>, originally the Red Hat Package Manager and now
+ <em class="firstterm">RPM</em><a class="indexterm" name="id2832861"></a>, originally the Red Hat Package Manager and now
the RPM Package Manager, is not just a file format. RPM is
also a system that tracks and interconnects software and
version information. The RPM system is quite popular, and many
@@ -111,8 +111,8 @@
<strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/4/i386/os/Fedora
ln ../../SRPMS SRPMS</code></strong>
</pre><p>
- The documentation for <span><strong class="application">anaconda</strong></span><a class="indexterm" name="id2593032"></a>, the Fedora Core installation program, calls this directory
- structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2593045"></a>. This is because the package data on each CD is extracted,
+ The documentation for <span><strong class="application">anaconda</strong></span><a class="indexterm" name="id2833014"></a>, the Fedora Core installation program, calls this directory
+ structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2833028"></a>. This is because the package data on each CD is extracted,
or exploded, to a large directory tree with a predetermined structure.
The <span><strong class="application">anaconda</strong></span> installer expects this structure
to some extent.
Index: sn-server-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/sn-server-config.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- sn-server-config.php 11 Nov 2005 16:59:59 -0000 1.6
+++ sn-server-config.php 17 Nov 2005 12:42:57 -0000 1.7
@@ -66,7 +66,7 @@
create the configuration file
<code class="filename">/etc/httpd/conf.d/mirror.conf</code>. The
following listing is an example:
- </p><div class="example"><a name="id2594710"></a><pre class="screen">
+ </p><div class="example"><a name="id2834693"></a><pre class="screen">
<code class="computeroutput"># The name at which the mirror will be shared,
# followed by the name of the root directory of that tree.
Alias /mirror /var/www/mirror
@@ -103,12 +103,12 @@
you build your mirror in another directory, you may need to
modify the SELinux policy.
</p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-solving-dependencies"></a>3.3. Solving Dependencies</h3></div></div></div><p>
- Every RPM package has a <a class="indexterm" name="id2594827"></a><em class="firstterm">header</em> that contains all
+ Every RPM package has a <a class="indexterm" name="id2834810"></a><em class="firstterm">header</em> that contains all
the vital information about that package. This information
includes name, version and release, contents, the capabilities
provided by the package, and any prerequisites. These
prerequisites may include
- <span class="emphasis"><em>dependencies</em></span><a class="indexterm" name="id2594853"></a>. A dependency is a requirement for one or more
+ <span class="emphasis"><em>dependencies</em></span><a class="indexterm" name="id2834836"></a>. A dependency is a requirement for one or more
additional packages.
</p><p>
Packages installed without satisfying their dependencies may not
@@ -119,7 +119,7 @@
automatically, providing an improved user experience.
</p><p>
The Yellow Dog Updater Modified, or
- <span class="emphasis"><em>yum</em></span><a class="indexterm" name="id2594886"></a>, is a Python-based system for computing and solving
+ <span class="emphasis"><em>yum</em></span><a class="indexterm" name="id2834869"></a>, is a Python-based system for computing and solving
RPM dependencies. A <code class="command">yum</code> client retrieves a
cache of headers from its repository server, as well as a list
of available RPM packages and their exact locations on the
@@ -144,7 +144,7 @@
to <a href="http://fedora.redhat.com/docs/yum/" target="_top">http://fedora.redhat.com/docs/yum/</a>.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-repositories"></a>3.4. Configuring Repositories</h3></div></div></div><p>
A <code class="command">yum</code>
- <span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2594986"></a> is a collection of packages on a server which
+ <span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2834969"></a> is a collection of packages on a server which
supports <code class="command">yum</code> clients. Repositories can serve
both types of clients if desired.
</p><p>
@@ -165,31 +165,34 @@
<span class="emphasis"><em>must</em></span> use <code class="command">createrepo</code> on
your server's repositories.
</p></td></tr></table></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sn-yum-arch"></a>3.4.1. <code class="command">yum-arch</code></h4></div></div></div><p>
- A directory which supports older versions of
- <code class="command">yum</code> (before 2.2) is named
- <code class="filename">headers</code>. It is created by using the
- command <code class="command">yum-arch</code>, which is run against the
- directory <span class="emphasis"><em>under which</em></span> you want the
- <code class="filename">headers</code> directory to appear. The
+ The <code class="command">yum-arch</code> command creates a directory
+ named <code class="filename">headers/</code> which supports older
+ versions of <code class="command">yum</code> (before 2.2). The
<code class="command">yum-arch</code> program searches recursively
- through that directory and any subdirectories for RPM
- packages, and includes them in the header data.
+ through a target directory and any subdirectories for RPM
+ packages, and includes them in the header data. The
+ <code class="command">yum-arch</code> command always creates the
+ <code class="filename">headers/</code> directory in the current working
+ directory. Therefore you should change your working directory
+ to the directory where you want <code class="filename">headers/</code>
+ to appear.
</p><pre class="screen">
-<strong class="userinput"><code>yum-arch -l -s /var/www/mirror/fedora/linux/core/4/i386/os</code></strong>
+<strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/4/i386/os
+su -c 'yum-arch -ls .'</code></strong>
</pre><p>
- The <code class="command">-l</code> switch follows symbolic links. The
+ Enter the root password at the prompt. The
+ <code class="command">-l</code> switch follows symbolic links. The
<code class="command">-s</code> switch includes SRPMS (source RPM
packages) in the header list. The command above creates the
<code class="command">yum</code> header cache in the directory
- <code class="filename">/var/www/mirror/fedora/linux/core/4/i386/os/headers</code>.
+ <code class="filename">/var/www/mirror/fedora/linux/core/4/i386/os/headers/</code>.
</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sn-createrepo"></a>3.4.2. <code class="command">createrepo</code></h4></div></div></div><p>
The <code class="command">createrepo</code> command creates repository
information to support newer versions of
<code class="command">yum</code> (and possibly other repository client
programs). The <code class="command">createrepo</code> command stores
this data in a folder named <code class="filename">repodata</code>.
- Just as with <code class="command">yum-arch</code>, run
- <code class="command">createrepo</code> against the directory
+ Run <code class="command">createrepo</code> against the directory
<span class="emphasis"><em>under which</em></span> you want the
<code class="filename">repodata</code> directory to appear. The
<code class="command">createrepo</code> program also searches
@@ -200,7 +203,7 @@
directory
<code class="filename">/var/www/mirror/fedora/linux/core/4/i386/os/repodata</code>.
</p><pre class="screen">
-<strong class="userinput"><code>createrepo /var/www/mirror/fedora/linux/core/4/i386/os</code></strong>
+<strong class="userinput"><code>su -c 'createrepo /var/www/mirror/fedora/linux/core/4/i386/os'</code></strong>
</pre><p>
To create repository data for package groups in addition to
the package files, use the <code class="command">createrepo -g</code>
@@ -212,7 +215,7 @@
group file
<code class="filename">/var/www/mirror/fedora/linux/core/4i386/os/Fedora/base/comps.xml</code>.
</p><pre class="screen">
-<strong class="userinput"><code>createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/4/i386/os</code></strong>
+<strong class="userinput"><code>su -c 'createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/4/i386/os'</code></strong>
</pre><p>
You may have certain clients who update their version of
<code class="command">yum</code> in a non-prescribed way. To minimize
More information about the fedora-extras-commits
mailing list