mirror-tutorial mirror-tutorial-en.xml,1.12,1.13
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Mon Oct 17 02:12:17 UTC 2005
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21805
Modified Files:
mirror-tutorial-en.xml
Log Message:
Add client configuration section, bump to 0.34 and republish beta
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- mirror-tutorial-en.xml 15 Oct 2005 15:54:57 -0000 1.12
+++ mirror-tutorial-en.xml 17 Oct 2005 02:12:01 -0000 1.13
@@ -6,8 +6,8 @@
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.33">
-<!ENTITY BOOKDATE "2005-10-15">
+<!ENTITY BOOKVERSION "0.34">
+<!ENTITY BOOKDATE "2005-10-16">
<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
<!ENTITY BUG-NUM "130125">
@@ -18,24 +18,15 @@
<articleinfo>
<title>Mirror Tutorial - <emphasis>BETA</emphasis></title>
<copyright>
- <year>
- 2004
- </year>
- <holder>
- Paul W. Frields
- </holder>
+ <year>2004</year>
+ <year>2005</year>
+ <holder>Paul W. Frields</holder>
</copyright>
<authorgroup>
<author>
- <surname>
- Frields
- </surname>
- <firstname>
- Paul
- </firstname>
- <othername role="mi">
- W.
- </othername>
+ <surname>Frields</surname>
+ <firstname>Paul</firstname>
+ <othername role="mi">W.</othername>
</author>
</authorgroup>
&LEGALNOTICE;
@@ -203,8 +194,8 @@
<title>Audience</title>
<para>
You will find this tutorial more useful if you are a system
- administrator, or a &FC; <quote>power user</quote> familiar with
- the following topics:
+ administrator, or a &FC; "power user" familiar with the
+ following topics:
</para>
<itemizedlist>
<listitem>
@@ -401,7 +392,7 @@
</para>
<para>
Copy all the files from the <filename>SRPMS</filename> folder on
- each of the <quote>Sources</quote> discs to the
+ each of the "Sources" discs to the
<filename>fedora/linux/core/&FCVER;/SRPMS</filename> folder on
the server. Make a link in the <filename>os</filename> folder
that occurs under each architecture. Follow this example:
@@ -502,15 +493,16 @@
</varlistentry>
<varlistentry>
<term>The <filename>development</filename> folder (formerly
- <quote>Rawhide</quote>).</term>
+ "Rawhide").</term>
<listitem>
<para>
- This folder contains all the latest <quote>bleeding-edge</quote>
+ This folder contains all the latest "bleeding-edge"
packages from the &FP;. If you participate in active &FED;
- development, you should not trim this branch. &FED; 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. &FED;
+ 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.
</para>
</listitem>
@@ -519,17 +511,18 @@
<term>The <filename>testing</filename> folders.</term>
<listitem>
<para>
- These branches contain updates that are being subjected to quality
- assurance through public testing, as well as the test or
- <quote>pre-release</quote> versions of the &FC; distribution. The
- <filename>testing</filename> folder under the main
- <filename>core</filename> tree is where test versions of the
- distribution, such as &FC; &FCTESTVER;, are kept. (Users of &FC;
- test distributions are often directed to use the
- <filename>development</filename> branch to update packages.) The
- <filename>testing</filename> folder, under
- <filename>updates</filename>, 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 &FC;
+ distribution. The <filename>testing</filename> folder
+ under the main <filename>core</filename> tree is where
+ test versions of the distribution, such as &FC;
+ &FCTESTVER;, are kept. (Users of &FC; test distributions
+ are often directed to use the
+ <filename>development</filename> branch to update
+ packages.) The <filename>testing</filename> folder, under
+ <filename>updates</filename>, contains package updates
+ that have not yet passed the public testing phase.
</para>
</listitem>
</varlistentry>
@@ -635,12 +628,13 @@
</listitem>
</itemizedlist>
<para>
- 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
- <command>wget</command> 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 <command>wget</command> man pages for more
+ information.
</para>
</section>
@@ -657,11 +651,10 @@
</para>
<para>
Begin by identifying the modules available on the upstream
- mirror site you have chosen. Note that the double colon
- <quote>::</quote> is always used after the host name to
- separate it from the rest of the <command>rsync</command>
- path. The following command generates a list of
- <quote>modules</quote> 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 <command>rsync</command> path. The following
+ command generates a list of "modules" on the upstream mirror.
</para>
<screen>
@@ -677,10 +670,9 @@
the <filename>fedora/linux/core</filename> path found at the
&FP; main download server. To list the contents of the &FC;
&FCVER; distribution folder on the upstream server, issue the
- following command. Do not forget the trailing slash
- <quote>/</quote>. 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.
</para>
<screen>
@@ -758,11 +750,11 @@
</screen>
<para id="rsync-n-switch">
- The <command>-n</command> switch performs a <quote>dry run</quote>
- using the other given parameters. Use this switch to test any
- <command>rsync</command> command if you are unsure what files you will
- receive. See also <xref
- linkend="rsync-possible-data-loss"/>.
+ The <command>-n</command> switch performs a "dry run" using
+ the other given parameters. Use this switch to test any
+ <command>rsync</command> command if you are unsure what files
+ you will receive. See also <xref
+ linkend="rsync-possible-data-loss"/>.
</para>
<para>
The <command>-z</command> switch enables compression during the
@@ -1257,6 +1249,48 @@
</section>
+ <section id="sn-client-config">
+ <title>Client Configuration</title>
+
+ <para>
+ Client systems that use <command>yum</command> to contact your
+ mirror also require configuration. The <command>yum</command>
+ repository configuration files are located in
+ <filename>/etc/yum.repos.d</filename> and end with the suffix
+ <filename>.repo</filename>. Below is an example configuration
+ file.
+ </para>
+
+ <example>
+ <title>Example
+ <filename>/etc/yum.repos.d/fedora.repo</filename></title>
+
+<screen>
+<computeroutput>[base]
+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</computeroutput>
+</screen>
+
+ </example>
+
+ <para>
+ Client systems should use a repository configuration file for each
+ &FED; branch your mirror provides. The base distribution and
+ released updates, for example, each require a separate
+ configuration file.
+ </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/"/>.
+ </para>
+
+ </section>
+
<!--
FIXME:
More information about the Fedora-docs-commits
mailing list