web/html/docs/mirror generated-index.php, 1.3, 1.4 index.php, 1.3, 1.4 ln-legalnotice.php, 1.3, 1.4 rv-revhistory.php, 1.3, 1.4 sn-client-config.php, 1.3, 1.4 sn-planning-and-setup.php, 1.3, 1.4 sn-server-config.php, 1.3, 1.4

Mon Feb 6 23:34:49 UTC 2006

Author: pfrields

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

Modified Files:
	generated-index.php index.php ln-legalnotice.php 
	rv-revhistory.php sn-client-config.php 
	sn-planning-and-setup.php sn-server-config.php 
Log Message:
Correct clog/revhistory




Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/index.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4

--- index.php	6 Feb 2006 23:32:20 -0000	1.3
+++ index.php	6 Feb 2006 23:34:47 -0000	1.4
@@ -37,7 +37,7 @@
 	    Using a command line interface
 	  </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-mirrors"></a>1.3. About Mirrors</h3></div></div></div><p>
 	A <span class="emphasis"><em>mirror</em></span>
-	<a class="indexterm" name="id2890585"></a> is a server
+	<a class="indexterm" name="id2598469"></a> is a server
 	that provides a copy of one or more collections of files.
 	Mirroring a site reduces traffic to the original source site,
 	thus spreading the stress and bandwidth costs of many users
@@ -47,7 +47,7 @@
 	managing Internet services.
       </p><p>
 	The site from which you retrieve files to build your mirror is
-	called an <span class="emphasis"><em>upstream mirror</em></span><a class="indexterm" name="id2890606"></a>. If possible, choose an upstream mirror that 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
 	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: rv-revhistory.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/rv-revhistory.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rv-revhistory.php	6 Feb 2006 23:32:20 -0000	1.3
+++ rv-revhistory.php	6 Feb 2006 23:34:47 -0000	1.4
@@ -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 0.37.2</td><td align="left">2005-12-28</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
+<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">
+        <p>
+          Add lftp section and push to 1.0
+        </p>
+      </td></tr><tr><td align="left">Revision 0.37.2</td><td align="left">2005-12-28</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
         <p>
           Minor revision updating entity names and incorporating
           variablelist.


Index: sn-client-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/sn-client-config.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sn-client-config.php	6 Feb 2006 23:32:20 -0000	1.3
+++ sn-client-config.php	6 Feb 2006 23:34:47 -0000	1.4
@@ -14,7 +14,7 @@
       <code class="filename">/etc/yum.repos.d</code> and end with the suffix
       <code class="filename">.repo</code>.  Below is an example configuration
       file.
-    </p><div class="example"><a name="id2893582"></a><pre class="screen">
+    </p><div class="example"><a name="id2601444"></a><pre class="screen">
 <code class="computeroutput">[mirror]
 name=Fedora Core $releasever - $basearch - Base
 baseurl=http://server.mydomain.net/mirror/fedora/linux/core/$releasever/$basearch


Index: sn-planning-and-setup.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/sn-planning-and-setup.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sn-planning-and-setup.php	6 Feb 2006 23:32:20 -0000	1.3
+++ sn-planning-and-setup.php	6 Feb 2006 23:34:47 -0000	1.4
@@ -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="id2890715"></a>, which is the collection of all Fedora-related
+	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
 	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="id2890959"></a>, originally the Red Hat Package Manager and now
+	  <em class="firstterm">RPM</em><a class="indexterm" name="id2597698"></a>, originally the Red Hat Package Manager and now
 	  the RPM Package Manager, is not just a file format. RPM is
 	  also a system that tracks and interconnects software and
 	  version information. The RPM system is quite popular, and many
@@ -111,8 +111,8 @@
 <strong class="userinput"><code>cd /var/www/mirror/fedora/linux/core/4/i386/os/Fedora
 ln ../../SRPMS SRPMS</code></strong>
 </pre><p>
-	The documentation for <span><strong class="application">anaconda</strong></span><a class="indexterm" name="id2889988"></a>, the Fedora Core installation program, calls this directory
-	structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2890001"></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="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,
 	or exploded, to a large directory tree with a predetermined structure.
 	The <span><strong class="application">anaconda</strong></span> installer expects this structure
 	to some extent.


Index: sn-server-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/mirror/sn-server-config.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sn-server-config.php	6 Feb 2006 23:32:20 -0000	1.3
+++ sn-server-config.php	6 Feb 2006 23:34:47 -0000	1.4
@@ -66,7 +66,7 @@
         create the configuration file
         <code class="filename">/etc/httpd/conf.d/mirror.conf</code>. The
         following listing is an example:
-       </p><div class="example"><a name="id2892811"></a><pre class="screen">
+       </p><div class="example"><a name="id2600673"></a><pre class="screen">
 <code class="computeroutput"># The name at which the mirror will be shared, 
 # followed by the name of the root directory of that tree.
 Alias /mirror /var/www/mirror
@@ -103,12 +103,12 @@
           you build your mirror in another directory, you may need to
           modify the SELinux policy.
         </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-solving-dependencies"></a>3.3. Solving Dependencies</h3></div></div></div><p>
-	Every RPM package has a <a class="indexterm" name="id2892927"></a><em class="firstterm">header</em> that contains all
+	Every RPM package has a <a class="indexterm" name="id2600789"></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="id2892953"></a>. A dependency is a requirement for one or more
+	<span class="emphasis"><em>dependencies</em></span><a class="indexterm" name="id2600815"></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="id2892986"></a>, is a Python-based system for computing and solving
+	<span class="emphasis"><em>yum</em></span><a class="indexterm" name="id2600849"></a>, is a Python-based system for computing and solving
 	RPM dependencies. A <code class="command">yum</code> client retrieves a
 	cache of headers from its repository server, as well as a list
 	of available RPM packages and their exact locations on the
@@ -144,7 +144,7 @@
 	to <a href="http://fedora.redhat.com/docs/yum/" target="_top">http://fedora.redhat.com/docs/yum/</a>.
       </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-repositories"></a>3.4. Configuring Repositories</h3></div></div></div><p>
       A <code class="command">yum</code>
-	<span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2893086"></a> is a collection of packages on a server which
+	<span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2600948"></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>


