docs-commits October 2005

docs-commits@lists.fedoraproject.org

1 participants
91 discussions

owners owners.list,1.7,1.8
by fedora-docs-commits＠redhat.com 18 Oct '05

18 Oct '05

Author: kwade Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9573 Modified Files: owners.list Log Message: New component added to cover all bugs for all formal Fedora Project websites. FDP can own the overall componet, and can and should reassign bugs to more appropriate owners. Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- owners.list 20 Jul 2005 16:37:35 -0000 1.7 +++ owners.list 18 Oct 2005 07:51:38 -0000 1.8 @@ -12,6 +12,8 @@ # Changelog: # * July 19 2005 Paul W. Frields # - Add global FDP components, make notation about roles +# * Oct 18 2005 Karsten Wade +# - Add content delivery/infrastructure components, fedora-websites added # # Roles in FDP (document-specific bugs) # initialowner = document author and/or document manager @@ -36,6 +38,12 @@ Fedora Documentation|project-tracking|Non-specific FDP work tracking bugs.|kwade@redhat.com|tfox@redhat.com|fedora-docs-list@redhat.com # +# Content delivery and infrastructure components +# + +Fedora Documentation|fedora-websites|Problems and requests for all formal Fedora Project websites, such as fedoraproject.org.|nman64@n-man.com|kwade@redhat.com| + +# # Specific FDP document components # Fedora Documentation|desktop-up2date|Keeping a desktop up-to-date using graphical tools.|fdr@eln.fastmail.fm|mjohnson@redhat.com|kwade@redhat.com

1 0

mirror-tutorial mirror-tutorial-en.xml,1.13,1.14
by fedora-docs-commits＠redhat.com 17 Oct '05

17 Oct '05

Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21943 Modified Files: mirror-tutorial-en.xml Log Message: Whoops, don't forget the revision history Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- mirror-tutorial-en.xml 17 Oct 2005 02:12:01 -0000 1.13 +++ mirror-tutorial-en.xml 17 Oct 2005 02:23:08 -0000 1.14 @@ -168,7 +168,17 @@ <authorinitials>PaulWFrields</authorinitials> <revdescription> <para> - Some style changes and more indexing + Some style changes and more indexing. + </para> + </revdescription> + </revision> + <revision> + <revnumber>0.34</revnumber> + <date>2005-10-16</date> + <authorinitials>PaulWFrields</authorinitials> + <revdescription> + <para> + Added client configuration section. </para> </revdescription> </revision>

1 0

mirror-tutorial mirror-tutorial-en.xml,1.12,1.13
by fedora-docs-commits＠redhat.com 17 Oct '05

17 Oct '05

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;)">  <!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:

1 0

mirror-tutorial mirror-tutorial-en.xml,1.11,1.12
by fedora-docs-commits＠redhat.com 15 Oct '05

15 Oct '05

Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22393 Modified Files: mirror-tutorial-en.xml Log Message: Some style and content changes, bump to 0.33 Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- mirror-tutorial-en.xml 12 Oct 2005 22:41:50 -0000 1.11 +++ mirror-tutorial-en.xml 15 Oct 2005 15:54:57 -0000 1.12 @@ -6,8 +6,8 @@ %FEDORA-ENTITIES-EN; <!ENTITY BOOKNAME "mirror-tutorial"> -<!ENTITY BOOKVERSION "0.32"> -<!ENTITY BOOKDATE "2005-10-12"> +<!ENTITY BOOKVERSION "0.33"> +<!ENTITY BOOKDATE "2005-10-15"> <!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">  <!ENTITY BUG-NUM "130125"> @@ -171,6 +171,16 @@ </para> </revdescription> </revision> + <revision> + <revnumber>0.33</revnumber> + <date>2005-10-15</date> + <authorinitials>PaulWFrields</authorinitials> + <revdescription> + <para> + Some style changes and more indexing + </para> + </revdescription> + </revision> </revhistory> </articleinfo> @@ -180,11 +190,12 @@ <title>Purpose</title> <para> This tutorial presents a number of related topics that allow an - administrator to seamlessly integrate mirroring and update services for - &FC;. You can use these services to provision a classroom, laboratory, - or office. These service provisions also increase ease of use and - enhance user experience, adding to the perceived value of - non-proprietary operating systems and software. + administrator to seamlessly integrate mirroring and update + services for &FC;. Use these services to provision a classroom, + laboratory, or office. These service provisions also increase + ease of use and enhance user experience. They also add to the + perceived value of non-proprietary operating systems and + software. </para> &BUG-REPORTING; </section> @@ -192,18 +203,18 @@ <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; <quote>power user</quote> familiar with + the following topics: </para> <itemizedlist> <listitem> <para> - &FC; system installation + &FC; system installation and administration </para> </listitem> <listitem> <para> - Basic Internet protocols (HTTP/Web, FTP) + Basic Internet protocols (HTTP/Web) </para> </listitem> <listitem> @@ -217,43 +228,45 @@ <title>About Mirrors</title> <para> A <emphasis>mirror</emphasis> - <indexterm><primary>mirror</primary></indexterm> 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 across many sites. Side benefits of - running a local mirror include very fast access through the local - network, providing custom services to local users, and increasing your - skills in managing Internet services. - </para> - <para> - The site from which you retrieve files to build your mirror is called an - <emphasis>upstream mirror</emphasis><indexterm> - <primary>mirror</primary> <secondary>upstream</secondary> - </indexterm>. 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 that are intended for public - access, unless you have permission from the upstream mirror site - administrator. + <indexterm><primary>mirror</primary></indexterm> 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 + across many sites. Side benefits of running a local mirror + include very fast access through the local network, providing + custom services to local users, and increasing your skills in + managing Internet services. + </para> + <para> + The site from which you retrieve files to build your mirror is + called an <emphasis>upstream mirror</emphasis><indexterm> + <primary>mirror</primary> <secondary>upstream</secondary> + </indexterm>. 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 + that are intended for public access, unless you have permission + from the upstream mirror site administrator. </para> </section> <section id="sn-additional-resources"> <title>Additional Resources</title> <para> For more information on installing &FC; see the &FC; &IG; at - &IG-URL;. For more information on basic Internet protocols, see <ulink - url="http://library.albany.edu/internet/internet.html">http://library.albany.edu/internet/internet.html</ulink>, + &IG-URL;. For more information on basic Internet protocols, see + <ulink + url="http://library.albany.edu/internet/internet.html">http://library.albany.edu/internet/internet.html</ulink>, or search Google at <ulink - url="http://www.google.com/">http://www.google.com/</ulink>. For more - general information about mirrors, see <ulink - url="http://en.wikipedia.org/wiki/Mirror_(computing)">http://en.wikipedia.org/wiki/Mirror_(computing)</ulink>. + url="http://www.google.com/">http://www.google.com/</ulink>. + For more general information about mirrors, see <ulink + url="http://en.wikipedia.org/wiki/Mirror_(computing)">http://en.wikipedia.org/wiki/Mirror_(computing)</ulink>. </para> </section> <section id="sn-acknowledgements"> <title>Acknowledgements</title> <para> - Karsten Wade provided editorial services, keeping the style crisp and - consistent. + Karsten Wade provided editorial services and kept the style + crisp and consistent. </para> </section> </section> @@ -265,13 +278,15 @@ <title>The Distribution Structure</title> <para> The &FED; <emphasis>distribution</emphasis><indexterm> - <primary>distribution</primary> - </indexterm>, which is the collection of all &FED;-related files, uses - the directory tree in <xref linkend="ex-fedora-dir-tree"/>. It may - include multiple versions of &FC;. The tree design makes "trimming" of - unnecessary or undesired files easier. When setting up a mirror, - duplicate this tree exactly, or as closely as possible. Doing so makes - automating nightly updates easier. + <primary>distribution</primary> + </indexterm>, which is the collection of all &FED;-related + files, uses the directory tree in <xref + linkend="ex-fedora-dir-tree"/>. It may include multiple + versions of &FC;. The tree design makes it easier to "trim" + unnecessary or undesired files. When you set up a mirror, + duplicate this tree exactly, or as closely as possible. If you + duplicate the tree, it will be easier to automate nightly + updates. </para> <example id="ex-fedora-dir-tree"> @@ -318,13 +333,13 @@ <title>Naming conventions</title> <para> Throughout the rest of the document, - <filename>/var/www/mirror</filename> represents the folder where - all your mirrored files are stored. You may substitute a different - location. This location simplifies sharing your mirror, due to the - shipping configuration of &FC;. See <xref linkend="sn-server-config"/> - for more information. The site name - <computeroutput>mirror.example.com</computeroutput> represents the - upstream mirror. + <filename>/var/www/mirror</filename> represents the folder + where all your mirrored files are stored. You may substitute a + different location. This location simplifies sharing your + mirror, due to the shipping configuration of &FC;. See <xref + linkend="sn-server-config"/> for more information. The site + name <computeroutput>mirror.example.com</computeroutput> + represents the upstream mirror. </para> </note> <para> @@ -348,7 +363,7 @@ <firstterm>RPM</firstterm><indexterm> <primary>RPM</primary> </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 + also a system that tracks and interconnects software and version information. The RPM system is quite popular, and many other Linux distributions use RPM as well. Read more information on RPM at <ulink @@ -356,16 +371,18 @@ </para> </note> <para> - The <filename>SRPMS</filename> folders under architecture-specific - branches are links which point to the main <filename>SRPMS</filename> - folder for that distribution. For example, - <filename>fedora/linux/core/2/i386/os/SRPMS</filename> is a link which - points to <filename>fedora/linux/core/2/SRPMS</filename>. + The <filename>SRPMS</filename> folders under + architecture-specific branches are links that point to the main + <filename>SRPMS</filename> folder for that distribution. For + example, <filename>fedora/linux/core/2/i386/os/SRPMS</filename> + is a link that points to + <filename>fedora/linux/core/2/SRPMS</filename>. </para> <para> A &FED; mirror consists of at least the original ISO images - <emphasis>or</emphasis> the distribution files. If possible, include - both, provided you have sufficient disk space and/or bandwidth. + <emphasis>or</emphasis> the distribution files. If possible, + include both, provided you have sufficient disk space and/or + bandwidth. </para> </section> @@ -373,21 +390,21 @@ <title>Copying the Original Distribution</title> <para> If you already have reliable CD-ROM installation discs of a - distribution, reduce your initial bandwidth and time spent mirroring by - copying the files from the discs to your server. Copy all files from - Installation Disc 1 into the + distribution, reduce your initial bandwidth and time spent + mirroring by copying the files from the discs to your server. + Copy all files from Installation Disc 1 into the <filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/os</filename> - folder. Then copy all files from the <filename>&FED;</filename> folder - of each of the remaining Installation discs into the + folder. Then copy all files from the <filename>&FED;</filename> + folder of each of the remaining Installation discs into the <filename>fedora/linux/core/&FCVER;/<replaceable>arch</replaceable>/os/&FED;</filename> folder on the server. </para> <para> - Copy all the files from the <filename>SRPMS</filename> folder on each of - the <quote>Sources</quote> 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: + Copy all the files from the <filename>SRPMS</filename> folder on + each of the <quote>Sources</quote> 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: </para> <screen> @@ -422,11 +439,12 @@ </screen> <para> - The <application>anaconda</application> application automatically - detects these folders and uses them properly. In addition, system - configuration tools such as - <application>system-config-packages</application> also continue to work - properly when pointed at the parent of the ISO image mount points. + The <application>anaconda</application> installer application + automatically detects these folders and uses them properly. In + addition, system configuration tools such as + <application>system-config-packages</application> also continue + to work properly when pointed at the parent of the ISO image + mount points. </para> <para> There are drawbacks to using CD ISO images in this fashion. For @@ -543,33 +561,35 @@ </varlistentry> </variablelist> <para> - Unless your site closely manages workstation configuration, you should - probably not trim any of the <filename>updates</filename> branches for - the distributions you support. These locations contain packages handling - bug fixes, security patches, and errata updates which your users - probably want. + Unless your site closely manages workstation configuration, you + should probably not trim any of the <filename>updates</filename> + branches for the distributions you support. These locations + contain packages with bug fixes, security patches, and errata + updates that your users probably want. </para> </section> <section id="sn-download-files"> <title>Downloading the Files</title> <para> - Locate a public mirror site for &FC; by referring to the main project - site's mirror page, &FDP-URL;. Once you have selected a nearby mirror - site, note what services it offers (FTP, HTTP, and/or rsync). A mirror - is usually servicing a large number of users. Choose off-peak hours, - when possible, to download a large set of files. Be aware of any - timezone differences when estimating off-peak hours. + Locate a public mirror site for &FC; by referring to the main + project site's mirror page, &FDP-URL;. Once you have selected a + nearby mirror site, note what services it offers (FTP, HTTP, + and/or rsync). A mirror is usually servicing a large number of + users. Choose off-peak hours, when possible, to download a large + set of files. Be aware of any timezone differences when + estimating off-peak hours. </para> <section id="sn-http-and-ftp-download"> <title>Download Using HTTP or FTP</title> <para> - To download via HTTP or FTP, use the <command>wget</command> command. - <command>wget</command> recurses subdirectories automatically and - pulls down entire trees of data with a single command. If you are not - careful, however, it is possible to pull down much more data than you - intended. The following commands mirror the entire current &FC; + To download via HTTP or FTP, use the <command>wget</command> + command. <command>wget</command> recurses subdirectories + automatically and pulls down entire trees of data with a + single command. If you are not careful, however, it is + possible to pull down much more data than you intended. The + following commands mirror the entire current &FC; distribution: </para> @@ -584,60 +604,64 @@ <itemizedlist> <listitem> <para> - <command>--mirror</command> turns on recursion (descends into all - subdirectories), and duplicates file timestamps; + <command>--mirror</command> turns on recursion (descends + into all subdirectories), and duplicates file timestamps; </para> </listitem> <listitem> <para> - <command>-np</command> prevents <command>wget</command> from - ascending into the parent directory; + <command>-np</command> prevents <command>wget</command> + from ascending into the parent directory; </para> </listitem> <listitem> <para> - <command>-nH</command> prevents <command>wget</command> from - writing a directory named after the host (in this case, + <command>-nH</command> prevents <command>wget</command> + from writing a directory named after the host (in this + case, <filename><replaceable>mirror.example.com</replaceable></filename>); </para> </listitem> <listitem> <para> <command>--cut-dirs=<replaceable>n</replaceable></command> - truncates the first <replaceable>n</replaceable> directories in - the path. In the example above, <command>--cut-dirs=2</command> - prevents <command>wget</command> from writing the + truncates the first <replaceable>n</replaceable> + directories in the path. In the example above, + <command>--cut-dirs=2</command> prevents + <command>wget</command> from writing the <filename><replaceable>/pub/mirror</replaceable></filename> portion of the path into your mirror. </para> </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 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> <section id="sn-rsync"> <title>The <command>rsync</command> Command</title> <para> - Use the <command>rsync</command> command to synchronize a set of files - and/or directories with a remote host. It operates in much the same - way as <command>rcp</command>, but it is usually faster. One reason - for the speed is that <command>rsync</command> has a special protocol - that evaluates and skips files (or portions of files) that are already + Use the <command>rsync</command> command to synchronize a set + of files and/or directories with a remote host. It operates in + much the same way as <command>rcp</command>, but it is usually + faster. One reason for the speed is that + <command>rsync</command> has a special protocol that evaluates + and skips files (or portions of files) that are already downloaded. </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. + 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. </para> <screen> @@ -645,16 +669,18 @@ </screen> <para> - These modules are roughly equivalent to top-level directories, and - they follow the same rules. To list any subdirectory of the upstream - mirror, add the directory path to the command above. For example, on - many mirrors, the <filename>fedora-linux-core</filename> module is - equivalent to the <filename>fedora/linux/core</filename> path found at - the &FP; main download server. To list the contents of the &FC; + These modules are roughly equivalent to top-level directories, + and they follow the same rules. To list any subdirectory of + the upstream mirror, add the directory path to the command + above. For example, on many mirrors, the + <filename>fedora-linux-core</filename> module is equivalent to + 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 + <quote>/</quote>. Without it, you only receive a listing of a + folder name that matches the last component of the remote + path. </para> <screen> @@ -666,12 +692,13 @@ <section id="sn-rsync-download"> <title>Downloading Using <command>rsync</command></title> <para> - To download via <command>rsync</command>, add a destination path on - your system to the end of the command line. The resulting tree of - files from the listing you perform are downloaded to the local path - you specify. Remember, if you leave off the trailing slash on the - remote path, then the last component of that path is created as a - folder, and its contents are copied. + To download via <command>rsync</command>, add a destination + path on your system to the end of the command line. The + resulting tree of files from the listing you perform are + downloaded to the local path you specify. Remember, if you + leave off the trailing slash on the remote path, then the last + component of that path is created as a folder, and its + contents are copied. </para> <screen> @@ -1000,8 +1027,8 @@ Alias /mirror /var/www/mirror # Share options for the installation tree. -# Only allow connections from the local host and machines -# whose IP addresses start with 192.168.1 +# Only allow connections from localhost and +# IP addresses which start with 192.168.1 <Directory /var/www/mirror> AllowOverride None @@ -1040,185 +1067,191 @@ </section> - <section id="sn-solving-dependencies"> - <title>Solving Dependencies</title> - <para> - Every RPM package has a <emphasis>header</emphasis> 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 - <emphasis>dependencies</emphasis><indexterm> - <primary>dependencies</primary> </indexterm>. A dependency is a - requirement for one or more additional packages. - </para> - <para> - 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; provides the - <command>yum</command> utility for solving these dependencies - automatically, providing an improved user experience. - </para> + <section id="sn-solving-dependencies"> + <title>Solving Dependencies</title> + <para> + Every RPM package has a <indexterm> <primary>RPM</primary> + <secondary>header</secondary> + </indexterm><firstterm>header</firstterm> 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 + <emphasis>dependencies</emphasis><indexterm> + <primary>RPM</primary> + <secondary>dependencies</secondary> + </indexterm>. A dependency is a requirement for one or more + additional packages. + </para> + <para> + 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; provides the + <command>yum</command> utility for solving these dependencies + automatically, providing an improved user experience. + </para> - <para> + <para> The Yellow Dog Updater Modified, or - <emphasis>yum</emphasis><indexterm> <primary>yum</primary> + <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 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> + 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 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> + </section> - <section id="sn-repositories"> - <title>Configuring Repositories</title> - <para> + <section id="sn-repositories"> + <title>Configuring Repositories</title> + <para> A <command>yum</command> - <emphasis>repository</emphasis><indexterm> - <primary>repository</primary> <secondary>yum</secondary> - </indexterm> is a collection of packages on a server which - supports <command>yum</command> clients. Repositories can serve - both types of clients if desired. - </para> + <emphasis>repository</emphasis><indexterm> + <primary>repository</primary> + </indexterm> is a collection of packages on a server which + supports <command>yum</command> clients. Repositories can serve + both types of clients if desired. + </para> - <para> - To set up a <command>yum</command> repository, you must write a - directory that contains information which the clients require to - resolve RPM dependencies. The directory's name depends on the - version of <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> - <para> - A directory which supports older versions of - <command>yum</command> (before 2.2) is named - <filename>headers</filename>. It is created by using the command - <command>yum-arch</command>, which is run against the directory - <emphasis>under which</emphasis> you want the - <filename>headers</filename> directory to appear. The - <command>yum-arch</command> program searches recursively through - that directory and any subdirectories for RPM packages, and - includes them in the header data. + To set up a <command>yum</command> repository, you must write a + directory that contains information which the clients require to + resolve RPM dependencies. The directory's name depends on the + version of <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> + <para> + A directory which supports older versions of + <command>yum</command> (before 2.2) is named + <filename>headers</filename>. It is created by using the + command <command>yum-arch</command>, which is run against the + directory <emphasis>under which</emphasis> you want the + <filename>headers</filename> directory to appear. The + <command>yum-arch</command> program searches recursively + through that directory and any subdirectories for RPM + packages, and includes them in the header data. + </para> <screen> <userinput>yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput> </screen> - <para> - The <command>-l</command> switch follows symbolic links. The - <command>-s</command> switch includes SRPMS (source RPM - packages) in the header list. The command above creates the - <command>yum</command> header cache in the directory - <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/headers</filename>. - </para> - </section> + <para> + The <command>-l</command> switch follows symbolic links. The + <command>-s</command> switch includes SRPMS (source RPM + packages) in the header list. The command above creates the + <command>yum</command> header cache in the directory + <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/headers</filename>. + </para> + </section> - <section id="sn-createrepo"> - <title><command>createrepo</command></title> - <para> - The <command>createrepo</command> command creates repository - information to support newer versions of <command>yum</command> - (and possibly other repository client programs). The - <command>createrepo</command> command stores this data in a - folder named <filename>repodata</filename>. Just as with - <command>yum-arch</command>, run <command>createrepo</command> - against the directory <emphasis>under which</emphasis> you want - the <filename>repodata</filename> directory to appear. The - <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/www/mirror/fedora/linux/core/&FCVER;/i386/os/repodata</filename>. - </para> + <section id="sn-createrepo"> + <title><command>createrepo</command></title> + <para> + The <command>createrepo</command> command creates repository + information to support newer versions of + <command>yum</command> (and possibly other repository client + programs). The <command>createrepo</command> command stores + this data in a folder named <filename>repodata</filename>. + Just as with <command>yum-arch</command>, run + <command>createrepo</command> against the directory + <emphasis>under which</emphasis> you want the + <filename>repodata</filename> directory to appear. The + <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/www/mirror/fedora/linux/core/&FCVER;/i386/os/repodata</filename>. + </para> <screen> <userinput>createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput> </screen> - <para> - You may not be able to foresee all the possible uses for your - server's repositories. You may have certain clients who update - their version of <command>yum</command> in a non-prescribed way. - To minimize problems for your clients, create both kinds of - repository data for any repositories. The extra repository - information is relatively small and will not affect your - mirror's proper function. - </para> + <para> + You may have certain clients who update their version of + <command>yum</command> in a non-prescribed way. To minimize + problems for your clients, create both kinds of repository + data for any repositories. The extra repository information + is relatively small and will not affect your mirror's proper + function. + </para> - </section> + </section> - <section id="sn-repository-locations"> - <title>Repository Locations</title> - <para> - Typically <command>yum-arch</command> or - <command>createrepo</command> is run against at least the - following locations: - </para> - <itemizedlist> - <listitem> - <para> - The stock distribution; for example, - <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/</filename>. - For <command>yum-arch</command> use the - <command>-l</command> and <command>-s</command> options to - follow the linked directory <filename>SRPMS</filename> and - include the source packages therein. - </para> - </listitem> - <listitem> - <para> - Official updates to the distribution; for example, - <filename>/var/mirror/fedora/linux/core/updates/&FCVER;/</filename>. - Once again, for <command>yum-arch</command> use - <command>-l</command> and/or <command>-s</command> if - appropriate. - </para> - </listitem> - </itemizedlist> - </section> + <section id="sn-repository-locations"> + <title>Repository Locations</title> + <para> + Typically you will run <command>yum-arch</command> or + <command>createrepo</command> against at least the following + locations: + </para> + <itemizedlist> + <listitem> + <para> + The stock distribution; for example, + <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/</filename>. + For <command>yum-arch</command>, use the + <command>-l</command> and <command>-s</command> options to + follow the linked directory <filename>SRPMS</filename> and + include the source packages therein. + </para> + </listitem> + <listitem> + <para> + Official updates to the distribution; for example, + <filename>/var/mirror/fedora/linux/core/updates/&FCVER;/</filename>. + Once again, for <command>yum-arch</command> use + <command>-l</command> and/or <command>-s</command> if + appropriate. + </para> + </listitem> + </itemizedlist> + </section> </section>

1 0

yum-software-management yum-software-management-en.xml,1.47,1.48
by fedora-docs-commits＠redhat.com 13 Oct '05

13 Oct '05

Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31612 Modified Files: yum-software-management-en.xml Log Message: Fix wording (#170584), push to 1.0.3 Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.47 retrieving revision 1.48 diff -u -r1.47 -r1.48 --- yum-software-management-en.xml 4 Sep 2005 13:53:03 -0000 1.47 +++ yum-software-management-en.xml 13 Oct 2005 11:34:47 -0000 1.48 @@ -4,7 +4,7 @@ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent"> %FEDORA-ENTITIES-EN; -<!ENTITY BOOKID "yum-software-management-1.0.2 (2005-08-26)">  +<!ENTITY BOOKID "yum-software-management-1.0.3 (2005-10-13)">   <!ENTITY BUG-NUM "155190"> @@ -88,6 +88,16 @@ </para> </revdescription> </revision> + <revision> + <revnumber>1.0.3</revnumber> + <date>2005-10-13</date> + <authorinitials>PaulWFrields</authorinitials> + <revdescription> + <para> + Fix wording (#170584). + </para> + </revdescription> + </revision> </revhistory> </articleinfo> @@ -582,7 +592,7 @@ </indexterm> <para> The <command>yum</command> utility is a complete software - management system. &FC; also includes other several other + management system. &FC; also includes several other applications that can supplement <command>yum</command>. </para>

1 0

mirror-tutorial mirror-tutorial-en.xml,1.10,1.11
by fedora-docs-commits＠redhat.com 12 Oct '05

12 Oct '05

Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10438 Modified Files: mirror-tutorial-en.xml Log Message: Major changes to simplify, more on the way... Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- mirror-tutorial-en.xml 18 Sep 2005 22:43:44 -0000 1.10 +++ mirror-tutorial-en.xml 12 Oct 2005 22:41:50 -0000 1.11 @@ -5,7 +5,10 @@ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent"> %FEDORA-ENTITIES-EN; -<!ENTITY BOOKID "mirror-tutorial-0.31 (2005-08-29)">  +<!ENTITY BOOKNAME "mirror-tutorial"> +<!ENTITY BOOKVERSION "0.32"> +<!ENTITY BOOKDATE "2005-10-12"> +<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">  <!ENTITY BUG-NUM "130125"> <!ENTITY FCLOCALVER "4"> @@ -158,6 +161,16 @@ </para> </revdescription> </revision> + <revision> + <revnumber>0.32</revnumber> + <date>2005-10-12</date> + <authorinitials>PaulWFrields</authorinitials> + <revdescription> + <para> + Fix default network sharing protocol (#169581, #169584) + </para> + </revdescription> + </revision> </revhistory> </articleinfo> @@ -305,7 +318,7 @@ <title>Naming conventions</title> <para> Throughout the rest of the document, - <filename>/var/ftp/pub/mirror</filename> represents the folder where + <filename>/var/www/mirror</filename> represents the folder where all your mirrored files are stored. You may substitute a different location. This location simplifies sharing your mirror, due to the shipping configuration of &FC;. See <xref linkend="sn-server-config"/> @@ -332,17 +345,14 @@ <note> <title>RPM packages</title> <para> - <firstterm>RPM</firstterm><indexterm> - <primary>RPM</primary> - </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 - well. Read more information on RPM at <ulink - url="http://www.rpm.org/">http://www.rpm.org/</ulink>. This document - contains helpful hints on making the most of RPM, in <xref - linkend="sn-server-config"/> and - <xref linkend="sn-client-config"/>. + <firstterm>RPM</firstterm><indexterm> <primary>RPM</primary> + </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 well. Read more + information on RPM at <ulink + url="http://www.rpm.org/">http://www.rpm.org/</ulink>. </para> </note> <para> @@ -381,7 +391,7 @@ </para> <screen> -<userinput>cd /var/ftp/pub/mirror/fedora/linux/core/&FCVER;/i386/os/Fedora +<userinput>cd /var/www/mirror/fedora/linux/core/&FCVER;/i386/os/Fedora ln ../../SRPMS SRPMS</userinput> </screen> @@ -408,7 +418,7 @@ </para> <screen> -<computeroutput>/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0</computeroutput> +<computeroutput>/<replaceable>path</replaceable>/i386/iso/FC&FCVER;-i386-disc1.iso /<replaceable>path</replaceable>/i386/os/disc1 iso9660 defaults 0 0</computeroutput> </screen> <para> @@ -433,7 +443,7 @@ </para> <screen> -<computeroutput>/path/i386/iso/FC&FCVER;-i386-DVD.iso /path/i386/os iso9660 defaults 0 0</computeroutput> +<computeroutput>/<replaceable>path</replaceable>/i386/iso/FC&FCVER;-i386-DVD.iso /<replaceable>path</replaceable>/i386/os iso9660 defaults 0 0</computeroutput> </screen> </section> @@ -564,7 +574,7 @@ </para> <screen> -<userinput>cd /var/ftp/pub/mirror +<userinput>cd /var/www/mirror wget --mirror -np -nH --cut-dirs=<replaceable>2</replaceable> http://mirror.example.com/pub/mirror/fedora/linux/core/&FCVER;/</userinput> </screen> @@ -665,7 +675,7 @@ </para> <screen> -<userinput>rsync filehouse.example.org::files/misc/ /var/ftp/pub/misc/</userinput> +<userinput>rsync filehouse.example.org::files/misc/ /var/www/misc/</userinput> </screen> <para> @@ -717,7 +727,7 @@ </caution> <screen> -<userinput>rsync -PHav mirror.example.org::fedora-linux-core/&FCVER;/ /var/ftp/pub/mirror/fedora/core/&FCVER;</userinput> +<userinput>rsync -PHav mirror.example.org::fedora-linux-core/&FCVER;/ /var/www/mirror/fedora/linux/core/&FCVER;</userinput> </screen> <para id="rsync-n-switch"> @@ -877,11 +887,11 @@ <userinput>rsync -Pan --delete --exclude "**x86_64**" --exclude "**headers**" \ --exclude "**debug**" --exclude "**iso**" \ mirror.example.com::fedora-linux-core/&FCVER;/ \ - /var/ftp/pub/mirror/fedora/core/&FCVER;</userinput> + /var/www/mirror/fedora/core/&FCVER;</userinput> </screen> </section> - + </section> <section id="sn-maintenance"> @@ -951,638 +961,264 @@ </section> <section id="sn-server-config"> - <title>Server Configuration Planning</title> - <para> - Decide what services your mirror will offer to clients. There are at least - three services useful for providing &FED; installation and update - services: HTTP, FTP, and NFS. Some or all of these services can be used - for offering post-installation functions such as updates or installing - additional packages. - </para> - <para> - Install the <filename>vsftpd</filename> package for FTP services. Install - the <filename>httpd</filename> package to use the Apache HTTP server. Most - &FC; systems already have the <command>nfs-utils</command> package - installed, which contains the NFS server. - </para> - <para> - To start a service, use the <command>/sbin/service - <replaceable>service</replaceable> start</command> command. To enable that - server by default at boot time, use the <command>chkconfig - <replaceable>service</replaceable> on</command> command. - </para> - <para> - One recommended method is to download all mirrored files into - <filename>/var/ftp/pub</filename>, add a link in - <filename>/var/www/html</filename> that points to - <filename>/var/ftp/pub</filename>, and share out - <filename>/var/ftp/pub</filename> via NFS as well. FTP and HTTP services - do not require any further configuration to work properly. - <emphasis>However, you should evaluate your site's security needs before - enabling them.</emphasis> NFS service configuration is explained below - in <xref linkend="sn-nfs-config"/>. - </para> - <para> - To share out the public FTP area via HTTP, issue the following - command: - </para> - -<screen> -<userinput>ln -s /var/ftp/pub /var/www/html/pub</userinput> -</screen> - - <para> - Your clients may now visit any area of your mirror by using the URL - <replaceable>http://server.mydomain.org/pub/path</replaceable>. To create - an NFS share, add a line to <filename>/etc/exports</filename>. This - example shares out the &FC; &FCVER; i386 stock distribution with read-only - access for any host in the <computeroutput>mydomain.org</computeroutput> - domain. - </para> - -<screen> -<userinput>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os *.mydomain.org(ro,sync,root_squash)</userinput> -</screen> + <title>Server Configuration</title> <para> - To reread the NFS server configuration files and export the new share, use - the following command: + This section gives guidance on setting up a HTTP (Web) server that + provides installation and update mirror services. </para> -<screen> -<userinput>exportfs -ar</userinput> -</screen> - - <para> - Refer to <xref linkend="sn-nfs-config"/> for a list of commands for - starting services both on demand and at boot time. - </para> - - <section id="sn-solving-dependencies"> - <title>How to Solve Dependencies</title> - <para> - Every RPM package has a <emphasis>header</emphasis> 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 - <emphasis>dependencies</emphasis><indexterm> - <primary>dependencies</primary> - </indexterm>. A dependency is a requirement for one or more additional - packages. - </para> - <para> - 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; provides the - <command>yum</command> utility for solving these - dependencies automatically, providing an improved user experience. - </para> + <section id="sn-setting-up-apache"> + <title>Setting Up Apache</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> 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/"/>. + The HTTP service, provided by the Apache server in the + <filename>httpd</filename> 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 <filename>httpd</filename> package, if you have not + already done so, use the following command: </para> - </section> - - <section id="sn-repositories"> - <title>Configuring Repositories</title> - <para> - A <command>yum</command> <emphasis>repository</emphasis><indexterm> - <primary>repository</primary> - <secondary>yum</secondary> - </indexterm> is a collection of packages on a server which supports - <command>yum</command> clients. Repositories can serve both types of - clients if desired. - </para> +<screen> +<userinput>su - -c "yum install httpd"</userinput> +</screen> <para> - To set up a <command>yum</command> repository, you must write a - directory that contains information which the clients require to resolve - RPM dependencies. The directory's name depends on the version of - <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. + Next, create a configuration file + <filename>/etc/httpd/conf.d/mirror.conf</filename> for your + mirror files. The following listing is an example: </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> - <para> - A directory which supports older versions of <command>yum</command> - (before 2.2) is named <filename>headers</filename>. It is created by - using the command <command>yum-arch</command>, which is run against - the directory <emphasis>under which</emphasis> you want the - <filename>headers</filename> directory to appear. The - <command>yum-arch</command> program searches recursively through that - directory and any subdirectories for RPM packages, and includes them - in the header data. - </para> + <example> + <title>Apache 2.x configuration file for installation + mirror</title> <screen> -<userinput>yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput> -</screen> - - <para> - The <command>-l</command> switch follows symbolic links. The - <command>-s</command> switch includes SRPMS (source RPM packages) in - the header list. The command above creates the <command>yum</command> - header cache in the directory - <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers</filename>. - </para> - </section> +<computeroutput><![CDATA[# The name at which the installation tree will be shared, +# followed by the name of the root directory of that tree. +Alias /mirror /var/www/mirror - <section id="sn-createrepo"> - <title><command>createrepo</command></title> - <para> - The <command>createrepo</command> command creates repository - information to support newer versions of <command>yum</command> (and - possibly other repository client programs). The - <command>createrepo</command> command stores this data in a folder - named <filename>repodata</filename>. Just as with - <command>yum-arch</command>, run <command>createrepo</command> against - the directory <emphasis>under which</emphasis> you want the - <filename>repodata</filename> directory to appear. The - <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> +# Share options for the installation tree. +# Only allow connections from the local host and machines +# whose IP addresses start with 192.168.1 -<screen> -<userinput>createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput> +<Directory /var/www/mirror> + AllowOverride None + Order Deny,Allow + Deny from all + Allow from 127.0.0.1 192.168.1 + Options Indexes +</Directory>]]></computeroutput> </screen> - <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. - </para> - - </section> - - <section id="sn-repository-locations"> - <title>Repository Locations</title> - <para> - Typically <command>yum-arch</command> or <command>createrepo</command> - is run against at least the following locations: - </para> - <itemizedlist> - <listitem> - <para> - The stock distribution; for example, - <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>. - For <command>yum-arch</command> use the <command>-l</command> and - <command>-s</command> options to follow the linked directory - <filename>SRPMS</filename> and include the source packages - therein. - </para> - </listitem> - <listitem> - <para> - Official updates to the distribution; for example, - <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>. - Once again, for <command>yum-arch</command> use - <command>-l</command> and/or <command>-s</command> if appropriate. - </para> - </listitem> - </itemizedlist> - </section> - - </section> - - <section id="sn-nfs-config"> - <title>Configuring NFS</title> - <para> - Some client-side utilities also resolve dependencies automatically. - These utilities require more detailed configuration of the client - workstation. For more information, see <xref - linkend="sn-client-config"/> below. These utilities, however, require - standard file system access to package collections. For this reason, you - may require NFS on your mirror. Configuration of the client depends - in large part on how you decide to implement NFS sharing on the mirror. - </para> - <para> - It is difficult to share subdirectories of other shared directories. - Therefore, think of your mirror as offering many services, each one to - be considered for NFS sharing. For example, share both the stock - distribution of &FC; 2 and the stock distribution of &FC; 3. - </para> - <para> - The client side tools discussed later can use a directory of ISO images - or an exploded tree of package data (see <xref - linkend="sn-copying-original-distribution"/>). You may share out any or - all of these, provided your shares do not clash as described above. - </para> - - + </example> <para> - To share via NFS, edit the <filename>/etc/exports</filename> file. A - typical share, exported with read-only access for any host on any - network, looks like this: + To start the <command>httpd</command> service, use the following + command: </para> <screen> -<computeroutput>/mnt/media *(ro,all_squash,async)</computeroutput> +<userinput>/sbin/service httpd start</userinput> </screen> <para> - The <command>all_squash</command> option ensures that no users accessing - the share using their local root account receive equivalent access on - the share. This feature keeps some small measure of security even on a - public share, since a file readable only by root on the server is not - readable by an NFS client. The <command>async</command> option allows - asynchronous read/writes, which is not dangerous in this case because - the share is read-only. The <command>*</command> is a host designator, - in this case matching any host name or IP address. You may wish to - restrict this share to your internal network. You may declare either a - matching name or IP address specification. You can find more detailed - information by reading the man pages for the - <filename>/etc/exports</filename> file by using the command <command>man - 5 exports</command>. - </para> - <important> - <title>Access control format</title> - <para> - Be certain that you do not have a space between the host specification - and the option listing in parentheses <computeroutput>( - )</computeroutput>. A space causes the NFS daemon to consider that - entry as <emphasis>two separate access controls</emphasis>. In the - example above, a space causes the first access control to match all - hosts and allow write access, which is the default! The second access - control is never reached because the first matches any host first. - </para> - </important> - <para> - To share the proper directories from your mirror, use one of the - following forms. To share your exploded tree, export the directory that - contains the &FED; folder (note the capitalization). For i386 - architectures: + To enable that server by default at boot time, use the following + command: </para> <screen> -<userinput>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os *(ro,all_squash,async)</userinput> +<userinput>chkconfig httpd on</userinput> </screen> <para> - To share a directory full of ISO images, export that directory: + Your clients may now visit any area of your mirror by using the + URL + http://<replaceable>server.mydomain.org</replaceable>/mirror/<replaceable>path</replaceable>. </para> -<screen> -<userinput>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/iso *(ro,all_squash,async)</userinput> -</screen> - - + <section id="sn-repositories"> + <title>Configuring Repositories</title> + <para> + A <command>yum</command> + <emphasis>repository</emphasis><indexterm> + <primary>repository</primary> <secondary>yum</secondary> + </indexterm> is a collection of packages on a server which + supports <command>yum</command> clients. Repositories can serve + both types of clients if desired. + </para> + <para> + To set up a <command>yum</command> repository, you must write a + directory that contains information which the clients require to + resolve RPM dependencies. The directory's name depends on the + version of <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> - Once you have edited the <filename>/etc/exports</filename> file, make - sure that the NFS server is installed and started properly on the - mirror. The <filename>portmap</filename> and - <filename>nfs-utils</filename> packages must be installed. Configure - them to be turned on at boot time by default. + &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> -<screen> -<userinput>/sbin/chkconfig portmap on -/sbin/chkconfig nfslock on -/sbin/chkconfig nfs on</userinput> -</screen> - + <section id="sn-yum-arch"> + <title><command>yum-arch</command></title> <para> - To check if any of these services are currently running, use the - <command>/sbin/service <replaceable>service_name</replaceable> - status</command> command: + A directory which supports older versions of + <command>yum</command> (before 2.2) is named + <filename>headers</filename>. It is created by using the command + <command>yum-arch</command>, which is run against the directory + <emphasis>under which</emphasis> you want the + <filename>headers</filename> directory to appear. The + <command>yum-arch</command> program searches recursively through + that directory and any subdirectories for RPM packages, and + includes them in the header data. </para> <screen> -<userinput>/sbin/service portmap status -/sbin/service nfslock status -/sbin/service nfs status</userinput> +<userinput>yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput> </screen> <para> - To restart a service, use the <command>/sbin/service - <replaceable>service_name</replaceable> restart</command> command: + The <command>-l</command> switch follows symbolic links. The + <command>-s</command> switch includes SRPMS (source RPM + packages) in the header list. The command above creates the + <command>yum</command> header cache in the directory + <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/headers</filename>. </para> + </section> -<screen> -<userinput>/sbin/service portmap restart -/sbin/service nfslock restart -/sbin/service nfs restart</userinput> -</screen> - + <section id="sn-createrepo"> + <title><command>createrepo</command></title> + <para> + The <command>createrepo</command> command creates repository + information to support newer versions of <command>yum</command> + (and possibly other repository client programs). The + <command>createrepo</command> command stores this data in a + folder named <filename>repodata</filename>. Just as with + <command>yum-arch</command>, run <command>createrepo</command> + against the directory <emphasis>under which</emphasis> you want + the <filename>repodata</filename> directory to appear. The + <command>createrepo</command> program also searches recursively + for RPM packages to include in the repository data. + </para> <para> - If any service is not started, use the command <command>/sbin/service - <replaceable>service_name</replaceable> start</command> to start it, as - in the following examples: + The following command creates the repository data in the + directory + <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/repodata</filename>. </para> <screen> -<userinput>/sbin/service portmap start -/sbin/service nfslock start -/sbin/service nfs start</userinput> +<userinput>createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput> </screen> <para> - To change your exports when the NFS service is already running, use the - command <command>/usr/sbin/exportfs -ar</command>. The command - <command>/usr/sbin/showmount -e</command> displays a list of the - current NFS exports on the local host machine. + You may not be able to foresee all the possible uses for your + server's repositories. You may have certain clients who update + their version of <command>yum</command> in a non-prescribed way. + To minimize problems for your clients, create both kinds of + repository data for any repositories. The extra repository + information is relatively small and will not affect your + mirror's proper function. </para> </section> - </section> - - <section id="sn-client-config"> - <title>Client Configuration</title> - <para> - You must also correctly configure the client workstations that use your - mirror. Using the mirror as a source for RPM packages, clients may have - seamless access for installing basic software through - <application>system-config-packages</application>, solving RPM package - installations at the command line, and pulling bug fix and security errata - updates. - </para> - - <section id="sn-system-config-packages"> - <title>Configuring <application>system-config-packages</application></title> + <section id="sn-repository-locations"> + <title>Repository Locations</title> <para> - Users typically run the - <application>system-config-packages</application> application from the - GUI menu, by choosing <guimenu>System Settings</guimenu>, - <guimenuitem>Add/Remove Applications</guimenuitem>. This program allows - the user to change the stock installation, provided no updates have - taken place yet that interfere. - </para> - <para> - Often, <application>system-config-packages</application> stops - functioning optimally after certain updates are installed. This is - because <application>system-config-packages</application> solves - dependencies based on the stock distribution. It is impossible for - <application>system-config-packages</application> to predict version - numbers of updates. If you intend to carry updates on your mirror, you - should be aware that installing certain updates causes - <application>system-config-packages</application> to lose its - effectiveness. Some sites do not mirror all updates due to configuration - management concerns. The guidance in this section is especially useful - in those scenarios. - </para> - - <tip id="tp-s-c-p-stock-only"> - <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 original - distribution versions, <command>yum</command> becomes much - more useful. The preferred method for installing a package in that - case would be <command>yum install - <replaceable>package_name</replaceable></command>. See <xref - linkend="sn-solving-dependencies"/> for more information. - </para> - </tip> - - <section id="sn-autofs"> - <title>Setting Up <command>autofs</command></title> - <para> - The <command>autofs</command><indexterm> - <primary>autofs</primary> - </indexterm> facility allows a &FC; system to mount file systems on - demand. The <filename>/etc/auto.master</filename> file contains an - <emphasis>automounter map</emphasis><indexterm> - <primary>automounter map</primary> - </indexterm> - <indexterm> - <primary>map</primary> - <secondary>automounter</secondary> - <see>automounter map</see> - </indexterm>. On &FC;, the automounter map is a list of additional - definition files that should be loaded, one for each directory in the - map. An example line from <filename>/etc/auto.master</filename> is - shown below: - </para> - -<screen> -<computeroutput>/misc /etc/auto.misc --timeout=60</computeroutput> -</screen> - - <para> - The first term in the line is the directory which is reserved for - automounting. The second term is the automount file which should be - consulted to determine any maps for that directory. The third term in - the example indicates that if a map under /misc is not busy for 60 - seconds, it is unmounted. - </para> - <para> - The <filename>/etc/auto.misc</filename> file contains entries similar - to the following example. - </para> - -<screen> -<computeroutput>remote -ro,soft,intr host.foobar.org:/pub</computeroutput> -</screen> - - <para> - This line is contained in the automounter map file for the - <filename>/misc</filename> directory. The first term is a key which is - the name of a directory that appears upon demand. The second term is - actually a list of options, identical to those that would be used for - a real <command>mount</command> command. The final term is the file - system (local or remote) to mount. In the above example, if the user - of this station accesses the directory - <filename>/misc/remote</filename>, an NFS mount is automatically - performed. The user's command appears to hesitate, depending on how - fast the NFS server responds. Then <filename>/misc/remote</filename> - appears to be full of whatever content is on host.foobar.org in the - <filename>/pub</filename> NFS share. - </para> - <para> - You can use this function to provide NFS access to the stock - distribution for &FC;. Choose a directory to map in the - <filename>/etc/auto.master</filename> file, and match it to a - corresponding automounter map file. The easiest way to do this is to - simply remove the comment <computeroutput>#</computeroutput> from the - front of the line attaching <filename>/misc</filename> to - <filename>/etc/auto.misc</filename>. The default timeout should be - sufficient. - </para> - <para> - Make an entry in <filename>/etc/auto.misc</filename> similar to - this. You can have multiple entries, each one with a different - key. For instance, each key could be mapped to a different version of - &FC; that you have available on the local mirror. - </para> - -<screen> -<userinput>fc&FCVER; -ro,soft,intr mirror.mydomain.org:/var/ftp/pub/linux/fedora/core/&FCVER;</userinput> -</screen> - - <para> - Now restart the <command>autofs</command> service: - </para> - -<screen> -<userinput>/sbin/service autofs restart</userinput> -</screen> - - <para> - To access the stock distribution for &FC; &FCVER; the user can simply - type <command>cd /misc/fc&FCVER;</command>. The share is automatically - mounted and the files simply appear in that local directory. - </para> - - </section> - - <section id="sn-shared-desktop-s-c-p"> - <title><filename>/usr/share/applications/system-config-packages</filename></title> - <para> - Now that <command>autofs</command> has been configured, your client - workstations need to be configured so that - <application>system-config-packages</application> points to the - mirror's NFS share. Edit the - <filename>/usr/share/applications/system-config-packages</filename> - file's <command>Exec=</command> line to add a switch pointing to the - share: - </para> - -<screen> -<userinput>Exec=/usr/bin/system-config-packages --tree=/misc/fc&FCVER;/i386/os</userinput> -</screen> - - <para> - When users choose <guimenu>System Settings</guimenu>, - <guimenuitem>Add/Remove Applications</guimenuitem> from the GUI main - menu, the system now automatically resolves package dependencies from - the mirror. The restrictions stated above in <xref - linkend="tp-s-c-p-stock-only"/> apply. - </para> - </section> - - <section id="sn-rpm-aid"> - <title>The <command>rpm --aid</command> Switch</title> - <para> - The <command>--aid</command> switch for the <command>rpm</command> - command also automatically solves dependencies. It performs this - function based on the <filename>rpmdb-fedora</filename> package. That - package is a preset database for a system that has every RPM package - in the &FC; distribution installed. Even if a system does not - <emphasis>itself</emphasis> have every package installed, it can - consult the <filename>rpmdb-fedora</filename> package database to see - what such a system <emphasis>would</emphasis> look like. By using the - <command>--aid</command> switch, clients can issue a single - <command>rpm --install --aid</command> command against an original - &FC; package, and have all dependencies automatically installed as - well. - </para> - <para> - Two steps are required for this process. First, install the - <filename>rpmdb-fedora</filename> package: - </para> - -<screen> -<userinput>rpm --install /misc/fc&FCVER;/i386/os/&FED;/RPMS/rpmdb-fedora-*.rpm</userinput> -</screen> - - <para> - Then, edit the file <filename>/etc/rpm/macros.solve</filename>, which - is part of the <filename>rpmdb-fedora</filename> package. Change the - following lines to enable package resolution: - </para> - -<screen> -<computeroutput>%_solve_pkgsdir /misc/fc&FCVER;/i386/os/&FED;/RPMS/ -%_solve_name_fmt %{?_solve_pkgsdir}%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm</computeroutput> -</screen> - - <para> - Users now issue a single command to install any package from - the stock distribution, and all dependencies are solved for - them. For example: - </para> - -<screen> -<userinput>rpm --install --aid /misc/fc&FCVER;/i386/os/&FED;/RPMS/kdeutils-*.rpm</userinput> -</screen> - - <para> - If a user forgets the <command>--aid</command> switch, they still - receive hints. Normally <command>rpm</command> displays a slightly - cryptic list of capability requirements, instead of straightforward - package names. If you edit <filename>/etc/rpm/macros.solve</filename> - as shown, <command>rpm</command> displays a list of required package - names instead. - </para> - <para> - Package dependency solutions using <command>--aid</command> are also - restricted as shown above in <xref linkend="tp-s-c-p-stock-only"/>. - </para> - - </section> + Typically <command>yum-arch</command> or + <command>createrepo</command> is run against at least the + following locations: + </para> + <itemizedlist> + <listitem> + <para> + The stock distribution; for example, + <filename>/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/</filename>. + For <command>yum-arch</command> use the + <command>-l</command> and <command>-s</command> options to + follow the linked directory <filename>SRPMS</filename> and + include the source packages therein. + </para> + </listitem> + <listitem> + <para> + Official updates to the distribution; for example, + <filename>/var/mirror/fedora/linux/core/updates/&FCVER;/</filename>. + Once again, for <command>yum-arch</command> use + <command>-l</command> and/or <command>-s</command> if + appropriate. + </para> + </listitem> + </itemizedlist> + </section> </section>

1 0

docs-common/common opl.xml,NONE,1.1
by fedora-docs-commits＠redhat.com 12 Oct '05

12 Oct '05

Author: pfrields Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27788/common Added Files: opl.xml Log Message: Add OPL for reference and possible later use --- NEW FILE opl.xml --- <title>Open Publication License</title> <simpara> v1.0, 8 June 1999 </simpara> <section id="opl.require"> <title>I. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS</title> <simpara> The Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction. </simpara> <simpara> Proper form for an incorporation by reference is as follows: </simpara> <para> Copyright (c) <year> by <author's name or designee>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at <ulink url="&url.opl;">&url.opl;</ulink> </para> <simpara> The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see section VI). Commercial redistribution of Open Publication-licensed material is permitted. Any publication in standard (paper) book form shall require the citation of the original publisher and author. The publisher and author's names shall appear on all outer surfaces of the book. On all outer surfaces of the book the original publisher's name shall be as large as the title of the work and cited as possessive with respect to the title. </simpara> </section> <section id="opl.copyright"> <title>II. COPYRIGHT</title> <simpara> The copyright to each Open Publication is owned by its author(s) or designee. </simpara> </section> <section id="opl.scope"> <title>III. SCOPE OF LICENSE</title> <simpara> The following license terms apply to all Open Publication works, unless otherwise explicitly stated in the document. </simpara> <simpara> Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice. </simpara> <simpara> SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force. </simpara> <simpara> NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement. </simpara> </section> <section id="opl.modified.works"> <title>IV. REQUIREMENTS ON MODIFIED WORKS</title> <para> All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements: </para> <para> <orderedlist> <listitem> <simpara> The modified version must be labeled as such. </simpara> </listitem> <listitem> <simpara> The person making the modifications must be identified and the modifications dated. </simpara> </listitem> <listitem> <simpara> Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices. </simpara> </listitem> <listitem> <simpara> The location of the original unmodified document must be identified. </simpara> </listitem> <listitem> <simpara> The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. </simpara> </listitem> </orderedlist> </para> </section> <section id="opl.good-practice"> <title>V. GOOD-PRACTICE RECOMMENDATIONS</title> <simpara> In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that: </simpara> <para> <orderedlist> <listitem> <simpara> If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document. </simpara> </listitem> <listitem> <simpara> All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document. </simpara> </listitem> <listitem> <simpara> Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). </simpara> </listitem> </orderedlist> </para> </section> <section id="opl.options"> <title>VI. LICENSE OPTIONS</title> <simpara> The author(s) and/or publisher of an Open Publication-licensed document may elect certain options by appending language to the reference to or copy of the license. These options are considered part of the license instance and must be included with the license (or its incorporation by reference) in derived works. </simpara> <simpara> A. To prohibit distribution of substantively modified versions without the explicit permission of the author(s). "Substantive modification" is defined as a change to the semantic content of the document, and excludes mere changes in format or typographical corrections. </simpara> <simpara> To accomplish this, add the phrase `Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.' to the license reference or copy. </simpara> <simpara> B. To prohibit any publication of this work or derivative works in whole or in part in standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. </simpara> <simpara> To accomplish this, add the phrase 'Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder.' to the license reference or copy. </simpara> </section>

1 0

docs-common/packaging titlegrab.py,1.1,1.2
by fedora-docs-commits＠redhat.com 12 Oct '05

12 Oct '05

Author: pfrields Update of /cvs/docs/docs-common/packaging In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26358/packaging Modified Files: titlegrab.py Log Message: Fix magic line Index: titlegrab.py =================================================================== RCS file: /cvs/docs/docs-common/packaging/titlegrab.py,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- titlegrab.py 3 Oct 2005 02:32:06 -0000 1.1 +++ titlegrab.py 12 Oct 2005 15:00:42 -0000 1.2 @@ -1,4 +1,4 @@ -#!/usr/bin/python -d +#!/usr/bin/python -tt import sys import xml.dom.minidom from xml.dom.minidom import Node

1 0

docs-common Makefile,1.1,1.2
by fedora-docs-commits＠redhat.com 12 Oct '05

12 Oct '05

Author: pfrields Update of /cvs/docs/docs-common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26305 Modified Files: Makefile Log Message: Fix packaging to properly add menu and desktop files Index: Makefile =================================================================== RCS file: /cvs/docs/docs-common/Makefile,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Makefile 12 Oct 2005 00:09:37 -0000 1.1 +++ Makefile 12 Oct 2005 14:59:44 -0000 1.2 @@ -40,6 +40,7 @@ find . -maxdepth 1 -type d $ \ -name 'common' -o \ -name 'css' -o \ + -name 'packaging' -o \ -name 'stylesheet-images' $ | xargs -i \ find {} -maxdepth 1 -type f ! \( \ -name '.*' -o -name '*~' -o \

1 0

docs-common/packaging fedora-documentation.menu, NONE, 1.1 fedora-doc-common.spec, 1.1, 1.2 fedora-doc.desktop.in.common, 1.2, 1.3
by fedora-docs-commits＠redhat.com 12 Oct '05

12 Oct '05

Author: pfrields Update of /cvs/docs/docs-common/packaging In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26305/packaging Modified Files: fedora-doc-common.spec fedora-doc.desktop.in.common Added Files: fedora-documentation.menu Log Message: Fix packaging to properly add menu and desktop files --- NEW FILE fedora-documentation.menu --- <!DOCTYPE Menu PUBLIC "-//freedesktop//DTD Menu 1.0//EN" "http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd"> <Menu> <Name>Applications</Name> <Menu> <Name>Documentation</Name> <Directory>Documentation.directory</Directory> <Include> <Category>X-Fedora-Documentation</Category> </Include> </Menu> </Menu> Index: fedora-doc-common.spec =================================================================== RCS file: /cvs/docs/docs-common/packaging/fedora-doc-common.spec,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- fedora-doc-common.spec 12 Oct 2005 00:09:41 -0000 1.1 +++ fedora-doc-common.spec 12 Oct 2005 14:59:43 -0000 1.2 @@ -35,6 +35,10 @@ install -d -m 755 $RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/css/ install -m 644 $RPM_BUILD_DIR/%{name}-%{release}/css/* \ $RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/css/ +install -d -m 755 $RPM_BUILD_ROOT/%{_sysconfdir}/xdg/menus/applications-merged/ +install -m 644 \ + $RPM_BUILD_DIR/%{name}-%{release}/packaging/fedora-documentation.menu \ + $RPM_BUILD_ROOT/%{_sysconfdir}/xdg/menus/applications-merged/ install -d -m 755 $RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/stylesheet-images/ install -m 644 $RPM_BUILD_DIR/%{name}-%{release}/stylesheet-images/* \ $RPM_BUILD_ROOT/%{_datadir}/fedora/doc/docs-common/stylesheet-images/ @@ -50,6 +54,6 @@ %{_datadir}/fedora/doc/docs-common/common/* %{_datadir}/fedora/doc/docs-common/css/* %{_datadir}/fedora/doc/docs-common/stylesheet-images/* - +%{_sysconfdir}/xdg/menus/applications-merged/* %changelog Index: fedora-doc.desktop.in.common =================================================================== RCS file: /cvs/docs/docs-common/packaging/fedora-doc.desktop.in.common,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- fedora-doc.desktop.in.common 3 Oct 2005 02:38:12 -0000 1.2 +++ fedora-doc.desktop.in.common 12 Oct 2005 14:59:43 -0000 1.3 @@ -1,6 +1,6 @@ [Desktop Entry] Encoding=UTF-8 -Categories=Application;Documentation;X-Red-Hat-Base; +Categories=X-Fedora-Documentation; Name=@TITLE@ GenericName=@TITLE@ Exec=gnome-help file:///usr/share/fedora/doc/fedora-doc-@DOCBASE@/C/@DOCBASE@-en.xml

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits October 2005