web/html/docs/beta/mirror-tutorial sn-client-config.php, NONE, 1.1 generated-index.php, 1.1, 1.2 index.php, 1.1, 1.2 ln-legalnotice.php, 1.1, 1.2 rv-revhistory.php, 1.1, 1.2 sn-planning-and-setup.php, 1.1, 1.2 sn-server-config.php, 1.1, 1.2

Mon Oct 17 02:17:58 UTC 2005

Author: pfrields

Update of /cvs/fedora/web/html/docs/beta/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21875

Modified Files:
	generated-index.php index.php ln-legalnotice.php 
	rv-revhistory.php sn-planning-and-setup.php 
	sn-server-config.php 
Added Files:
	sn-client-config.php 
Log Message:
Push 0.34 version


***** Error reading new file: [Errno 2] No such file or directory: 'sn-client-config.php'

Index: generated-index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/generated-index.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2

--- generated-index.php	15 Oct 2005 15:57:32 -0000	1.1
+++ generated-index.php	17 Oct 2005 02:17:56 -0000	1.2
@@ -7,7 +7,7 @@
 
 ?>
 
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-server-config.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="generated-index"></a>Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>A</h3><dl><dt>anaconda, <a href="sn-planning-and-setup.php#sn-copying-original-distribution">Copying the Original Distribution</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>distribution, <a href="sn-planning-and-setup.php#sn-hierarchy">The Distribution Structure</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>exploded tree, <a href="sn-planning-and-setup.php#sn-copying-original-distribution">Copying the Original Distribution</a></dt></dl></div><div class="indexdi!
 v"><h3>M</h3><dl><dt>mirror, <a href="index.php#sn-about-mirrors">About Mirrors</a></dt><dd><dl><dt>upstream, <a href="index.php#sn-about-mirrors">About Mirrors</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>repository, <a href="sn-server-config.php#sn-repositories">Configuring Repositories</a></dt><dt>RPM, <a href="sn-planning-and-setup.php#sn-hierarchy">The Distribution Structure</a></dt><dd><dl><dt>dependencies, <a href="sn-server-config.php#sn-solving-dependencies">Solving Dependencies</a></dt><dt>header, <a href="sn-server-config.php#sn-solving-dependencies">Solving Dependencies</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>yum, <a href="sn-server-config.php#sn-solving-dependencies">Solving Dependencies</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-server-config.php">Prev</a> </td><td width="20%" align=!
 "center"> </td><td width="40%" align="right"> </td><!
 /tr><t
td width="40%" align="left" valign="top">3. Server Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-client-config.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="generated-index"></a>Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>A</h3><dl><dt>anaconda, <a href="sn-planning-and-setup.php#sn-copying-original-distribution">Copying the Original Distribution</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>distribution, <a href="sn-planning-and-setup.php#sn-hierarchy">The Distribution Structure</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>exploded tree, <a href="sn-planning-and-setup.php#sn-copying-original-distribution">Copying the Original Distribution</a></dt></dl></div><div class="indexdi!
 v"><h3>M</h3><dl><dt>mirror, <a href="index.php#sn-about-mirrors">About Mirrors</a></dt><dd><dl><dt>upstream, <a href="index.php#sn-about-mirrors">About Mirrors</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>repository, <a href="sn-server-config.php#sn-repositories">Configuring Repositories</a></dt><dt>RPM, <a href="sn-planning-and-setup.php#sn-hierarchy">The Distribution Structure</a></dt><dd><dl><dt>dependencies, <a href="sn-server-config.php#sn-solving-dependencies">Solving Dependencies</a></dt><dt>header, <a href="sn-server-config.php#sn-solving-dependencies">Solving Dependencies</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>yum, <a href="sn-server-config.php#sn-solving-dependencies">Solving Dependencies</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-client-config.php">Prev</a> </td><td width="20%" align=!
 "center"> </td><td width="40%" align="right"> </td><!
 /tr><t
td width="40%" align="left" valign="top">4. Client Configuration </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div>
 
 <?
 


Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/index.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.php	15 Oct 2005 15:57:32 -0000	1.1
+++ index.php	17 Oct 2005 02:17:56 -0000	1.2
@@ -7,17 +7,7 @@
 
 ?>
 
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Mirror Tutorial - <span class="emphasis"><em>BETA</em></span></th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-planning-and-setup.php">Next</a></td></tr></table><hr></div><div class="article" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="mirror-tutorial"></a>Mirror Tutorial - <span class="emphasis"><em>BETA</em></span></h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">
-	  Paul
-	</span> <span class="othername">
-	  W.
-	</span> <span class="surname">
-	  Frields
-	</span></h3></div></div></div><div><p class="copyright">Copyright © 
-	2004
-       
-	Paul W. Frields
-      </p></div><div><a href="ln-legalnotice.php">Legal Notice</a></div><div><a href="rv-revhistory.php">Revision History</a></div></div><hr></div><div class="toc"><dl><dt><span class="section"><a href="index.php#sn-introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="index.php#sn-purpose">1.1. Purpose</a></span></dt><dt><span class="section"><a href="index.php#sn-audience">1.2. Audience</a></span></dt><dt><span class="section"><a href="index.php#sn-about-mirrors">1.3. About Mirrors</a></span></dt><dt><span class="section"><a href="index.php#sn-additional-resources">1.4. Additional Resources</a></span></dt><dt><span class="section"><a href="index.php#sn-acknowledgements">1.5. Acknowledgements</a></span></dt></dl></dd><dt><span class="section"><a href="sn-planning-and-setup.php">2. Planning and Setup</a></span></dt><dd><dl><dt><span class="section"><a href="sn-planning-and-setup.php#sn-hierarchy">2.1. The Distribution Structure</a></span></!
 dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-copying-original-distribution">2.2. Copying the Original Distribution</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-trimming-tree">2.3. Trimming Branches</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-download-files">2.4. Downloading the Files</a></span></dt><dd><dl><dt><span class="section"><a href="sn-planning-and-setup.php#sn-http-and-ftp-download">2.4.1. Download Using HTTP or FTP</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-rsync">2.4.2. The <code class="command">rsync</code> Command</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-rsync-download">2.4.3. Downloading Using <code class="command">rsync</code></a></span></dt></dl></dd><dt><span class="section"><a href="sn-planning-and-setup.php#sn-maintenance">2.5. Maintaining Your Mirror</a></span></dt></dl></dd><dt><span class="!
 section"><a href="sn-server-config.php">3. Server Configuratio!
 n</a><
an></dt><dd><dl><dt><span class="section"><a href="sn-server-config.php#sn-setting-up-apache">3.1. Setting Up Apache</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-solving-dependencies">3.2. Solving Dependencies</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repositories">3.3. Configuring Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sn-server-config.php#sn-yum-arch">3.3.1. <code class="command">yum-arch</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-createrepo">3.3.2. <code class="command">createrepo</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repository-locations">3.3.3. Repository Locations</a></span></dt></dl></dd></dl></dd><dt><span class="index"><a href="generated-index.php">Index</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-int!
 roduction"></a>1. Introduction</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-purpose"></a>1.1. Purpose</h3></div></div></div><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Mirror Tutorial - <span class="emphasis"><em>BETA</em></span></th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-planning-and-setup.php">Next</a></td></tr></table><hr></div><div class="article" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="mirror-tutorial"></a>Mirror Tutorial - <span class="emphasis"><em>BETA</em></span></h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></h3></div></div></div><div><p class="copyright">Copyright © 2004, 2005 Paul W. Frields</p></div><div><a href="ln-legalnotice.php">Legal Notice</a></div><div><a href="rv-revhistory.php">Revision History</a></div></div><hr></div><div class=!
 "toc"><dl><dt><span class="section"><a href="index.php#sn-introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="index.php#sn-purpose">1.1. Purpose</a></span></dt><dt><span class="section"><a href="index.php#sn-audience">1.2. Audience</a></span></dt><dt><span class="section"><a href="index.php#sn-about-mirrors">1.3. About Mirrors</a></span></dt><dt><span class="section"><a href="index.php#sn-additional-resources">1.4. Additional Resources</a></span></dt><dt><span class="section"><a href="index.php#sn-acknowledgements">1.5. Acknowledgements</a></span></dt></dl></dd><dt><span class="section"><a href="sn-planning-and-setup.php">2. Planning and Setup</a></span></dt><dd><dl><dt><span class="section"><a href="sn-planning-and-setup.php#sn-hierarchy">2.1. The Distribution Structure</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-copying-original-distribution">2.2. Copying the Original Distribution</a></span></dt><dt><s!
 pan class="section"><a href="sn-planning-and-setup.php#sn-trim!
 ming-t
">2.3. Trimming Branches</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-download-files">2.4. Downloading the Files</a></span></dt><dd><dl><dt><span class="section"><a href="sn-planning-and-setup.php#sn-http-and-ftp-download">2.4.1. Download Using HTTP or FTP</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-rsync">2.4.2. The <code class="command">rsync</code> Command</a></span></dt><dt><span class="section"><a href="sn-planning-and-setup.php#sn-rsync-download">2.4.3. Downloading Using <code class="command">rsync</code></a></span></dt></dl></dd><dt><span class="section"><a href="sn-planning-and-setup.php#sn-maintenance">2.5. Maintaining Your Mirror</a></span></dt></dl></dd><dt><span class="section"><a href="sn-server-config.php">3. Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sn-server-config.php#sn-setting-up-apache">3.1. Setting Up Apache</a></span></dt><dt><span class="section"><!
 a href="sn-server-config.php#sn-solving-dependencies">3.2. Solving Dependencies</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repositories">3.3. Configuring Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sn-server-config.php#sn-yum-arch">3.3.1. <code class="command">yum-arch</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-createrepo">3.3.2. <code class="command">createrepo</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repository-locations">3.3.3. Repository Locations</a></span></dt></dl></dd></dl></dd><dt><span class="section"><a href="sn-client-config.php">4. Client Configuration</a></span></dt><dt><span class="index"><a href="generated-index.php">Index</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-introduction"></a>1. Introduction</h2></div></div></div><div!
  class="section" lang="en"><div class="titlepage"><div><div><h!
 3 clas
title"><a name="sn-purpose"></a>1.1. Purpose</h3></div></div></div><p>
         This tutorial presents a number of related topics that allow an
         administrator to seamlessly integrate mirroring and update
         services for Fedora Core.  Use these services to provision a classroom,
@@ -30,15 +20,15 @@
     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.33 (2005-10-15).
+    mirror-tutorial-0.34 (2005-10-16).
   </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
     improvements.
   </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-audience"></a>1.2. Audience</h3></div></div></div><p>
 	You will find this tutorial more useful if you are a system
-	administrator, or a Fedora Core “<span class="quote">power user</span>” familiar with
-	the following topics:
+	administrator, or a Fedora Core "power user" familiar with the
+	following topics:
       </p><div class="itemizedlist"><ul type="disc"><li><p>
 	    Fedora Core system installation and administration
 	  </p></li><li><p>
@@ -47,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="id2591998"></a> is a server
+	<a class="indexterm" name="id2558431"></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
@@ -57,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="id2592019"></a>. If possible, choose an upstream mirror that is
+	called an <span class="emphasis"><em>upstream mirror</em></span><a class="indexterm" name="id2558213"></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.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ln-legalnotice.php	15 Oct 2005 15:57:32 -0000	1.1
+++ ln-legalnotice.php	17 Oct 2005 02:17:56 -0000	1.2
@@ -26,7 +26,7 @@
     They all may be freely redistributed with documentation
     produced for the Fedora Project.
     </p><p>
-    mirror-tutorial-0.33 (2005-10-15)
+    mirror-tutorial-0.34 (2005-10-16)
   </p><p>
     Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux
     Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts,




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.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-planning-and-setup.php	15 Oct 2005 15:57:32 -0000	1.1
+++ sn-planning-and-setup.php	17 Oct 2005 02:17:56 -0000	1.2
@@ -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="id2591853"></a>, which is the collection of all Fedora-related
+	The Fedora <span class="emphasis"><em>distribution</em></span><a class="indexterm" name="id2558320"></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="id2638877"></a>, originally the Red Hat Package Manager and now
+	  <em class="firstterm">RPM</em><a class="indexterm" name="id2605290"></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
@@ -103,7 +103,7 @@
 	folder on the server.
       </p><p>
 	Copy all the files from the <code class="filename">SRPMS</code> folder on
-	each of the “<span class="quote">Sources</span>” discs to the
+	each of the "Sources" discs to the
 	<code class="filename">fedora/linux/core/4/SRPMS</code> folder on
 	the server. Make a link in the <code class="filename">os</code> folder
 	that occurs under each architecture. Follow this example:
@@ -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="id2639035"></a>, the Fedora Core installation program, calls this directory
-	structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2639048"></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="id2605444"></a>, the Fedora Core installation program, calls this directory
+	structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2605458"></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.
@@ -166,26 +166,28 @@
 	      support x86-64 hosts later, though, you must restore mirroring of
 	      these branches.
 	    </p></dd><dt><span class="term">The <code class="filename">development</code> folder (formerly
-	    “<span class="quote">Rawhide</span>”).</span></dt><dd><p>
-	      This folder contains all the latest “<span class="quote">bleeding-edge</span>”
+	    "Rawhide").</span></dt><dd><p>
+	      This folder contains all the latest "bleeding-edge"
 	      packages from the Fedora Project. If you participate in active Fedora
-	      development, you should not trim this branch. Fedora 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
+	      development, you should not trim this branch. Fedora
+	      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.
 	    </p></dd><dt><span class="term">The <code class="filename">testing</code> folders.</span></dt><dd><p>
-	      These branches contain updates that are being subjected to quality
-	      assurance through public testing, as well as the test or
-	      “<span class="quote">pre-release</span>” versions of the Fedora Core distribution. The
-	      <code class="filename">testing</code> folder under the main
-	      <code class="filename">core</code> tree is where test versions of the
-	      distribution, such as Fedora Core 4 test1, are kept. (Users of Fedora Core
-	      test distributions are often directed to use the
-	      <code class="filename">development</code> branch to update packages.) The
-	      <code class="filename">testing</code> folder, under
-	      <code class="filename">updates</code>, contains package updates that have
-	      not yet passed the public testing phase.
+	      These branches contain updates that are being subjected to
+	      quality assurance through public testing, as well as the
+	      test or "pre-release" versions of the Fedora Core
+	      distribution. The <code class="filename">testing</code> folder
+	      under the main <code class="filename">core</code> tree is where
+	      test versions of the distribution, such as Fedora Core
+	      4 test1, are kept. (Users of Fedora Core test distributions
+	      are often directed to use the
+	      <code class="filename">development</code> branch to update
+	      packages.) The <code class="filename">testing</code> folder, under
+	      <code class="filename">updates</code>, contains package updates
+	      that have not yet passed the public testing phase.
 	    </p></dd><dt><span class="term">The <code class="filename">debug</code> folders.</span></dt><dd><p>
 	      These folders contain packages that enable developers and
 	      skilled users to interpret data created when a program
@@ -247,12 +249,13 @@
 	      <code class="filename"><em class="replaceable"><code>/pub/mirror</code></em></code>
 	      portion of the path into your mirror.
 	    </p></li></ul></div><p>
-	  The same syntax works for both HTTP and FTP mirrors. It is
-	  possible that you may download some extraneous files if the
-	  HTTP site formats its pages for browser viewing. These files
-	  can be safely deleted, but return each time the mirror updates
-	  unless you exclude them using special options. See the
-	  <code class="command">wget</code> man pages for more information.
+	  The same syntax works for both HTTP and FTP upstream
+	  mirrors. It is possible that you may download some extraneous
+	  files if the HTTP site formats its pages for browser
+	  viewing. These files can be safely deleted, but return each
+	  time the mirror updates unless you exclude them using special
+	  options. See the <code class="command">wget</code> man pages for more
+	  information.
 	</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sn-rsync"></a>2.4.2. The <code class="command">rsync</code> Command</h4></div></div></div><p>
 	  Use the <code class="command">rsync</code> command to synchronize a set
 	  of files and/or directories with a remote host. It operates in
@@ -263,11 +266,10 @@
 	  downloaded.
 	</p><p>
 	  Begin by identifying the modules available on the upstream
-	  mirror site you have chosen. Note that the double colon
-	  “<span class="quote">::</span>” is always used after the host name to
-	  separate it from the rest of the <code class="command">rsync</code>
-	  path. The following command generates a list of
-	  “<span class="quote">modules</span>” on the upstream mirror.
+	  mirror site you have chosen. Note that the double colon "::"
+	  is always used after the host name to separate it from the
+	  rest of the <code class="command">rsync</code> path. The following
+	  command generates a list of "modules" on the upstream mirror.
 	</p><pre class="screen">
 <strong class="userinput"><code>rsync mirror.example.org::</code></strong>
 </pre><p>
@@ -279,10 +281,9 @@
 	  the <code class="filename">fedora/linux/core</code> path found at the
 	  Fedora Project main download server. To list the contents of the Fedora Core
 	  4 distribution folder on the upstream server, issue the
-	  following command. Do not forget the trailing slash
-	  “<span class="quote">/</span>”.  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 "/".
+	  Without it, you only receive a listing of a folder name that
+	  matches the last component of the remote path.
 	</p><pre class="screen">
 <strong class="userinput"><code>rsync mirror.example.org::fedora-linux-core/4/</code></strong>
 </pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sn-rsync-download"></a>2.4.3. Downloading Using <code class="command">rsync</code></h4></div></div></div><p>
@@ -324,10 +325,10 @@
 	  </p></td></tr></table></div><pre class="screen">
 <strong class="userinput"><code>rsync -PHav mirror.example.org::fedora-linux-core/4/ /var/www/mirror/fedora/linux/core/4</code></strong>
 </pre><p><a name="rsync-n-switch"></a>
-	  The <code class="command">-n</code> switch performs a “<span class="quote">dry run</span>”
-	  using the other given parameters. Use this switch to test any
-	  <code class="command">rsync</code> command if you are unsure what files you will
-	  receive. See also <a href="sn-planning-and-setup.php#rsync-possible-data-loss" title="Possible data loss">Possible data loss</a>.
+	  The <code class="command">-n</code> switch performs a "dry run" using
+	  the other given parameters. Use this switch to test any
+	  <code class="command">rsync</code> command if you are unsure what files
+	  you will receive. See also <a href="sn-planning-and-setup.php#rsync-possible-data-loss" title="Possible data loss">Possible data loss</a>.
 	</p><p>
 	  The <code class="command">-z</code> switch enables compression during the
 	  <code class="command">rsync</code> process. The server compresses data before


Index: sn-server-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/sn-server-config.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-server-config.php	15 Oct 2005 15:57:32 -0000	1.1
+++ sn-server-config.php	17 Oct 2005 02:17:56 -0000	1.2
@@ -7,7 +7,7 @@
 
 ?>
 
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Server Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-planning-and-setup.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="generated-index.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-server-config"></a>3. Server Configuration</h2></div></div></div><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Server Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-planning-and-setup.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-client-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-server-config"></a>3. Server Configuration</h2></div></div></div><p>
       This section gives guidance on setting up a HTTP (Web) server that
       provides installation and update mirror services.
     </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-setting-up-apache"></a>3.1. Setting Up Apache</h3></div></div></div><p>
@@ -23,7 +23,7 @@
 	Next, create a configuration file
 	<code class="filename">/etc/httpd/conf.d/mirror.conf</code> for your
 	mirror files.  The following listing is an example:
-      </p><div class="example"><a name="id2640529"></a><pre class="screen">
+      </p><div class="example"><a name="id2606915"></a><pre class="screen">
 <code class="computeroutput"># The name at which the installation tree will be shared, 
 # followed by the name of the root directory of that tree.
 Alias /mirror /var/www/mirror
@@ -55,12 +55,12 @@
 	URL
 	http://<em class="replaceable"><code>server.mydomain.org</code></em>/mirror/<em class="replaceable"><code>path</code></em>.
       </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-solving-dependencies"></a>3.2. Solving Dependencies</h3></div></div></div><p>
-	Every RPM package has a <a class="indexterm" name="id2640619"></a><em class="firstterm">header</em> that contains all
+	Every RPM package has a <a class="indexterm" name="id2607005"></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="id2640640"></a>. A dependency is a requirement for one or more
+	<span class="emphasis"><em>dependencies</em></span><a class="indexterm" name="id2607026"></a>. A dependency is a requirement for one or more
 	additional packages.
       </p><p>
 	Packages installed without satisfying their dependencies may not
@@ -71,7 +71,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="id2640675"></a>, is a Python-based system for computing and solving
+	<span class="emphasis"><em>yum</em></span><a class="indexterm" name="id2607061"></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
@@ -96,7 +96,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.3. Configuring Repositories</h3></div></div></div><p>
       A <code class="command">yum</code>
-	<span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2640774"></a> is a collection of packages on a server which
+	<span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2607160"></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>
@@ -177,7 +177,7 @@
 	      Once again, for <code class="command">yum-arch</code> use
 	      <code class="command">-l</code> and/or <code class="command">-s</code> if
 	      appropriate.
-	    </p></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-planning-and-setup.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Planning and Setup </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> Index</td></tr></table></div>
+	    </p></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-planning-and-setup.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn-client-config.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Planning and Setup </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 4. Client Configuration</td></tr></table></div>
 
 <?
 


