Author: pfrields
Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29805
Modified Files: Makefile mirror-tutorial-en.xml Log Message: Update Makefile as well as some content editing
Index: Makefile =================================================================== RCS file: /cvs/docs/mirror-tutorial/Makefile,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- Makefile 29 Jun 2005 14:34:37 -0000 1.5 +++ Makefile 18 Sep 2005 22:43:44 -0000 1.6 @@ -8,13 +8,9 @@ # Copyright 2005 Tommy Reynolds, MegaCoder.com ###############################################################################
-XSLPDF = ../docs-common/xsl/main-pdf.xsl -XSLHTML = ../docs-common/xsl/main-html.xsl -XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl -LANG = en -DOCNAME = mirror-tutorial-$(LANG) -XMLFILE = $(DOCNAME).xml -XMLEXTRAFILES = +LANGUAGES = en +DOCBASE = mirror-tutorial +XMLEXTRAFILES-en =
###################################################### include ../docs-common/Makefile.common
Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- mirror-tutorial-en.xml 2 Aug 2005 22:07:37 -0000 1.9 +++ mirror-tutorial-en.xml 18 Sep 2005 22:43:44 -0000 1.10 @@ -5,7 +5,7 @@ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent"> %FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "mirror-tutorial-0.30 (2005-08-01)"> <!-- change version of manual and date here --> +<!ENTITY BOOKID "mirror-tutorial-0.31 (2005-08-29)"> <!-- change version of manual and date here -->
<!ENTITY BUG-NUM "130125"> <!ENTITY FCLOCALVER "4"> @@ -13,7 +13,7 @@
<article id="mirror-tutorial" lang="en"> <articleinfo> - <title>Mirror Tutorial</title> + <title>Mirror Tutorial - <emphasis>BETA</emphasis></title> <copyright> <year> 2004 @@ -148,6 +148,16 @@ </para> </revdescription> </revision> + <revision> + <revnumber>0.31</revnumber> + <date>2005-08-29</date> + <authorinitials>PaulWFrields</authorinitials> + <revdescription> + <para> + Use bug reporting entity, add BETA classification. + </para> + </revdescription> + </revision> </revhistory> </articleinfo>
@@ -163,7 +173,7 @@ enhance user experience, adding to the perceived value of non-proprietary operating systems and software. </para> - &DRAFTNOTICE; + &BUG-REPORTING; </section> <section id="sn-audience"> <title>Audience</title> @@ -307,22 +317,24 @@ <para> The <filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/os</filename> - directory contains a copy of all the original distribution files for - &FC; &FCVER;. They are the same files found on the CD-ROM version of the - distribution. The <filename>&FED;</filename> subfolder contains all the - files that are necessary for installation, including the entire - collection of &FC; RPM packages. The <filename>images</filename> folder - contains copies of any floppy diskette or CD-ROM images that boot a - system into installation or rescue modes. The + directory contains a copy of all the original distribution files + for &FC; &FCVER;. They are the same files found on the DVD and + CD-ROM version of the distribution. The + <filename>&FED;</filename> subfolder contains all the files that + are necessary for installation, including the entire collection + of &FC; RPM packages. The <filename>images</filename> folder + contains copies of any floppy diskette or CD-ROM images that + boot a system into installation or rescue modes. The <filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/iso</filename> - folder contains images of the CD-ROM version of the distribution. + folder contains images of the CD-ROM version of the + distribution. </para> <note> <title>RPM packages</title> <para> <firstterm>RPM</firstterm><indexterm> <primary>RPM</primary> - </indexterm>, originally the Red Hat Package Manager, now the RPM + </indexterm>, originally the Red Hat Package Manager and now the RPM Package Manager, is not just a file format. RPM is also a system which tracks and interconnects software and version information. The RPM system is quite popular, and many other Linux distributions use RPM as @@ -396,7 +408,7 @@ </para>
<screen> -<computeroutput>/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0</computeroutput> +<computeroutput>/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0</computeroutput> </screen>
<para> @@ -406,9 +418,6 @@ <application>system-config-packages</application> also continue to work properly when pointed at the parent of the ISO image mount points. </para> - -<!-- FIXME: Is the above true? See other questions below... --> - <para> There are drawbacks to using CD ISO images in this fashion. For instance, no one directory contains the entire distribution of RPM @@ -418,6 +427,15 @@ hardware, however, cannot use this image to make discs for their own use. </para> + <para> + You only need a single line in <filename>/etc/fstab</filename> + for mounting the &FC; DVD ISO image. The entry looks like this: + </para> + +<screen> +<computeroutput>/path/i386/iso/FC&FCVER;-i386-DVD.iso /path/i386/os iso9660 defaults 0 0</computeroutput> +</screen> + </section>
<section id="sn-trimming-tree"> @@ -491,13 +509,13 @@ <term>The <filename>debug</filename> folders.</term> <listitem> <para> - These folders contain packages that enable developers and skilled - users to interpret data created when a program crashes or - encounters a bug. If you participate actively in &FED; - development, you should not trim these folders. If you trim this - branch, you may still download individual packages on an - <foreignphrase>ad hoc</foreignphrase> basis from a nearby public - mirror site. + These folders contain packages that enable developers and + skilled users to interpret data created when a program + crashes or encounters a bug. If you participate actively + in &FED; development, you should not trim these + folders. If you trim this branch, you may still download + individual packages as needed from a nearby public mirror + site. </para> </listitem> </varlistentry> @@ -506,10 +524,10 @@ thereto).</term> <listitem> <para> - These folders contain the original source for all the binary RPM - packages in the distribution. You may download these packages on - an <foreignphrase>ad hoc</foreignphrase> basis if you need to save - space on your local mirror. + These folders contain the original source for all the + binary RPM packages in the distribution. You may download + these packages individually as needed to save space on + your local mirror. </para> </listitem> </varlistentry> @@ -1016,61 +1034,40 @@ Packages installed without satisfying their dependencies may not work correctly. Dependencies may create a problem for users who are trying to install a single package. Manually determining and resolving - dependencies is difficult. &FC; has several methods for solving these + dependencies is difficult. &FC; provides the + <command>yum</command> utility for solving these dependencies automatically, providing an improved user experience. </para>
- <section id="sn-rhn-history"> - <title>Red Hat Network</title> - <para> - <emphasis>Red Hat Network</emphasis><indexterm> - <primary>Red Hat Network</primary> - </indexterm>, or <emphasis>RHN</emphasis><indexterm> - <primary>RHN</primary> - <see>Red Hat Network</see> - </indexterm>, is a systems management and deployment tool that was - introduced in Red Hat Linux, and continues to be used with Red Hat - Enterprise Linux. RHN makes updates available to registered users, and - allows them to remotely schedule and manage their systems using a - single Web-based console. The client systems run the - <application>up2date</application> application to communicate with - RHN. - </para> - <para> - Although &FC; systems do not inter-operate with RHN, they still include - an <application>up2date</application> client. This client is - enhanced to support non-RHN update services. These services, like RHN, - solve RPM package dependencies automatically. - </para> - </section> - - <section id="sn-yum"> - <title><command>yum</command></title> - <para> - The Yellow Dog Updater Modified, or - <emphasis>yum</emphasis><indexterm> - <primary>yum</primary> - </indexterm>, is a Python-based system for computing and solving RPM - dependencies. A <command>yum</command> 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 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 RPM packages once it has finished. The - <command>yum</command> command relies on <command>rpm</command> to - perform all computation involved in the process. - </para> - <para> - A drawback to <command>yum</command> is that the first time it is run, - it must download a header for every package installed on the system in - order to determine available updates. However, running a local mirror - nullifies this drawback. The <command>yum</command> command can, of - course, download many megabytes of headers almost instantly on a - standard Ethernet LAN. <command>yum</command> is the most popular - update method for &FC;. - </para> - </section> + <para> + The Yellow Dog Updater Modified, or + <emphasis>yum</emphasis><indexterm> <primary>yum</primary> + </indexterm>, is a Python-based system for computing and solving + RPM dependencies. A <command>yum</command> 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 + 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 + 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. + </para> + <para> + A drawback to <command>yum</command> is that the first time it + is run, it must download a header for every package installed on + the system in order to determine available updates. However, + running a local mirror nullifies this drawback. The + <command>yum</command> command can, of course, download many + megabytes of headers almost instantly on a standard Ethernet + LAN. The <command>yum</command> utility is the most popular + update method for &FC;. + </para> + <para> + For more information about using <command>yum</command>, refer + to <ulink url="http://fedora.redhat.com/docs/yum/"/>. + </para>
</section>
@@ -1092,6 +1089,21 @@ <command>yum</command> it supports. It is permissible to have both kinds of repository information in a single repository. </para> + <para> + To support older <command>yum</command> clients, use the + <command>yum-arch</command> command. To support current + <command>yum</command> clients, use the + <command>createrepo</command> command. + </para> + <important> + <title>Supporting &FC; 3 and beyond</title> + <para> + &FC; 3 ships with a newer version of <command>yum</command>. + To support &FC; 3 <command>yum</command> clients, you + <emphasis>must</emphasis> use <command>createrepo</command> on + your server's repositories. + </para> + </important>
<section id="sn-yum-arch"> <title><command>yum-arch</command></title> @@ -1133,25 +1145,16 @@ <command>createrepo</command> program also searches recursively for RPM packages to include in the repository data. </para> + <para> + The following command creates the repository data in the directory + <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/repodata</filename>. + </para>
<screen> <userinput>createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput> </screen>
<para> - The command above creates the repository data in the directory - <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/repodata</filename>. - </para> - <important> - <title>Supporting &FC; 3 and beyond</title> - <para> - &FC; 3 ships with a newer version of <command>yum</command>. To - support &FC; 3 <command>yum</command> clients, you - <emphasis>must</emphasis> use <command>createrepo</command> on your - server's repositories. - </para> - </important> - <para> You may not be able to foresee all the possible uses for your server's repositories. To minimize problems for your clients, create both kinds of repository data for any repositories. @@ -1389,18 +1392,18 @@ </para>
<tip id="tp-s-c-p-stock-only"> - <title><application>up2date</application> and + <title><command>yum</command> and <application>system-config-packages</application></title> <para> If you plan to carry updates on your mirror, as most administrators do, you will probably not use <application>system-config-packages</application> much. Once the - installed package versions become out of sync with the stock - distribution versions, <application>up2date</application> becomes much + installed package versions become out of sync with the original + distribution versions, <command>yum</command> becomes much more useful. The preferred method for installing a package in that - case would be <command>up2date --install + case would be <command>yum install <replaceable>package_name</replaceable></command>. See <xref - linkend="sn-up2date"/> for more information. + linkend="sn-solving-dependencies"/> for more information. </para> </tip>
@@ -1583,119 +1586,6 @@
</section>
- <section id="sn-up2date"> - <title>Configuring <application>up2date</application></title> - <para> - The <application>up2date</application> application in &FC; now - allows use of <command>yum</command> and - <command>apt</command> repositories. The client must have a - configuration that points at the desired repositories. - </para> - - <section id="sn-up2date-config"> - <title><filename>/etc/sysconfig/rhn/up2date</filename></title> - <para> - The <filename>/etc/sysconfig/rhn/up2date</filename> file controls the - global configuration of the <application>up2date</application> - application. This file is well commented and is not explained in great - detail here. Here are some points to keep in mind, however: - </para> - <itemizedlist> - <listitem> - <para> - By default, the user must intervene to update - <command>kernel</command> packages. See the - <command>pkgSkipList</command> variable. At the command line, use - the <command>-f</command> option to force an override. At the GUI - interface, <application>up2date</application> allows the user to - override. - </para> - </listitem> - <listitem> - <para> - By default, <command>up2date</command> does not remove old - <command>kernel</command> packages. See the - <command>pkgsToInstallNotUpdate</command> variable. When - <command>up2date</command> installs a new kernel package, the old - version remains in place until removed explicitly. - </para> - </listitem> - <listitem> - <para> - The configuration file also allows use of an HTTP proxy if - desired. A number of variables pertain to this function. - </para> - </listitem> - <listitem> - <para> - By default, <application>up2date</application> sends mail to - <email>root@localhost</email> when packages are updated in batch - mode. (Running <command>up2date -u</command> starts - <application>up2date</application> in batch mode.) See the - <command>adminAddress</command> option. If you support multiple - clients and intend to use batch mode at your site, you should set - a new address here. - </para> - </listitem> - </itemizedlist> - - </section> - - <section id="sn-up2date-sources"> - <title><filename>/etc/sysconfig/rhn/sources</filename></title> - <para> - The <filename>/etc/sysconfig/rhn/sources</filename> file is used to - declare the repositories that are used with - <application>up2date</application>. A repository is declared in any of - the following ways: - </para> - -<screen> -<computeroutput>apt <replaceable>label</replaceable> <replaceable>service:server</replaceable> <replaceable>path</replaceable> <replaceable>repository_name</replaceable> -yum <replaceable>label</replaceable> <replaceable>URL</replaceable> -dir <replaceable>label</replaceable> <replaceable>local_path</replaceable></computeroutput> -</screen> - - <para> - For <command>apt</command> repositories, - <command>service:server</command> is the standard Internet protocol - and host name — for example, http://mirror.example.com. For - <command>yum</command> repositories, the URL points to the directory - on a server which <emphasis>contains</emphasis> the - <filename>headers</filename> folder. A <command>dir</command> - repository simply points to a folder that contains RPM packages. The - folder may contain the RPM packages in subdirectories. - </para> - <para> - The <command>yum-mirror</command> syntax points to a file that is a - list of alternative sources for the same repository: - </para> - -<screen> -<computeroutput>yum-mirror <replaceable>label</replaceable> <replaceable>URL</replaceable></computeroutput> -</screen> - - <para> - Edit <filename>/etc/sysconfig/rhn/sources</filename> for the clients - at your site to point to your repository. For any repository, point to - the URL for the directory containing the <filename>headers</filename> - folder. You created this folder using <command>yum-arch</command> in - <xref linkend="sn-repositories"/>. You will likely have two - repositories, one for the stock distribution and one for updates. - Examples are shown below; you may wish to point to an internal address - rather than an outward-facing server. Use a URL appropriate to your - network and Apache configuration. - </para> - -<screen> -<userinput>yum fedora-core-&FCVER; http://www.mydomain.org/pub/linux/fedora/core/&FCVER;/i386/os -yum fc&FCVER;-updates http://www.mydomain.org/pub/linux/fedora/core/updates/&FCVER;/i386</userinput> -</screen> - - </section> - - </section> - </section>
<!-- @@ -1721,3 +1611,10 @@ </index>
</article> + +<!-- +Local variables: +mode: xml +fill-column: 72 +End: +-->
docs-commits@lists.fedoraproject.org