web/html/docs/beta/mirror-tutorial 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.2, 1.3 sn-planning-and-setup.php, 1.3, 1.4 sn-server-config.php, 1.3, 1.4
Paul W. Frields (pfrields)
fedora-extras-commits at redhat.com
Wed Nov 9 23:48:18 UTC 2005
Author: pfrields
Update of /cvs/fedora/web/html/docs/beta/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9101
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:
Republish revision 0.35
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/index.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.php 17 Oct 2005 02:23:31 -0000 1.3
+++ index.php 9 Nov 2005 23:48:16 -0000 1.4
@@ -7,7 +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, 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>
+<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-installing-apache">3.1. Installing The Apache Web Server</a></span></dt><dt><span cl!
ass="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-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="clea!
r: bot
<a name="sn-introduction"></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>
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,
@@ -20,7 +20,7 @@
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.34 (2005-10-16).
+ mirror-tutorial-0.35 (2005-11-09).
</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
@@ -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="id2545805"></a> is a server
+ <a class="indexterm" name="id2724840"></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="id2545826"></a>. If possible, choose an upstream mirror that is
+ called an <span class="emphasis"><em>upstream mirror</em></span><a class="indexterm" name="id2724860"></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
@@ -61,7 +61,8 @@
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>
Karsten Wade provided editorial services and kept the style
- crisp and consistent.
+ 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>
<?
Index: ln-legalnotice.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/ln-legalnotice.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ln-legalnotice.php 17 Oct 2005 02:23:31 -0000 1.3
+++ ln-legalnotice.php 9 Nov 2005 23:48:16 -0000 1.4
@@ -26,28 +26,10 @@
They all may be freely redistributed with documentation
produced for the Fedora Project.
</p><p>
- mirror-tutorial-0.34 (2005-10-16)
+ mirror-tutorial-0.35 (2005-11-09)
</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,
- Rawhide and all Red Hat-based trademarks and logos are trademarks or registered
- trademarks of Red Hat, Inc. in the United States and other countries.
- </p><p>
- Linux is a registered trademark of Linus Torvalds.
- </p><p>
- Motif and UNIX are registered trademarks of The Open Group.
- </p><p>
- Intel and Pentium are registered trademarks of Intel Corporation. Itanium
- and Celeron are trademarks of Intel Corporation.
- </p><p>
- AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced Micro
- Devices, Inc.
- </p><p>
- Windows is a registered trademark of Microsoft Corporation.
- </p><p>
- SSH and Secure Shell are trademarks of SSH Communications Security, Inc.
- </p><p>
- FireWire is a trademark of Apple Computer Corporation.
+ Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of
+ Red Hat, Inc. in the United States and other countries.
</p><p>
All other trademarks and copyrights referred to are the property of their
respective owners.
Index: rv-revhistory.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/rv-revhistory.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rv-revhistory.php 17 Oct 2005 02:23:31 -0000 1.3
+++ rv-revhistory.php 9 Nov 2005 23:48:16 -0000 1.4
@@ -68,6 +68,10 @@
<p>
Added client configuration section.
</p>
+ </td></tr><tr><td align="left">Revision 0.35</td><td align="left">2005-11-09</td><td align="left">PaulWFrields</td></tr><tr><td align="left" colspan="3">
+ <p>
+ Added some security info and fixes (#169584).
+ </p>
</td></tr></table></div></div>
<?
Index: sn-client-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/sn-client-config.php,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sn-client-config.php 17 Oct 2005 02:23:31 -0000 1.2
+++ sn-client-config.php 9 Nov 2005 23:48:16 -0000 1.3
@@ -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="id2595207"></a><pre class="screen">
+ </p><div class="example"><a name="id2775504"></a><pre class="screen">
<code class="computeroutput">[base]
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/beta/mirror-tutorial/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 17 Oct 2005 02:23:31 -0000 1.3
+++ sn-planning-and-setup.php 9 Nov 2005 23:48:16 -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="id2545935"></a>, which is the collection of all Fedora-related
+ The Fedora <span class="emphasis"><em>distribution</em></span><a class="indexterm" name="id2724970"></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="id2592886"></a>, originally the Red Hat Package Manager and now
+ <em class="firstterm">RPM</em><a class="indexterm" name="id2772811"></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="id2593040"></a>, the Fedora Core installation program, calls this directory
- structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2593054"></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="id2772965"></a>, the Fedora Core installation program, calls this directory
+ structure an <em class="firstterm">exploded tree</em><a class="indexterm" name="id2772978"></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.
@@ -418,7 +418,7 @@
</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.3. Configuring Repositories">Section 3.3, “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>
Index: sn-server-config.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/mirror-tutorial/sn-server-config.php,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sn-server-config.php 17 Oct 2005 02:23:31 -0000 1.3
+++ sn-server-config.php 9 Nov 2005 23:48:16 -0000 1.4
@@ -8,59 +8,107 @@
?>
<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>
- The HTTP service, provided by the Apache server in the
- <code class="filename">httpd</code> package, is the easiest service to
- configure. You can also use Apache to offer post-installation
- functions such as updates or installing additional packages. To
- install the <code class="filename">httpd</code> package, if you have not
- already done so, use the following command:
+ 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>
+ 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
+ installed with the <span><strong class="guilabel">Server</strong></span> installation
+ type. You may have installed it later in order to run websites
+ or Web applications. Fedora Extras also offers alternative HTTP servers,
+ which are beyond the scope of this document.
+ </p><p>
+ To install the <code class="filename">httpd</code> package, if you have
+ not already done so, use the following command:
+ </p><pre class="screen">
+<strong class="userinput"><code>su -c 'yum install httpd'</code></strong>
+</pre><p>
+ Enter the password for the
+ <code class="systemitem">root</code> account when
+ prompted.
+ </p><p>
+ To start the service, use the following command:
</p><pre class="screen">
-<strong class="userinput"><code>su - -c "yum install httpd"</code></strong>
+<strong class="userinput"><code>su -c '/sbin/service httpd start'</code></strong>
</pre><p>
- 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="id2594511"></a><pre class="screen">
-<code class="computeroutput"># The name at which the installation tree will be shared,
+ Enter the password for the
+ <code class="systemitem">root</code> account when
+ prompted.
+ </p><p>
+ To enable this service to load automatically at boot time, use
+ the following command:
+ </p><pre class="screen">
+<strong class="userinput"><code>su -c '/sbin/chkconfig --level 345 httpd on'</code></strong>
+</pre><p>
+ Enter the password for the
+ <code class="systemitem">root</code> account when
+ prompted.
+ </p><p>
+ The default firewall configuration for Fedora blocks access from
+ remote systems. To enable other systems to connect to your HTTP
+ 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>.
+ </p></li><li><p>
+ Enter the password for the
+ <code class="systemitem">root</code> account when
+ prompted.
+ </p></li><li><p>
+ Select <span><strong class="guilabel">WWW (HTTP)</strong></span> from the list of
+ services.
+ </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>
+ 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="id2774644"></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
-# Share options for the installation tree.
+# Share options for the mirror.
# Only allow connections from localhost and
# IP addresses which start with 192.168.1
-
-<Directory /var/www/mirror>
- AllowOverride None
- Order Deny,Allow
- Deny from all
- 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 installation
- mirror</b></p></div><p>
- To start the <code class="command">httpd</code> service, use the following
- command:
- </p><pre class="screen">
-<strong class="userinput"><code>/sbin/service httpd start</code></strong>
-</pre><p>
- To enable that server by default at boot time, use the following
- command:
+ <Directory /var/www/mirror>
+ AllowOverride None
+ Order Deny,Allow
+ Deny from all
+ 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>
+ You must use root privileges to create or copy files in the
+ directory <code class="filename">/etc/httpd/conf.d/</code>.
+ </p><p>
+ To update an active <code class="command">httpd</code> service with a new
+ configuration, use the following command:
</p><pre class="screen">
-<strong class="userinput"><code>chkconfig httpd on</code></strong>
+<strong class="userinput"><code>/sbin/service httpd reload</code></strong>
</pre><p>
- Your clients may now visit any area of your mirror by using the
- 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="id2594601"></a><em class="firstterm">header</em> that contains all
+ Enter the password for the
+ <code class="systemitem">root</code> account when
+ prompted.
+ </p><p>
+ Your clients may now visit any area of your mirror by using the
+ URL
+ http://<em class="replaceable"><code>server.mydomain.org</code></em>/mirror/<em class="replaceable"><code>path</code></em>.
+ </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Apache and SELinux"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Apache and SELinux</th></tr><tr><td align="left" valign="top"><p>
+ The default SELinux configuration for Fedora permits Apache to
+ 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="id2724530"></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="id2594622"></a>. A dependency is a requirement for one or more
+ <span class="emphasis"><em>dependencies</em></span><a class="indexterm" name="id2724550"></a>. A dependency is a requirement for one or more
additional packages.
</p><p>
Packages installed without satisfying their dependencies may not
@@ -71,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="id2594657"></a>, is a Python-based system for computing and solving
+ <span class="emphasis"><em>yum</em></span><a class="indexterm" name="id2774959"></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
@@ -94,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.3. Configuring Repositories</h3></div></div></div><p>
+ </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="id2594756"></a> is a collection of packages on a server which
+ <span class="emphasis"><em>repository</em></span><a class="indexterm" name="id2775055"></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>
@@ -116,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.3.1. <code class="command">yum-arch</code></h4></div></div></div><p>
+ </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>
A directory which supports older versions of
<code class="command">yum</code> (before 2.2) is named
<code class="filename">headers</code>. It is created by using the
@@ -134,7 +182,7 @@
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.3.2. <code class="command">createrepo</code></h4></div></div></div><p>
+ </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>
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
@@ -160,7 +208,7 @@
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.3.3. Repository Locations</h4></div></div></div><p>
+ </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>
Typically you will run <code class="command">yum-arch</code> or
<code class="command">createrepo</code> against at least the following
locations:
@@ -173,7 +221,7 @@
include the source packages therein.
</p></li><li><p>
Official updates to the distribution; for example,
- <code class="filename">/var/mirror/fedora/linux/core/updates/4/</code>.
+ <code class="filename">/var/www/mirror/fedora/linux/core/updates/4/</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.
More information about the fedora-extras-commits
mailing list