web/html/docs/mirror/en generated-index.php, 1.1, 1.2 index.php, 1.1, 1.2 rv-revhistory.php, 1.1, 1.2 sn-client-config.php, 1.1, 1.2 sn-planning-and-setup.php, 1.1, 1.2 sn-server-config.php, 1.1, 1.2

Paul W. Frields (pfrields) fedora-websites-list at redhat.com
Tue Aug 15 03:19:40 UTC 2006 

Author: pfrields

Update of /cvs/fedora/web/html/docs/mirror/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16794

Modified Files:
	generated-index.php index.php rv-revhistory.php 
	sn-client-config.php sn-planning-and-setup.php 
	sn-server-config.php 
Log Message:
Update English version to 1.0.1 as well


Index: generated-index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/en/generated-index.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- generated-index.php	14 Aug 2006 17:34:25 -0000	1.1
+++ generated-index.php	15 Aug 2006 03:19:37 -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-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>
+<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="indexdiv"><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><tr><td width="40%" !
 align=
ft" 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/mirror/en/index.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.php	14 Aug 2006 17:34:25 -0000	1.1
+++ index.php	15 Aug 2006 03:19:37 -0000	1.2
@@ -7,7 +7,7 @@
 
 ?>
 
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Mirror Tutorial</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</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><span class="section"><a href="sn-planning-and-setup.php#sn-trimming-tree">2.3. Trimming Branc!
 hes</a></span></dt><dt><span class="section"><a href="sn-plann!
 ing-an
etup.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-installing-apache">3.1. Installing The Apache Web Server</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-configuring-apache">3.2. Configuring The Apac!
 he Web Server</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-solving-dependencies">3.3. Solving Dependencies</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repositories">3.4. Configuring Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sn-server-config.php#sn-yum-arch">3.4.1. <code class="command">yum-arch</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-createrepo">3.4.2. <code class="command">createrepo</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repository-locations">3.4.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-introduct!
 ion"></a>1. Introduction</h2></div></div></div><div class!
 ="sect
" 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</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-US"><div class="titlepage"><div><div><h1 class="title"><a name="mirror-tutorial"></a>Mirror Tutorial</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="othercredit"><span class="firstname">José</span> <span class="othername">Nuno</span> <span class="surname">Pires</span></p></div><div><p class="othercredit"><span class="firstname">Diego</span> <span class="othername">Búrigo</span> <span class="surname">Zacarão</span></p></div><div><p class="othercredit!
 "><span class="firstname">Hugo</span> <span class="surname">Cisneiros</span></p></div><div><p class="copyright">Copyright © 2004, 2005 Paul W. Frields</p></div><div><a href="ln-legalnotice-opl.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 hre!
 f="sn-
nning-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-mainten!
 ance">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-installing-apache">3.1. Installing The Apache Web Server</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-configuring-apache">3.2. Configuring The Apache Web Server</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-solving-dependencies">3.3. Solving Dependencies</a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-repositories">3.4. Configuring Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sn-server-config.php#sn-yum-arch">3.4.1. <code class="command">yum-arch</code></a></span></dt><dt><span class="section"><a href="sn-server-config.php#sn-createrepo">3.4.2. <code class="command">createrepo</code></a></span></dt><dt><span class="section"><a href="sn-server-confi!
 g.php#sn-repository-locations">3.4.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-US"><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-US"><div class="titlepage"><div><div><h3 class="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,
@@ -17,15 +17,15 @@
         software.
       </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Reporting Document Errors"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Reporting Document Errors</th></tr><tr><td align="left" valign="top"><p>
     To report an error or omission in this document, file a bug report in Bugzilla
-    at <a href="http://bugzilla.redhat.com/" target="_top">http://bugzilla.redhat.com/</a>.  When you file your bug, select "Fedora Documentation" as the
+    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-1.0 (2006-02-06).
+    mirror-tutorial-1.0.1 (2006-08-07).
   </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>
+  </p></td></tr></table></div></div><div class="section" lang="en-US"><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 "power user" familiar with the
 	following topics:
@@ -35,9 +35,9 @@
 	    Basic Internet protocols (HTTP/Web)
 	  </p></li><li><p>
 	    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>
+	  </p></li></ul></div></div><div class="section" lang="en-US"><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="id2598469"></a> is a server
+	<a class="indexterm" name="id2796049"></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,23 +47,23 @@
 	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="id2598490"></a>. If possible, choose an upstream mirror that is
+	called an <span class="emphasis"><em>upstream mirror</em></span><a class="indexterm" name="id2796070"></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
 	that are intended for public access, unless you have permission
 	from the upstream mirror site administrator.
-      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-additional-resources"></a>1.4. Additional Resources</h3></div></div></div><p>
+      </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-additional-resources"></a>1.4. Additional Resources</h3></div></div></div><p>
 	For more information on installing Fedora Core see the Fedora Core Installation Guide at
 	<a href="http://fedora.redhat.com/docs/fedora-install-guide-en/" target="_top">http://fedora.redhat.com/docs/fedora-install-guide-en/</a>. For more information on basic Internet protocols, see
 	<a href="http://library.albany.edu/internet/internet.html" target="_top">http://library.albany.edu/internet/internet.html</a>, 
 	or search Google at <a href="http://www.google.com/" target="_top">http://www.google.com/</a>.
 	For more general information about mirrors, see <a href="http://en.wikipedia.org/wiki/Mirror_(computing)" target="_top">http://en.wikipedia.org/wiki/Mirror_(computing)</a>.
-      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-acknowledgements"></a>1.5. Acknowledgements</h3></div></div></div><p>
+      </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-acknowledgements"></a>1.5. Acknowledgements</h3></div></div></div><p>
 	Karsten Wade provided editorial services and kept the style
 	crisp and consistent.  Stuart Ellis provided some additional
 	security-related information.
-      </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn-planning-and-setup.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> 2. Planning and Setup</td></tr></table></div>
+      </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn-planning-and-setup.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> 2. Planning and Setup</td></tr></table></div>
 
 <?
 


Index: rv-revhistory.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/en/rv-revhistory.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- rv-revhistory.php	14 Aug 2006 17:34:25 -0000	1.1
+++ rv-revhistory.php	15 Aug 2006 03:19:37 -0000	1.2
@@ -7,7 +7,11 @@
 
 ?>
 
-<div class="revhistory"><div class="revhistory"><table border="1" width="100%" summary="Revision history - Mirror Tutorial"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.0</td><td align="left">2006-02-06</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
+<div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.0.1</td><td align="left">2006-08-06</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
+        <p>
+          Fix mirror list URL (#201558)
+        </p>
+      </td></tr><tr><td align="left">Revision 1.0</td><td align="left">2006-02-06</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
         <p>
           Add lftp section and push to 1.0
         </p>
@@ -95,7 +99,7 @@
         <p>
           Initial version for editorial process.
         </p>
-      </td></tr></table></div></div>
+      </td></tr></table></div>
 
 <?
 


Index: sn-client-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/en/sn-client-config.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-client-config.php	14 Aug 2006 17:34:25 -0000	1.1
+++ sn-client-config.php	15 Aug 2006 03:19:37 -0000	1.2
@@ -7,21 +7,21 @@
 
 ?>
 
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4. Client Configuration</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"> <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-client-config"></a>4. Client Configuration</h2></div></div></div><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4. Client Configuration</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"> <a accesskey="n" href="generated-index.php">Next</a></td></tr></table><hr></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-client-config"></a>4. Client Configuration</h2></div></div></div><p>
       Client systems that use <code class="command">yum</code> to contact your
       mirror also require configuration.  The <code class="command">yum</code>
       repository configuration files are located in
       <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="id2601444"></a><pre class="screen">
+    </p><div class="example"><a name="id2850786"></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
 enabled=1
 gpgcheck=1
 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora</code>
-</pre><p class="title"><b>Example 3. Example
+</pre><p class="title"><b>Example 3. Example
       <code class="filename">/etc/yum.repos.d/fedora-mirror.repo</code></b></p></div><p>
       Client systems should use a repository configuration file for each
       Fedora branch your mirror provides.  The base distribution and
@@ -42,7 +42,7 @@
       of new repositories for end users.  Whether you use such a package
       yourself will depend on the number and skill set of clients your
       repository serves.
-    </p></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"> <a accesskey="n" href="generated-index.php">Next</a></td></tr><tr><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"> Index</td></tr></table></div>
+    </p></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"> <a accesskey="n" href="generated-index.php">Next</a></td></tr><tr><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"> Index</td></tr></table></div>
 
 <?
 


Index: sn-planning-and-setup.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/en/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	14 Aug 2006 17:34:25 -0000	1.1
+++ sn-planning-and-setup.php	15 Aug 2006 03:19:37 -0000	1.2
@@ -7,9 +7,9 @@
 
 ?>
 
-<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="id2598599"></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
+<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-US"><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-US"><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="id2796547"></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,
 	duplicate this tree exactly, or as closely as possible.  If you
@@ -21,7 +21,7 @@
     +-- core
         |-- 1 
         |   ... 
-        +-- 4 
+        +-- 5 
         |   +-- SRPMS 
         |   +-- i386 
         |   |   +-- debug 
@@ -39,41 +39,41 @@
         +-- updates 
             +-- 1 
             |   ... 
-            +-- 4 
+            +-- 5 
             |   +-- SRPMS 
             |   +-- i386 
             |   +-- x86_64 
             +-- testing 
                 +-- 1 
                 |   ... 
-                +-- 4 
+                +-- 5 
                     +-- SRPMS 
                     +-- i386 
                     +-- x86_64</code>
-</pre><p class="title"><b>Example 1. Fedora directory tree</b></p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Naming conventions"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Naming conventions</th></tr><tr><td align="left" valign="top"><p>
+</pre><p class="title"><b>Example 1. Fedora directory tree</b></p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Naming conventions"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Naming conventions</th></tr><tr><td align="left" valign="top"><p>
 	  Throughout the rest of the document,
 	  <code class="filename">/var/www/mirror</code> represents the folder
 	  where all your mirrored files are stored. You may substitute a
 	  different location. This location simplifies sharing your
-	  mirror, due to the shipping configuration of Fedora Core. See <a href="sn-server-config.php" title="3. Server Configuration">Section 3, “Server Configuration”</a> for more information.  The site
+	  mirror, due to the shipping configuration of Fedora Core. See <a href="sn-server-config.php" title="3. Server Configuration">Section 3, “Server Configuration”</a> for more information.  The site
 	  name <code class="computeroutput">mirror.example.com</code>
 	  represents the upstream mirror.
 	</p></td></tr></table></div><p>
 	The
-	<code class="filename">fedora/linux/core/4/<em class="replaceable"><code>arch</code></em>/os</code>
+	<code class="filename">fedora/linux/core/5/<em class="replaceable"><code>arch</code></em>/os</code>
 	directory contains a copy of all the original distribution files
-	for Fedora Core 4. They are the same files found on the DVD and
+	for Fedora Core 5. They are the same files found on the DVD and
 	CD-ROM version of the distribution. The
 	<code class="filename">Fedora</code> subfolder contains all the files that
 	are necessary for installation, including the entire collection
 	of Fedora Core RPM packages. The <code class="filename">images</code> folder
 	contains copies of any floppy diskette or CD-ROM images that
 	boot a system into installation or rescue modes. The
-	<code class="filename">fedora/linux/core/4/<em class="replaceable"><code>arch</code></em>/iso</code>
+	<code class="filename">fedora/linux/core/5/<em class="replaceable"><code>arch</code></em>/iso</code>
 	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="id2597698"></a>, originally the Red Hat Package Manager and now
+	  <em class="firstterm">RPM</em><a class="indexterm" name="id2795116"></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
@@ -91,28 +91,28 @@
 	<span class="emphasis"><em>or</em></span> the distribution files. If possible,
 	include both, provided you have sufficient disk space and/or
 	bandwidth.
-      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-copying-original-distribution"></a>2.2. Copying the Original Distribution</h3></div></div></div><p>
+      </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-copying-original-distribution"></a>2.2. Copying the Original Distribution</h3></div></div></div><p>
 	If you already have reliable CD-ROM installation discs of a
 	distribution, reduce your initial bandwidth and time spent
 	mirroring by copying the files from the discs to your server.
 	Copy all files from Installation Disc 1 into the
-	<code class="filename">fedora/linux/core/4/<em class="replaceable"><code>arch</code></em>/os</code>
+	<code class="filename">fedora/linux/core/5/<em class="replaceable"><code>arch</code></em>/os</code>
 	folder. Then copy all files from the <code class="filename">Fedora</code>
 	folder of each of the remaining Installation discs into the
-	<code class="filename">fedora/linux/core/4/<em class="replaceable"><code>arch</code></em>/os/Fedora</code>
+	<code class="filename">fedora/linux/core/5/<em class="replaceable"><code>arch</code></em>/os/Fedora</code>
 	folder on the server.
       </p><p>
 	Copy all the files from the <code class="filename">SRPMS</code> folder on
 	each of the "Sources" discs to the
-	<code class="filename">fedora/linux/core/4/SRPMS</code> folder on
+	<code class="filename">fedora/linux/core/5/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:
       </p><pre class="screen">
-<strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/4/i386/os/Fedora
+<strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/5/i386/os/Fedora
 ln ../../SRPMS SRPMS</code></strong>
 </pre><p>
-	The documentation for <span><strong class="application">anaconda</strong></span><a class="indexterm" name="id2597850"></a>, the Fedora Core installation program, calls this directory
-	structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2597863"></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="id2795258"></a>, the Fedora Core installation program, calls this directory
+	structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2795271"></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.
@@ -126,7 +126,7 @@
 	to perform this mount automatically in case of a reboot. Each entry
 	looks like this:
       </p><pre class="screen">
-<code class="computeroutput">/<em class="replaceable"><code>path</code></em>/i386/iso/FC4-i386-disc1.iso  /<em class="replaceable"><code>path</code></em>/i386/os/disc1  iso9660  defaults  0 0</code>
+<code class="computeroutput">/<em class="replaceable"><code>path</code></em>/i386/iso/FC5-i386-disc1.iso  /<em class="replaceable"><code>path</code></em>/i386/os/disc1  iso9660  defaults  0 0</code>
 </pre><p>
 	The <span><strong class="application">anaconda</strong></span> installer application
 	automatically detects these folders and uses them properly. In
@@ -146,8 +146,8 @@
 	You only need a single line in <code class="filename">/etc/fstab</code>
 	for mounting the Fedora Core DVD ISO image.  The entry looks like this:
       </p><pre class="screen">
-<code class="computeroutput">/<em class="replaceable"><code>path</code></em>/i386/iso/FC4-i386-DVD.iso  /<em class="replaceable"><code>path</code></em>/i386/os  iso9660  defaults  0 0</code>
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-trimming-tree"></a>2.3. Trimming Branches</h3></div></div></div><p>
+<code class="computeroutput">/<em class="replaceable"><code>path</code></em>/i386/iso/FC5-i386-DVD.iso  /<em class="replaceable"><code>path</code></em>/i386/os  iso9660  defaults  0 0</code>
+</pre></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-trimming-tree"></a>2.3. Trimming Branches</h3></div></div></div><p>
 	You may omit almost any branch of the tree that you do not plan to use.
 	Consider carefully the impact of excluding that folder. Branches you
 	might trim from your mirror include:
@@ -182,7 +182,7 @@
 	      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
-	      5 test2, are kept. (Users of Fedora Core test distributions
+	      6 test2, 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
@@ -208,15 +208,15 @@
 	branches for the distributions you support. These locations
 	contain packages with bug fixes, security patches, and errata
 	updates that your users probably want.
-      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-download-files"></a>2.4. Downloading the Files</h3></div></div></div><p>
+      </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-download-files"></a>2.4. Downloading the Files</h3></div></div></div><p>
 	Locate a public mirror site for Fedora Core by referring to the main
-	project site's mirror page, <a href="http://fedora.redhat.com/projects/docs/" target="_top">http://fedora.redhat.com/projects/docs/</a>. Once you have selected a
-	nearby mirror site, note what services it offers (FTP, HTTP,
-	and/or rsync). A mirror is usually servicing a large number of
-	users. Choose off-peak hours, when possible, to download a large
-	set of files. Be aware of any timezone differences when
-	estimating off-peak hours.
-      </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sn-http-and-ftp-download"></a>2.4.1. Download Using HTTP or FTP</h4></div></div></div><p>
+	project site's mirror page, <a href="http://fedora.redhat.com/Download/mirrors.html" target="_top">http://fedora.redhat.com/Download/mirrors.html</a>. Once you have
+	selected a nearby mirror site, note what services it offers
+	(FTP, HTTP, and/or rsync). A mirror is usually servicing a large
+	number of users. Choose off-peak hours, when possible, to
+	download a large set of files. Be aware of any timezone
+	differences when estimating off-peak hours.
+      </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h4 class="title"><a name="sn-http-and-ftp-download"></a>2.4.1. Download Using HTTP or FTP</h4></div></div></div><p>
 	  To download via HTTP or FTP, use either the
 	  <code class="command">wget</code> or <code class="command">lftp</code>
 	  command. The <code class="command">wget</code> command recurses
@@ -227,7 +227,7 @@
 	  Fedora Core distribution:
 	</p><pre class="screen">
 <strong class="userinput"><code>cd /var/www/mirror 
-wget --mirror -np -nH --cut-dirs=<em class="replaceable"><code>2</code></em> http://mirror.example.com/pub/mirror/fedora/linux/core/4/</code></strong>
+wget --mirror -np -nH --cut-dirs=<em class="replaceable"><code>2</code></em> http://mirror.example.com/pub/mirror/fedora/linux/core/5/</code></strong>
 </pre><p>
 	  Note the options used above:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -274,7 +274,7 @@
 	  <code class="command">lftp</code>:
 	</p><pre class="screen">
 <strong class="userinput"><code>cd /var/www/mirror && \
-lftp -c "open http://mirror.example.com/pub/mirror/linux/core/4/i386/ && \
+lftp -c "open http://mirror.example.com/pub/mirror/linux/core/5/i386/ && \
 mirror --delete --verbose"</code></strong>
 </pre><p>
 	  The <code class="option">-c</code> parameter executes a set of commands
@@ -312,7 +312,7 @@
 	</p><pre class="screen">
 <strong class="userinput"><code>cd /var/www/mirror && \
 lftp -c "set mirror:exclude-regex 'debug\/|repodata\/' && \
-open http://mirror.example.com/pub/mirror/linux/core/updates/4/i386/ && \
+open http://mirror.example.com/pub/mirror/linux/core/updates/5/i386/ && \
 mirror --delete --verbose"</code></strong>
 </pre><p>Consult the <code class="command">lftp</code> man pages for more
 	details and usage options.</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Using Proxy for HTTP or FTP retrieval"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Using Proxy for HTTP or FTP retrieval</th></tr><tr><td align="left" valign="top"><p>
@@ -324,7 +324,7 @@
 	  </p><pre class="screen">
 <strong class="userinput"><code>export http_proxy=http://<em class="replaceable"><code>username</code></em>:<em class="replaceable"><code>password</code></em>@<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>port</code></em>
 export ftp_proxy=http://<em class="replaceable"><code>username</code></em>:<em class="replaceable"><code>password</code></em>@<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>port</code></em></code></strong>
-</pre></td></tr></table></div></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>
+</pre></td></tr></table></div></div><div class="section" lang="en-US"><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
 	  much the same way as <code class="command">rcp</code>, but it is usually
@@ -348,13 +348,13 @@
 	  <code class="filename">fedora-linux-core</code> module is equivalent to
 	  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
+	  5 distribution folder on the upstream server, issue the
 	  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>
+<strong class="userinput"><code>rsync mirror.example.org::fedora-linux-core/5/</code></strong>
+</pre></div><div class="section" lang="en-US"><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>
 	  To download via <code class="command">rsync</code>, add a destination
 	  path on your system to the end of the command line. The
 	  resulting tree of files from the listing you perform are
@@ -391,7 +391,7 @@
 	    use as an example only. Do not run this command if you do not
 	    understand the consequences.
 	  </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>
+<strong class="userinput"><code>rsync -PHav mirror.example.org::fedora-linux-core/5/ /var/www/mirror/fedora/linux/core/5</code></strong>
 </pre><p><a name="rsync-n-switch"></a>
 	  The <code class="command">-n</code> switch performs a "dry run" using
 	  the other given parameters. Use this switch to test any
@@ -417,7 +417,7 @@
 	    If you are not exceedingly careful in using these switches, it is
 	    possible to delete large portions of your mirrored data. Fixing this
 	    problem might require performing the copying steps outlined
-	    in <a href="sn-planning-and-setup.php#sn-copying-original-distribution" title="2.2. Copying the Original Distribution">Section 2.2, “Copying the Original Distribution”</a> above. On the
+	    in <a href="sn-planning-and-setup.php#sn-copying-original-distribution" title="2.2. Copying the Original Distribution">Section 2.2, “Copying the Original Distribution”</a> above. On the
 	    other hand, if you are also careless about your destination path,
 	    and you are running as root, you could put your entire system at
 	    risk. Know your environment before using these switches:
@@ -429,7 +429,7 @@
 		what is your current security context?
 	      </p></li><li><p>
 		Have you tested this command using the <code class="command">-n</code>
-		switch (see <a href="sn-planning-and-setup.php#rsync-n-switch">Section 2.4.3, “Downloading Using <code class="command">rsync</code>”</a>)?
+		switch (see <a href="sn-planning-and-setup.php#rsync-n-switch">Section 2.4.3, “Downloading Using <code class="command">rsync</code>”</a>)?
 	      </p></li></ul></div></td></tr></table></div><p>
 	  Use the <code class="command">--exclude</code> switch, along with a simple
 	  pattern, to disallow download of certain files and/or folders. For
@@ -466,7 +466,7 @@
 	    <code class="command">--exclude "**x86_64**"</code>. This matches not only
 	    folders marked <code class="filename">x86_64</code>, but also files such as
 	    ISO images for x86_64, which are indicated by file names such as
-	    <code class="filename">FC4-x86_64-disc1.iso</code>.
+	    <code class="filename">FC5-x86_64-disc1.iso</code>.
 	  </p></td></tr></table></div><p>
 	  Process a long list of exclusions and deletions with the
 	  <code class="command">--exclude-from</code> and <code class="command">--delete-from</code>
@@ -481,12 +481,12 @@
 	  examine the resulting list of files in the editor or pager of your
 	  choice.
 	</p><p>
-	  The following example mirrors the entire Fedora Core 4 distribution,
+	  The following example mirrors the entire Fedora Core 5 distribution,
 	  with <code class="command">--exclude</code> options that avoid downloading:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 	      Any information for x86_64 architecture;
 	    </p></li><li><p>
-	      Any <code class="command">yum</code> headers (see <a href="sn-server-config.php#sn-repositories" title="3.4. Configuring Repositories">Section 3.4, “Configuring Repositories”</a>);
+	      Any <code class="command">yum</code> headers (see <a href="sn-server-config.php#sn-repositories" title="3.4. Configuring Repositories">Section 3.4, “Configuring Repositories”</a>);
 	    </p></li><li><p>
 	      Any <code class="filename">debuginfo</code> packages; and,
 	    </p></li><li><p>
@@ -498,9 +498,9 @@
 	</p><pre class="screen">
 <strong class="userinput"><code>rsync -Pan --delete --exclude "**x86_64**" --exclude "**headers**" \
   --exclude "**debug**" --exclude "**iso**" \
-  mirror.example.com::fedora-linux-core/4/ \
-  /var/www/mirror/fedora/core/4</code></strong>
-</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-maintenance"></a>2.5. Maintaining Your Mirror</h3></div></div></div><p>
+  mirror.example.com::fedora-linux-core/5/ \
+  /var/www/mirror/fedora/core/5</code></strong>
+</pre></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-maintenance"></a>2.5. Maintaining Your Mirror</h3></div></div></div><p>
 	Fedora mirrors are even more useful when they are more than just a
 	snapshot of the distribution at release time. Most mirror administrators
 	also choose to carry updates and errata packages. Repositories of
@@ -510,7 +510,7 @@
 	  If you plan to do regular updates of your mirror that include large
 	  amounts of data, you should ask permission from the administrator of
 	  the upstream mirror. Downloading nightly package updates for the
-	  official releases of Fedora Core 4 should not require notification, as
+	  official releases of Fedora Core 5 should not require notification, as
 	  they are rarely more than a few megabytes. However, the
 	  <code class="filename">development</code> tree routinely turns over several
 	  hundred megabytes nightly. Take these factors into consideration
@@ -543,7 +543,7 @@
 	    specify differently. Read the <code class="command">crontab(5)</code> man
 	    pages for additional information, with the command <code class="command">man 5
 	      crontab</code>.
-	  </p></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn-server-config.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Mirror Tutorial </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 3. Server Configuration</td></tr></table></div>
+	  </p></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn-server-config.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Mirror Tutorial </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 3. Server Configuration</td></tr></table></div>
 
 <?
 


Index: sn-server-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/en/sn-server-config.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-server-config.php	14 Aug 2006 17:34:25 -0000	1.1
+++ sn-server-config.php	15 Aug 2006 03:19:37 -0000	1.2
@@ -7,10 +7,10 @@
 
 ?>
 
-<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>
+<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-US"><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 describes how to set up a HTTP (Web) server to
       support Fedora installation and software management applications.
-    </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-installing-apache"></a>3.1. Installing The Apache Web Server</h3></div></div></div><p>
+    </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-installing-apache"></a>3.1. Installing The Apache Web Server</h3></div></div></div><p>
         Fedora Core provides the Apache server in the
         <code class="filename">httpd</code> package.  The
         <code class="filename">httpd</code> package is included on Fedora systems
@@ -50,7 +50,7 @@
         service, use the
         <span><strong class="application">system-config-securitylevel</strong></span> utility:
       </p><div class="procedure"><ol type="1"><li><p>
-            Choose <span><strong class="guimenu">Desktop</strong></span>-><span><strong class="guisubmenu">System Settings</strong></span>-><span><strong class="guimenuitem">Security Level</strong></span>.
+            Choose <span><strong class="guimenu">Desktop</strong></span> → <span><strong class="guisubmenu">System Settings</strong></span> → <span><strong class="guimenuitem">Security Level</strong></span>.
           </p></li><li><p>
             Enter the password for the
             <code class="systemitem">root</code> account when
@@ -61,12 +61,12 @@
           </p></li><li><p>
             When prompted, select <span><strong class="guilabel">Yes</strong></span> to update the
             firewall configuration.
-          </p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-configuring-apache"></a>3.2. Configuring The Apache Web Server</h3></div></div></div><p>
+          </p></li></ol></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-configuring-apache"></a>3.2. Configuring The Apache Web Server</h3></div></div></div><p>
         To enable HTTP access to the files in your mirror directory,
         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="id2600673"></a><pre class="screen">
+       </p><div class="example"><a name="id2850062"></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
@@ -81,7 +81,7 @@
       Allow from 127.0.0.1 192.168.1
       Options Indexes
     </Directory></code>
-</pre><p class="title"><b>Example 2. Apache 2.x configuration file for Fedora mirror</b></p></div><p>
+</pre><p class="title"><b>Example 2. Apache 2.x configuration file for Fedora mirror</b></p></div><p>
         You must use root privileges to create or copy files in the
         directory <code class="filename">/etc/httpd/conf.d/</code>.
       </p><p>
@@ -102,13 +102,13 @@
           use files in the <code class="filename">/var/www/</code> directory. If
           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="id2600789"></a><em class="firstterm">header</em> that contains all
+        </p></td></tr></table></div></div><div class="section" lang="en-US"><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="id2850171"></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="id2600815"></a>. A dependency is a requirement for one or more
+	<span class="emphasis"><em>dependencies</em></span><a class="indexterm" name="id2850195"></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="id2600849"></a>, is a Python-based system for computing and solving
+	<span class="emphasis"><em>yum</em></span><a class="indexterm" name="id2850230"></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
@@ -142,9 +142,9 @@
       </p><p>
 	For more information about using <code class="command">yum</code>, refer
 	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>
+      </p></div><div class="section" lang="en-US"><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="id2600948"></a> is a collection of packages on a server which
+	<span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2850328"></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>
@@ -164,7 +164,7 @@
 	  To support Fedora Core 3 <code class="command">yum</code> clients, you
 	  <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>
+	</p></td></tr></table></div><div class="section" lang="en-US"><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>
 	  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
@@ -177,7 +177,7 @@
 	  to the directory where you want <code class="filename">headers/</code>
 	  to appear.
 	</p><pre class="screen">
-<strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/4/i386/os
+<strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/5/i386/os
 su -c 'yum-arch -ls .'</code></strong>
 </pre><p>
 	  Enter the root password at the prompt.  The
@@ -185,8 +185,8 @@
 	  <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>.
-	</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>
+	  <code class="filename">/var/www/mirror/fedora/linux/core/5/i386/os/headers/</code>.
+	</p></div><div class="section" lang="en-US"><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
@@ -201,9 +201,9 @@
 	</p><p>
 	  The following command creates the repository data in the
 	  directory
-	  <code class="filename">/var/www/mirror/fedora/linux/core/4/i386/os/repodata</code>.
+	  <code class="filename">/var/www/mirror/fedora/linux/core/5/i386/os/repodata</code>.
 	</p><pre class="screen">
-<strong class="userinput"><code>su -c '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/5/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>
@@ -213,9 +213,9 @@
 	  command creates the package group data corresponding to the
 	  repository directly above.  Note the relative location of the
 	  group file
-	  <code class="filename">/var/www/mirror/fedora/linux/core/4i386/os/Fedora/base/comps.xml</code>.
+	  <code class="filename">/var/www/mirror/fedora/linux/core/5i386/os/Fedora/base/comps.xml</code>.
 	</p><pre class="screen">
-<strong class="userinput"><code>su -c '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/5/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
@@ -223,24 +223,24 @@
 	  data for any repositories.  The extra repository information
 	  is relatively small and will not affect your mirror's proper
 	  function.
-	</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="sn-repository-locations"></a>3.4.3. Repository Locations</h4></div></div></div><p>
+	</p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h4 class="title"><a name="sn-repository-locations"></a>3.4.3. Repository Locations</h4></div></div></div><p>
 	  Typically you will run <code class="command">yum-arch</code> or
 	  <code class="command">createrepo</code> against at least the following
 	  locations:
 	</p><div class="itemizedlist"><ul type="disc"><li><p>
 	      The stock distribution; for example,
-	      <code class="filename">/var/www/mirror/fedora/linux/core/4/i386/os/</code>. 
+	      <code class="filename">/var/www/mirror/fedora/linux/core/5/i386/os/</code>. 
 	      For <code class="command">yum-arch</code>, use the
 	      <code class="command">-l</code> and <code class="command">-s</code> options to
 	      follow the linked directory <code class="filename">SRPMS</code> and
 	      include the source packages therein.
 	    </p></li><li><p>
 	      Official updates to the distribution; for example,
-	      <code class="filename">/var/www/mirror/fedora/linux/core/updates/4/</code>. 
+	      <code class="filename">/var/www/mirror/fedora/linux/core/updates/5/</code>. 
 	      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="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>
+	    </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>
 
 <?

More information about the Fedora-websites-list mailing list