mirror-tutorial mirror-tutorial-en.xml,1.15,1.16

[Paul W. Frields (pfrields)]

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20424

Modified Files:
	mirror-tutorial-en.xml 
Log Message:
Update information on repo files (#172815)


Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- mirror-tutorial-en.xml	9 Nov 2005 23:41:58 -0000	1.15
+++ mirror-tutorial-en.xml	11 Nov 2005 15:33:22 -0000	1.16
@@ -6,8 +6,8 @@
 %FEDORA-ENTITIES-EN;
 
 <!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.35">
-<!ENTITY BOOKDATE "2005-11-09">
+<!ENTITY BOOKVERSION "0.36">
+<!ENTITY BOOKDATE "2005-11-11">
 <!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
 
 <!ENTITY BUG-NUM "130125">
@@ -192,6 +192,17 @@
 	  </para>
 	</revdescription>
       </revision>
+      <revision>
+	<revnumber>0.36</revnumber>
+	<date>2005-11-11</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Added some additional information about repository
+	    configuration (#172815).
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
@@ -804,7 +815,7 @@
 	  <para>
 	    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 simply require performing the copying steps outlined
+	    problem might require performing the copying steps outlined
 	    in <xref linkend="sn-copying-original-distribution"/> 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
@@ -1192,7 +1203,7 @@
 	server. It can do this via HTTP or FTP, as well as using
 	standard file system calls (either local or remote via NFS). The
 	client computes solutions to any package dependencies using the
-	downloaded header information, and simply requests all necessary
+	downloaded header information, and requests all necessary
 	RPM packages once it has finished. The <command>yum</command>
 	command relies on <command>rpm</command> functions to perform
 	many of the computations involved in the process.
@@ -1361,10 +1372,10 @@
 
     <example>
       <title>Example
-      <filename>/etc/yum.repos.d/fedora.repo</filename></title>
+      <filename>/etc/yum.repos.d/fedora-mirror.repo</filename></title>
 
 <screen>
-<computeroutput>[base]
+<computeroutput>[mirror]
 name=Fedora Core $releasever - $basearch - Base
 baseurl=http://server.mydomain.net/mirror/fedora/linux/core/$releasever/$basearch
 enabled=1
@@ -1382,9 +1393,22 @@
     </para>
 
     <para>
-      For more information about these configuration files, refer to the
-      "Software Management with <command>yum</command>" tutorial online
-      at <ulink url="http://fedora.redhat.com/docs/yum/"/>.
+      If you want clients to use your mirror in place of the official
+      repositories, disable the existing repositories.  To do this, edit
+      the client's file for the official repository to include the
+      directive <userinput>enabled=0</userinput>.  You will need
+      <systemitem class="username">root</systemitem> access to edit
+      these files.
+    </para>
+
+    <para>
+      Many repositories provide their own installable RPM packages
+      containing these configuration files.  When a user installs the
+      RPM, the new files in <filename>/etc/yum.repos.d/</filename>
+      reference that repository.  These packages simplify the addition
+      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.
     </para>
 
   </section>