From fedora-docs-commits at redhat.com Fri Jul 1 00:08:57 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Thu, 30 Jun 2005 20:08:57 -0400 Subject: jargon-buster fedora-jargon-buster-en.xml,1.8,1.9 Message-ID: <200507010008.j6108vY8027841@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/jargon-buster In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27824 Modified Files: fedora-jargon-buster-en.xml Log Message: Changed apt-get reference to authoritative source Index: fedora-jargon-buster-en.xml =================================================================== RCS file: /cvs/docs/jargon-buster/fedora-jargon-buster-en.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- fedora-jargon-buster-en.xml 30 Sep 2004 16:27:19 -0000 1.8 +++ fedora-jargon-buster-en.xml 1 Jul 2005 00:08:54 -0000 1.9 @@ -163,7 +163,7 @@ apt-get Refer to freshrpms.net. APT (Advanced + url="https://moin.conectiva.com.br/AptRpm">https://moin.conectiva.com.br/AptRpm. APT (Advanced Package Tool) is a dependency tool, well known to Debian users since it is used by default with their dpkg packages. But apt has been ported to work with RPM packages too, by Conectiva, who has now used From fedora-docs-commits at redhat.com Thu Jul 7 16:22:41 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Thu, 7 Jul 2005 12:22:41 -0400 Subject: docs-common/bin xmlformat-fdp.conf,1.1,1.2 Message-ID: <200507071622.j67GMf7u030416@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/bin In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30384/d/bin Modified Files: xmlformat-fdp.conf Log Message: Revise handling of <*name> and tagging Index: xmlformat-fdp.conf =================================================================== RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- xmlformat-fdp.conf 27 Jun 2005 19:49:21 -0000 1.1 +++ xmlformat-fdp.conf 7 Jul 2005 16:22:38 -0000 1.2 @@ -30,6 +30,7 @@ firstname surname othername entry-break = 0 exit-break = 0 + normalize = yes revnumber date authorinitials entry-break = 0 @@ -55,7 +56,7 @@ exit-break = 0 normalize = yes -emphasis literal +emphasis literal abbrev format = inline trademark From fedora-docs-commits at redhat.com Thu Jul 7 22:37:40 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Thu, 7 Jul 2005 18:37:40 -0400 Subject: desktop-up2date Makefile,1.3,1.4 Message-ID: <200507072237.j67MbeaX009140@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/desktop-up2date In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8993 Modified Files: Makefile Log Message: Updated Makefile Index: Makefile =================================================================== RCS file: /cvs/docs/desktop-up2date/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Makefile 29 Jun 2005 00:45:22 -0000 1.3 +++ Makefile 7 Jul 2005 22:37:38 -0000 1.4 @@ -1,33 +1,30 @@ ############################################################################### # Makefile for RHLP docs project # Created by: Tammy Fox -# Last edited by: Stuart Ellis +# Last edited by: Tommy Reynolds # WARNING: need passivetex 1.24 for pdf generation to work # License: GPL # Copyright 2003 Tammy Fox, Red Hat, Inc. +# Copyright 2005 Tommy Reynolds, MegaCoder.com ############################################################################### -XSLPDF = ../docs-common/xsl/main-pdf.xsl -XSLHTML = ../docs-common/xsl/main-html.xsl -LANG = en -DOCNAME = desktop-up2date-$(LANG) -XMLFILE = $(DOCNAME).xml +XSLPDF = ../docs-common/xsl/main-pdf.xsl +XSLHTML = ../docs-common/xsl/main-html.xsl +XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl +LANG = en +DOCNAME = desktop-up2date-$(LANG) +XMLFILE = $(DOCNAME).xml +XMLEXTRAFILES = ###################################################### - include ../docs-common/Makefile.common - -###################################################### -html: - @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE) - @mkdir -p $(DOCNAME)/stylesheet-images - @cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images - @cp ../docs-common/css/fedora.css $(DOCNAME) - - -pdf: - @xmlto pdf -x $(XSLPDF) $(XMLFILE) ###################################################### -clean: - @rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz +# If you want to add additional steps to any of the +# targets defined in "Makefile.common", be sure to use +# a double-colon in your rule here. For example, to +# print the message "FINISHED AT LAST" after building +# the HTML document version, uncomment the following +# line: +#${DOCNAME}/index.html:: +# echo FINISHED AT LAST From fedora-docs-commits at redhat.com Fri Jul 8 20:31:32 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 8 Jul 2005 16:31:32 -0400 Subject: xml-normalize desktop-up2date-en.xml,NONE,1.1 Message-ID: <200507082031.j68KVWC6009295@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/xml-normalize In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9275 Added Files: desktop-up2date-en.xml Log Message: Added as test --- NEW FILE desktop-up2date-en.xml --- %FEDORA-ENTITIES-EN; ]>
Updating Your Desktop with <application>up2date</application> 2005 Stuart Ellis Ellis Stuart 0.3 2005-06-05 StuartEllis Initial CVS commit. &LEGALNOTICE; &DRAFTNOTICE;
Audience This tutorial is intended for new users. It explains how to use the supplied graphical tools to keep a &FED; desktop system updated. Experienced users may still find this software useful, but are likely to use yum to both update their systems and install new software.
Introduction &FC; provides a pair of utilities that work together to enable desktop users to update their systems. The Alert Icon on your desktop keeps you informed about package updates. Until your system is updated this appears as a red circle with a flashing exclamation mark. The Alert Icon is integrated with up2date, which enables you to easily install updates for your system. In addition to these tools, &FC; also includes yum, a command-line utility that is the current recommmended option for software administration. The yum utility enables you to automatically locate, install and update any software with the latest version. Command-Line Version of <application>up2date</application> This tutorial does not document the command-line version of up2date, which provides some of the features of yum.
About Packages packages, defined All of the software and documentation prepared for use with &FED; is supplied in the form of files called RPM packages. Each package is a compressed archive containing product information, program files, icons, documentation and management scripts. Packages also include a digital signature to prove their source. These files are used by management applications to safely locate, install, update and remove software. For example, the &FED; installation process uses the packages supplied with &FC; to build or upgrade a system to your requirements. Verifying Packages The up2date application automatically downloads the &FP; public keys used to verify the digital signatures of updated packages.
About Channels channels, defined The up2date application uses repositories, specially prepared Web and FTP sites that hold software packages. Whatever their type, they are all described as channels within up2date. These repositories are also used by software management systems like yum to install and update software. If you configure yum to use additional repositories then you should add these to up2date as well.
Enabling and Disabling the <application>Alert Icon</application> Alert Icon, enabling To enable the Alert Icon, either double-click it, or right-click it and select Configuration. Click Forward to move to the Terms of Service. Click Forward once more to agree to the terms and move on to the Proxy Configuration. proxy server, with the Alert Icon To use a Web proxy server, enter the settings in the Proxy Configuration. Select the check-box next to Enable HTTP Proxy and enter the name of your proxy server. If your proxy server requires a username and password to access the Internet select the check-box next to Use Authentication and enter the relevant Username and Password. Click Forward a third time to complete the configuration. Select Apply to confirm the settings and immediately start an update.
Disabling the Update <application>Alert Icon</application> Alert Icon, disabling To disable the Alert Icon, follow these steps: Right-click it and select Configuration. Click Forward to move to the next screen. Click Remove From Panel . Re-enabling The <application>Alert Icon</application> You can re-enable the Alert Icon by selecting System ToolsRed Hat Network Alert Icon from the main menu.
Using the <application>Alert Icon</application> Alert Icon, using Once the Alert Icon is configured the rhnsd service on your system periodically checks for updates, and changes the icon to reflect the status of your system. The default period is every two hours. You may check for updates at any time by either double-clicking the icon, or by right-clicking it and selecting Check for updates. The icon displays the status of your system by showing one of four states: Grey with a check mark: the first check is in progress. Blue with a check mark: your system is up to date. Green with double arrows: currently checking for updates. Red with a flashing exclamation mark: there are newer packages available for the software installed on your system. Rest your mouse pointer over the icon to show the number of outstanding updates for your system. Only &FED; Updates are Shown The Alert Icon can only inform you of updates for the packages provided by the &FP;. To update all of the packages on your system, use yum.
Configuring <application>up2date</application> up2date, configuring If you select Check for updates you are shown a list of available updates, and can Launch Up2date by clicking the button. Alternatively, you can right-click the Alert Icon and select Launch Up2date. You are prompted for the root password before the application continues. proxy server, with up2date The configuration screen is displayed the first time that you run up2date. This has the same proxy server options as the Alert Icon. If you use a proxy server you should enter the same settings again. By default up2date has two safety restrictions that you may wish to remove. The first is that it will not update any package where the configuration files have been modified. To remove this safety restriction, click on the Retrieval/Installation tab and clear the check-box for Do not upgrade packages where the local configuration file has been modified. The other safety measure is that it will not automatically update the kernel on your system. Click on the Package exceptions tab, select kernel* and then click Remove to enable kernel updates. Click OK when you have finished configuring up2date. If this is the first time that you have run up2date the &FED; public key is downloaded. Click Yes .
Updating Your System with <application>up2date</application> up2date, using However you launched up2date, you begin with the Welcome to Red Hat Update Agent screen. Click Forward to move to the Channels screen. You may choose not to check a channel for updates by clearing the check-box next to the channel name. Click Forward to continue, or Cancel to abort. If you continue all of the chosen channels are checked for updates to the packages installed on your system, and a list of packages is displayed. Click the check-box next to the name of the package to select it for updating. To select all of the packages on the list, click Select all packages. Click Forward to begin the update process. This may take some time as the new packages are downloaded. The Retrieving Packages screen displays the progress of the downloads. Once the downloads have completed, click Forward . Your updates are then installed in the correct sequence, replacing older versions of the same packages. Click Forward to move on to the Finish Page. This lists all of the updates that have been installed.
Managing <application>up2date</application> Channels You may add or remove channels from up2date by editing /etc/sysconfig/rhn/sources. Each channel is defined by a line in this file. The &FP; repositories are already listed, with standard repositories enabled, and the package repositories for test versions of packages disabled. Software Repository Types Any software repository that supports apt or yum can be used as an up2date channel.
Enabling and Disabling Channels channels, enabling channels, disabling Channels are disabled by placing a comment marker at the beginning of the line. To re-enable a channel, remove the # character at the beginning of the line.
Adding and Removing Channels channels, adding channels, removing To add a new channel, add a new line to /etc/sysconfig/rhn/sources. You must specify three settings for each channel. The type should be yum unless the provider is using an alternate system. The channel-label is the name that the channel will be known by. The url is the full URL to the directory holding the RPM packages. This is an example channel listing, for a repository hosted on the server fedora.multikabel.nl: Format of <application>up2date</application> Channels The &FC; channels use yum-mirror, rather than yum. This means that up2date automatically fetches a list of servers from the file specified by the url, and then randomly select a download server from the list. Another server is automatically chosen if the selected server fail to respond. Repositories for <command>apt</command> Some third-party package providers use apt, rather than yum. Many support both types to ensure compatibility. If the provider requires apt, then substitute apt for yum in your channel definition. To remove a channel, delete the relevant line from /etc/sysconfig/rhn/sources. Managing Public Keys Remember to add or remove the public key for the package provider from your software management system when adding or removing channels for third-party packages.
From fedora-docs-commits at redhat.com Fri Jul 8 20:38:38 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 8 Jul 2005 16:38:38 -0400 Subject: xml-normalize desktop-up2date-en.xml,1.1,1.2 Message-ID: <200507082038.j68Kcc7m009330@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/xml-normalize In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9308 Modified Files: desktop-up2date-en.xml Log Message: Test commit 2. From fedora-docs-commits at redhat.com Fri Jul 8 20:45:51 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 8 Jul 2005 16:45:51 -0400 Subject: xml-normalize desktop-up2date-en.xml,1.2,1.3 Message-ID: <200507082045.j68KjpVr009401@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/xml-normalize In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9380 Modified Files: desktop-up2date-en.xml Log Message: Test commit 3. From fedora-docs-commits at redhat.com Fri Jul 8 20:53:14 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Fri, 8 Jul 2005 16:53:14 -0400 Subject: xml-normalize desktop-up2date-en.xml,1.3,1.4 Message-ID: <200507082053.j68KrEXw009433@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/xml-normalize In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9412 Modified Files: desktop-up2date-en.xml Log Message: Test From fedora-docs-commits at redhat.com Sat Jul 9 15:07:09 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Sat, 9 Jul 2005 11:07:09 -0400 Subject: yum-software-management Makefile, 1.3, 1.4 yum-software-management-en.xml, 1.5, 1.6 Message-ID: <200507091507.j69F7RgG003258@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3215 Modified Files: Makefile yum-software-management-en.xml Log Message: - Update Makefile to use Makefile.common - Amended to cover auto GPG key import - Added section on localinstall Index: Makefile =================================================================== RCS file: /cvs/docs/yum-software-management/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Makefile 29 Jun 2005 00:41:23 -0000 1.3 +++ Makefile 9 Jul 2005 15:06:36 -0000 1.4 @@ -1,30 +1,30 @@ ############################################################################### # Makefile for RHLP docs project # Created by: Tammy Fox -# Last edited by: Stuart Ellis +# Last edited by: Tommy Reynolds # WARNING: need passivetex 1.24 for pdf generation to work # License: GPL # Copyright 2003 Tammy Fox, Red Hat, Inc. +# Copyright 2005 Tommy Reynolds, MegaCoder.com ############################################################################### -XSLPDF = ../docs-common/xsl/main-pdf.xsl -XSLHTML = ../docs-common/xsl/main-html.xsl -LANG = en -DOCNAME = yum-software-management-$(LANG) -XMLFILE = $(DOCNAME).xml +XSLPDF = ../docs-common/xsl/main-pdf.xsl +XSLHTML = ../docs-common/xsl/main-html.xsl +XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl +LANG = en +DOCNAME = yum-software-management-$(LANG) +XMLFILE = $(DOCNAME).xml +XMLEXTRAFILES = + ###################################################### include ../docs-common/Makefile.common ###################################################### -html: - @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE) - @mkdir -p $(DOCNAME)/stylesheet-images - @cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images - @cp ../docs-common/css/fedora.css $(DOCNAME) - - -pdf: - @xmlto pdf -x $(XSLPDF) $(XMLFILE) -###################################################### -clean: - @rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz +# If you want to add additional steps to any of the +# targets defined in "Makefile.common", be sure to use +# a double-colon in your rule here. For example, to +# print the message "FINISHED AT LAST" after building +# the HTML document version, uncomment the following +# line: +#${DOCNAME}/index.html:: +# echo FINISHED AT LAST View full diff with command: /usr/bin/cvs -f diff -kk -u -N -r 1.5 -r 1.6 yum-software-management-en.xml Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- yum-software-management-en.xml 22 Jun 2005 00:07:32 -0000 1.5 +++ yum-software-management-en.xml 9 Jul 2005 15:06:36 -0000 1.6 @@ -4,1139 +4,1318 @@ %FEDORA-ENTITIES-EN; - + - + ]> -
- - Software Management with <command>yum</command> - - 2005 - Stuart Ellis - - - - Ellis - Stuart - - +
+ + Software Management with <command>yum</command> + + 2005 + Stuart Ellis + + + + Ellis + Stuart + + &LEGALNOTICE; - 0.4 - 2005-06-01 - StuartEllis - - - Initial import into CVS. + 0.4 + 2005-06-01 + StuartEllis + + + Initial import into CVS. - - + + - - +
- Introduction - + Introduction &DRAFTNOTICE; +
+ Audience -
- Audience - - The yum utility is currently the recommended method for - managing software on &FED; systems. All &FED; users responsible for - maintaining their own systems will find yum an essential tool. - -
- -
- Using This Document - - This document is a reference for using yum. You may - wish to read some or all of the sections, depending upon your needs and - level of experience. - - - If you are a new user, read the before using - yum for the first time. - - - Experienced Linux users should start with . - - - Anyone with several &FED; systems on a network may benefit from setting - up their own software repositories to manage the process of installation and - updates. The details of maintaining your own repositories are explained - in . - - - Most of the examples use the package tsclient, - which is included with &FC; to provide an application for remote desktop - access. If it is installed successfully you may start the application - by choosing - ApplicationsInternetTerminal - Server Client. To use the examples, - substitute the name of the relevant package for tsclient. - - - Avoid Logging in with the Root Account - - You do not need to log in with the root account in order to manage your - &FC; system. All of the commands shown in this tutorial that require - root access will prompt you for the root password. The example - terminal commands use su to - provide this facility. - - -
+ + The yum utility is currently the recommended + method for managing software on &FED; systems. All &FED; users + responsible for maintaining their own systems will find + yum an essential tool. + +
+
+ Using This Document -
- Additional Resources - - yum, documentation - - - yum, man pages - - - The yum utility has features and options that - are not discussed in this document. Read the man pages - for yum(8) and yum.conf(5) to - learn more. - - - yum, Websites - - - The official Website for yum is: - - - http://linux.duke.edu/projects/yum/ - - - Yum, mailing lists - - - The official mailing list for yum users is: - - - https://lists.dulug.duke.edu/mailman/listinfo/yum - - - The archive for the yum development mailing list is here: - - - https://lists.dulug.duke.edu/pipermail/yum-devel/ - + + This document is a reference for using yum. + You may wish to read some or all of the sections, depending upon + your needs and level of experience. + + + + If you are a new user, read the + before + using yum for the first time. + + + + Experienced Linux users should start with + . + [...2082 lines suppressed...]
- Updating a Repository - - repositories, updating - - - Whenever a package is added, or replaced with a different version, you - must run createrepo again for the index files to be updated. - If you are mirroring an existing repository then you may assume that - the site administrator updates the indexes, but for safety you should - add this to your synchronization scripts. The - createrepo utility can be run as frequently as you wish. + Updating a Repository + + repositories, updating + + + Whenever a package is added, or replaced with a different + version, you must run createrepo again for + the index files to be updated. If you are mirroring an existing + repository then you may assume that the site administrator + updates the indexes, but for safety you should add this to your + synchronization scripts. The createrepo + utility can be run as frequently as you wish. -
- +
- -
- Using <command>yum</command> with a Proxy Server - +
+ Using <command>yum</command> with a Proxy Server + proxy server, with yum - - + + yum, using a proxy server - - - Repositories may be accessed through standard proxy servers. If your - system is connected to the Internet through a Web proxy server, specify - the details of the server in /etc/yum.conf. The - proxy setting must specify the proxy server as a - complete URL, including the TCP port number. If your proxy server - requires a username and password, specify these by adding - proxy_username and proxy_password settings. - - - - For example, the settings below enable yum to use the - proxy server mycache.mydomain.com, connecting to port - 3128, with the username yum-user and the password qwerty. - + + + Repositories may be accessed through standard proxy servers. If + your system is connected to the Internet through a Web proxy + server, specify the details of the server in + /etc/yum.conf. The proxy + setting must specify the proxy server as a complete URL, including + the TCP port number. If your proxy server requires a username and + password, specify these by adding + proxy_username and + proxy_password settings. + + + + For example, the settings below enable yum to + use the proxy server mycache.mydomain.com, + connecting to port 3128, with the username + yum-user and the password + qwerty. + - + Configuration File Settings for Using A Proxy Server - + - + - + Global Settings + - Defining a proxy server in /etc/yum.conf means that - all users connect to the proxy server with those - details when using yum. - - - - - To enable proxy access for a specific user, add the lines in the - example box below to their shell profile. For the default - bash shell, the profile is the file - .bash_profile. The settings below enable yum to - use the proxy server mycache.mydomain.com, connecting to port 3128. - - + Defining a proxy server in /etc/yum.conf + means that all users connect to the proxy + server with those details when using yum. + + + + + To enable proxy access for a specific user, add the lines in the + example box below to their shell profile. For the default + bash shell, the profile is the file + .bash_profile. The settings below enable + yum to use the proxy server + mycache.mydomain.com, connecting to port + 3128. + + + Profile Settings for Using a Proxy Server - + - + + + + If the proxy server requires a username and password then add + these to the URL. For example, to include the username + yum-user and the password + qwerty: + - - If the proxy server requires a username and password then add these to the - URL. For example, to include the username - yum-user and the password qwerty: - - + Profile Settings for a Secured Proxy Server - + - - - <command>http_proxy</command> Variable with Other Utilities - - The http_proxy variable is also used by curl and - other utilities. Although yum itself may use http_proxy in - either upper-case or lower-case, curl requires - the name of the variable to be in lower-case. - - + -
+ + <command>http_proxy</command> Variable with Other Utilities + + The http_proxy variable is also used by + curl and other utilities. Although + yum itself may use + http_proxy in either upper-case or + lower-case, curl requires the name of the + variable to be in lower-case. + + +
- +
- - From fedora-docs-commits at redhat.com Mon Jul 11 19:26:00 2005 From: fedora-docs-commits at redhat.com (Elliot Lee (sopwith)) Date: Mon, 11 Jul 2005 15:26:00 -0400 Subject: owners - Imported sources Message-ID: <200507111926.j6BJQ0cJ010329@cvs-int.fedora.redhat.com> Author: sopwith Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10315 Log Message: Initial import Status: Vendor Tag: FEDORA Release Tags: V0_0 N owners/owners.list No conflicts created by this import From fedora-docs-commits at redhat.com Mon Jul 11 19:34:28 2005 From: fedora-docs-commits at redhat.com (Elliot Lee (sopwith)) Date: Mon, 11 Jul 2005 15:34:28 -0400 Subject: owners owners.list,1.1.1.1,1.2 Message-ID: <200507111934.j6BJYSmp010382@cvs-int.fedora.redhat.com> Author: sopwith Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10365 Modified Files: owners.list Log Message: fix Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -u -r1.1.1.1 -r1.2 --- owners.list 11 Jul 2005 19:25:58 -0000 1.1.1.1 +++ owners.list 11 Jul 2005 19:34:25 -0000 1.2 @@ -1,5 +1,5 @@ # Format: -# product|component|initialowner|initialqacontact|initialcclist +# product|component|description|initialowner|initialqacontact|initialcclist # # If you don't know what product & component are, ask someone who knows bugzilla :) # initialowner is the initial owner of bugs on this component @@ -7,4 +7,3 @@ # initialcclist is the list of people initially CC'd for bugs on this component # # All e-mail addresses used here MUST correspond to existing bugzilla accounts! - From fedora-docs-commits at redhat.com Tue Jul 12 00:11:37 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Mon, 11 Jul 2005 20:11:37 -0400 Subject: desktop-up2date desktop-up2date-en.xml,1.4,1.5 Message-ID: <200507120011.j6C0BbLM017305@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/desktop-up2date In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17286 Modified Files: desktop-up2date-en.xml Log Message: Minor edits. Index: desktop-up2date-en.xml =================================================================== RCS file: /cvs/docs/desktop-up2date/desktop-up2date-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- desktop-up2date-en.xml 14 Jun 2005 22:30:42 -0000 1.4 +++ desktop-up2date-en.xml 12 Jul 2005 00:11:33 -0000 1.5 @@ -4,13 +4,13 @@ %FEDORA-ENTITIES-EN; - + - + ]> @@ -24,20 +24,30 @@ - Ellis - Stuart + Ellis + Stuart - 0.3 - 2005-06-05 - StuartEllis - - + 0.3 + 2005-06-05 + StuartEllis + + Initial CVS commit. - + + + + 0.4 + 2005-07-10 + StuartEllis + + + Minor revisions. + + &LEGALNOTICE; @@ -47,385 +57,468 @@
Audience + - This tutorial is intended for new users. It explains how to use the - supplied graphical tools to keep a &FED; desktop system updated. - Experienced users may still find this software useful, but are likely to use yum to both update their systems and install new software. + This tutorial is intended for new users. It explains how to use + the supplied graphical tools to keep a &FED; desktop system + updated. Experienced users may still find this software useful, + but are likely to use yum to both update their + systems and install new software. -
+ - -
+
Introduction - - &FC; provides a pair of utilities that work together to enable desktop - users to update their systems. The Alert - Icon on your desktop keeps you informed about package updates. Until - your system is updated this appears as a red circle with a flashing - exclamation mark. The Alert Icon is integrated with - up2date, which enables you to easily install - updates for your system. - - - In addition to these tools, &FC; also includes yum, a - command-line utility that is the current recommmended option for software - administration. The yum utility enables you to - automatically locate, install and update any software with the latest version. - - - Command-Line Version of <application>up2date</application> - - This tutorial does not document the command-line version of - up2date, which provides some of the features of yum. - - - - -
- About Packages - - packages, defined - - - All of the software and documentation prepared for use with &FED; is - supplied in the form of files called RPM packages. - Each package is a compressed archive containing product - information, program files, icons, documentation and management - scripts. Packages also include a digital signature to prove - their source. These files are used by management applications to - safely locate, install, update and remove software. For - example, the &FED; installation process uses the packages - supplied with &FC; to build or upgrade a system to your requirements. + + + &FC; provides a pair of utilities that work together to enable + desktop users to update their systems. The Alert + Icon on your desktop keeps you informed about + package updates. Until your system is updated this appears as a + red circle with a flashing exclamation mark. The + Alert Icon is integrated with + up2date, which enables you to easily + install updates for your system. + + + + In addition to these tools, &FC; also includes + yum, a command-line utility that is the current + recommended option for software administration. The + yum utility enables you to automatically + locate, install and update any software with the latest version. + + + Command-Line Version of <application>up2date</application> + + + This tutorial does not document the command-line version of + up2date, which provides some of the features + of yum. + + + +
+ About Packages + + packages, defined + + + All of the software and documentation prepared for use with + &FED; is supplied in the form of files called RPM + packages. Each package is a compressed + archive containing product information, program files, icons, + documentation and management scripts. Packages also include a + digital signature to prove their source. These files are used by + management applications to safely locate, install, update and + remove software. For example, the &FED; installation process + uses the packages supplied with &FC; to build or upgrade a + system to your requirements. + + - Verifying Packages + Verifying Packages + - The up2date application automatically - downloads the &FP; public keys used to verify the digital - signatures of updated packages. - + The up2date application + automatically downloads the &FP; public keys used to verify + the digital signatures of updated packages. + -
- +
-
- About Channels - - channels, defined - - - The up2date application uses - repositories, specially prepared Web and FTP sites - that hold software packages. Whatever their type, they are all described - as channels within up2date. - - - These repositories are also used by software management systems like - yum to install and update software. If you configure - yum to use additional repositories then you should add - these to up2date as well. - -
-
+
+ About Channels + + channels, defined + + + The up2date application uses + repositories, specially prepared Web and + FTP sites that hold software packages. Whatever their type, they + are all described as channels within + up2date. + + + These repositories are also used by software management systems + like yum to install and update software. If + you configure yum to use additional + repositories then you should add these to + up2date as well. + +
+
-
+
Enabling and Disabling the <application>Alert Icon</application> - Alert Icon, enabling + Alert Icon, enabling - To enable the Alert Icon, either double-click it, or right-click it and - select Configuration. Click - Forward to move to the Terms of - Service. Click Forward once more to agree to the terms and move - on to the Proxy Configuration. + To enable the Alert Icon, either + double-click it, or right-click it and select + Configuration. Click + Forward + to move to the Terms of Service. Click + Forward + once more to agree to the terms and move on to the Proxy + Configuration. - proxy server, with the Alert Icon + proxy server, with the Alert Icon + - To use a Web proxy server, enter the settings in the Proxy Configuration. Select the check-box next to Enable HTTP - Proxy and enter the name of your proxy server. If your - proxy server requires a username and password to access the Internet select the check-box next to Use - Authentication and enter the relevant - Username and Password. - - - Click Forward a third time to complete the - configuration. Select Apply to confirm the settings - and immediately start an update. + To use a Web proxy server, enter the settings in the + Proxy Configuration. Select the check-box + next to Enable HTTP Proxy and enter the name + of your proxy server. If your proxy server requires a username and + password to access the Internet select the check-box next to + Use Authentication and enter the relevant + Username and Password. -
- Disabling the Update <application>Alert Icon</application> + + + Click + Forward + a third time to complete the configuration. Select + Apply + to confirm the settings and immediately start an update. + + +
+ Disabling the Update <application>Alert Icon</application> + + Alert Icon, disabling + + + To disable the Alert Icon, follow + these steps: + + + + Right-click it and select + Configuration. + + + + + Click + Forward + to move to the next screen. + + + + + Click + Remove From Panel + . + + + + + + Re-enabling The <application>Alert Icon</application> + + You can re-enable the Alert Icon by + selecting System + ToolsRed Hat Network Alert + Icon from the main menu. + + +
+
+ +
+ Using the <application>Alert Icon</application> - Alert Icon, disabling + Alert Icon, using - - To disable the Alert Icon, follow these steps: - + + Once the Alert Icon is configured the + rhnsd service on your system periodically + checks for updates, and changes the icon to reflect the status of + your system. The default period is every two hours. You may check + for updates at any time by either double-clicking the icon, or by + right-clicking it and selecting Check for + updates. + + + + The icon displays the status of your system by showing one of six + states: + - Right-click it and select Configuration. - + + Grey with a check mark: the first check is in progress. + - Click Forward to move to the next screen. - + + Blue with a check mark: your system is up to date. + - Click Remove From Panel. - - - - - - - Re-enabling The <application>Alert Icon</application> - - You can re-enable the Alert Icon by selecting - System ToolsRed Hat - Network Alert Icon from the main menu. + + Green with double arrows: currently checking for updates. - - -
- -
- - -
- Using the <application>Alert Icon</application> - - Alert Icon, using - - - Once the Alert Icon is configured the rhnsd service - on your system periodically checks for updates, and changes the icon to - reflect the status of your system. The default period is every two - hours. You may check for updates at any time by either double-clicking - the icon, or by right-clicking it and selecting Check for - updates. - - - The icon displays the status of your system by showing one of four states: - - - Grey with a check mark: the first check is in progress. - - - - Blue with a check mark: your system is up to date. + + + + Red with a flashing exclamation mark: there are newer + packages available for the software installed on your + system. - - - Green with double arrows: currently checking for updates. + + + + Grey with a question mark: + up2date is not able to obtain + update information from the server. - - - Red with a flashing exclamation mark: there are newer - packages available for the software installed on your system. + + + + Grey with double arrows, struck-through with a red line: No + network connection to the server. - - - + + + - - Rest your mouse pointer over the icon to show the number of outstanding updates for your system. - + + Rest your mouse pointer over the icon to show the number of + outstanding updates for your system. + - + Only &FED; Updates are Shown - The Alert Icon can only inform you of updates for the packages - provided by the &FP;. To update all of the packages on your system, use - yum. - - - -
+ + The Alert Icon can only inform you of + updates for the packages provided by the &FP;. To update all of + the packages on your system, use yum. + + +
-
- Configuring <application>up2date</application> - +
+ Configuring <application>up2date</application> + up2date, configuring - - - If you select Check for updates you are shown a list of - available updates, and can Launch Up2date by - clicking the button. Alternatively, you can right-click the Alert Icon - and select Launch Up2date. You are prompted for - the root password before the application continues. - - + + + If you select Check for updates you are shown + a list of available updates, and can + Launch Up2date + by clicking the button. Alternatively, you can right-click the + Alert Icon and select Launch + Up2date. You are prompted for the + root password before the + application continues. + + proxy server, with up2date - - - The configuration screen is displayed the first time that you run - up2date. This has the same proxy server - options as the Alert Icon. If you use a proxy server you should enter - the same settings again. - - - By default up2date has two safety restrictions that - you may wish to remove. The first is that it will not update any - package where the configuration files have been modified. To remove - this safety restriction, click on the - Retrieval/Installation tab and clear the check-box - for Do not upgrade packages where the local configuration file - has been modified. The other safety measure is that it will - not automatically update the kernel on your system. Click on the - Package exceptions tab, select - kernel* and then click - Remove to enable kernel updates. - - - Click OK when you have finished configuring - up2date. + + + The configuration screen is displayed the first time that you run + up2date. This has the same proxy server + options as the Alert Icon. If you use a + proxy server you should enter the same settings again. + + + + By default up2date has two safety + restrictions that you may wish to remove. The first is that it + will not update any package where the configuration files have + been modified. To remove this safety restriction, click on the + Retrieval/Installation tab and clear the + check-box for Do not upgrade packages where the local + configuration file has been modified. The other safety + measure is that it will not automatically update the kernel on + your system. Click on the Package exceptions + tab, select kernel* and then click + Remove + to enable kernel updates. + - If this is the first time that you have run - up2date the &FED; public key is downloaded. Click Yes. + Click + OK + when you have finished configuring + up2date. -
+ + If this is the first time that you have run + up2date the &FED; public key is + downloaded. Click + Yes + . + +
-
+
Updating Your System with <application>up2date</application> - up2date, using + up2date, using - However you launched up2date, you begin - with the Welcome to Red Hat Update Agent screen. Click - Forward to move to the - Channels screen. You may choose not to check a - channel for updates by clearing the check-box next to the channel name. + However you launched up2date, you begin + with the Welcome to Red Hat Update Agent + screen. Click + Forward + to move to the Channels screen. You may + choose not to check a channel for updates by clearing the + check-box next to the channel name. + - Click Forward to continue, or - Cancel to abort. If you continue all of the chosen - channels are checked for updates to the packages installed on your - system, and a list of packages is displayed. + Click + Forward + to continue, or + Cancel + to abort. If you continue all of the chosen channels are checked + for updates to the packages installed on your system, and a list + of packages is displayed. + - Click the check-box next to the name of the package to select it for - updating. To select all of the packages on the list, click Select all packages. + Click the check-box next to the name of the package to select it + for updating. To select all of the packages on the list, click + Select all packages. + - Click Forward to begin the update process. This - may take some time as the new packages are downloaded. The Retrieving - Packages screen displays the progress of the downloads. + Click + Forward + to begin the update process. This may take some time as the new + packages are downloaded. The Retrieving + Packages screen displays the progress of the downloads. + - Once the downloads have completed, click Forward. Your - updates are then installed in the correct sequence, replacing older - versions of the same packages. + Once the downloads have completed, click + Forward + . Your updates are then installed in the correct sequence, + replacing older versions of the same packages. + - Click Forward to move on to the Finish - Page. This lists all of the updates that have been installed. + Click + Forward + to move on to the Finish Page. This lists all + of the updates that have been installed. -
- +
-
+
Managing <application>up2date</application> Channels + - You may add or remove channels from up2date by editing - /etc/sysconfig/rhn/sources. Each channel is - defined by a line in this file. The &FP; repositories are already - listed, with standard repositories enabled, and the package repositories - for test versions of packages disabled. - - + You may add or remove channels from + up2date by editing + /etc/sysconfig/rhn/sources. Each channel is + defined by a line in this file. The &FP; repositories are already + listed, with standard repositories enabled, and the package + repositories for test versions of packages disabled. + + Software Repository Types - - Any software repository that supports apt or - yum can be used as an - up2date channel. - - - - + + Any software repository that supports apt or + yum can be used as an + up2date channel. + +
- Enabling and Disabling Channels - - channels, enabling - - - channels, disabling - - - Channels are disabled by placing a comment marker at the beginning of - the line. To re-enable a channel, remove the # character at the - beginning of the line. - + Enabling and Disabling Channels + + channels, enabling + + + channels, disabling + + + Channels are disabled by placing a comment marker at the + beginning of the line. To re-enable a channel, remove the # + character at the beginning of the line. +
-
- Adding and Removing Channels - - channels, adding - - - channels, removing - - - To add a new channel, add a new line to /etc/sysconfig/rhn/sources. - - - You must specify three settings for each channel. The type - should be yum unless the provider is using an - alternate system. The channel-label is the name - that the channel will be known by. The url is the - full URL to the directory holding the RPM packages. - - - This is an example channel listing, for a repository hosted on the - server fedora.multikabel.nl: - - - Format of <application>up2date</application> Channels - + Adding and Removing Channels + + channels, adding + + + channels, removing + + + To add a new channel, add a new line to + /etc/sysconfig/rhn/sources. + + + + You must specify three settings for each channel. The + type should be yum unless + the provider is using an alternate system. The + channel-label is the name that the channel + will be known by. The url is the full URL to + the directory holding the RPM packages. + + + + This is an example channel listing, for a repository hosted on + the server fedora.multikabel.nl: + + + + Format of <application>up2date</application> Channels + - - - The &FC; channels use yum-mirror, rather than - yum. This means that - up2date automatically fetches a list of - servers from the file specified by the url, and - then randomly select a download server from the list. Another server - is automatically chosen if the selected server fail to respond. - - - Repositories for <command>apt</command> - Some third-party package providers use apt, rather than - yum. Many support both types to ensure - compatibility. If the provider requires apt, - then substitute apt for yum in - your channel definition. - - - - To remove a channel, delete the relevant line from /etc/sysconfig/rhn/sources. - + + + + The &FC; channels use yum-mirror, rather than + yum. This means that + up2date automatically fetches a list + of servers from the file specified by the + url, and then randomly select a download + server from the list. Another server is automatically chosen if + the selected server fail to respond. + + + Repositories for <command>apt</command> + + Some third-party package providers use apt, + rather than yum. Many support both types to + ensure compatibility. If the provider requires + apt, then substitute apt + for yum in your channel definition. + + + + To remove a channel, delete the relevant line from + /etc/sysconfig/rhn/sources. + + - Managing Public Keys + Managing Public Keys + - Remember to add or remove the public key for the package provider - from your software management system when adding or removing channels - for third-party packages. - + Remember to add or remove the public key for the package + provider from your software management system when adding or + removing channels for third-party packages. + -
+
-
- - - +
From fedora-docs-commits at redhat.com Tue Jul 12 07:26:50 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 12 Jul 2005 03:26:50 -0400 Subject: owners owners.list,1.2,1.3 Message-ID: <200507120726.j6C7QofS026212@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26195 Modified Files: owners.list Log Message: First stab at defining components for bugzilla, this includes multiple editor assignments. In some cases, these are logical and shall continue, in others, they are placeholders. This happened with a few of the writer/initialowner groupings, holes needed to be filled. Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- owners.list 11 Jul 2005 19:34:25 -0000 1.2 +++ owners.list 12 Jul 2005 07:26:47 -0000 1.3 @@ -7,3 +7,43 @@ # initialcclist is the list of people initially CC'd for bugs on this component # # All e-mail addresses used here MUST correspond to existing bugzilla accounts! + +# Initial edit 11-JUL-2005 by kwade at redhat.com +# +# Roles in FDP +# initialowner = document author and/or document manager +# intialqacontact = document editor and/or document manager +# intialcclist = document manager,others +# +# Some relevant bugzilla accounts: +# kwade at redhat.com +# stickster at gmail.com +# Tommy.Reynolds at MegaCoder.com +# mjohnson at redhat.com +# tfox at redhat.com +# ghenry at suretecsystems.com +# fdr at eln.fastmail.fm +# relnotes at fedoraproject.org +# sarahs at redhat.com + +Fedora Documentation|desktop-up2date|Keeping a desktop up-to-date using graphical tools.|fdr at eln.fastmail.fm|mjohnson at redhat.com|kwade at redhat.com +Fedora Documentation|developer-guide|Striving to be the canonical Fedora development reference.|tfox at redhat.com|Tommy.Reynolds at MegaCoder.com|kwade at redhat.com +Fedora Documentation|documentation-guide|The Guide is the canonical set of guidelines and howtos for FDP contributors.|stickster at redhat.com|tfox at redhat.com|kwade at redhat.com +Fedora Documentation|docs-common|Common files and tools for documentation contributors.|kwade at redhat.com|Tommy.Reynolds at MegaCoder.com|stickster at gmail.com,mjohnson at redhat.com +Fedora Documentation|example-tutorial|The canonical reference document for how to use XML/DocBook for the FDP.|Tommy.Reynolds at MegaCoder.com|tfox at redhat.com| +Fedora Documentation|install-guide|Installation guide for Fedora Core.|fdr at eln.fastmail.fm|stickster at gmail.com| +Fedora Documentation|hardening|System hardening for Fedora Core 3.|tuckser at gmail.com|kwade at redhat.com| +Fedora Documentation|jargon-buster|Striving to be the canonical glossary for all things Fedora.|tfox at redhat.com|stickster at redhat.com| +Fedora Documentation|mirror-tutorial|Mirroring and update services for Fedora Core.|stickster at gmail.com|kwade at redhat.com| +Fedora Documentation|proxy-guide|Building and maintaining a secure proxy server.|stickster at redhat.com|ghenry at suretecsystems.com| +Fedora Documentation|release-notes|Fedora Core release notes, bugs, and requests.|relnotes at fedoraproject.org|kwade at redhat.com| +Fedora Documentation|selinux-apache|Using SELinux and Apache HTTP Server in Fedora Core.|walters at redhat.com|kwade at redhat.com| +Fedora Documentation|selinux-faq|FAQs about SELinux in Fedora Core.|kwade at redhat.com|kwade at redhat.com| +Fedora Documentation|sudo-tutorial|Short tutorial on using sudo.|Tommy.Reynolds at MegaCoder.com|stickster at redhat.com| +Fedora Documentation|toolchain-devel|For bugs and requests of the documentation tools.|kwade at redhat.com|mjohnson at redhat.com|Tommy.Reynolds at MegaCoder.com +Fedora Documentation|translation-guide|The canonical reference for translating all aspects of the Fedora Project.|sarahs at redhat.com|tfox at redhat.com|kwade at redhat.com +Fedora Documentation|translation-guide-windows|Tutorial for translators working in a Microsoft Windows environment.|sarahs at redhat.com|tfox at redhat.com| +Fedora Documentation|updates|Tutorial for keeping a system up-to-date.|tfox at redhat.com|kwade at redhat.com| +Fedora Documentation|usb-hotplug|Using USB and hotplug.|stickster at gmail.com|fdr at eln.fastmail.fm| +Fedora Documentation|xml-normalize|Development of XML normalization tools.|Tommy.Reynolds at MegaCoder.com|stickster at gmail.com| +Fedora Documentation|yum-software-management|Managing systems with yum.|stickster at gmail.com|fdr at eln.fastmail.fm| From fedora-docs-commits at redhat.com Tue Jul 12 15:28:39 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Tue, 12 Jul 2005 11:28:39 -0400 Subject: docs-common Makefile.common,1.6,1.7 Message-ID: <200507121528.j6CFSdxt003978@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/docs-common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3961 Modified Files: Makefile.common Log Message: Added "make view" target to display the HTML-formatted document using the htmlview(1) tool's default viewier. Index: Makefile.common =================================================================== RCS file: /cvs/docs/docs-common/Makefile.common,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- Makefile.common 29 Jun 2005 14:41:37 -0000 1.6 +++ Makefile.common 12 Jul 2005 15:28:36 -0000 1.7 @@ -53,6 +53,15 @@ cp ../docs-common/stylesheet-images/*.png stylesheet-images cp ../docs-common/css/fedora.css . +# The "view" target ensures that the HTML version of the document is built +# then displays it using the "htmlview" tool to start up the browser. It +# assumes that the current working directory is immediately above the HTML +# document directory. (We could change this if we wanted to futz around +# with making up an absolute pathname, but why bother.) + +view:: ${DOCNAME}/index.html + /usr/bin/htmlview file://localhost/${PWD}/${DOCNAME}/index.html + # The "clean" or "distclean" target will remove all generated and temporary # files. From fedora-docs-commits at redhat.com Tue Jul 12 20:20:31 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 12 Jul 2005 16:20:31 -0400 Subject: owners owners.list,1.3,1.4 Message-ID: <200507122020.j6CKKVIF012812@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12795 Modified Files: owners.list Log Message: It was late, what can I say? Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- owners.list 12 Jul 2005 07:26:47 -0000 1.3 +++ owners.list 12 Jul 2005 20:20:28 -0000 1.4 @@ -28,18 +28,18 @@ Fedora Documentation|desktop-up2date|Keeping a desktop up-to-date using graphical tools.|fdr at eln.fastmail.fm|mjohnson at redhat.com|kwade at redhat.com Fedora Documentation|developer-guide|Striving to be the canonical Fedora development reference.|tfox at redhat.com|Tommy.Reynolds at MegaCoder.com|kwade at redhat.com -Fedora Documentation|documentation-guide|The Guide is the canonical set of guidelines and howtos for FDP contributors.|stickster at redhat.com|tfox at redhat.com|kwade at redhat.com +Fedora Documentation|documentation-guide|The Guide is the canonical set of guidelines and howtos for FDP contributors.|stickster at gmail.com|tfox at redhat.com|kwade at redhat.com Fedora Documentation|docs-common|Common files and tools for documentation contributors.|kwade at redhat.com|Tommy.Reynolds at MegaCoder.com|stickster at gmail.com,mjohnson at redhat.com Fedora Documentation|example-tutorial|The canonical reference document for how to use XML/DocBook for the FDP.|Tommy.Reynolds at MegaCoder.com|tfox at redhat.com| Fedora Documentation|install-guide|Installation guide for Fedora Core.|fdr at eln.fastmail.fm|stickster at gmail.com| Fedora Documentation|hardening|System hardening for Fedora Core 3.|tuckser at gmail.com|kwade at redhat.com| -Fedora Documentation|jargon-buster|Striving to be the canonical glossary for all things Fedora.|tfox at redhat.com|stickster at redhat.com| +Fedora Documentation|jargon-buster|Striving to be the canonical glossary for all things Fedora.|tfox at redhat.com|stickster at gmail.com| Fedora Documentation|mirror-tutorial|Mirroring and update services for Fedora Core.|stickster at gmail.com|kwade at redhat.com| -Fedora Documentation|proxy-guide|Building and maintaining a secure proxy server.|stickster at redhat.com|ghenry at suretecsystems.com| +Fedora Documentation|proxy-guide|Building and maintaining a secure proxy server.|stickster at gmail.com|ghenry at suretecsystems.com| Fedora Documentation|release-notes|Fedora Core release notes, bugs, and requests.|relnotes at fedoraproject.org|kwade at redhat.com| Fedora Documentation|selinux-apache|Using SELinux and Apache HTTP Server in Fedora Core.|walters at redhat.com|kwade at redhat.com| Fedora Documentation|selinux-faq|FAQs about SELinux in Fedora Core.|kwade at redhat.com|kwade at redhat.com| -Fedora Documentation|sudo-tutorial|Short tutorial on using sudo.|Tommy.Reynolds at MegaCoder.com|stickster at redhat.com| +Fedora Documentation|sudo-tutorial|Short tutorial on using sudo.|Tommy.Reynolds at MegaCoder.com|stickster at gmail.com| Fedora Documentation|toolchain-devel|For bugs and requests of the documentation tools.|kwade at redhat.com|mjohnson at redhat.com|Tommy.Reynolds at MegaCoder.com Fedora Documentation|translation-guide|The canonical reference for translating all aspects of the Fedora Project.|sarahs at redhat.com|tfox at redhat.com|kwade at redhat.com Fedora Documentation|translation-guide-windows|Tutorial for translators working in a Microsoft Windows environment.|sarahs at redhat.com|tfox at redhat.com| From fedora-docs-commits at redhat.com Tue Jul 12 20:30:13 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 12 Jul 2005 16:30:13 -0400 Subject: desktop-up2date desktop-up2date-en.xml,1.5,1.6 Message-ID: <200507122030.j6CKUDj7012929@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/desktop-up2date In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12886 Modified Files: desktop-up2date-en.xml Log Message: - Updated for FC4 yum integration. Index: desktop-up2date-en.xml =================================================================== RCS file: /cvs/docs/desktop-up2date/desktop-up2date-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- desktop-up2date-en.xml 12 Jul 2005 00:11:33 -0000 1.5 +++ desktop-up2date-en.xml 12 Jul 2005 20:30:11 -0000 1.6 @@ -142,12 +142,26 @@ - These repositories are also used by software management systems - like yum to install and update software. If - you configure yum to use additional - repositories then you should add these to - up2date as well. + Repositories are also used by other software management + utilities to install and update software. On &FC; &FCLOCALVER; + systems up2date uses the repositories that + are specified in the yum configuration files, + in addition to any other channels. The &FP; repositories are + automatically specified in the yum + configuration. + + + Previous Versions of &FC; + + + The version of up2date on &FC; 3 + and earlier systems is configured to use the &FP; repositories + with settings in the up2date + configuration file. These versions do not use the + yum configuration on the system. + + @@ -456,6 +470,17 @@ channels, removing + + Channels and <command>yum</command> + + + Repositories configured within yum are + automatically used by up2date on + &FC; &FCLOCALVER;. Manually add yum + repositories as channels on older versions of &FC;. + + + To add a new channel, add a new line to /etc/sysconfig/rhn/sources. From fedora-docs-commits at redhat.com Sun Jul 17 15:00:56 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 17 Jul 2005 11:00:56 -0400 Subject: owners owners.list,1.4,1.5 Message-ID: <200507171500.j6HF0uBe009966@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9949 Modified Files: owners.list Log Message: Reversed author/editor to better reflect roles in BZ ownership Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- owners.list 12 Jul 2005 20:20:28 -0000 1.4 +++ owners.list 17 Jul 2005 15:00:54 -0000 1.5 @@ -35,7 +35,7 @@ Fedora Documentation|hardening|System hardening for Fedora Core 3.|tuckser at gmail.com|kwade at redhat.com| Fedora Documentation|jargon-buster|Striving to be the canonical glossary for all things Fedora.|tfox at redhat.com|stickster at gmail.com| Fedora Documentation|mirror-tutorial|Mirroring and update services for Fedora Core.|stickster at gmail.com|kwade at redhat.com| -Fedora Documentation|proxy-guide|Building and maintaining a secure proxy server.|stickster at gmail.com|ghenry at suretecsystems.com| +Fedora Documentation|proxy-guide|Building and maintaining a secure proxy server.|ghenry at suretecsystems.com|stickster at gmail.com| Fedora Documentation|release-notes|Fedora Core release notes, bugs, and requests.|relnotes at fedoraproject.org|kwade at redhat.com| Fedora Documentation|selinux-apache|Using SELinux and Apache HTTP Server in Fedora Core.|walters at redhat.com|kwade at redhat.com| Fedora Documentation|selinux-faq|FAQs about SELinux in Fedora Core.|kwade at redhat.com|kwade at redhat.com| @@ -46,4 +46,4 @@ Fedora Documentation|updates|Tutorial for keeping a system up-to-date.|tfox at redhat.com|kwade at redhat.com| Fedora Documentation|usb-hotplug|Using USB and hotplug.|stickster at gmail.com|fdr at eln.fastmail.fm| Fedora Documentation|xml-normalize|Development of XML normalization tools.|Tommy.Reynolds at MegaCoder.com|stickster at gmail.com| -Fedora Documentation|yum-software-management|Managing systems with yum.|stickster at gmail.com|fdr at eln.fastmail.fm| +Fedora Documentation|yum-software-management|Managing systems with yum.|fdr at eln.fastmail.fm|stickster at gmail.com| From fedora-docs-commits at redhat.com Sun Jul 17 17:28:56 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 17 Jul 2005 13:28:56 -0400 Subject: yum-software-management yum-software-management-en.xml,1.6,1.7 Message-ID: <200507171728.j6HHSuk9013938@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13921 Modified Files: yum-software-management-en.xml Log Message: Began editing process; kicking back for more authorial attention Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- yum-software-management-en.xml 9 Jul 2005 15:06:36 -0000 1.6 +++ yum-software-management-en.xml 17 Jul 2005 17:28:53 -0000 1.7 @@ -46,55 +46,57 @@
Introduction &DRAFTNOTICE; +
+ Purpose + + + This tutorial presents basic concepts of software management on + &FED; systems. It outlines the major functions of + yum, the recommended software management tool + for &FED;. + +
+
Audience - The yum utility is currently the recommended - method for managing software on &FED; systems. All &FED; users - responsible for maintaining their own systems will find - yum an essential tool. + This tutorial is intended for &FED; users of all experience + levels. +
Using This Document - This document is a reference for using yum. You may wish to read some or all of the sections, depending upon - your needs and level of experience. + your needs and level of experience. If you are a new user, read + before using + yum for the first time. If you are an + experienced Linux user, start with . - If you are a new user, read the - before - using yum for the first time. - - - - Experienced Linux users should start with - . - - - - Anyone with several &FED; systems on a network may benefit from - setting up their own software repositories to manage the process - of installation and updates. The details of maintaining your own - repositories are explained in - . + If you have several &FED; systems on a network, you may benefit + from setting up your own software repositories to manage the + process of installation and updates. Refer to + for details of + maintaining your own repositories. Most of the examples in this document use the package - tsclient, which is included with &FC; to - provide an application for remote desktop access. If it is - installed successfully you may start the application by choosing - ApplicationsInternetTerminal - Server Client. To use the examples, - substitute the name of the relevant package for - tsclient. + tsclient, which is included with &FC;. The + tsclient package provides an application + for remote desktop access. If you install it successfully, you + may start the application by choosing + ApplicationsInternetTerminal + Server Client. To use the + examples, substitute the name of the relevant package for + tsclient. @@ -102,10 +104,10 @@ You do not need to log in with the root account in order to - manage your &FC; system. All of the commands shown in this - tutorial that require root access will prompt you for the root - password. The example terminal commands use su - to provide this facility. + manage your &FC; system. Any commands in this tutorial which + require root access will prompt you for the root password. The + procedures use the command su + to provide this facility.
@@ -113,45 +115,45 @@
Additional Resources - yum, documentation + yum + documentation - yum, man pages + yum + man pages The yum utility has features and options that - are not discussed in this document. Read the - man pages for yum(8) and - yum.conf(5) to learn more. - - - yum, Websites - - - The official Website for yum is: - - - - http://linux.duke.edu/projects/yum/ - - - yum, mailing lists - - - The official mailing list for yum users is: - - - - https://lists.dulug.duke.edu/mailman/listinfo/yum - - - - The archive for the yum development mailing - list is here: - - - - https://lists.dulug.duke.edu/pipermail/yum-devel/ + are not discussed in this document. Read the + man pages for yum(8) and + yum.conf(5) to learn more, using the + following commands: + + + + man yum man yum.conf + + + If you want to use a para for the next bit, + use sentences and graft them together. Otherwise, you can use a + variablelist, or an itemizedlist. [PWF] + + + yum + home page + + + The official home page for yum on the World + Wide Web is . + + yum + mailing lists + The official mailing list for + yum users is at . + The archive for the yum development mailing + list is at .
@@ -162,82 +164,88 @@
About Packages - packages, defined + packages + defined - All of the software and documentation prepared for use with - &FED; is supplied in the form of files called RPM - packages. Each package is a compressed - archive containing product information, program files, icons, - documentation and management scripts. These files are used by - management applications to safely locate, install, update and - remove software. For example, the &FED; installation process - uses the packages supplied with &FC; to build or upgrade a - system to your requirements. + &FED; software and documentation is supplied in the form of RPM + packages. Each package is a compressed + archive which contains product information, program files, + icons, documentation and management scripts. Management + applications use these files to safely locate, install, update + and remove software. For example, the &FED; installation process + uses the packages supplied with &FC; to build or upgrade a + system to your requirements. Packages also include a digital signature to prove their source. - This digital signature is verified by software management - utilities by using a GPG public key. Both - the yum and rpm utilities - share a common keyring that stores all of - the public keys for the package sources approved by the system - administrator. + Software management utilities verify this digital signature with + a GPG public key. The + yum and rpm utilities + share a common keyring which stores all + public keys for the package sources approved by the system + administrator.
About Repositories - repositories, defined + repositories + defined - Software management utilities like yum - automatically locate and obtain the correct RPM packages for an - application from repositories, which are - prepared directories or Websites. This method frees you from - having to manually find and install new applications or updates: - you may use a single command to update all of the software that - makes up your system, or to search for new software by - specifying criteria. In each case the management utility - connects to the repositories that it is configured to use, and - checks the indexes that they provide to find the correct - packages. + A repository is a directory which + contains prepared files which refer to software packages. + Software management utilities such as yum + automatically locate and obtain the correct RPM packages for an + application from these repositories. This + method frees you from having to manually find and install new + applications or updates. You may use a single command to update + all of your system's software, or search for new software by + specifying criteria. In each case, the management utility + connects to the configured repositories and checks files in each + one to find the correct packages. - Using repositories also ensures also that you always receive the - current version of the software. If several versions of the same - package are available then your management utility automatically - selects the latest version. + If you use repositories, you always receive the current version + of the software. If several versions of the same package are + available, your management utility automatically selects the + latest version. - For these reasons you should only manually install software when - you are confident that there is no repository that can currently - provide it. If a piece of software on your system is not - available from a repository then no update feature can - automatically find or install newer versions, and you must keep - that product updated yourself. + For these reasons, you should only manually install software + when you are confident that no repository can currently provide + it. If a piece of installed software is not available from a + repository, you cannot automatically find or install newer + versions. You must keep that product updated manually. The package management utilities in &FC; are automatically - configured to use the network of repository servers maintained - by the &FP;. These repositories hold both the software included - with &FC;, and a large selection of additional software, known - as &FEX;. Third-party software developers also provide - repositories for their &FED; compatible packages. + configured to use the network of repository servers maintained + by the &FP;. These repositories contain the software included + with &FC;, and a large selection of additional software known as + &FEX;. Third-party software developers also provide repositories + for their &FED; compatible packages. + Use the terminology from the &FP; web site. + Personally, I have no quibble with "free" vs. "open source" + software, but rule #1 is to be consistent across the whole + project. Since the web site says "open source," let's use + that. [PWF] + - All &FED; Packages are Free Software + Open Source Software - All of the software provided by the &FP; is Free Software, or - Open Source, and can therefore be downloaded and installed - from the network of &FED; repositories without restrictions. + All of the software provided by the &FP; is open source + software. For more information about open source software, + refer to .
@@ -245,36 +253,40 @@
About Dependencies - dependencies, defined + dependencies + defined You must consider package dependencies - when manually installing software. To avoid conflicts and - inconsistencies Linux distributions supply program library files - as separate packages to the applications that use their - functions. Many libraries and command-line utilities are used by - multiple applications. + when manually installing software. For RPM software, a + dependency is a capability provided by one package on which + other packages rely. Some programs rely on external shared + libraries to run properly. If a library + is provided by an external package, that package may be a + dependency for numerous other packages. Management tools like yum use the information - on dependencies stored within packages to ensure that all of the - requirements are met when you install an application. The - packages for any supporting software are automatically be - installed first, if they are not already present on your system. - If a new application has requirements that conflict with - existing software then the installation process safely aborts - without making any changes to your system. + on dependencies stored within packages to ensure that all of the + requirements are met when you install an application. The + yum utility installs all required packages + which are not already present on your system. If a new + application has requirements that conflict with existing + software, yum aborts without making any + changes to your system.
Understanding Package Names - packages, hardware compatibility + packages + hardware compatibility - packages, naming + packages + naming Each package file has a long name that indicates several key @@ -285,17 +297,19 @@ tsclient-0.132-4.i386.rpm - Use just the name of the package itself with - yum, except when it is necessary to specify - the exact version or type. To specify the exact version of the - application, use name-version. The package - listings provided by yum itself use the - format name.architecture, to specify the - type of computer that the package is intended for. + Use only the name of the package itself with + yum, except when it is necessary to specify + the exact version or type. When exactly is + that necessary? Make this clear. [PWF] To specify the exact + version of the application, use + name-version. The package listings provided + by yum use the format + name.architecture, to specify the type of + computer for which the package is intended. - These are valid for the file shown above: + These properties are valid for the file shown above: @@ -320,23 +334,24 @@ The hardware architecture is the minimum - type of machine required for that specific package. Packages - with run on any current Intel-compatible - computer. Packages for PowerPC machines, such as Apple Macs, are - indicated with . Packages with - have no architecture requirement. + type of machine required for that specific package. Packages + with architecture run on any current + Intel-compatible computer. Packages for PowerPC machines, such + as Apple Macs, are indicated with . Packages + with architecture have no architecture + requirement. Some software can be optimized for particular types of - Intel-compatible machine, and separate packages are provided for - , , - and . A computer - with at least an Intel Pentium, VIA C3 or compatible chip is an - . Computers with an Intel Pentium II and - above, or a current model of AMD chip, are - machines. 64-bit PCs use packages for - full 64-bit support. + Intel-compatible machine, and separate packages may be provided + for , , + and . A computer + with at least an Intel Pentium, VIA C3 or compatible CPU is an + . Computers with an Intel Pentium II or + later, or a current model of AMD chip, are + machines. 64-bit PCs use packages for + full 64-bit support. @@ -356,7 +371,7 @@ Add/Remove Applications utility - alert icon + Alert Icon up2date @@ -368,40 +383,54 @@ - On your desktop is an alert icon that + On your desktop is an Alert Icon that keeps you informed about package updates. Until your system is - updated this appears as a red circle with a flashing exclamation - mark. The alert icon is integrated with - up2date, which enables you to easily - install updates for your system. + updated, the icon appears as a red circle with a flashing + exclamation mark. The Alert Icon is + integrated with up2date, which enables + you to easily install updates for your system. Both up2date and yum are configured to use official &FED; repositories. If you add - other repositories to yum then for consistency + other repositories to yum, for consistency you should also configure up2date to use them. + + Repository Configuration + + In &FC; 4 and beyond, up2date is + configured to automatically use repositories configured for + yum. If you configure any new repositories + for yum, up2date + will use them also. + + + Also included in &FC; is - system-config-packages. From the main - menu, this is System - SettingsAdd/Remove - Applications. Unlike - up2date and yum, it - installs software packages from your &FC; installation discs, and - does not use repositories. You may find this application useful - for systems that do not have a network connection. + system-config-packages. To run this + utility, rom the Main Menu, select + System + SettingsAdd/Remove + Applications. Unlike + up2date and yum, + this utility installs software packages from your &FC; + installation discs, and does not use repositories. This + application is used on systems that do not have a network + connection. The rpm command-line utility has many functions - for working with individual RPM packages, and can also be used to - manually install and remove packages from your system. Installing - software with the rpm utility can be difficult, - and is not recommended. + for working with individual RPM packages. The + rpm command can also be used to manually + install and remove packages from your system. Installing software + with the rpm utility can be difficult for + novices, and is not recommended. @@ -419,28 +448,42 @@
Updating Your System with <command>yum</command> - updating, full system + updating + full system - yum, updating full system + yum + updating full system - - You may update all of the software that makes up your &FC; system - in a single operation. This is done with the - function. - - - - To carry out a full system update, type this command in a terminal - window: + + Your original paragraph below was: "You may + update all of the software that makes up your &FC; system in a + single operation. This is done with the + function." Remember this should be a procedural tutorial, so focus + on telling the user what to do. In technical docs "To ABC, do XYZ" + is much more effective than "You may do XYZ if you want to ABC." + It's also easier to translate, and keeps you from slipping into + passive voice. [PWF] + + + To update all of your &FED; system's software in a single + operation, select + Applications + System Tools + Terminal + and type: su -c 'yum update' - Enter the root password when prompted. + Enter the password for the root account when prompted. + + + Data files are downloaded from each of the repositories that yum is configured to use. These index and @@ -1465,3 +1508,10 @@ + + From fedora-docs-commits at redhat.com Sun Jul 17 21:19:58 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Sun, 17 Jul 2005 17:19:58 -0400 Subject: yum-software-management yum-software-management-en.xml,1.7,1.8 Message-ID: <200507172119.j6HLJwl2018848@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18824 Modified Files: yum-software-management-en.xml Log Message: Sync working copy with CVS. Overwrites previous commit. - Restructured to draw together common elements of yum operations. - Added initial package groups support. - New layout, may be less than optimal. - Lots of minor amendments. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- yum-software-management-en.xml 17 Jul 2005 17:28:53 -0000 1.7 +++ yum-software-management-en.xml 17 Jul 2005 21:19:55 -0000 1.8 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -40,74 +40,86 @@ + + 0.5 + 2005-07-17 + StuartEllis + + + Updated for &FC; &FCLOCALVER;. + + +
Introduction &DRAFTNOTICE; -
- Purpose - - - This tutorial presents basic concepts of software management on - &FED; systems. It outlines the major functions of - yum, the recommended software management tool - for &FED;. - -
-
Audience - This tutorial is intended for &FED; users of all experience - levels. + The yum utility is currently the recommended + method for managing software on &FED; systems. All &FED; users + responsible for maintaining their own systems will find + yum an essential tool. -
Using This Document + This document is a reference for using yum. You may wish to read some or all of the sections, depending upon - your needs and level of experience. If you are a new user, read - before using - yum for the first time. If you are an - experienced Linux user, start with . + your needs and level of experience. + + + + If you are a new user, read the + before + using yum for the first time. - If you have several &FED; systems on a network, you may benefit - from setting up your own software repositories to manage the - process of installation and updates. Refer to - for details of - maintaining your own repositories. + Experienced Linux users should start with + . + + + + Anyone with several &FED; systems on a network may benefit from + setting up their own software repositories to manage the process + of installation and updates. The details of maintaining your own + repositories are explained in + . Most of the examples in this document use the package - tsclient, which is included with &FC;. The - tsclient package provides an application - for remote desktop access. If you install it successfully, you - may start the application by choosing - ApplicationsInternetTerminal - Server Client. To use the - examples, substitute the name of the relevant package for - tsclient. + tsclient, which is included with &FC; to + provide an application for remote desktop access. If it is + installed successfully you may start the application by choosing + ApplicationsInternetTerminal + Server Client. To use the examples, + substitute the name of the relevant package for + tsclient. Avoid Logging in with the Root Account - You do not need to log in with the root account in order to - manage your &FC; system. Any commands in this tutorial which - require root access will prompt you for the root password. The - procedures use the command su - to provide this facility. + You do not need to log in with the + root account in + order to manage your &FC; system. All of the commands shown in + this tutorial that require + root access will + prompt you for the + root password. The + example terminal commands use su + to provide this facility.
@@ -115,45 +127,45 @@
Additional Resources - yum - documentation + yum, documentation - yum - man pages + yum, man pages The yum utility has features and options that - are not discussed in this document. Read the - man pages for yum(8) and - yum.conf(5) to learn more, using the - following commands: - - - - man yum man yum.conf - - - If you want to use a para for the next bit, - use sentences and graft them together. Otherwise, you can use a - variablelist, or an itemizedlist. [PWF] - - - yum - home page - - - The official home page for yum on the World - Wide Web is . - - yum - mailing lists - The official mailing list for - yum users is at . - The archive for the yum development mailing - list is at . + are not discussed in this document. Read the + man pages for yum(8) and + yum.conf(5) to learn more. + + + yum, Websites + + + The official Website for yum is: + + + + http://linux.duke.edu/projects/yum/ + + + yum, mailing lists + + + The official mailing list for yum users is: + + + + https://lists.dulug.duke.edu/mailman/listinfo/yum/ + + + + The archive for the yum development mailing + list is here: + + + + https://lists.dulug.duke.edu/pipermail/yum-devel/
@@ -164,129 +176,128 @@
About Packages - packages - defined + packages, defined - &FED; software and documentation is supplied in the form of RPM - packages. Each package is a compressed - archive which contains product information, program files, - icons, documentation and management scripts. Management - applications use these files to safely locate, install, update - and remove software. For example, the &FED; installation process - uses the packages supplied with &FC; to build or upgrade a - system to your requirements. + All of the software and documentation prepared for use with + &FED; is supplied in the form of files called RPM + packages. Each package is a compressed + archive containing product information, program files, icons, + documentation and management scripts. These files are used by + management applications to safely locate, install, update and + remove software. For example, the &FED; installation process + uses the packages supplied with &FC; to build or upgrade a + system to your requirements. Packages also include a digital signature to prove their source. - Software management utilities verify this digital signature with - a GPG public key. The - yum and rpm utilities - share a common keyring which stores all - public keys for the package sources approved by the system - administrator. + This digital signature is verified by software management + utilities by using a GPG public key. Both + the yum and rpm utilities + share a common keyring that stores all of + the public keys for the package sources approved by the system + administrator.
About Repositories - repositories - defined + repositories, defined - A repository is a directory which - contains prepared files which refer to software packages. - Software management utilities such as yum - automatically locate and obtain the correct RPM packages for an - application from these repositories. This - method frees you from having to manually find and install new - applications or updates. You may use a single command to update - all of your system's software, or search for new software by - specifying criteria. In each case, the management utility - connects to the configured repositories and checks files in each - one to find the correct packages. - - - - If you use repositories, you always receive the current version - of the software. If several versions of the same package are - available, your management utility automatically selects the - latest version. - - - - For these reasons, you should only manually install software - when you are confident that no repository can currently provide - it. If a piece of installed software is not available from a - repository, you cannot automatically find or install newer - versions. You must keep that product updated manually. + Software management utilities like yum + automatically locate and obtain the correct RPM packages for an + application from repositories, which are + prepared directories or Websites. This method frees you from + having to manually find and install new applications or updates: + you may use a single command to update all of the software that + makes up your system, or to search for new software by + specifying criteria. In each case the management utility + connects to the repositories that it is configured to use, and + checks the indexes that they provide to find the correct + packages. The package management utilities in &FC; are automatically - configured to use the network of repository servers maintained - by the &FP;. These repositories contain the software included - with &FC;, and a large selection of additional software known as - &FEX;. Third-party software developers also provide repositories - for their &FED; compatible packages. + configured to use the network of repository servers maintained + by the &FP;. These repositories hold both the software included + with &FC;, and a large selection of additional software, known + as &FEX;. Third-party software developers also provide + repositories for their &FED; compatible packages. - Use the terminology from the &FP; web site. - Personally, I have no quibble with "free" vs. "open source" - software, but rule #1 is to be consistent across the whole - project. Since the web site says "open source," let's use - that. [PWF] - - Open Source Software + All &FED; Packages are Free Software - All of the software provided by the &FP; is open source - software. For more information about open source software, - refer to . + All of the software provided by the &FP; is Free Software, or + Open Source, and can therefore be downloaded and installed + from the network of &FED; repositories without restrictions. + + package groups, defined + + + You may also manage related packages as sets by using the + package groups provided by the &FED; + repositories. Third-party repositories organize their packages + into additional groups where necessary. + + + + Using repositories ensures that you always receive the current + version of the software. If several versions of the same package + are available then your management utility automatically selects + the latest version. + + + + For all of these reasons you should only manually install + software when you are confident that there is no repository that + can currently provide it. If a piece of software on your system + is not available from a repository then no update feature can + automatically find or install newer versions, and you must keep + that product updated yourself. +
About Dependencies - dependencies - defined + dependencies, defined You must consider package dependencies - when manually installing software. For RPM software, a - dependency is a capability provided by one package on which - other packages rely. Some programs rely on external shared - libraries to run properly. If a library - is provided by an external package, that package may be a - dependency for numerous other packages. + when manually installing software. To avoid conflicts and + inconsistencies Linux distributions supply program library files + as separate packages to the applications that use their + functions. Many libraries and command-line utilities are used by + multiple applications. Management tools like yum use the information - on dependencies stored within packages to ensure that all of the - requirements are met when you install an application. The - yum utility installs all required packages - which are not already present on your system. If a new - application has requirements that conflict with existing - software, yum aborts without making any - changes to your system. + on dependencies stored within packages to ensure that all of the + requirements are met when you install an application. The + packages for any supporting software are automatically be + installed first, if they are not already present on your system. + If a new application has requirements that conflict with + existing software then the installation process safely aborts + without making any changes to your system.
Understanding Package Names - packages - hardware compatibility + packages, hardware compatibility - packages - naming + packages, naming Each package file has a long name that indicates several key @@ -297,19 +308,17 @@ tsclient-0.132-4.i386.rpm - Use only the name of the package itself with - yum, except when it is necessary to specify - the exact version or type. When exactly is - that necessary? Make this clear. [PWF] To specify the exact - version of the application, use - name-version. The package listings provided - by yum use the format - name.architecture, to specify the type of - computer for which the package is intended. + Use just the name of the package itself with + yum, except when it is necessary to specify + the exact version or type. To specify the exact version of the + application, use name-version. The package + listings provided by yum itself use the + format name.architecture, to specify the + type of computer that the package is intended for. - These properties are valid for the file shown above: + These are valid for the file shown above: @@ -334,34 +343,24 @@ The hardware architecture is the minimum - type of machine required for that specific package. Packages - with architecture run on any current - Intel-compatible computer. Packages for PowerPC machines, such - as Apple Macs, are indicated with . Packages - with architecture have no architecture - requirement. + type of machine required for that specific package. Packages for + run on any current Intel-compatible + computer. Packages for PowerPC machines, such as Apple Macs, are + indicated with . Packages specified as + have no architecture requirement. - Some software can be optimized for particular types of - Intel-compatible machine, and separate packages may be provided - for , , - and . A computer - with at least an Intel Pentium, VIA C3 or compatible CPU is an - . Computers with an Intel Pentium II or - later, or a current model of AMD chip, are - machines. 64-bit PCs use packages for - full 64-bit support. + Some software may be optimized for particular types of + Intel-compatible machine. For these products, separate packages + are provided for , , + and computers. A + machine with at least an Intel Pentium, VIA C3 or compatible + chip is an . Computers with an Intel + Pentium II and above, or a current model of AMD chip, are + machines. 64-bit PCs use + packages for full 64-bit support. - - - Other Naming Conventions are Supported - - - Refer to for - more information on specifying packages by name or type. - -
@@ -371,7 +370,7 @@ Add/Remove Applications utility - Alert Icon + alert icon up2date @@ -383,54 +382,40 @@ - On your desktop is an Alert Icon that + On your desktop is an alert icon that keeps you informed about package updates. Until your system is - updated, the icon appears as a red circle with a flashing - exclamation mark. The Alert Icon is - integrated with up2date, which enables - you to easily install updates for your system. + updated this appears as a red circle with a flashing exclamation + mark. The alert icon is integrated with + up2date, which enables you to easily + install updates for your system. Both up2date and yum are configured to use official &FED; repositories. If you add - other repositories to yum, for consistency + other repositories to yum then for consistency you should also configure up2date to use them. - - Repository Configuration - - In &FC; 4 and beyond, up2date is - configured to automatically use repositories configured for - yum. If you configure any new repositories - for yum, up2date - will use them also. - - - Also included in &FC; is - system-config-packages. To run this - utility, rom the Main Menu, select - System - SettingsAdd/Remove - Applications. Unlike - up2date and yum, - this utility installs software packages from your &FC; - installation discs, and does not use repositories. This - application is used on systems that do not have a network - connection. + system-config-packages. From the main + menu, this is System + SettingsAdd/Remove + Applications. Unlike + up2date and yum, it + installs software packages from your &FC; installation discs, and + does not use repositories. You may find this application useful + for systems that do not have a network connection. The rpm command-line utility has many functions - for working with individual RPM packages. The - rpm command can also be used to manually - install and remove packages from your system. Installing software - with the rpm utility can be difficult for - novices, and is not recommended. + for working with individual RPM packages, and may also be used to + manually install and remove packages from your system. Installing + software with the rpm utility requires you to + manually check and install the dependencies of the software. @@ -445,100 +430,264 @@
-
- Updating Your System with <command>yum</command> - - updating - full system - +
+ Managing Software with <command>yum</command> - yum - updating full system + yum, package management - - Your original paragraph below was: "You may - update all of the software that makes up your &FC; system in a - single operation. This is done with the - function." Remember this should be a procedural tutorial, so focus - on telling the user what to do. In technical docs "To ABC, do XYZ" - is much more effective than "You may do XYZ if you want to ABC." - It's also easier to translate, and keeps you from slipping into - passive voice. [PWF] - - - To update all of your &FED; system's software in a single - operation, select - Applications - System Tools - Terminal - and type: + + The yum utility may modify the software on your + system in three ways: - -su -c 'yum update' - + - Enter the password for the root account when prompted. + + + + By installing new software from repositories or a package + file. + + + + + By updating existing software on your system. + + + + + By removing unwanted software from your system. + + + - - + + In each case you must specify the function and the criteria, such + as the name of the package or package group. Simple examples are + given in each section. + + + Package Names + + You may use any of the following formats for specifying a + package in a yum operation: + name, + name.architecture, + name-version, + name-version-release, + name-version-release.architecture, and + epoch:name-version-release.architecture. + + + + To use the repositories yum downloads data + files from each of the repositories that it is configured to use. + On a slow connection downloading the repository index files and + the header file for each package may take + several seconds to complete. + - Data files are downloaded from each of the repositories that - yum is configured to use. These index and - header files are searched for information about newer versions of - packages. On a slow connection the download process may take - several seconds. + When installing, updating or removing software, + yum first determines the best set of actions to + produce the required result, and displays the transaction for you + to approve. This may include installing, updating or removing + other packages in addition to the package that you specified, in + order to resolve the dependencies of the software. - A list of all of the available updates for your system is - displayed. Press y to accept the updates. - If you accept the updates the relevant packages are then - downloaded and installed. + As an example, this is the transaction for installing + tsclient: + + + +============================================================================= + Package Arch Version Repository Size +============================================================================= +Installing: + tsclient i386 0.132-6 base 247 k +Installing for dependencies: + rdesktop i386 1.4.0-2 base 107 k + +Transaction Summary +============================================================================= +Install 2 Package(s) +Update 0 Package(s) +Remove 0 Package(s) +Total download size: 355 k +Is this ok [y/N]: + + + + Review the list of changes before pressing + y to accept and begin the process. No + packages are downloaded or changed if you press + n. -
- Automatically Updating Your System + + Package Versions + + + Only the newest version of each package is displayed and used by + yum, unless you specify an older version of a + package. + + + + Downloads are Cached + + Downloaded data files and packages are kept for reuse. You may + copy packages from the repository cache directories under + /var/cache/yum/, and use them elsewhere if + you wish. Removing a package from the cache does not affect the + copy of the software installed on your system. + + +
+ Installing New Software with <command>yum</command> - automatic updating + installing software with yum + + + software, installing - If your system is permanently connected to the network then - updates can be performed at any time. The - yum package includes scripts that can - automatically carry out full updates every day. + To install the package tsclient, enter the + command: + + +su -c 'yum install tsclient' + + + Enter the root + password when prompted. - To activate automatic daily updating, type this line: + To install the package group MySQL + Database, enter the command: -su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' +su -c 'yum groupinstall "MySQL Database"' + + + Enter the root + password when prompted. + + + + New Services Require Activation + + + Installing a service does not activate or start it. To + configure a new service to run on bootup, choose + DesktopSystem + Settings Server Settings + Services, or run + chkconfig in a terminal window. + + +
+ +
+ Updating Software with <command>yum</command> + + updating software with yum + + + software, updating + + + To update the tsclient package to the + latest version, type: + + +su -c 'yum update tsclient' + + + Enter the root + password when prompted. + + + + New Software Versions Require Reloading + + + If a piece of software is use whilst it is updated then the + old version remains active until the software is next loaded. + Services are reloaded by restarting the service. Kernel + updates take effect the next time that the system is booted. + + + + + To update all of the packages in the package group + MySQL Database, enter the command: + + +su -c 'yum groupupdate "MySQL Database"' - Enter the root password when prompted. + Enter the root + password when prompted. - How Daily Updates are Run + Updating the Entire System - There is no separate yum service that runs - on your system. The command given above enables the control - script /etc/rc.d/init.d/yum. This control - script activates the script - /etc/cron.daily/yum.cron, so that the - cron service will perform the system update - as one of the tasks that are automatically run each day. + To update all of the packages that make up your &FED; system, + use the commands described in + .
+ +
+ Removing Software with <command>yum</command> + + removing software with yum + + + software, removing + + + To remove software, yum examines your system + for both the specified software, and any other software that + must also be removed in order to safely uninstall it. + + + + To remove the tsclient package from your + system the full command is: + + +su -c 'yum remove tsclient' + + + Enter the root + password when prompted. + + + + To remove all of the packages in the package group + MySQL Database, enter the command: + + +su -c 'yum groupremove "MySQL Database"' + + + Enter the root + password when prompted. + +
- Searching for Software with <command>yum</command> + Searching with <command>yum</command> packages, locating @@ -563,6 +712,12 @@ + + The format of the results depends upon the option. If the query + produces no information then no packages matching the criteria + have been found. + +
Searching by Package Name and Attributes @@ -582,19 +737,6 @@ yum list tsclient-0.132 - - Package Attributes - - You may use any of the following formats for specifying a - package in a yum query: - name, - name.architecture, - name-version, - name-version-release, - name-version-release.architecture, and - epoch:name-version-release.architecture. - -
@@ -663,204 +805,176 @@ shadow-util? or Shadow*. - - - When several versions of the same package are available, only - the newest is used. -
-
- Managing Software with <command>yum</command> +
+ Updating Your System with <command>yum</command> - yum, package management + updating, full system + + + yum, updating full system - The yum utility has four basic management - functions: + Use the option to upgrade all of the + software on your &FED; system to the latest version with one + operation. - - - - new software from the repositories. - - - - - existing software. - - - - - unwanted software. - - - - - , to install software from a - individual package. - - - + To carry out a full system update, type this command in a terminal + window: - + +su -c 'yum update' + - In each case you must specify the function and the criteria. Some - simple examples are given in each section. + Enter the root password + when prompted. - - Search Criteria - - - See for details of - search criteria. The management options of - yum are case-sensitive. - - - - - As with the search and system update functions, - yum begins the process by downloading data - files from each of the repositories that it is configured to use. - Once yum has determined the steps to carry out - the task you are presented with the proposed package changes, - which you can either approve or reject. By default no changes are - made to your system unless you approve. - - - Downloaded Packages - - The RPM packages downloaded and used by yum - are held in sub-directories of - /var/cache/yum/, with one sub-directory per - repository. You may copy these cached packages and use them - elsewhere if you wish. Removing a package from your system does - not delete the downloaded RPM from the cache. See - for details on - purging the caches. - - -
- Installing New Software with <command>yum</command> - - installing software with yum - +
+ Automatically Updating Your System - software, installing + automatic updating - To install or update software, yum examines - the package caches on your system and each of the configured - package sources to determine the best set of actions to produce - the required result. This may include installing or updating - other packages in addition to the package that you specified. + If your system is permanently connected to the network then + updates can be performed at any time. The + yum package includes scripts that can + automatically carry out full updates every day. - To install the package tsclient, enter the - command: + To activate automatic daily updating, type this line: -su -c 'yum install tsclient' +su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' - Enter the root password when prompted. + Enter the root + password when prompted. + + + How Daily Updates are Run + + + There is no separate yum service that runs + on your system. The command given above enables the control + script /etc/rc.d/init.d/yum. This control + script activates the script + /etc/cron.daily/yum.cron, so that the + cron service will perform the system update + as one of the tasks that are automatically run each day. + +
+
-
- Installing Software from a Package with <command>yum</command> - - installing software with yum (from a package) - - - software, installing from a package - - - Use the option to install software - from an individual package file on your system. In this mode - yum simply installs the specified package - without connecting to any repository. You are responsible for - ensuring that all of the dependencies are already installed on - your system. - +
+ Using <command>yum</command> with a Proxy Server + + proxy server, with yum + + + yum, using a proxy server + + + Repositories may be accessed through standard Web proxy servers. + If your system is connected to the Internet through a Web proxy + server, specify the details of the server in + /etc/yum.conf. The proxy + setting must specify the proxy server as a complete URL, including + the TCP port number. If your proxy server requires a username and + password, specify these by adding + proxy_username and + proxy_password settings. + + + + For example, the settings below enable yum to + use the proxy server mycache.mydomain.com, + connecting to port 3128, with the username + yum-user and the password + qwerty. + + + + Configuration File Settings for Using A Proxy Server + + + + + + + Global Settings - To install the package - tsclient-0.132-4.i386.rpm, enter the - command: - - -su -c 'yum localinstall tsclient-0.132-4.i386.rpm' - - - Enter the root password when prompted. + Defining a proxy server in /etc/yum.conf + means that all users connect to the proxy + server with those details when using yum. + + + + To enable proxy access for a specific user, add the lines in the + example box below to their shell profile. For the default + bash shell, the profile is the file + .bash_profile. The settings below enable + yum to use the proxy server + mycache.mydomain.com, connecting to port + 3128. + - - Public Key is Required + + Profile Settings for Using a Proxy Server + + + + - - You must ensure that the public key for the package source has - been imported before installing a package without a - repository. Refer to - - - -
+ + If the proxy server requires a username and password then add + these to the URL. For example, to include the username + yum-user and the password + qwerty: + -
- Updating Software with <command>yum</command> - - updating software with yum - - - software, updating - - - Updating a software package follows the same process as - installing a new package. For example, to update the - tsclient package to the latest version, - type: - - -su -c 'yum update tsclient' - - - Enter the root password when prompted. - -
+ + Profile Settings for a Secured Proxy Server + + + + -
- Removing Software with <command>yum</command> - - removing software with yum - - - software, removing - - - To remove software, yum examines your system - for both the specified software, and any other software that - must also be removed in order to safely uninstall it. - + + <command>http_proxy</command> Variable with Other Utilities - To remove the tsclient package from your - system the full command is: - - -su -c 'yum remove tsclient' - - - Enter the root password when prompted. + The http_proxy variable is also used by + curl and other utilities. Although + yum itself may use + http_proxy in either upper-case or + lower-case, curl requires the name of the + variable to be in lower-case. -
+
@@ -875,36 +989,30 @@ searching for repositories - Projects and individuals that provide RPM packages through - yum repositories will provide details on their - Website. The &FEX; project is the official source for additional - packages. - - - - The Website for &FEX; is here: - - - - http://fedora.redhat.com/projects/extras/ + &FC; automatically uses the &FED; repositories. These include + &FEX;, the default source of packages for software that is not + included with &FC;. - Repositories for Early Versions of &FC; + &FEX; Repositories for Previous Versions of &FC; - &FEX; does not provides packages for &FC; 2 or earlier. The - official Website for additional packages for &FC; 1 and &FC; 2 - is: - http://www.fedora.us/ + You must manually configure &FC; 3 systems to use &FEX;, using + the instructions at: + http://fedora.redhat.com/projects/extras/. + Refer to this Website for additional packages for &FC; 1 and + &FC; 2: + http://www.fedora.us/. - You should use these sites for software that is not included with - &FC;. If these sites do not provide packages for a specific piece - of software, the manufacturer of the software may provide or - recommend a repository. + If the &FED; project does not provide packages for a specific + piece of software, the manufacturer of the software may provide or + recommend a separate repository. Members of the community also + maintain repositories to provide packages for &FED; systems. + Third-party repositories provide information on their Websites.
@@ -916,9 +1024,7 @@ repository definition files, installing - &FC; includes a yum package that has &FED; - repositories in the configuration. To add an extra repository, - place a definition file in the + To add an extra repository, place a definition file in the /etc/yum.repos.d/ directory on your system. Package providers make the definition files for their repositories available on their Websites. @@ -931,15 +1037,17 @@ - Adding a file to the definitions directory requires root access. - To copy the definition file example.repo, - type the command: + Adding a file to the definitions directory requires + root access. To copy + the definition file example.repo, type the + command: su -c 'cp example.repo /etc/yum.repos.d/' - Enter the root password when prompted. + Enter the root + password when prompted. @@ -955,9 +1063,11 @@ Repositories and <application>up2date</application> Channels - You should also add new package repositories as - up2date channels to ensure - consistency between the behavior of the two applications. + On &FC; &FCLOCALVER; systems yum + repositories are automatically used as + up2date channels. Repositories must + be separately configured as channels on &FC; 3 and earlier + systems.
@@ -977,7 +1087,8 @@ su -c 'rpm --import GPG-PUB-KEY.asc' - Enter the root password when prompted. + Enter the root + password when prompted. @@ -1039,15 +1150,65 @@ The data format for repository indexes changed with version 2.11 of yum. This was the version supplied with &FC; 3. Repository providers should specify the versions - of &FC; that they support. All repositories compatible with - current versions of yum can also be - identified by the fact that they have a sub-directory called - repo-data/. + of &FC; that they support. To confirm that an unlabeled + repository is compatible with current versions of + yum, check that it has a sub-directory + called repo-data/.
+
+ Manually Installing Software + + installing software with yum (from a package) + + + software, installing from a package + + + Use repositories and the standard yum commands + to install new software, unless the software is only available as + a package. In these cases, use the + option to install the software from the package file without + connecting to any repository. + + + + Public Key is Required + + + You must ensure that the public key for the package source has + been imported before installing a package without a repository. + Refer to + + + + + As an example, enter this command to install the package + tsclient-0.132-4.i386.rpm: + + +su -c 'yum localinstall tsclient-0.132-4.i386.rpm' + + + Enter the root password + when prompted. + + + + Dependencies Must Be Met + + + You must ensure that all of the dependencies are already + installed on your system, as yum cannot + download additional packages to complete the installation in + this mode. + + +
+
Maintaining <command>yum</command> @@ -1126,7 +1287,8 @@ su -c 'rpm -e gpg-pubkey-4f2a6fd2-3f9d9d3b' - Enter the root password when prompted. + Enter the root + password when prompted.
@@ -1137,8 +1299,8 @@ By design, yum does not automatically delete - any of the packages or package header files that it downloads, - so that these can be reused. Header files accumulate over time, + any of the packages or package data files that it downloads, so + that these can be reused. The header files accumulate over time, and these may be purged with the command: @@ -1152,14 +1314,16 @@ su -c 'yum clean packages' - In both cases, enter the root password when prompted. + In both cases, enter the + root password when + prompted.
Managing <command>yum</command> Repositories - + You may wish to create your own software repositories, or maintain a copy of another repository. @@ -1202,7 +1366,11 @@ - To make a directory into a yum repository: + To make a directory into a yum repository, + carry the following tasks. These instructions assume that the + repository is the directory + /var/www/repository/, and that the package + group index file is called groups.xml: @@ -1212,29 +1380,43 @@ + Create a groups file, as explained in + + + + + + Copy the groups file into the directory, alongside the + packages. + + + + Open a terminal window. In the terminal window type: createrepo - /path/to/directory. Substitute the path to - your package directory for - /path/to/directory/. + /var/www/repository. + + + + + In the terminal window type: createrepo -g + /var/www/repository/groups.xml. In the terminal window type: chmod a+x - /path/to/directory/repodata/. Substitute the - path to your package directory for - /path/to/directory/. + /var/www/repository/repodata/. - Ensure that the directory is available via your chosen - network protocols. + Ensure that the directory is available with your chosen + network protocols (HTTP, FTP, or NFS). @@ -1272,6 +1454,115 @@
+
+ Package Group Index Files + + + package group index files, creating + + + package group index files, editing + + + Create and edit package group files with a text editor. + Definition files are XML with a standard format: + + + + Format of <command>yum</command> Group Index Files + + + + + + group-id + Group Name + Descriptive Text. + true or false + true or false + + group-name + + + package-name or package-name + + + + + Category Name + + Name of Member Group + + + + + ]]> + + + + + The id and name that + identify each group must either match those of a &FED; package + group, or be unique. If the group matches a &FED; package group + then systems using the repository add the the listed packages to + that group when carrying out yum operations. + + + + The example group file shown below defines the package groups + Base and Site Custom Application + Packages. The Base package group + adds extra mandatory packages to the &FED; package group for the + systems using the repository. Site Custom Application + Packages provides three packages. + + + + Example <command>yum</command> Group Index File + + + + + + base + Base + Additional packages for the Fedora Base package group. + true + true + + my-customadminpackage + my-othercustomadminpackage + + + site-apps + Site Custom Application Packages + Custom group for the site-specific applications. + false + true + + base + + + my-customapplication + my-othercustomapplication + my-optionalcustomapplication + + + + Site Custom Packages + + Site Custom Application Packages + + + + + ]]> + + +
+
Repository Definition Files @@ -1302,11 +1593,12 @@ The baseurl must specify the complete URL for - the root directory of the repository, including the - http://, https:// or - ftp:// prefix. You may also specify a - directory on your system, by using the prefix - file:// in the baseurl. + the root directory of + the repository, including the http://, + https:// or ftp:// prefix. + You may also specify a directory on your system, by using the + prefix file:// in the + baseurl. Logging in to Protected Repositories @@ -1338,9 +1630,8 @@ - A definition file is shown below that uses all of these - features. In this example, copies of the repository are held in - the directory + The definition file shown below uses all of these features. In + this example, copies of the repository are held in the directory /srv/software/&FED;/&FCVER;/mypackages/ on the system itself, in the directory software/&FED;/&FCVER;/mypackages/ on the @@ -1402,116 +1693,5 @@
-
- Using <command>yum</command> with a Proxy Server - - proxy server, with yum - - - yum, using a proxy server - - - Repositories may be accessed through standard proxy servers. If - your system is connected to the Internet through a Web proxy - server, specify the details of the server in - /etc/yum.conf. The proxy - setting must specify the proxy server as a complete URL, including - the TCP port number. If your proxy server requires a username and - password, specify these by adding - proxy_username and - proxy_password settings. - - - - For example, the settings below enable yum to - use the proxy server mycache.mydomain.com, - connecting to port 3128, with the username - yum-user and the password - qwerty. - - - - Configuration File Settings for Using A Proxy Server - - - - - - - Global Settings - - - Defining a proxy server in /etc/yum.conf - means that all users connect to the proxy - server with those details when using yum. - - - - - To enable proxy access for a specific user, add the lines in the - example box below to their shell profile. For the default - bash shell, the profile is the file - .bash_profile. The settings below enable - yum to use the proxy server - mycache.mydomain.com, connecting to port - 3128. - - - - Profile Settings for Using a Proxy Server - - - - - - - If the proxy server requires a username and password then add - these to the URL. For example, to include the username - yum-user and the password - qwerty: - - - - Profile Settings for a Secured Proxy Server - - - - - - - <command>http_proxy</command> Variable with Other Utilities - - - The http_proxy variable is also used by - curl and other utilities. Although - yum itself may use - http_proxy in either upper-case or - lower-case, curl requires the name of the - variable to be in lower-case. - - -
- - - From fedora-docs-commits at redhat.com Sun Jul 17 21:39:43 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 17 Jul 2005 17:39:43 -0400 Subject: yum-software-management yum-software-management-en.xml,1.8,1.9 Message-ID: <200507172139.j6HLdhFB019179@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19162 Modified Files: yum-software-management-en.xml Log Message: Added local variables for Emacs happiness Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- yum-software-management-en.xml 17 Jul 2005 21:19:55 -0000 1.8 +++ yum-software-management-en.xml 17 Jul 2005 21:39:41 -0000 1.9 @@ -1695,3 +1695,10 @@ + + From fedora-docs-commits at redhat.com Sun Jul 17 23:57:55 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Sun, 17 Jul 2005 19:57:55 -0400 Subject: yum-software-management yum-software-management-en.xml,1.9,1.10 Message-ID: <200507172357.j6HNvt1W021795@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21778 Modified Files: yum-software-management-en.xml Log Message: Amendments, per P. Frields editing. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- yum-software-management-en.xml 17 Jul 2005 21:39:41 -0000 1.9 +++ yum-software-management-en.xml 17 Jul 2005 23:57:52 -0000 1.10 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -42,7 +42,7 @@ 0.5 - 2005-07-17 + 2005-07-18 StuartEllis @@ -56,14 +56,23 @@
Introduction &DRAFTNOTICE; +
+ Purpose + + + This document presents basic concepts of software management on + &FED; systems. It outlines the major functions of + yum, the recommended software management tool + for &FED;. + +
+
Audience - The yum utility is currently the recommended - method for managing software on &FED; systems. All &FED; users - responsible for maintaining their own systems will find - yum an essential tool. + This document is intended for &FED; users of all levels of + experience.
@@ -73,34 +82,28 @@ This document is a reference for using yum. You may wish to read some or all of the sections, depending upon - your needs and level of experience. - - - - If you are a new user, read the - before - using yum for the first time. - - - + your needs and level of experience. If you are a new user, read + the + before using yum for the first time. Experienced Linux users should start with . - Anyone with several &FED; systems on a network may benefit from - setting up their own software repositories to manage the process - of installation and updates. The details of maintaining your own - repositories are explained in - . + If you have several &FED; systems on a network you may benefit + from setting up their own software repositories to manage the + process of installation and updates. Refer to + for the details of + maintaining your own repositories. Most of the examples in this document use the package - tsclient, which is included with &FC; to - provide an application for remote desktop access. If it is - installed successfully you may start the application by choosing + tsclient, which is included with &FC;. The + tsclient package provides an application + for remote desktop access. If you install it successfully you + may start the application by choosing ApplicationsInternetTerminal Server Client. To use the examples, substitute the name of the relevant package for @@ -136,37 +139,54 @@ The yum utility has features and options that are not discussed in this document. Read the man pages for yum(8) and - yum.conf(5) to learn more. + yum.conf(5) to learn more, using the + following commands: + + +man yum man yum.conf + + yum, Websites - - The official Website for yum is: - - - - http://linux.duke.edu/projects/yum/ - yum, mailing lists - - The official mailing list for yum users is: - - - - https://lists.dulug.duke.edu/mailman/listinfo/yum/ - + + + + The Website for yum is: + + + + http://linux.duke.edu/projects/yum/ + + + - - The archive for the yum development mailing - list is here: - + + + The mailing list for yum users is: + + + + https://lists.dulug.duke.edu/mailman/listinfo/yum/ + + + - - https://lists.dulug.duke.edu/pipermail/yum-devel/ - + + +The archive for the yum development mailing list is: + + + + https://lists.dulug.duke.edu/pipermail/yum-devel/ + + + +
@@ -183,18 +203,18 @@ &FED; is supplied in the form of files called RPM packages. Each package is a compressed archive containing product information, program files, icons, - documentation and management scripts. These files are used by - management applications to safely locate, install, update and - remove software. For example, the &FED; installation process - uses the packages supplied with &FC; to build or upgrade a - system to your requirements. + documentation and management scripts. Management applications + use these files to safely locate, install, update and remove + software. For example, the &FED; installation process uses the + packages supplied with &FC; to build or upgrade a system to your + requirements. Packages also include a digital signature to prove their source. This digital signature is verified by software management - utilities by using a GPG public key. Both - the yum and rpm utilities + utilities by using a GPG public key. The + yum and rpm utilities share a common keyring that stores all of the public keys for the package sources approved by the system administrator. @@ -207,17 +227,17 @@ repositories, defined + A repository is a prepared directory or + Website that contains software packages and index files. Software management utilities like yum - automatically locate and obtain the correct RPM packages for an - application from repositories, which are - prepared directories or Websites. This method frees you from - having to manually find and install new applications or updates: - you may use a single command to update all of the software that - makes up your system, or to search for new software by - specifying criteria. In each case the management utility - connects to the repositories that it is configured to use, and - checks the indexes that they provide to find the correct - packages. + automatically locate and obtain the correct RPM packages from + these repositories. This method frees you from having to + manually find and install new applications or updates: you may + use a single command to update all of the software that makes up + your system, or to search for new software by specifying + criteria. In each case the management utility connects to the + repositories that it is configured to use, and checks the + indexes that they provide to find the correct packages. @@ -230,14 +250,15 @@ - All &FED; Packages are Free Software + All &FED; Packages are Open Source Software - All of the software provided by the &FP; is Free Software, or - Open Source, and can therefore be downloaded and installed + All of the software provided by the &FP; is Open Source + software, or and can therefore be downloaded and installed from the network of &FED; repositories without restrictions. + package groups, defined @@ -259,9 +280,9 @@ For all of these reasons you should only manually install software when you are confident that there is no repository that can currently provide it. If a piece of software on your system - is not available from a repository then no update feature can - automatically find or install newer versions, and you must keep - that product updated yourself. + is not available from a repository then you cannot automatically + find or install newer versions. You must keep that product + updated yourself. @@ -289,6 +310,7 @@ existing software then the installation process safely aborts without making any changes to your system. +
@@ -318,7 +340,7 @@ - These are valid for the file shown above: + These naming conventions are valid for the file shown above: @@ -353,13 +375,14 @@ Some software may be optimized for particular types of Intel-compatible machine. For these products, separate packages - are provided for , , - and computers. A - machine with at least an Intel Pentium, VIA C3 or compatible - chip is an . Computers with an Intel - Pentium II and above, or a current model of AMD chip, are - machines. 64-bit PCs use - packages for full 64-bit support. + may be provided for , + , and + computers. A machine with at least an + Intel Pentium, VIA C3 or compatible CPU is an + . Computers with an Intel Pentium II and + above, or a current model of AMD chip, are + machines. 64-bit PCs use packages for + full 64-bit support.
@@ -370,7 +393,7 @@ Add/Remove Applications utility - alert icon + Alert Icon up2date @@ -382,7 +405,7 @@ - On your desktop is an alert icon that + On your desktop is an Alert Icon that keeps you informed about package updates. Until your system is updated this appears as a red circle with a flashing exclamation mark. The alert icon is integrated with @@ -406,16 +429,18 @@ Applications. Unlike up2date and yum, it installs software packages from your &FC; installation discs, and - does not use repositories. You may find this application useful - for systems that do not have a network connection. + does not use repositories. This application is used on systems + that do not have a network connection. The rpm command-line utility has many functions - for working with individual RPM packages, and may also be used to + for working with individual RPM packages. It may also be used to manually install and remove packages from your system. Installing software with the rpm utility requires you to - manually check and install the dependencies of the software. + manually check and install the dependencies of the software. For + this reason, using the rpm utility to manage + software is not recommended. @@ -561,8 +586,9 @@ su -c 'yum install tsclient' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -573,8 +599,9 @@ su -c 'yum groupinstall "MySQL Database"' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -607,8 +634,9 @@ su -c 'yum update tsclient' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -630,8 +658,9 @@ su -c 'yum groupupdate "MySQL Database"' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -668,8 +697,9 @@ su -c 'yum remove tsclient' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -680,8 +710,9 @@ su -c 'yum groupremove "MySQL Database"' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -823,8 +854,7 @@ - To carry out a full system update, type this command in a terminal - window: + To carry out a full system update, type this command: su -c 'yum update' @@ -853,8 +883,9 @@ su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -1046,8 +1077,9 @@ su -c 'cp example.repo /etc/yum.repos.d/' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -1087,8 +1119,9 @@ su -c 'rpm --import GPG-PUB-KEY.asc' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -1287,8 +1320,9 @@ su -c 'rpm -e gpg-pubkey-4f2a6fd2-3f9d9d3b' - Enter the root - password when prompted. + Enter the password for the + root account when + prompted. @@ -1333,7 +1367,7 @@ Old versions of yum use a different repository utility - These procedures are for repositories that are compatible with + These procedures create repositories that are compatible with version 2.11 of yum and above. You must use the yum-arch utility that was included with yum 2.10 to enable repositories for older @@ -1349,11 +1383,11 @@ A software repository is simply a directory containing package files, with a sub-directory for the package index files used by - yum. Other types of files can be held in the - main directory without interfering with use of the repository. - The data/ sub-directory and the XML files - it contains are created and updated with the - createrepo utility + yum. The main directory may also contain + other types of file without interfering with the use of the + repository. Do not modify the data/ + sub-directory and the XML files within it. These are created and + updated with the createrepo utility. From fedora-docs-commits at redhat.com Mon Jul 18 00:08:00 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Sun, 17 Jul 2005 20:08:00 -0400 Subject: yum-software-management yum-software-management-en.xml,1.10,1.11 Message-ID: <200507180008.j6I0805x022954@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22937 Modified Files: yum-software-management-en.xml Log Message: Minor tweaks. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- yum-software-management-en.xml 17 Jul 2005 23:57:52 -0000 1.10 +++ yum-software-management-en.xml 18 Jul 2005 00:07:57 -0000 1.11 @@ -265,8 +265,7 @@ You may also manage related packages as sets by using the package groups provided by the &FED; - repositories. Third-party repositories organize their packages - into additional groups where necessary. + repositories. Third-party repositories may add packages to these groups, or provide packages in additional groups where necessary. @@ -1161,7 +1160,7 @@ - You should still always check the Website of the provider for + You should always check the Website of the provider for compatibility information before attempting to use a repository. Repositories often provide packages that are specifically intended for use with packages that are supplied by other @@ -1399,6 +1398,8 @@ + + To make a directory into a yum repository, carry the following tasks. These instructions assume that the @@ -1420,12 +1421,6 @@ - Copy the groups file into the directory, alongside the - packages. - - - - Open a terminal window. @@ -1438,7 +1433,7 @@ In the terminal window type: createrepo -g - /var/www/repository/groups.xml. + /var/www/repository/groups.xml /var/www/repository/. From fedora-docs-commits at redhat.com Mon Jul 18 19:25:38 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Mon, 18 Jul 2005 15:25:38 -0400 Subject: yum-software-management yum-software-management-en.xml,1.11,1.12 Message-ID: <200507181925.j6IJPc9b015764@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15747 Modified Files: yum-software-management-en.xml Log Message: Style fixes. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- yum-software-management-en.xml 18 Jul 2005 00:07:57 -0000 1.11 +++ yum-software-management-en.xml 18 Jul 2005 19:25:35 -0000 1.12 @@ -158,33 +158,33 @@ The Website for yum is: - - - http://linux.duke.edu/projects/yum/ - - + + + http://linux.duke.edu/projects/yum/ + + - + The mailing list for yum users is: - - - https://lists.dulug.duke.edu/mailman/listinfo/yum/ - - + + + https://lists.dulug.duke.edu/mailman/listinfo/yum/ + + - + The archive for the yum development mailing list is: - - - https://lists.dulug.duke.edu/pipermail/yum-devel/ - - + + + https://lists.dulug.duke.edu/pipermail/yum-devel/ + + @@ -265,7 +265,9 @@ You may also manage related packages as sets by using the package groups provided by the &FED; - repositories. Third-party repositories may add packages to these groups, or provide packages in additional groups where necessary. + repositories. Third-party repositories may add packages to these + groups, or provide packages in additional groups where + necessary. @@ -331,11 +333,12 @@ Use just the name of the package itself with yum, except when it is necessary to specify - the exact version or type. To specify the exact version of the - application, use name-version. The package - listings provided by yum itself use the - format name.architecture, to specify the - type of computer that the package is intended for. + the exact version or type. For example, use + name-version to specify the exact version + of the application. The package listings provided by + yum itself use the format + name.architecture, to specify the type of + computer that the package is intended for. @@ -642,7 +645,7 @@ New Software Versions Require Reloading - If a piece of software is use whilst it is updated then the + If a piece of software is in use whilst it is updated then the old version remains active until the software is next loaded. Services are reloaded by restarting the service. Kernel updates take effect the next time that the system is booted. @@ -725,10 +728,10 @@ searching for packages - You may use yum to find software that is - available from the defined repositories, or is already installed - on your system. Searches automatically include both installed and - available packages. + Use the search features of yum to find software + that is available from the defined repositories, or is already + installed on your system. Searches automatically include both + installed and available packages. @@ -775,6 +778,9 @@ If you do not know the name of the package, use either the or options. + + + checks the names, descriptions, summaries and listed package maintainers of all of the available packages to find those that match. For example, to search for @@ -1160,14 +1166,14 @@ - You should always check the Website of the provider for - compatibility information before attempting to use a repository. - Repositories often provide packages that are specifically - intended for use with packages that are supplied by other - repositories. In some cases separate third-party repository - providers may each offer different versions of the same - software, preventing those repositories from being safely used - together by your &FC; system. + Before attempting to use a repository, read the Website for + information on package compatibility. . Repositories often + provide packages that are specifically intended for use with + packages that are supplied by other repositories. In some cases + separate third-party repository providers may each offer + different versions of the same software, preventing those + repositories from being safely used together by your &FC; + system. @@ -1291,12 +1297,15 @@ public keys, removing - If you will not be using any more packages from that source then - you should also remove their public key from the - rpm keyring. To remove a public key you first - need to know the identification name used by - rpm. You may view the details of all public - keys with the command: + In addition, remove the public key for the package provider from + the rpm keyring, if you will not be using any + more packages from that source. + + + + To remove a public key from the keyring you must know the + identification name used by rpm. Run this + command to view the details of the public keys on the keyring: rpm -qi gpg-pubkey-* @@ -1397,9 +1406,7 @@ from &FC; in order to be able to make repositories. - - To make a directory into a yum repository, carry the following tasks. These instructions assume that the @@ -1433,7 +1440,8 @@ In the terminal window type: createrepo -g - /var/www/repository/groups.xml /var/www/repository/. + /var/www/repository/groups.xml + /var/www/repository/. @@ -1459,10 +1467,10 @@ Create a definition file for this new repository. If you are distributing packages that you have created yourself then you also need to make the GPG public key for your signature - available, so that others can verify the packages. The simplest - way to make these files available is to put the public key and - repository definition files on the same Website or FTP site as - the repository. + available, so that others are able to verify the packages. The + simplest way to make these files available is to put the public + key and repository definition files on the same Website or FTP + site as the repository. @@ -1641,7 +1649,7 @@ If possible, list more than one directory or server that holds a copy of the repository. This enables yum to - use another repository if the first is unavailable. By default + use another repository if the first is unavailable. By default, yum randomly selects repositories from the baseurl list. To force yum to use them in sequence, add the option @@ -1649,13 +1657,13 @@ - It is also good practice to use variables like - $releasever in the URL, rather than setting - these to a specific value. The available variables are listed on - the man page for - yum.conf. Using variables enables the same + Write the URL with variables, such as + $releasever, rather than specifying fixed + values for these attributes. Using variables enables the same definition to function when your system is upgraded to a later version, or if the configuration is copied to another machine. + The available variables are listed on the man + page for yum.conf. @@ -1672,8 +1680,8 @@ yum will access the FTP server with the username yum-user and the password qwerty. The failovermethod - ensures that yum will check the copy on the - local machine, before trying the servers in sequence. + ensures that yum checks the copy on the local + system, before trying the servers in sequence. @@ -1712,12 +1720,12 @@ Whenever a package is added, or replaced with a different - version, you must run createrepo again for - the index files to be updated. If you are mirroring an existing - repository then you may assume that the site administrator - updates the indexes, but for safety you should add this to your - synchronization scripts. The createrepo - utility can be run as frequently as you wish. + version, you must run createrepo again to + update the index files. If you are mirroring an existing + repository then add createrepo to your + synchronization scripts, even though the original copy may have + index files. This ensures that the indexes on your copy of the + site are accurate. From fedora-docs-commits at redhat.com Mon Jul 18 21:39:31 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Mon, 18 Jul 2005 17:39:31 -0400 Subject: yum-software-management yum-software-management-en.xml,1.12,1.13 Message-ID: <200507182139.j6ILdVlW018662@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18638 Modified Files: yum-software-management-en.xml Log Message: - Removed repository creation/managment material, so that this document focuses on the use of yum itself. - More style fixes. - Moved localinstall and proxy server sections to the end, since they aren't standard usages. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- yum-software-management-en.xml 18 Jul 2005 19:25:35 -0000 1.12 +++ yum-software-management-en.xml 18 Jul 2005 21:39:27 -0000 1.13 @@ -91,14 +91,6 @@ - If you have several &FED; systems on a network you may benefit - from setting up their own software repositories to manage the - process of installation and updates. Refer to - for the details of - maintaining your own repositories. - - - Most of the examples in this document use the package tsclient, which is included with &FC;. The tsclient package provides an application @@ -265,9 +257,8 @@ You may also manage related packages as sets by using the package groups provided by the &FED; - repositories. Third-party repositories may add packages to these - groups, or provide packages in additional groups where - necessary. + repositories. Some third-party repositories add packages to + these groups, or provide their packages as additional groups. @@ -909,110 +900,6 @@ -
- Using <command>yum</command> with a Proxy Server - - proxy server, with yum - - - yum, using a proxy server - - - Repositories may be accessed through standard Web proxy servers. - If your system is connected to the Internet through a Web proxy - server, specify the details of the server in - /etc/yum.conf. The proxy - setting must specify the proxy server as a complete URL, including - the TCP port number. If your proxy server requires a username and - password, specify these by adding - proxy_username and - proxy_password settings. - - - - For example, the settings below enable yum to - use the proxy server mycache.mydomain.com, - connecting to port 3128, with the username - yum-user and the password - qwerty. - - - - Configuration File Settings for Using A Proxy Server - - - - - - - Global Settings - - - Defining a proxy server in /etc/yum.conf - means that all users connect to the proxy - server with those details when using yum. - - - - - To enable proxy access for a specific user, add the lines in the - example box below to their shell profile. For the default - bash shell, the profile is the file - .bash_profile. The settings below enable - yum to use the proxy server - mycache.mydomain.com, connecting to port - 3128. - - - - Profile Settings for Using a Proxy Server - - - - - - - If the proxy server requires a username and password then add - these to the URL. For example, to include the username - yum-user and the password - qwerty: - - - - Profile Settings for a Secured Proxy Server - - - - - - - <command>http_proxy</command> Variable with Other Utilities - - - The http_proxy variable is also used by - curl and other utilities. Although - yum itself may use - http_proxy in either upper-case or - lower-case, curl requires the name of the - variable to be in lower-case. - - -
-
Using Other Software Repositories @@ -1025,9 +912,9 @@ searching for repositories - &FC; automatically uses the &FED; repositories. These include - &FEX;, the default source of packages for software that is not - included with &FC;. + &FED; systems automatically use the &FP; repositories. These + include &FEX;, the default source of packages for software that is + not included with &FC;. @@ -1044,8 +931,8 @@ - If the &FED; project does not provide packages for a specific - piece of software, the manufacturer of the software may provide or + If the &FP; does not provide packages for a specific piece of + software, the manufacturer of the software may provide or recommend a separate repository. Members of the community also maintain repositories to provide packages for &FED; systems. Third-party repositories provide information on their Websites. @@ -1100,10 +987,10 @@ Repositories and <application>up2date</application> Channels - On &FC; &FCLOCALVER; systems yum + On &FED; &FCLOCALVER; systems yum repositories are automatically used as up2date channels. Repositories must - be separately configured as channels on &FC; 3 and earlier + be separately configured as channels on &FED; 3 and earlier systems. @@ -1143,7 +1030,7 @@ The up2date utility automatically - uses the public key for &FC; packages. It does not add the + uses the public key for &FED; packages. It does not add the public key to the keyring that is used by both yum and the rpm utility. @@ -1167,28 +1054,27 @@ Before attempting to use a repository, read the Website for - information on package compatibility. . Repositories often - provide packages that are specifically intended for use with - packages that are supplied by other repositories. In some cases - separate third-party repository providers may each offer - different versions of the same software, preventing those - repositories from being safely used together by your &FC; - system. + information on package compatibility. Repositories often provide + packages that are specifically intended for use with packages + that are supplied by other repositories. In some cases separate + third-party repository providers may each offer different + versions of the same software, preventing those repositories + from being safely used together by your &FED; system. - Packages that have been made for one version of &FC; are usually - not compatible with other versions of &FC;. The Website of the - provider should specifically state which versions of &FC; they - support. + Packages that have been made for one version of &FED; are + usually not compatible with other versions of &FED;. The Website + of the provider should specifically state which versions of + &FED; they support. Old Versions of <command>yum</command> and Current Repositories The data format for repository indexes changed with version 2.11 of yum. This was the version supplied - with &FC; 3. Repository providers should specify the versions - of &FC; that they support. To confirm that an unlabeled + with &FED; 3. Repository providers should specify the versions + of &FED; that they support. To confirm that an unlabeled repository is compatible with current versions of yum, check that it has a sub-directory called repo-data/. @@ -1197,56 +1083,6 @@
-
- Manually Installing Software - - installing software with yum (from a package) - - - software, installing from a package - - - Use repositories and the standard yum commands - to install new software, unless the software is only available as - a package. In these cases, use the - option to install the software from the package file without - connecting to any repository. - - - - Public Key is Required - - - You must ensure that the public key for the package source has - been imported before installing a package without a repository. - Refer to - - - - - As an example, enter this command to install the package - tsclient-0.132-4.i386.rpm: - - -su -c 'yum localinstall tsclient-0.132-4.i386.rpm' - - - Enter the root password - when prompted. - - - - Dependencies Must Be Met - - - You must ensure that all of the dependencies are already - installed on your system, as yum cannot - download additional packages to complete the installation in - this mode. - - -
-
Maintaining <command>yum</command> @@ -1255,8 +1091,8 @@ maintenance. It is useful to disable or remove repository definitions that are no longer required, as each repository that is defined and enabled is checked for every operation. You may - also wish to periodically remove files relating to unwanted - packages, in order to save disk space. + also remove files relating to unwanted packages, in order to + recover disk space.
@@ -1363,371 +1199,161 @@
-
- Managing <command>yum</command> Repositories - + + +
+ Manually Installing Software + + installing software with yum (from a package) + + + software, installing from a package + - You may wish to create your own software repositories, or maintain - a copy of another repository. + Use repositories and the standard yum commands + to install new software, unless the software is only available as + a package. In these cases, use the + function to install the software from the package file. The + function does not connect to any + repository. - - Old versions of yum use a different repository utility - - - These procedures create repositories that are compatible with - version 2.11 of yum and above. You must use - the yum-arch utility that was included with - yum 2.10 to enable repositories for older - versions of yum. - - + + Public Key is Required -
- Creating a New Repository - - repositories, creating - - A software repository is simply a directory containing package - files, with a sub-directory for the package index files used by - yum. The main directory may also contain - other types of file without interfering with the use of the - repository. Do not modify the data/ - sub-directory and the XML files within it. These are created and - updated with the createrepo utility. + You must ensure that the public key for the package source has + been imported before installing a package without a repository. + Refer to + - - Creating Repositories Requires an Extra Package - - - You must install the createrepo package - from &FC; in order to be able to make repositories. - - - - - To make a directory into a yum repository, - carry the following tasks. These instructions assume that the - repository is the directory - /var/www/repository/, and that the package - group index file is called groups.xml: - - - - Copy the RPM packages that you are distributing into the - directory. - - - - - Create a groups file, as explained in - - - - - - Open a terminal window. - - - - - In the terminal window type: createrepo - /var/www/repository. - - - - - In the terminal window type: createrepo -g - /var/www/repository/groups.xml - /var/www/repository/. - - - - - In the terminal window type: chmod a+x - /var/www/repository/repodata/. - - - - - Ensure that the directory is available with your chosen - network protocols (HTTP, FTP, or NFS). - - - - + + As an example, enter this command to install the package + tsclient-0.132-4.i386.rpm: + + +su -c 'yum localinstall tsclient-0.132-4.i386.rpm' + + + Enter the root password + when prompted. + - - The repository is now ready for use. - + + Dependencies Must Be Met - Create a definition file for this new repository. If you are - distributing packages that you have created yourself then you - also need to make the GPG public key for your signature - available, so that others are able to verify the packages. The - simplest way to make these files available is to put the public - key and repository definition files on the same Website or FTP - site as the repository. + You must ensure that all of the dependencies are already + installed on your system, as yum cannot + download additional packages to complete the installation when + performing a operation. + +
- - Creating a definition file is described in - . Packaging building is - beyond the scope of this document. - - - Repositories and Management Utilities - - The createrepo utility makes no changes to - the directory other than adding a - repo-data/ sub-directory. Adding index - files for other utilities does not interfere with - yum. - - -
+
+ Using <command>yum</command> with a Proxy Server + + proxy server, with yum + + + yum, using a proxy server + + + Repositories may be accessed through standard Web proxy servers. + If your system is connected to the Internet through a Web proxy + server, specify the details of the server in + /etc/yum.conf. The proxy + setting must specify the proxy server as a complete URL, including + the TCP port number. If your proxy server requires a username and + password, specify these by adding + proxy_username and + proxy_password settings. + -
- Package Group Index Files - - - package group index files, creating - - - package group index files, editing - - - Create and edit package group files with a text editor. - Definition files are XML with a standard format: - + + For example, the settings below enable yum to + use the proxy server mycache.mydomain.com, + connecting to port 3128, with the username + yum-user and the password + qwerty. + - - Format of <command>yum</command> Group Index Files + + Configuration File Settings for Using A Proxy Server - - - - - group-id - Group Name - Descriptive Text. - true or false - true or false - - group-name - - - package-name or package-name - - - - - Category Name - - Name of Member Group - - - - - ]]> - - - - - The id and name that - identify each group must either match those of a &FED; package - group, or be unique. If the group matches a &FED; package group - then systems using the repository add the the listed packages to - that group when carrying out yum operations. - - - - The example group file shown below defines the package groups - Base and Site Custom Application - Packages. The Base package group - adds extra mandatory packages to the &FED; package group for the - systems using the repository. Site Custom Application - Packages provides three packages. - + + + - - Example <command>yum</command> Group Index File - - - - - - base - Base - Additional packages for the Fedora Base package group. - true - true - - my-customadminpackage - my-othercustomadminpackage - - - site-apps - Site Custom Application Packages - Custom group for the site-specific applications. - false - true - - base - - - my-customapplication - my-othercustomapplication - my-optionalcustomapplication - - - - Site Custom Packages - - Site Custom Application Packages - - - - - ]]> - - -
+ + Global Settings -
- Repository Definition Files - - repository definition files, creating - - - repository definition files, editing - - Create and edit repository definition files with a text editor. - Definition files are plain-text with a standard format: + Defining a proxy server in /etc/yum.conf + means that all users connect to the proxy + server with those details when using yum. + - - Format of <command>yum</command> Repository Definition Files - - - - - - - The baseurl must specify the complete URL for - the root directory of - the repository, including the http://, - https:// or ftp:// prefix. - You may also specify a directory on your system, by using the - prefix file:// in the - baseurl. - - - Logging in to Protected Repositories - - To use a password-protected repository, include the correct - username and password in the baseurl. For - example, - ftp://user:password at myrepository.com/$releasever/mypackages/. - - - - If possible, list more than one directory or server that holds a - copy of the repository. This enables yum to - use another repository if the first is unavailable. By default, - yum randomly selects repositories from the - baseurl list. To force yum - to use them in sequence, add the option - failovermethod=priority. - + + To enable proxy access for a specific user, add the lines in the + example box below to their shell profile. For the default + bash shell, the profile is the file + .bash_profile. The settings below enable + yum to use the proxy server + mycache.mydomain.com, connecting to port + 3128. + - - Write the URL with variables, such as - $releasever, rather than specifying fixed - values for these attributes. Using variables enables the same - definition to function when your system is upgraded to a later - version, or if the configuration is copied to another machine. - The available variables are listed on the man - page for yum.conf. - + + Profile Settings for Using a Proxy Server + + + + - - The definition file shown below uses all of these features. In - this example, copies of the repository are held in the directory - /srv/software/&FED;/&FCVER;/mypackages/ on - the system itself, in the directory - software/&FED;/&FCVER;/mypackages/ on the - Web server www.my-repository.com/, and - in the directory - pub/software/&FED;/&FCVER;/mypackages/ on - the FTP server - server.another-repository.org. Here, - yum will access the FTP server with the - username yum-user and the password - qwerty. The failovermethod - ensures that yum checks the copy on the local - system, before trying the servers in sequence. - + + If the proxy server requires a username and password then add + these to the URL. For example, to include the username + yum-user and the password + qwerty: + - - A <command>yum</command> Repository Definition File with Failover + + Profile Settings for a Secured Proxy Server - - - - - - To use a list of servers, substitute - mirrorlist for baseurl. - + + + - - Set gpgcheck=0 if it is necessary to disable - signature checking for the packages provided by this repository. - Avoid distributing or installing unsigned packages. - -
+ + <command>http_proxy</command> Variable with Other Utilities -
- Updating a Repository - - repositories, updating - - Whenever a package is added, or replaced with a different - version, you must run createrepo again to - update the index files. If you are mirroring an existing - repository then add createrepo to your - synchronization scripts, even though the original copy may have - index files. This ensures that the indexes on your copy of the - site are accurate. + The http_proxy variable is also used by + curl and other utilities. Although + yum itself may use + http_proxy in either upper-case or + lower-case, curl requires the name of the + variable to be in lower-case. -
+
From fedora-docs-commits at redhat.com Mon Jul 18 22:32:08 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Mon, 18 Jul 2005 18:32:08 -0400 Subject: securing-filesystems - Imported sources Message-ID: <200507182232.j6IMW8E5019905@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19891 Log Message: Securing Filesystems Documentation Status: Vendor Tag: trjones Release Tags: devel No conflicts created by this import From fedora-docs-commits at redhat.com Mon Jul 18 22:45:26 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Mon, 18 Jul 2005 18:45:26 -0400 Subject: securing-filesystems/images - New directory Message-ID: <200507182245.j6IMjQho019953@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems/images In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19939/images Log Message: Directory /cvs/docs/securing-filesystems/images added to the repository From fedora-docs-commits at redhat.com Tue Jul 19 02:36:07 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Mon, 18 Jul 2005 22:36:07 -0400 Subject: yum-software-management yum-software-management-en.xml,1.13,1.14 Message-ID: <200507190236.j6J2a7Fn025134@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25117 Modified Files: yum-software-management-en.xml Log Message: More style fixes. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- yum-software-management-en.xml 18 Jul 2005 21:39:27 -0000 1.13 +++ yum-software-management-en.xml 19 Jul 2005 02:36:04 -0000 1.14 @@ -1,10 +1,10 @@ - %FEDORA-ENTITIES-EN; - + @@ -42,7 +42,7 @@ 0.5 - 2005-07-18 + 2005-07-19 StuartEllis @@ -99,7 +99,9 @@ ApplicationsInternetTerminal Server Client. To use the examples, substitute the name of the relevant package for - tsclient. + tsclient. The &FED; package group + MySQL Database is used for the package + group examples. @@ -108,7 +110,7 @@ You do not need to log in with the root account in - order to manage your &FC; system. All of the commands shown in + order to manage your &FED; system. All of the commands shown in this tutorial that require root access will prompt you for the @@ -261,6 +263,17 @@ these groups, or provide their packages as additional groups. + + + Available Package Groups + + + To view a list of all of the available package groups for your + &FED; system, run the command yum + . + + + Using repositories ensures that you always receive the current version of the software. If several versions of the same package @@ -276,6 +289,18 @@ find or install newer versions. You must keep that product updated yourself. + + + Manual Package Installation + + + The yum commands shown in this document use + repositories as package sources. Refer to + for details of + using yum to manually install software from + a package file. + +
@@ -711,7 +736,7 @@
- Searching with <command>yum</command> + Searching for Packages with <command>yum</command> packages, locating @@ -790,7 +815,7 @@ To search for all packages that include files called - libneon you type: + libneon, type: yum provides libneon @@ -866,14 +891,14 @@ automatic updating - If your system is permanently connected to the network then - updates can be performed at any time. The - yum package includes scripts that can - automatically carry out full updates every day. + If your &FED; system is permanently connected to the network + then updates may be performed at any time. The + yum package includes scripts to + automatically carry out full system updates every day. - To activate automatic daily updating, type this line: + To activate automatic daily updating, enter this command: su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' @@ -921,7 +946,7 @@ &FEX; Repositories for Previous Versions of &FC; - You must manually configure &FC; 3 systems to use &FEX;, using + You must manually configure &FED; 3 systems to use &FEX;, using the instructions at: http://fedora.redhat.com/projects/extras/. Refer to this Website for additional packages for &FC; 1 and @@ -1025,16 +1050,6 @@ su -c 'rpm --import http://www.therepository.com/GPG-PUB-KEY.asc' - - Public Keys and <application>up2date</application> - - - The up2date utility automatically - uses the public key for &FED; packages. It does not add the - public key to the keyring that is used by both - yum and the rpm utility. - -
@@ -1192,8 +1207,8 @@ su -c 'yum clean packages' - In both cases, enter the - root password when + In both cases, enter the password for the + root account when prompted.
From fedora-docs-commits at redhat.com Tue Jul 19 03:56:21 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Mon, 18 Jul 2005 23:56:21 -0400 Subject: release-notes/FC4 kernel.xml,1.9,1.10 Message-ID: <200507190356.j6J3uLoZ026621@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26603 Modified Files: kernel.xml Log Message: Added instructions to set the kernel Makefile variable EXTRAVERSION to match the running kernel. Index: kernel.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/kernel.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- kernel.xml 22 Jun 2005 18:43:07 -0000 1.9 +++ kernel.xml 19 Jul 2005 03:56:19 -0000 1.10 @@ -23,7 +23,7 @@ features. For this reason, the &FC; kernel may not be line-for-line equivalent to the so-called vanilla kernel from the kernel.org + url="http://www.kernel.org">kernel.org web site. @@ -42,12 +42,12 @@ Native kernel, in both uniprocessor and SMP - varieties. + varieties. Configured sources are available in the - kernel-devel-<version>.<arch>.rpm - package. + kernel-devel-<version>.<arch>.rpm + package. @@ -56,19 +56,19 @@ Configured sources are available in the - kernel-xen0-devel-<version>.<arch>.rpm - package. + kernel-xen0-devel-<version>.<arch>.rpm + package. Sources for both kernel flavors may be installed at the same time. The files will be installed into the - /usr/src/kernels/<version>[-xen0]-<arch>/ + /usr/src/kernels/<version>[-xen0]-<arch>/ tree. Use the command: -rpm -Uvh kernel-devel[-xen0]-<version>.<arch>.rpm +rpm -Uvh kernel-devel[-xen0]-<version>.<arch>.rpm as appropriate. @@ -77,11 +77,11 @@ Following Generic Textbooks Many of the tutorials, examples, and textbooks about Linux - kernel development assume the kernel sources are installed under - the /usr/src/linux directory. If you make a - symbolic link, as shown below, you should be able to use those - learning materials with the &FC; packages. Install the - appropriate kernel sources, as shown earlier, and then: + kernel development assume the kernel sources are installed under + the /usr/src/linux directory. If you make a + symbolic link, as shown below, you should be able to use those + learning materials with the &FC; packages. Install the + appropriate kernel sources, as shown earlier, and then: ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux @@ -112,7 +112,7 @@ kernel-source package provided by older versions. Instead, configured sources are available as described in . Users that require access to &FC; + linkend="sn-kernel-flavors"/>. Users that require access to &FC; original kernel sources can find them in the kernel .src.rpm package. To create an exploded source tree from this file, perform the @@ -121,12 +121,12 @@ These Instructions Refer to the Currently-running Kernel! - To simplify the following directions, we have assumed that you - want to configure the kernel sources to match your - currently-running kernel. In the steps below, you must - understand that the phrase - <version> refers to the kernel - version shown by this command: + To simplify the following directions, we have assumed that you + want to configure the kernel sources to match your + currently-running kernel. In the steps below, you must + understand that the phrase + <version> refers to the kernel + version shown by this command: uname -r @@ -136,15 +136,15 @@ Obtain the - kernel-<version>.src.rpm - file from one of the following sources: + kernel-<version>.src.rpm + file from one of the following sources: - The SRPMS directory on the - appropriate SRPMS - CD iso image. + The SRPMS directory on the + appropriate SRPMS + CD iso image. @@ -165,16 +165,16 @@ Install - kernel-<version>.src.rpm - using the command: + kernel-<version>.src.rpm + using the command: rpm -Uvh kernel-<version>.src.rpm This writes the RPM contents into - /usr/src/redhat/SOURCES and - /usr/src/redhat/SPECS. + /usr/src/redhat/SOURCES and + /usr/src/redhat/SPECS. @@ -187,12 +187,12 @@ The kernel source tree will be located in the - /usr/src/redhat/BUILD/kernel-<version> - directory. It is common practice to move the resulting - linux-<version> - directory to the /usr/src tree; while not - strictly necessary, we suggest that you do this to match the - generally-available documentation. + /usr/src/redhat/BUILD/kernel-<version> + directory. It is common practice to move the resulting + linux-<version> + directory to the /usr/src tree; while not + strictly necessary, we suggest that you do this to match the + generally-available documentation. cd /usr/src/redhat/BUILD/kernel-<version> /usr/src/ @@ -205,16 +205,37 @@ The configurations for the specific kernels shipped in - &DISTRO; &DISTROVER; are in the configs/ - directory. For example, the i686 SMP configuration file is - named - configs/kernel-<version>-i686-smp.config. - Issue the following command to place the desired configuration - file in the proper place for building: + &DISTRO; &DISTROVER; are in the configs/ + directory. For example, the i686 SMP configuration file is + named + configs/kernel-<version>-i686-smp.config. + Issue the following command to place the desired configuration + file in the proper place for building: cp configs/<desired-config-file> .config + + You can also find the .config file that matches your current kernel configuration in the /lib/modules/<version>/build/.config file. + + + + + Every kernel gets a name based on its version number. + This is the value the uname -r command displays. + The kernel name is defined by the first four lines of the kernel Makefile. + To protect the innocent, the Makefile has been changed to generate a kernel with a different name from that of the running kernel. + Before a module will be accepted by the running kernel, that module must have been compiled for a kernel with the correct name. + + + Assume that uname -r returns the string 2.6.11-1.234_FC4 and correct the kernel name by editing the kernel Makefile, changing the EXTRAVERSION definition from this: + + EXTRAVERSION = -prep + to this: + EXTRAVERSION = -1.234_FC4 + + that is, substitude everything from the final dash onward. + @@ -263,13 +284,13 @@ utilities, such as management daemons. Consequently, to remove such a kernel, perhaps after an update, you cannot simply use the rpm -e - kernel-<version> + kernel-<version> command as in earlier distributions because these userspace packages depend on the kernel package. You may either list both the kernel package and its userspace dependant packages on the rpm -e command, or you may wish to use the yum remove - kernel-<version> + kernel-<version> command instead since yum automatically removes dependant packages if necesssary. From fedora-docs-commits at redhat.com Tue Jul 19 04:24:10 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 19 Jul 2005 00:24:10 -0400 Subject: release-notes/FC4 kernel.xml,1.10,1.11 Message-ID: <200507190424.j6J4OA3m027782@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27765 Modified Files: kernel.xml Log Message: Small edits for clarity. I notice that tidy-bowl has not been run on this before check-in, you might want to do that manually, there was a lot of whitespace diff because of non-standard indenting in the last check-in. Index: kernel.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/kernel.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- kernel.xml 19 Jul 2005 03:56:19 -0000 1.10 +++ kernel.xml 19 Jul 2005 04:24:07 -0000 1.11 @@ -225,10 +225,12 @@ This is the value the uname -r command displays. The kernel name is defined by the first four lines of the kernel Makefile. To protect the innocent, the Makefile has been changed to generate a kernel with a different name from that of the running kernel. - Before a module will be accepted by the running kernel, that module must have been compiled for a kernel with the correct name. + Before a module can be accepted by the running kernel, that + module must have been compiled for a kernel with the correct + name. To do this, you must edit the kernel Makefile - Assume that uname -r returns the string 2.6.11-1.234_FC4 and correct the kernel name by editing the kernel Makefile, changing the EXTRAVERSION definition from this: + For example, if the uname -r returns the string 2.6.11-1.234_FC4, change the EXTRAVERSION definition from this: EXTRAVERSION = -prep to this: From fedora-docs-commits at redhat.com Tue Jul 19 04:59:40 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Tue, 19 Jul 2005 00:59:40 -0400 Subject: docs-common/common cvs-en.xml,1.4,1.5 Message-ID: <200507190459.j6J4xeD9028025@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28008 Modified Files: cvs-en.xml Log Message: Tidy bowl normalization. Index: cvs-en.xml =================================================================== RCS file: /cvs/docs/docs-common/common/cvs-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- cvs-en.xml 14 May 2005 20:00:15 -0000 1.4 +++ cvs-en.xml 19 Jul 2005 04:59:38 -0000 1.5 @@ -1,4 +1,5 @@ + + CVS - - The Concurrent Versions System (CVS) provides a framework where multiple users can edit the same files. - As you can imagine, if a group of users edits the files in a single directory, chaos would reign. - Using CVS, however, a group of people can safely work on the same set of files. - CVS keeps the master copy of the files, and it records who changed what and when in a central repository. - If conflicts arise, CVS lets you know. - CVS is often used so that programmers can share code, but it also works well for documentation. - - + The Concurrent Versions System (CVS) + provides a framework where multiple users can edit the same files. + As you can imagine, if a group of users edits the files in a single + directory, chaos would reign. Using CVS, + however, a group of people can safely work on the same set of files. + CVS keeps the master copy of the files, + and it records who changed what and when in a central repository. If + conflicts arise, CVS lets you know. + CVS is often used so that programmers can + share code, but it also works well for documentation. + cvs -
How CVS Works - cvs how it works - cvs overview - - In most cases, each set of files that make up a package or project is stored as a module on the CVS server. + In most cases, each set of files that make up a package or project + is stored as a module on the CVS server. - When working with files from CVS, you checkout a copy of the module on your local file system. - After modifying one or more files, you commit them back to the central CVS repository server. + When working with files from CVS, you + checkout a copy of the module on your local + file system. After modifying one or more files, you + commit them back to the central + CVS repository server. - With CVS you may edit a file without first getting permission or locking the file. - The concurrent part of the CVS name comes from its ability to allow several different people to edit different parts of the same file. - As long as none of the changes overlap, CVS can correctly record their changes. - In case of duplicate changes, they are clearly marked in the files and the authors must resolve the issue among themselves. + With CVS you may edit a file without + first getting permission or locking the file. The + concurrent part of the + CVS name comes from its ability to + allow several different people to edit different parts of the same + file. As long as none of the changes overlap, + CVS can correctly record their changes. + In case of duplicate changes, they are clearly marked in the files + and the authors must resolve the issue among themselves. - When you commit changes, only changes to files the server knows about are committed. - In other words, if you created a file in your local checkout of a module, the new file is not automatically uploaded to the server. - You must add the file to the repository and then commit it. - If you remove a file from your local checkout of a module, you must specify that you want to remove it from the repository on the CVS server and then commit the removal of the file. + When you commit changes, only changes to files the server knows + about are committed. In other words, if you created a file in your + local checkout of a module, the new file is not automatically + uploaded to the server. You must add the + file to the repository and then commit it. If you remove a file + from your local checkout of a module, you must specify that you + want to remove it from the repository on the CVS server and then + commit the removal of the file. - The specific commands to perform these actions are discussed in . + The specific commands to perform these actions are discussed in + . - If someone has modified the file between the last time you grabbed the file from CVS and when you try to commit a change, CVS will try to merge the changes into the master copy of the CVS server. - If the content you changed is in a different location in the file than the content changed by someone else, chances are, the commit action will go through without a conflict. - If someone modified the same content as the content you just changed and tried to commit, you will see a message that a file conflict has occurred. - Thus, you need to update your files frequently. - It is a good practice to update them right before you start modifying a file. - Refer to for instructions on resolving conflicts. - - + If someone has modified the file between the last time you grabbed + the file from CVS and when you try to commit a change, + CVS will try to merge the changes into + the master copy of the CVS server. If + the content you changed is in a different location in the file + than the content changed by someone else, chances are, the commit + action will go through without a conflict. + If someone modified the same content as the content you just + changed and tried to commit, you will see a message that a file + conflict has occurred. Thus, you need to + update your files frequently. It is a good + practice to update them right before you start modifying a file. + Refer to for + instructions on resolving conflicts. +
-
Preparing For CVS Use - cvs preparing for use - - Before using CVS, you need to establish an account with the CVS server. - After getting an account, you do not need to perform these actions again. + Before using CVS, you need to establish + an account with the CVS server. After + getting an account, you do not need to perform these actions + again.
Is CVS Installed On Your System - cvs RPM installation - You must have the CVS - RPM package installed. - Verify its presence by typing the command: + RPM package installed. Verify its presence by + typing the command: - - $ rpm -q cvs - +$ rpm -q cvs - If you see output similar to cvs-1.11.19-1, then the package is installed. - A message similar to package cvs is not installed means you must install the cvs package before continuing. - If you do not know how to do this, consult your system administrator who can install it for you. + If you see output similar to + cvs-1.11.19-1, then the package + is installed. A message similar to package cvs + is not installed means you must install the + cvs package before continuing. If you + do not know how to do this, consult your system administrator + who can install it for you. -
@@ -119,348 +138,382 @@ OpenSSH authorization keys - - The CVS server uses SSH Protocol 2 keys to authenticate users. - Thus, you need to generate a pair of keys before applying for a CVS account. - If you already have an SSH - DSA key, you may skip this step. + The CVS server uses + SSH Protocol 2 keys to authenticate + users. Thus, you need to generate a pair of keys before applying + for a CVS account. If you already + have an SSH DSA key, + you may skip this step. - Tip - You already have a DSA key if you have the file ~/.ssh/id_dsa.pub on the system. + You already have a DSA key if you have the + file ~/.ssh/id_dsa.pub on the system. - If your existing DSA key does not require a passphrase, you are strongly urged to generate one that does require a passphrase. + If your existing DSA key does not require a + passphrase, you are strongly urged to + generate one that does require a passphrase. - - Use the following steps to generate a DSA key used by SSH Protocol 2. - It is required for an cvs.fedora.redhat.com + Use the following steps to generate a DSA key + used by SSH Protocol 2. It is + required for an + cvs.fedora.redhat.com CVS account. OpenSSH - - ssh-keygen + ssh-keygen - - ssh-keygen + ssh-keygen - To generate a DSA key to work with version 2.0 protocol, at a shell prompt, type the command: + To generate a + DSA + key to work with version 2.0 protocol, at a shell prompt, + type the command: - $ ssh-keygen -t dsa +$ ssh-keygen -t dsa - Accept the default file location of ~/.ssh/id_dsa. - You are strongly urged to define and use a passphrase to enhance the security of your key. - Enter a passphrase different than your account password and confirm it by entering it again. + Accept the default file location of + ~/.ssh/id_dsa. You are strongly urged + to define and use a passphrase to + enhance the security of your key. Enter a passphrase + different than your account password and confirm it by + entering it again. - Copy your new key to the correct file by typing the following at a shell prompt. + Copy your new key to the correct file by typing the + following at a shell prompt. - $ cat ~/.ssh/id_dsa.pub>>~/.ssh/authorized_keys +$ cat ~/.ssh/id_dsa.pub>>~/.ssh/authorized_keys - Check this command carefully before you press the ENTER key. - If ~/.ssh/authorized_keys already exists, the contents of ~/.ssh/id_dsa.pub will be appended to the end of the ~/.ssh/authorized_keys file. + Check this command carefully before you press the + ENTER + key. If ~/.ssh/authorized_keys + already exists, the contents of + ~/.ssh/id_dsa.pub will be appended to + the end of the ~/.ssh/authorized_keys + file. - Change the permissions of your ~/.ssh directory and your keys with the commands: - - $ chmod 755 ~/.ssh + Change the permissions of your ~/.ssh + directory and your keys with the commands: + +$ chmod 755 ~/.ssh $ chmod 644 ~/.ssh/authorized_keys - Tip - You can have your system remember your passphrase so that you do not have to type it every time you access the CVS server. - Refer to the documentation of the ssh-add program. + You can have your system remember your passphrase so that you + do not have to type it every time you access the + CVS server. Refer to the + documentation of the ssh-add + program.
-
-
Configuring For CVS Access - cvs configuring for access - cvs CVSROOT - cvs CVS_RSH - CVSROOT - CVS_RSH - cvs - - .cvsrc + .cvsrc - - .cvsrc + .cvsrc -
Avoiding Repetitive Typing - cvs avoiding repetitive typing - - Many CVS commands need certain command line switches to operate consistently. - Rather than typing them every time that command is used, you can save the switches in a file that CVS will read before executing your command line. + Many CVS commands need certain + command line switches to operate consistently. Rather than + typing them every time that command is used, you can save the + switches in a file that CVS will read + before executing your command line. - Create a file named ~/.cvsrc in your home directory. - It should contain the following commands, one per line: + Create a file named ~/.cvsrc in your home + directory. It should contain the following commands, one per + line: cvs -z3 diff -uNp rdiff -uNp update -dP -
Configuring for Read-Only CVS Access - cvs configuring read-only access - cvs anonymous access - - If your goal is to download the various &FC; documents and to render them on your system, you only need read-only access to the CVS repository. - Follow the instructions in this section and then skip directly to . + If your goal is to download the various &FC; documents and to + render them on your system, you only need read-only access to + the CVS repository. Follow the + instructions in this section and then skip directly to + . - Change directories to where you want your files from CVS to be located, and execute the following commands: + Change directories to where you want your files from + CVS to be located, and execute the + following commands: - $ export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs +$ export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs $ cvs login $ cvs checkout docs-setup module-name $ cvs checkout module-name $ cd module-name - - Once you have checked the module out, it doesn't matter what your CVSROOT is set to because it is stored in the file CVS/Root for each directory in your local repository. - As long as your current working directory has a CVS/ directory, the CVS program will automatically locate the &FC; repository. - - + Once you have checked the module out, it doesn't matter what + your + CVSROOT + is set to because it is stored in the file + CVS/Root for each directory in your local + repository. As long as your current working directory has a + CVS/ directory, the + CVS program will automatically locate + the &FC; repository. +
Configuring Read/Write CVS Access - cvs configuring read/write access - cvs configuring access for authors - - To author a new document or to change an existing one, you must obtain full read/write access to the &FC; Docs CVS repository. - For the full details on this process, refer to the http://fedoraproject.org/wiki/DocsProject/NewWriters - web site. - Below is a summary: + To author a new document or to change an existing one, you must + obtain full read/write access to the &FC; Docs + CVS repository. For the full details + on this process, refer to the + http://fedoraproject.org/wiki/DocsProject/NewWriters + web site. Below is a summary: - Subscribe to the fedora-docs-list + Subscribe to the + fedora-docs-list , which is the main forum for the project. - + - Generate a GNU Privacy Guard (GPG) key to identify yourself to the project. - + Generate a GNU Privacy Guard (GPG) key to + identify yourself to the project. + - Register for a Bugzilla + Register for a + Bugzilla account, if you do not have one already. - Bugzilla is how we keep track of bugs, changes and projects. - + Bugzilla is how we keep track of bugs, + changes and projects. + - Post a self introduction to the list. - + Post a + self + introduction to the list. + - After your self introduction has been approved your CVS access will be granted. + After your + self + introduction has been approved your + CVS access will be granted. - Every author, and that includes you once your self introduction has been received, has a unique $CVSROOT to access the CVS repository: + Every author, and that includes you once your self introduction + has been received, has a unique + $CVSROOT + to access the CVS repository: - - $ export CVSROOT=:ext:yourname@cvs.fedora.redhat.com:/cvs/docs +$ export CVSROOT=:ext:yourname@cvs.fedora.redhat.com:/cvs/docs $ export CVS_RSH=/usr/bin/ssh - - - With the $CVSROOT and $CVS_RSH environment variables in place, you can access the repository: - - - $ cvs co -c - - You will be asked for the passphrase for your SSH key. - Press ENTER and you should receive a list of modules already in the repository. + With the + $CVSROOT + and + $CVS_RSH + environment variables in place, you can access the repository: + +$ cvs co -c + + You will be asked for the passphrase for your + SSH key. Press + ENTER + and you should receive a list of modules already in the + repository.
- -
- -
- Basic CVS Commands - +
+
+ Basic CVS Commands + + cvs + commands + + + After configuring your system to work with CVS, checkout the + modules you will be working on. + + + Tip + + To see if you need a correctly-set + $CVSROOT + variable, or the + repository command line switch, see + if you have a CVS/ subdirectory in your + working directory. + + + If you have a CVS/ directory, + CVS ignores any + $CVSROOT + or command line switch. + + +
+ Checking Out Modules cvs - commands + checking out modules - - After configuring your system to work with CVS, checkout the modules you will be working on. - - - - Tip - - To see if you need a correctly-set $CVSROOT variable, or the - repository command line switch, see if you have a CVS/ subdirectory in your working directory. - - - If you have a CVS/ directory, CVS ignores any $CVSROOT or command line switch. - - - -
- Checking Out Modules - - - cvs - checking out modules - - - - You only need to checkout a module once. After a local copy of the module is on your system, it is on your system. + You only need to checkout a module once. After a local copy of + the module is on your system, it is on your system. - + To checkout a module, use the following command: - - $ cvs co <module-name> - - - For example, to checkout the example-tutorial module, change to your work directory, and execute the following command: +$ cvs co <module-name> + + For example, to checkout the + example-tutorial module, change + to your work directory, and execute the following command: - - $ cvs co example-tutorial - - - A directory called example-tutorial/ is created in the current directory. +$ cvs co example-tutorial + + A directory called example-tutorial/ is + created in the current directory. - - If a branch name is not specified when checking out a module, it is referred to as the HEAD of the CVS module. + + If a branch name is not specified when checking out a module, it + is referred to as the HEAD of the + CVS module. -
- Checking Out Branches of Modules - - - cvs - check out modules - checking out branches - - - - Think of a CVS branch as a version of the files for a particular version of a manual or package. +
+ Checking Out Branches of Modules + + cvs + check out modules + checking out branches + + + Think of a CVS branch as a version + of the files for a particular version of a manual or package. - + To checkout a branch of a module, use the following command: - - $ cvs co <directory> <branchname> <module-name> - - - A directory named <directory> is created, and the files for the <branchname> branch of the <module-name> module are copied in the directory. +$ cvs co <directory> <branchname> <module-name> + + A directory named <directory> + is created, and the files for the + <branchname> branch of the + <module-name> module are + copied in the directory. - - For example, to checkout a branch named BRANCH-VERSION-1.2 from the mymodule module, use the command: + + For example, to checkout a branch named BRANCH-VERSION-1.2 + from the mymodule module, use + the command: - - $ cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule - - - The BRANCH-VERSION-1.2 branch of the module is checked out in the mymodule-1.2 directory on your system. +$ cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule + + The BRANCH-VERSION-1.2 branch of the module is checked out in + the mymodule-1.2 directory on your + system. - - To determine which branches and tags exist for a file, use the command: + + To determine which branches and tags exist for a file, use the + command: - $ cvs status <filename> - - - For example, the status of the file foo.sgml is as follows: - - +$ cvs status <filename> + + For example, the status of the file + foo.sgml is as follows: + + =================================================================== File: foo.sgml Status: Up-to-date @@ -475,264 +528,333 @@ BRANCH-VERSION-1.2 (branch: 1.25.2) - - - Only tags marked as branches in the second column under the Existing Tags section can be checked out as a branch. + + Only tags marked as branches in the second column under the + Existing Tags section can be + checked out as a branch. - -
-
+
-
- Updating Files - - - cvs - updating files - - - - To retrieve the latest versions of the files in a module, change to the directory that contains the files for the module and execute the command: +
+ Updating Files + + cvs + updating files + + + To retrieve the latest versions of the files in a module, change + to the directory that contains the files for the module and + execute the command: + +cvs update + + The latest versions of all the files in the module are + downloaded into your local copy. If you notice a file conflict, + refer to . - cvs update +
- - The latest versions of all the files in the module are downloaded into your local copy. - If you notice a file conflict, refer to . +
+ Committing Files + + cvs + committing files + + + After modifying files in your local version of a module, commit + them to save the changes on the CVS + server: - -
- -
- Committing Files - - - cvs - committing files - - +$ cvs commit "some log message" filename + - After modifying files in your local version of a module, commit them to save the changes on the CVS server: - - $ cvs commit "some log message" filename - - - - If you would prefer to write your log message with your favorite text editor, as defined by the $VISUAL or the $EDITOR environment variable, just omit the -m "some log message". - The buffer will already contain comments describing the change; you do not need to delete them as you enter your own text. + If you would prefer to write your log message with your + favorite text editor, as defined by the $VISUAL or the $EDITOR + environment variable, just omit the -m "some + log message". The buffer will already contain + comments describing the change; you do not need to delete them + as you enter your own text. - + - - The log message should be as descriptive as possible so that you and anyone else working on the module understands what changed. - Using a log message such as updated some files does not accurately describe what has changed and will not help you in the future. - If you are correcting a bug, use the Bugzilla reference. + + The log message should be as descriptive as possible so that you + and anyone else working on the module understands what changed. + Using a log message such as updated some + files does not accurately describe what has changed + and will not help you in the future. If you are correcting a + bug, use the Bugzilla reference. - - The <filename> can be one filename, a series of filenames separated by spaces, or a group of filenames specified using wildcards such as *.png or foo-*.sgml. + + The <filename> can be one + filename, a series of filenames separated by spaces, or a group + of filenames specified using wildcards such as + *.png or foo-*.sgml. - - If no filename or group of filenames is specified in the commit command, all outstanding changes of any kind are committed to the server. - The command is recursive and will include changes in any subdirectories of the module. - Use caution when issuing the commit command without any filenames because you might not remember exactly what files changed. + + If no filename or group of filenames is specified in the + commit command, all outstanding changes of + any kind are committed to the server. The command is recursive + and will include changes in any subdirectories of the module. + Use caution when issuing the commit command + without any filenames because you might not remember exactly + what files changed. - - If you notice a file conflict, refer to . + + If you notice a file conflict, refer to + . +
-
- - -
- Adding Files - - - cvs - adding files - - - - To add a file to a module, create the file in your local copy then execute the following command: +
+ Adding Files + + cvs + adding files + + + To add a file to a module, create the file in your local copy + then execute the following command: - $ cvs add file-to-add - - - After adding the file, you must commit the add to copy it to the server: +$ cvs add file-to-add + + After adding the file, you must commit the + add to copy it to the server: +$ cvs commit "some log message" file-to-add +
- $ cvs commit "some log message" file-to-add - -
- -
- Removing Files - - - cvs - removing files - +
+ Managing Binary Files + + cvs + binary files + + + The most commonly-archived files are simple text files but + sometimes binary files are also archived. The + cvs program recognizes most common + filename extentions such as .png or + .jpg, so cvs + usually "does the right thing". + - - If a file is no longer needed in the module, use the remove command to remove it from your local copy and then commit the removal to the server. - Even though the file is removed from current version of the module, an archived copy is still kept on the server and can be retrieved at any time with the add command. - - $ cvs rm -f file-to-remove + + When a copy of a file is checked out of the repository, + cvs scans it for special keywords, + such as "$id:$" and + replaces the string with a generated value, such as the file + version number. + + + This keyword substitution usually corrupts binary files, so it + must be turned off if cvs does not + recognize your file as binary. To mark your file as being + binary, and thus needing the keyword expansion turned off, use + the command: + +$ cvs filename + + Note that the file must already be checked in to the + CVS repository before the + command can be used. This is OK, since + the keyword expansion is done as the file is checked out and + copied to the local directory, not when the file is committed to + the repository. + + + Recovering a binary file - After removing the file, you must commit the removal: - - - $ cvs commit "some log message" file-to-remove + If you check a binary file into the repository and then find + it corrupted when it is checked out, do not panic. Simply use + the command as described above, delete + your local file copy, and check it out again. + + +
- - You can not use wildcards in the commit command to identify removed files. - They must be specified with a exact filename. +
+ Removing Files + + cvs + removing files + + + If a file is no longer needed in the module, use the + remove command to remove it from your local + copy and then commit the removal to the + server. Even though the file is removed from current version of + the module, an archived copy is still kept on the server and can + be retrieved at any time with the add + command. + +$ cvs rm -f file-to-remove + + After removing the file, you must commit the + removal: + +$ cvs commit "some log message" file-to-remove + + You can not use wildcards in the commit + command to identify removed files. They must be specified with a + exact filename. - - If you need to rename a file, it is best to rename the file on the CVS server so that the history of the file is preserved. - If you need to rename a file, send an email to + + If you need to rename a file, it is best to rename the file on + the CVS server so that the history of + the file is preserved. If you need to rename a file, send an + email to cvsdocs-administrator at fedora.redhat.com - asking to have the file renamed. - - -
- -
- Status of Files - - - cvs - status of files - - - - Sometimes it is necessary to view the status of a file in a CVS module. - To view the status of a file, use the command: + asking to have the file renamed. +
- $ cvs status filename - - +
+ Status of Files + + cvs + status of files + + + Sometimes it is necessary to view the + status of a file in a + CVS module. To view the status of a + file, use the command: + +$ cvs status filename + The status report of a repository file is as follows: - - - - - Up-to-date - - - - Your revision of the file is identical to the latest revision on the CVS server. - - - - - - Locally Modified - - - - You have updated to the latest revision from the server, but then you modified the file on your system. - - - - - - Locally Added - - - - You added the file with the cvs add command but have not yet committed the addition of the file. + + + + + Up-to-date + + + Your revision of the file is identical to the latest + revision on the CVS server. - - - - - Locally Removed - - - - You removed the file with the cvs remove command but have not yet committed the removal. + + + + + Locally Modified + + + You have updated to the latest revision from the server, + but then you modified the file on your system. - - - - - Needs Checkout - - - - A newer version of the file is on the server and needs to be retrieved. - Even though the status includes the word checkout, it really means that you need to update your files with the cvs update command. + + + + + Locally Added + + + You added the file with the cvs add + command but have not yet committed the addition of the + file. - - - - - Needs Patch - - - - The revision in your local checkout needs a patch to be the latest revision from the server. - Issue the cvs update command to resolve. + + + + + Locally Removed + + + You removed the file with the cvs + remove command but have not yet committed the + removal. - - - - - Needs Merge - - - - A newer revision exists on the server and your local version contains modification not yet committed. - This status usually occurs if you don't have the latest revision of the file and edit it anyway. + + + + + Needs Checkout + + + A newer version of the file is on the server and needs to + be retrieved. Even though the status includes the word + checkout, it really means that you need to update your + files with the cvs update command. - - - - - File had conflicts on merge - - - - Similar to Needs Merge, except when you tried to issue the cvs update command, the differences could not be resolved automatically. - Refer to for more information on resolving conflicts. + + + + + Needs Patch + + + The revision in your local checkout needs a patch to be + the latest revision from the server. Issue the + cvs update command to resolve. - - - - - Unknown - - - - The CVS server does not know anything about this file. - It has neither been added nor removed locally and has never been committed to the server. - This status usually occurs for files you should not commit to CVS such as generated-index.sgml or for files that you want to add to the repository but have not yet issued the cvs add command. - - - + + -
+ + Needs Merge + + + A newer revision exists on the server and your local + version contains modification not yet committed. This + status usually occurs if you don't have the latest + revision of the file and edit it anyway. + + + -
- Resolving Conflicts + + File had conflicts on merge + + + Similar to Needs Merge, + except when you tried to issue the cvs + update command, the differences could not be + resolved automatically. Refer to + for + more information on resolving conflicts. + + + - - cvs - resolving conflicts - + + Unknown + + + The CVS server does not know + anything about this file. It has neither been added nor + removed locally and has never been committed to the + server. This status usually occurs for files you should + not commit to CVS such as + generated-index.sgml or for files + that you want to add to the repository but have not yet + issued the cvs add command. + + + + +
- - If you modify a file and the same region is modified by someone else and committed first, you will probably see a message similar to the following when committing the file or updating your local copy of the module: +
+ Resolving Conflicts + + cvs + resolving conflicts + + + If you modify a file and the same region is modified by someone + else and committed first, you will probably see a message + similar to the following when committing the file or updating + your local copy of the module: - - + RCS file: /cvs/docs/module-name/filename.sgml,v retrieving revision 1.12 @@ -743,12 +865,13 @@ C filename.sgml - - - To resolve the conflict, open the file, search for <<<<<<< and determine which version of the content is correct. - For example: - - + + To resolve the conflict, open the file, search for + <<<<<<< + and determine which version of the content is correct. For + example: + + <para> Some sentence. @@ -760,150 +883,132 @@ </para> + + The content between the + <<<<<<<, + and the ======= is the content + from your working copy. The content between the + ======= and the + >>>>>>> is + the content from the server. + - - The content between the <<<<<<<, and the ======= is the content from your - working copy. - The content between the ======= and the >>>>>>> is the content from the server. - - - + Resolve the conflict by editing your copy, and commit the file. +
-
- - -
- Summary - - - cvs - commands - summary of - - - - All commands assume you are in the proper directory for the CVS module. +
+ Summary + + cvs + commands + summary of + + + All commands assume you are in the proper directory for the + CVS module. - - - Basic CVS Commands - - - - - - Command - Description - - - - - - cvs checkout - <module-name> - - or cvs co <module-name> - - - Creates a directory called +
+ Basic CVS Commands + + + + + + Command + Description + + + + + cvs checkout + <module-name> + or cvs co <module-name> + + Creates a directory called <module-name> with the contents of the module in the directory - - - - cvs co -d <directory> -r <branchname> - <module-name> - - - Creates the <directory> directory + + + cvs co -d <directory> -r <branchname><module-name> + + Creates the <directory> directory with the contents of the <branchname> branch of the <module-name> module - - - - cvs update or cvs up - - Update your files with the latest files from the CVS server - - - - cvs add <filename> - - - Add a new file "filename" to the CVS server - - - - cvs commit -m "My message" - <filename> - - - Update file <filename> with the + + + cvs update or cvs up + + Update your files with the latest files from the CVS server + + + cvs add <filename> + + Add a new file "filename" to the CVS server + + + cvs commit -m "My message" + <filename> + + Update file <filename> with the latest copy from your computer - - - - cvs log <filename> - - - View the commit messages for the file <filename> - - - - - cvs status <filename> - - - View status of the file, such as Locally + + + cvs log <filename> + + View the commit messages for the file <filename> + + + + cvs status <filename> + + View status of the file, such as Locally Modified - - - - - cvs status -v <filename> - - - View existing tags and branches for file - - - - cvs diff <filename> - - - Show diff of the working copy of the file and the latest + + + + cvs status -v <filename> + + View existing tags and branches for file + + + cvs diff <filename> + + Show diff of the working copy of the file and the latest version of the file for the branch - - - - cvs diff -r1.1 -r1.2 <filename> - - - Show diff of version 1.1 and 1.2 for file - - - -
- - - For more information, read the CVS manual available on your system at /usr/share/doc/cvs-<version-number>/cvs.ps (the CVS version might vary) and visit the CVS webpage available at http://www.cvshome.org/. + + + cvs diff -r1.1 -r1.2 <filename> + + Show diff of version 1.1 and 1.2 for file + + + + + + For more information, read the CVS manual available on your + system at + /usr/share/doc/cvs-<version-number>/cvs.ps + (the CVS version might vary) and visit the CVS webpage available + at + http://www.cvshome.org/. - - - Tip - - Since CVS is using ssh to connect to the CVS server, you will be prompted your password before performing your CVS request. - If you want to configure your machine so that you do not have to enter a password, refer to the - &RH; Linux 9 Customization Guide - - for details about using - ssh-agent. - - - -
- + + Tip + + Since CVS is using + ssh to connect to the + CVS server, you will be prompted + your password before performing your + CVS request. If you want to + configure your machine so that you do not have to enter a + password, refer to the + &RH; + Linux 9 Customization Guide for details + about using ssh-agent. + +
- - +
+ From fedora-docs-commits at redhat.com Tue Jul 19 12:02:05 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 19 Jul 2005 08:02:05 -0400 Subject: release-notes/FC4 kernel.xml,1.11,1.12 Message-ID: <200507191202.j6JC25rO005739@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5721 Modified Files: kernel.xml Log Message: Very minor changes - ispell is your friend Index: kernel.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/kernel.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- kernel.xml 19 Jul 2005 04:24:07 -0000 1.11 +++ kernel.xml 19 Jul 2005 12:02:01 -0000 1.12 @@ -90,16 +90,17 @@
@@ -236,7 +237,7 @@ to this: EXTRAVERSION = -1.234_FC4 - that is, substitude everything from the final dash onward. + that is, substitute everything from the final dash onward. @@ -279,7 +280,7 @@
- Userspace Dependancies on the Kernel + User Space Dependencies on the Kernel &DISTRO; adds support for clustered systems. This requires a special kernel that works in conjunction with some user-space @@ -287,14 +288,14 @@ such a kernel, perhaps after an update, you cannot simply use the rpm -e kernel-<version> - command as in earlier distributions because these userspace + command as in earlier distributions because these user space packages depend on the kernel package. You may either list both - the kernel package and its userspace dependant packages on the + the kernel package and its user space dependent packages on the rpm -e command, or you may wish to use the yum remove kernel-<version> command instead since yum automatically removes - dependant packages if necesssary. + dependent packages if necessary.
From fedora-docs-commits at redhat.com Tue Jul 19 19:42:25 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 19 Jul 2005 15:42:25 -0400 Subject: yum-software-management yum-software-management-en.xml,1.14,1.15 Message-ID: <200507191942.j6JJgPxC015549@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15532 Modified Files: yum-software-management-en.xml Log Message: - Added example public key header. - Change example transaction to an - Removed superfluous paragraph from the Tools overview. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- yum-software-management-en.xml 19 Jul 2005 02:36:04 -0000 1.14 +++ yum-software-management-en.xml 19 Jul 2005 19:42:22 -0000 1.15 @@ -1,4 +1,4 @@ - @@ -110,8 +110,8 @@ You do not need to log in with the root account in - order to manage your &FED; system. All of the commands shown in - this tutorial that require + order to manage your &FED; system. All of the commands shown + in this tutorial that require root access will prompt you for the root password. The @@ -432,14 +432,6 @@ - Both up2date and yum - are configured to use official &FED; repositories. If you add - other repositories to yum then for consistency - you should also configure up2date to - use them. - - - Also included in &FC; is system-config-packages. From the main menu, this is System @@ -543,8 +535,11 @@ As an example, this is the transaction for installing tsclient: - - + + + Format of <command>yum</command> Transaction Reports + + - + ]]> + + + Review the list of changes before pressing y to accept and begin the process. No @@ -630,8 +627,8 @@ configure a new service to run on bootup, choose DesktopSystem Settings Server Settings - Services, or run - chkconfig in a terminal window. + Services, or use the + chkconfig command-line utility. @@ -1162,11 +1159,34 @@ rpm -qi gpg-pubkey-* - The identification name for a key is - . For - example, the &FP; public key is currently version 4f2a6fd2, - release 3f9d9d3b. The rpm identification for - this key is . + Locate the heading for the relevant public key. The public key + headings follow this format: + + + + Format of <command>rpm</command> Public Key Headers + + ) +Description : + ]]> + + + + + Add the and + attributes to to make the complete + name of the key, in the form + . The + rpm identification for the &FP; public key + shown above is: . From fedora-docs-commits at redhat.com Tue Jul 19 20:22:47 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Tue, 19 Jul 2005 16:22:47 -0400 Subject: owners owners.list,1.5,1.6 Message-ID: <200507192022.j6JKMlqU016751@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16734 Modified Files: owners.list Log Message: Added components for docs-requests and project-tracking Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- owners.list 17 Jul 2005 15:00:54 -0000 1.5 +++ owners.list 19 Jul 2005 20:22:44 -0000 1.6 @@ -9,8 +9,11 @@ # All e-mail addresses used here MUST correspond to existing bugzilla accounts! # Initial edit 11-JUL-2005 by kwade at redhat.com +# Changelog: +# * July 19 2005 Paul W. Frields +# - Add global FDP components, make notation about roles # -# Roles in FDP +# Roles in FDP (document-specific bugs) # initialowner = document author and/or document manager # intialqacontact = document editor and/or document manager # intialcclist = document manager,others @@ -26,6 +29,15 @@ # relnotes at fedoraproject.org # sarahs at redhat.com +# +# Global FDP components +# +Fedora Documentation|docs-requests|Requests for new Fedora documentation.|kwade at redhat.com|stickster at gmail.com|fedora-docs-list at redhat.com +Fedora Documentation|project-tracking|Non-specific FDP work tracking bugs.|kwade at redhat.com|tfox at redhat.com|fedora-docs-list at redhat.com + +# +# Specific FDP document components +# Fedora Documentation|desktop-up2date|Keeping a desktop up-to-date using graphical tools.|fdr at eln.fastmail.fm|mjohnson at redhat.com|kwade at redhat.com Fedora Documentation|developer-guide|Striving to be the canonical Fedora development reference.|tfox at redhat.com|Tommy.Reynolds at MegaCoder.com|kwade at redhat.com Fedora Documentation|documentation-guide|The Guide is the canonical set of guidelines and howtos for FDP contributors.|stickster at gmail.com|tfox at redhat.com|kwade at redhat.com From fedora-docs-commits at redhat.com Tue Jul 19 20:41:05 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 19 Jul 2005 16:41:05 -0400 Subject: release-notes/FC4 RELEASE-NOTES-en.xml,1.10,1.11 Message-ID: <200507192041.j6JKf5gx016819@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16790/release-notes/FC4 Modified Files: RELEASE-NOTES-en.xml Log Message: Moving legalnotice to the front-area where it belongs, removing from the entity makes it part of the document itself. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-en.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- RELEASE-NOTES-en.xml 17 Jun 2005 14:38:34 -0000 1.10 +++ RELEASE-NOTES-en.xml 19 Jul 2005 20:41:03 -0000 1.11 @@ -37,7 +37,7 @@ - + @@ -53,7 +53,7 @@
- &DISTRO; &DISTROVER; Release Notes + &DISTRO; &DISTROVER; Release Notes <emphasis>(updated)</emphasis> 2005 &FORMAL-RHI; @@ -63,6 +63,10 @@ &SPLASH; +
+ Legalnotice + &LEGALNOTICE-CONTENT; +
&INTRO; &HARDWARE-REQS; @@ -77,8 +81,4 @@ x86_64 ) --> - - Legalnotice - &LEGALNOTICE-CONTENT; -
From fedora-docs-commits at redhat.com Tue Jul 19 20:41:05 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 19 Jul 2005 16:41:05 -0400 Subject: docs-common/common legalnotice-relnotes-en.xml,1.1,1.2 Message-ID: <200507192041.j6JKf5wp016825@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/docs-common/common In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16790/docs-common/common Modified Files: legalnotice-relnotes-en.xml Log Message: Moving legalnotice to the front-area where it belongs, removing from the entity makes it part of the document itself. Index: legalnotice-relnotes-en.xml =================================================================== RCS file: /cvs/docs/docs-common/common/legalnotice-relnotes-en.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- legalnotice-relnotes-en.xml 3 Jun 2005 03:43:08 -0000 1.1 +++ legalnotice-relnotes-en.xml 19 Jul 2005 20:41:03 -0000 1.2 @@ -10,6 +10,6 @@ This document is released under the terms of the GNU Free Documentation License. For more details, read the full legalnotice in . + linkend="sn-legalnotice" />. From fedora-docs-commits at redhat.com Tue Jul 19 20:48:51 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 19 Jul 2005 16:48:51 -0400 Subject: yum-software-management yum-software-management-en.xml,1.15,1.16 Message-ID: <200507192048.j6JKmpbX016866@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16849 Modified Files: yum-software-management-en.xml Log Message: - Broke out "Removing Public Keys" to a separate section. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- yum-software-management-en.xml 19 Jul 2005 19:42:22 -0000 1.15 +++ yum-software-management-en.xml 19 Jul 2005 20:48:48 -0000 1.16 @@ -1103,8 +1103,8 @@ maintenance. It is useful to disable or remove repository definitions that are no longer required, as each repository that is defined and enabled is checked for every operation. You may - also remove files relating to unwanted packages, in order to - recover disk space. + also clear the files from the yum caches in + order to recover disk space.
@@ -1141,19 +1141,28 @@ + + Remove Unneeded Public Keys + + + If you will not be using any further packages from a provider, + remove their public key from the rpm + keyring using the procedure described in + . + + +
+ +
+ Removing Public Keys public keys, removing - In addition, remove the public key for the package provider from - the rpm keyring, if you will not be using any - more packages from that source. - - - - To remove a public key from the keyring you must know the - identification name used by rpm. Run this - command to view the details of the public keys on the keyring: + To remove a public key from the keyring you first must determine + the full name of the key, as it registered in + rpm. Run this command to view the details of + the public keys on the rpm keyring: rpm -qi gpg-pubkey-* @@ -1213,8 +1222,8 @@ By design, yum does not automatically delete any of the packages or package data files that it downloads, so - that these can be reused. The header files accumulate over time, - and these may be purged with the command: + that they may be reused in future operations. To purge the + header files, use the command: su -c 'yum clean headers' @@ -1231,6 +1240,12 @@ root account when prompted. + + + Package management operations download header files and packages + as required, automatically replacing any purged files needed for + the operation. +
From fedora-docs-commits at redhat.com Tue Jul 19 21:07:45 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 19 Jul 2005 17:07:45 -0400 Subject: yum-software-management yum-software-management-en.xml,1.16,1.17 Message-ID: <200507192107.j6JL7jLH018084@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18031 Modified Files: yum-software-management-en.xml Log Message: - Style fixes. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- yum-software-management-en.xml 19 Jul 2005 20:48:48 -0000 1.16 +++ yum-software-management-en.xml 19 Jul 2005 21:07:42 -0000 1.17 @@ -888,14 +888,9 @@ automatic updating - If your &FED; system is permanently connected to the network - then updates may be performed at any time. The - yum package includes scripts to - automatically carry out full system updates every day. - - - - To activate automatic daily updating, enter this command: + The yum package supplied with &FC; includes + scripts to carry out full system updates every day. To activate + automatic daily updates, enter this command: su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' From fedora-docs-commits at redhat.com Wed Jul 20 00:55:59 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 19 Jul 2005 20:55:59 -0400 Subject: yum-software-management yum-software-management-en.xml,1.17,1.18 Message-ID: <200507200055.j6K0txZX022532@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22498 Modified Files: yum-software-management-en.xml Log Message: - Add su to search/list commands: these may not work as an unprivileged user unless previously run as root to fetch current indices. - Style fixes. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- yum-software-management-en.xml 19 Jul 2005 21:07:42 -0000 1.17 +++ yum-software-management-en.xml 20 Jul 2005 00:55:56 -0000 1.18 @@ -563,7 +563,7 @@ Review the list of changes before pressing y to accept and begin the process. No packages are downloaded or changed if you press - n. + N. @@ -773,15 +773,21 @@ package tsclient the command would be: -yum list tsclient +su -c 'yum list tsclient' + Enter the password for the + root account when + prompted. + + + To make your queries more specific, add other package attributes. For example, to search for version 0.132 of the application the command would be: -yum list tsclient-0.132 +su -c 'yum list tsclient-0.132' @@ -800,9 +806,15 @@ all packages that relate to PalmPilots, type: -yum search PalmPilot +su -c 'yum search PalmPilot' + Enter the password for the + root account when + prompted. + + + The function checks both the files included in the packages and the functions that the software provides. This option requires yum to @@ -815,7 +827,7 @@ libneon, type: -yum provides libneon +su -c 'yum provides libneon' To search for all packages that either provide an MTA (Mail @@ -823,8 +835,13 @@ mta in their name: -yum provides MTA +su -c 'yum provides MTA' + + For each command, enter the password for the + root account when + prompted. + Wildcards and Regular Expressions @@ -941,8 +958,8 @@ You must manually configure &FED; 3 systems to use &FEX;, using the instructions at: http://fedora.redhat.com/projects/extras/. - Refer to this Website for additional packages for &FC; 1 and - &FC; 2: + Refer to this Website for additional packages for &FED; 1 and + &FED; 2: http://www.fedora.us/. @@ -992,12 +1009,13 @@ - The configuration file for each repository should include the - location of the public key that verifies the packages provided - by that repository. This public key is automatically imported - the first time that you install software from the repository. If - the configuration file provided does not include this setting, - refer to . + The configuration file for each repository should include a + gpgkey setting to specify the location of the + public key that verifies the packages it provides. This public + key is automatically imported the first time that you install + software from the repository. If the configuration file provided + does not include this setting, refer to + . @@ -1060,13 +1078,14 @@ - Before attempting to use a repository, read the Website for - information on package compatibility. Repositories often provide - packages that are specifically intended for use with packages - that are supplied by other repositories. In some cases separate - third-party repository providers may each offer different - versions of the same software, preventing those repositories - from being safely used together by your &FED; system. + Refer to the Website of the repository for information on + package compatibility before adding it as a package source. + Repositories often provide packages that are specifically + intended for use with packages that are supplied by other + repositories. In some cases separate third-party repository + providers may each offer different versions of the same + software, preventing those repositories from being safely used + together by your &FED; system. @@ -1095,11 +1114,11 @@ The yum system does not require any routine - maintenance. It is useful to disable or remove repository - definitions that are no longer required, as each repository that - is defined and enabled is checked for every operation. You may - also clear the files from the yum caches in - order to recover disk space. + maintenance. To ensure that yum operations are + carried out at the best possible speed, disable or remove + repository definitions are no longer required. You may also clear + the files from the yum caches in order to + recover disk space.
@@ -1231,16 +1250,20 @@ su -c 'yum clean packages' - In both cases, enter the password for the + When using these commands, enter the password for the root account when prompted. - - Package management operations download header files and packages - as required, automatically replacing any purged files needed for - the operation. - + + Purged Files + + + Package management operations download header files and + packages as required, automatically replacing any deleted + files needed for the operation. + +
From fedora-docs-commits at redhat.com Wed Jul 20 04:32:52 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Wed, 20 Jul 2005 00:32:52 -0400 Subject: securing-filesystems gnufdl-en.xml,NONE,1.1 Message-ID: <200507200432.j6K4Wq1t027399@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27383/securing-filesystems Added Files: gnufdl-en.xml Log Message: GNU Free Documentation License Version 1.2 --- NEW FILE gnufdl-en.xml --- From fedora-docs-commits at redhat.com Wed Jul 20 04:36:18 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Wed, 20 Jul 2005 00:36:18 -0400 Subject: securing-filesystems setfacl-en.xml,NONE,1.1 Message-ID: <200507200436.j6K4aIUk027421@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27405/securing-filesystems Added Files: setfacl-en.xml Log Message: Setfacl Version 2.2.21 --- NEW FILE setfacl-en.xml --- . Please send your bug reports, suggested features and comments to the above address. ]]> From fedora-docs-commits at redhat.com Wed Jul 20 12:24:52 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Wed, 20 Jul 2005 08:24:52 -0400 Subject: securing-filesystems gnufdl-en.xml,1.1,NONE Message-ID: <200507201224.j6KCOqA5008695@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8680/securing-filesystems Removed Files: gnufdl-en.xml Log Message: Instructed to use the Boilerplate FDL rather than include local copy. --- gnufdl-en.xml DELETED --- From fedora-docs-commits at redhat.com Wed Jul 20 16:37:38 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Wed, 20 Jul 2005 12:37:38 -0400 Subject: owners owners.list,1.6,1.7 Message-ID: <200507201637.j6KGbcEg014716@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14699 Modified Files: owners.list Log Message: Testing to see if Bugzilla picks up new component descriptions after initial assignment. Index: owners.list =================================================================== RCS file: /cvs/docs/owners/owners.list,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- owners.list 19 Jul 2005 20:22:44 -0000 1.6 +++ owners.list 20 Jul 2005 16:37:35 -0000 1.7 @@ -32,7 +32,7 @@ # # Global FDP components # -Fedora Documentation|docs-requests|Requests for new Fedora documentation.|kwade at redhat.com|stickster at gmail.com|fedora-docs-list at redhat.com +Fedora Documentation|docs-requests|Requests for new Fedora documentation, and other miscellaneous work.|kwade at redhat.com|stickster at gmail.com|fedora-docs-list at redhat.com Fedora Documentation|project-tracking|Non-specific FDP work tracking bugs.|kwade at redhat.com|tfox at redhat.com|fedora-docs-list at redhat.com # From fedora-docs-commits at redhat.com Wed Jul 20 17:17:48 2005 From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr)) Date: Wed, 20 Jul 2005 13:17:48 -0400 Subject: owners pr-owners,NONE,1.1 Message-ID: <200507201717.j6KHHmEi016199@cvs-int.fedora.redhat.com> Author: jtr Update of /cvs/docs/owners In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16183 Added Files: pr-owners Log Message: The "pr-owners" script makes it easy to see what is in that machine-readable "owners.list" script. --- NEW FILE pr-owners --- #!/bin/sh ######################################################################## # This "pr-owners" script displays the content of the "owners.list" # file in a human readable format. Use it like this: # # $ ./pr-owners owners.list | less # ######################################################################## awk ' function trim( s, v ) { v = s sub( /^[ \t]*/, "", v ) sub( /[ \t]*$/, "", v ) return( v ) } BEGIN { FS = "|" } { sub( /#.*$/, "" ) } NF == 6 { product = trim( $1 ) component = trim( $2 ) description = trim( $3 ) initialowner = trim( $4 ) qacontact = trim( $5 ) initialcclist = trim( $6 ) if( others ) { printf "\n" } others = 1 printf "%s/%s\n\n", product, component printf "\tOwner:\t%s\n", initialowner printf "\tQA:\t%s\n", qacontact printf "\tCC:\t%s\n", initialcclist printf "\n" # printf "\t%s\n", description nwords = split( description, words, /[ \t]/ ) # printf "%d words\n", nwords leadin = "" sep = "" line = "" for( i = 1; i <= nwords; ++i ) { word = words[ i ] if( (length(word)+length(sep)+length(line)) >= 64 ) { printf "\t%s\n", line line = "" sep = "" } line = line sep word sep = " " } if( length( line ) > 0 ) { printf "\t%s\n", line } } ' $@ From fedora-docs-commits at redhat.com Thu Jul 21 16:54:47 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Thu, 21 Jul 2005 12:54:47 -0400 Subject: yum-software-management yum-software-management-en.xml,1.18,1.19 Message-ID: <200507211654.j6LGslMV016746@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16729/yum-software-management Modified Files: yum-software-management-en.xml Log Message: Some style edits, still working on this... Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- yum-software-management-en.xml 20 Jul 2005 00:55:56 -0000 1.18 +++ yum-software-management-en.xml 21 Jul 2005 16:54:45 -0000 1.19 @@ -124,59 +124,73 @@
Additional Resources - yum, documentation + yum + documentation - yum, man pages + yum + man pages - The yum utility has features and options that - are not discussed in this document. Read the - man pages for yum(8) and + The yum utility has features and options not + discussed in this document. Read the man + pages for yum(8) and yum.conf(5) to learn more, using the following commands: - -man yum man yum.conf +man yum +man yum.conf - yum, Websites + yum + web sites - yum, mailing lists + yum + mailing lists + + + + + + + Other useful yum resources on the Internet + include: + + - The Website for yum is: + Web home page - http://linux.duke.edu/projects/yum/ + - The mailing list for yum users is: - + Users mailing list + - https://lists.dulug.duke.edu/mailman/listinfo/yum/ + -The archive for the yum development mailing list is: - + Development mailing list + - https://lists.dulug.duke.edu/pipermail/yum-devel/ + @@ -190,7 +204,8 @@
About Packages - packages, defined + packages + defined All of the software and documentation prepared for use with @@ -206,12 +221,12 @@ Packages also include a digital signature to prove their source. - This digital signature is verified by software management - utilities by using a GPG public key. The - yum and rpm utilities - share a common keyring that stores all of - the public keys for the package sources approved by the system - administrator. + Software management utilities verify this digital signature by + using a GPG public key. The + yum and rpm utilities + share a common keyring that stores all of + the public keys for approved package sources. The system + administrator configures these approved package sources.
From fedora-docs-commits at redhat.com Fri Jul 22 11:39:48 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 22 Jul 2005 07:39:48 -0400 Subject: mirror-tutorial mirror-tutorial-en.xml,1.4,1.5 Message-ID: <200507221139.j6MBdmad010197@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10180 Modified Files: mirror-tutorial-en.xml Log Message: Removed references to yum-arch and replaced with createrepo; bump to 0.24 Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- mirror-tutorial-en.xml 18 Jun 2005 13:51:02 -0000 1.4 +++ mirror-tutorial-en.xml 22 Jul 2005 11:39:45 -0000 1.5 @@ -5,7 +5,7 @@ %FEDORA-ENTITIES-EN; - + ]> @@ -76,6 +76,17 @@ + + 0.24 + 2005-07-22 + PaulWFrields + + + Removed references to yum-arch and replaced with + createrepo. + + + @@ -1047,45 +1058,37 @@ To set up a yum repository, you must write a - directory of header information from which the clients pull the data - they require. The directory is named headers. It is - created by using the command yum-arch, which is run + directory of header information from which the clients extract the data that + they require. The directory is named repodata/. It is + created by using the command createrepo, which is run against the directory under which you want the - headers directory to appear. The - yum-arch program searches recursively through that + repodata/ directory to appear. The + createrepo program searches recursively through that directory and any subdirectories for RPM packages, and includes them in the header data. -yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os +createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os - The -l switch follows symbolic links. This is useful - in the first case below. The -s switch includes SRPMS - (source RPM packages) in the header list. The command above creates the - yum header cache in the directory + The command above creates the yum header cache in the directory /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers. - Typically yum-arch is run against at least the + Typically createrepo is run against at least the following locations: The stock distribution; for example, - /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/. - Use the -l and -s options to - follow the linked directory SRPMS and include - the source packages therein. + /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/. Official updates to the distribution; for example, - /var/ftp/pub/linux/fedora/core/updates/&FCVER;/. - Once again use -l and/or -s if - appropriate. + /var/ftp/pub/linux/fedora/core/updates/&FCVER;/. @@ -1589,7 +1592,7 @@ Edit /etc/sysconfig/rhn/sources for the clients at your site to point to your repository. For any repository, point to the URL for the directory containing the headers - folder. You created this folder using yum-arch in + folder. You created this folder using createrepo in . You will likely have two repositories, one for the stock distribution and one for updates. Examples are shown below; you may wish to point to an internal address @@ -1631,3 +1634,9 @@ + + From fedora-docs-commits at redhat.com Fri Jul 22 12:34:46 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 22 Jul 2005 08:34:46 -0400 Subject: mirror-tutorial mirror-tutorial-en.xml,1.5,1.6 Message-ID: <200507221234.j6MCYkvl011472@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11455 Modified Files: mirror-tutorial-en.xml Log Message: Rolled in newest mirror-tutorial (#163912) Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- mirror-tutorial-en.xml 22 Jul 2005 11:39:45 -0000 1.5 +++ mirror-tutorial-en.xml 22 Jul 2005 12:34:43 -0000 1.6 @@ -1,11 +1,11 @@ - + + %FEDORA-ENTITIES-EN; - + ]> @@ -78,12 +78,51 @@ 0.24 - 2005-07-22 + 2004-09-09 PaulWFrields - Removed references to yum-arch and replaced with - createrepo. + Brought introduction section in line with &FDP; standards. + + + + + 0.25 + 2004-10-13 + PaulWFrields + + + Incorporated all suggested changes by KWade. + + + + + 0.26 + 2004-12-01 + PaulWFrields + + + Updated repository setup to include createrepo. + + + + + 0.27 + 2004-12-01 + PaulWFrields + + + Minor corrections. + + + + + 0.28 + 2005-01-30 + PaulWFrields + + + Minor corrections. @@ -95,19 +134,19 @@
Purpose - This tutorial presents a number of related topics that allow an - administrator to seamlessly integrate mirroring and update services for - &FC;. These services are used 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. + 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. A note about &FC; and this document This document applies to &FC; &FCVER;, which may not be the newest - release of &FC;. Find more information about the newest version at - &FP-URL;. + release of &FC;. You can find more information about the newest + version at &FP-URL;.
@@ -151,11 +190,13 @@ The site from which you retrieve files to build your mirror is called an upstream mirror - mirror upstream + mirror upstream . 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. + and expensive. Use only upstream mirrors that are intended for public + access, unless you have permission from the upstream mirror site + administrator.
@@ -164,11 +205,11 @@ For more information on installing &FC; see the &FC; &IG;. For more information on basic Internet protocols, see http://library.albany.edu/internet/internet.html, + url="http://library.albany.edu/internet/internet.html">http://library.albany.edu/internet/internet.html, or search Google at http://www.google.com/. For more + url="http://www.google.com/">http://www.google.com/. For more general information about mirrors, see http://en.wikipedia.org/wiki/Mirror_(computing). + url="http://en.wikipedia.org/wiki/Mirror_(computing)">http://en.wikipedia.org/wiki/Mirror_(computing).
@@ -179,45 +220,23 @@
- +
Planning and Setup - - - - - - A mirror - mirror 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. - - - The upstream mirror - mirror - upstream is the site you retrieve - files from to build your mirror. 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. - - +
The Distribution Structure - The &FED; distribution + The &FED; distribution distribution , which is the collection of all &FED;-related files, uses the directory tree in . It may - include multiple versions of &FC;. The tree design makes trimming of + 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. + Fedora directory tree @@ -257,6 +276,7 @@ +-- x86_64 + Naming conventions @@ -322,7 +342,7 @@ Installation Disc 1 into the fedora/linux/core/&FCVER;/arch/os folder. Then copy all files from the &FED; folder - of each of the remaining installation discs into the + of each of the remaining Installation discs into the fedora/linux/core/&FCVER;/arch/os/&FED; folder on the server. @@ -395,22 +415,22 @@ - Older versions of &FC; (any numbered directory). + Older versions of &FC; (any numbered directory). - Before you exclude an old version, ensure this does not adversely - affect any of your users. These adverse affects can come in many - forms. For example, the level of support for certain hardware - sometimes changes between releases of &FC;. Users who cannot - install a previous version may not be able to use &FC;. Your users - might need to perform software-related tasks such as building - packages for different &FC; releases. Always remain aware of the - needs of your users during the planning stage. + Before you exclude an old version, ensure + this does not adversely affect any of your users. These adverse + affects can come in many forms. For example, the level of support + for certain hardware sometimes changes between releases of &FC;. + Users who cannot install a previous version may not be able to use + &FC;. Your users might need to perform software-related tasks such + as building packages for different &FC; releases. Always remain + aware of the needs of your users during the planning stage. - Folders for architectures your site does not support. + Folders for architectures your site does not support. If you do not have any x86-64 hosts to support, trimming these @@ -422,16 +442,16 @@ The development folder (formerly - rawhide). + Rawhide). - 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 regular - update cycle. + 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 + regular update cycle. @@ -441,9 +461,9 @@ 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 testing folder under the - main core tree is where test versions of the + pre-release versions of the &FC; distribution. The + testing folder under the main + core 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 development branch to update packages.) The @@ -454,21 +474,16 @@ - The debug folders. + The debug folders. These folders contain packages that enable developers and skilled users to interpret data created when a program crashes or encounters a bug. If you participate actively in &FED; development, you should not trim these folders. If you trim this - branch, you may still download individual packages on an ad hoc - basis from a nearby public mirror site. + branch, you may still download individual packages on an + ad hoc basis from a nearby public + mirror site. @@ -479,7 +494,8 @@ These folders contain the original source for all the binary RPM packages in the distribution. You may download these packages on - an ad hoc basis if you need to save space on your local mirror. + an ad hoc basis if you need to save + space on your local mirror. @@ -526,26 +542,26 @@ - turns on recursion (descends into all + --mirror turns on recursion (descends into all subdirectories), and duplicates file timestamps; - prevents wget from + -np prevents wget from ascending into the parent directory; - prevents wget from + -nH prevents wget from writing a directory named after the host (in this case, mirror.example.com); - + --cut-dirs=n truncates the first n directories in the path. In the example above, --cut-dirs=2 prevents wget from writing the @@ -576,11 +592,10 @@ Begin by identifying the modules available on the upstream 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 rsync path. The - following command generates a list of modules - on the upstream mirror. + you have chosen. Note that the double colon :: is + always used after the host name to separate it from the rest of the + rsync path. The following command generates a list + of modules on the upstream mirror. @@ -595,10 +610,9 @@ equivalent to the fedora/linux/core 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 - /. 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. @@ -614,8 +628,8 @@ 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 new - folder inside the target directory, and its contents are copied. + remote path, then the last component of that path is created as a + folder, and its contents are copied. @@ -625,7 +639,7 @@ When downloading using rsync for mirror purposes, use some of the command line switches to improve performance and - feedback. The switches enable the following + feedback. The switches -PHav enable the following rsync features: @@ -669,6 +683,7 @@ understand the consequences. + rsync -PHav mirror.example.org::fedora-linux-core/&FCVER;/ /var/ftp/pub/mirror/fedora/core/&FCVER; @@ -738,7 +753,7 @@ Use the --exclude switch, along with a simple pattern, to disallow download of certain files and/or folders. For instance, --exclude "*.iso" excludes the download - of any file that has the string x86_64 in its filename. + of any file whose name ends with the string ".iso". Use the --delete switch, again with a pattern, to @@ -1058,40 +1073,105 @@ To set up a yum repository, you must write a - directory of header information from which the clients extract the data that - they require. The directory is named repodata/. It is - created by using the command createrepo, which is run - against the directory under which you want the - repodata/ directory to appear. The - createrepo program searches recursively through that - directory and any subdirectories for RPM packages, and includes them in - the header data. + directory that contains information which the clients require to resolve + RPM dependencies. The directory's name depends on the version of + yum it supports. It is permissible to have both kinds + of repository information in a single repository. +
+ <command>yum-arch</command> + + A directory which supports older versions of yum is + named headers. It is created by using the command + yum-arch, which is run against the directory + under which you want the + headers directory to appear. The + yum-arch program searches recursively through that + directory and any subdirectories for RPM packages, and includes them + in the header data. + + + +yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os + + + + The -l switch follows symbolic links. The + -s switch includes SRPMS (source RPM packages) in + the header list. The command above creates the yum + header cache in the directory + /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers. + +
+ +
+ <command>createrepo</command> + + The createrepo command creates repository + information to support newer versions of yum (and + possibly other repository client programs). The + createrepo command stores this data in a folder + named repodata. Just as with + yum-arch, run createrepo against + the directory under which you want the + repodata directory to appear. The + createrepo program also searches recursively for + RPM packages to include in the repository data. + + createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os - - The command above creates the yum header cache in the directory - /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers. - Typically createrepo is run against at least the - following locations: - - - - - The stock distribution; for example, - /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/. - - - + + The command above creates the repository data in the directory + /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/repodata. + + + Supporting &FC; 3 and beyond - Official updates to the distribution; for example, - /var/ftp/pub/linux/fedora/core/updates/&FCVER;/. + &FC; 3 ships with a newer version of yum. To + support &FC; 3 yum clients, you + must use createrepo on your + server's repositories. - - + + + 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. + + +
+ +
+ Repository Locations + + Typically yum-arch or createrepo + is run against at least the following locations: + + + + + The stock distribution; for example, + /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/. + For yum-arch use the -l and + -s options to follow the linked directory + SRPMS and include the source packages + therein. + + + + + Official updates to the distribution; for example, + /var/ftp/pub/linux/fedora/core/updates/&FCVER;/. + Once again, for yum-arch use + -l and/or -s if appropriate. + + + +
@@ -1473,18 +1553,16 @@ - If a user forgets the --aid switch, they - still receive hints. Normally rpm - displays a slightly cryptic list of capability requirements, - instead of straightforward package names. If you edit - /etc/rpm/macros.solve as shown, - rpm displays a list of required package + If a user forgets the --aid switch, they still + receive hints. Normally rpm displays a slightly + cryptic list of capability requirements, instead of straightforward + package names. If you edit /etc/rpm/macros.solve + as shown, rpm displays a list of required package names instead. - Package dependency solutions using --aid - are also restricted as shown above in . + Package dependency solutions using --aid are also + restricted as shown above in .
@@ -1503,51 +1581,46 @@
<filename>/etc/sysconfig/rhn/up2date</filename> - The /etc/sysconfig/rhn/up2date file - controls the global configuration of the - up2date application. This file is - well commented and is not explained in great detail - here. Here are some points to keep in mind, however: + The /etc/sysconfig/rhn/up2date file controls the + global configuration of the up2date + application. This file is well commented and is not explained in great + detail here. Here are some points to keep in mind, however: By default, the user must intervene to update kernel packages. See the - pkgSkipList variable. At the command - line, use the -f option to force an - override. At the GUI interface, - up2date allows the user to + pkgSkipList variable. At the command line, use + the -f option to force an override. At the GUI + interface, up2date allows the user to override. - By default, up2date does not remove - old kernel packages. See the + By default, up2date does not remove old + kernel packages. See the pkgsToInstallNotUpdate variable. When - up2date installs a new kernel - package, the old version remains in place until removed - explicitly. + up2date installs a new kernel package, the old + version remains in place until removed explicitly. - The configuration file also allows use of an HTTP proxy - if desired. A number of variables pertain to this - function. + The configuration file also allows use of an HTTP proxy if + desired. A number of variables pertain to this function. - By default, up2date sends - mail to root at localhost when packages are - updated in batch mode. (Running up2date - -u starts up2date - in batch mode.) See the adminAddress - option. If you support multiple clients and intend to - use batch mode at your site, you should set a new - address here. + By default, up2date sends mail to + root at localhost when packages are updated in batch + mode. (Running up2date -u starts + up2date in batch mode.) See the + adminAddress option. If you support multiple + clients and intend to use batch mode at your site, you should set + a new address here. @@ -1592,7 +1665,7 @@ Edit /etc/sysconfig/rhn/sources for the clients at your site to point to your repository. For any repository, point to the URL for the directory containing the headers - folder. You created this folder using createrepo in + folder. You created this folder using yum-arch in . You will likely have two repositories, one for the stock distribution and one for updates. Examples are shown below; you may wish to point to an internal address @@ -1601,8 +1674,8 @@ -yum fedora-core-2 http://www.mydomain.org/pub/linux/fedora/core/2/i386/os -yum fc2-updates http://www.mydomain.org/pub/linux/fedora/core/updates/2/i386 +yum fedora-core-&FCVER; http://www.mydomain.org/pub/linux/fedora/core/&FCVER;/i386/os +yum fc&FCVER;-updates http://www.mydomain.org/pub/linux/fedora/core/updates/&FCVER;/i386
@@ -1611,7 +1684,7 @@ - From fedora-docs-commits at redhat.com Fri Jul 22 12:44:00 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 22 Jul 2005 08:44:00 -0400 Subject: mirror-tutorial mirror-tutorial-en.xml,1.6,1.7 Message-ID: <200507221244.j6MCi0u8011524@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/mirror-tutorial In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11507 Modified Files: mirror-tutorial-en.xml Log Message: Bump to 0.29, fix entities and note yum versioning for repodata change Index: mirror-tutorial-en.xml =================================================================== RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- mirror-tutorial-en.xml 22 Jul 2005 12:34:43 -0000 1.6 +++ mirror-tutorial-en.xml 22 Jul 2005 12:43:58 -0000 1.7 @@ -2,10 +2,10 @@ + %FEDORA-ENTITIES-EN; - + ]> @@ -126,6 +126,16 @@ + + 0.29 + 2005-07-22 + PaulWFrields + + + Minor note on yum versioning for repodata; fixed entities ref. + + + @@ -1082,10 +1092,10 @@
<command>yum-arch</command> - A directory which supports older versions of yum is - named headers. It is created by using the command - yum-arch, which is run against the directory - under which you want the + A directory which supports older versions of yum + (before 2.2) is named headers. It is created by + using the command yum-arch, which is run against + the directory under which you want the headers directory to appear. The yum-arch program searches recursively through that directory and any subdirectories for RPM packages, and includes them From fedora-docs-commits at redhat.com Fri Jul 22 22:31:10 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 22 Jul 2005 18:31:10 -0400 Subject: yum-software-management yum-software-management-en.xml,1.19,1.20 Message-ID: <200507222231.j6MMVAxR025430@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25413/yum-software-management Modified Files: yum-software-management-en.xml Log Message: All the changes I could make in the 90 seconds of editing time I had... :-) Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- yum-software-management-en.xml 21 Jul 2005 16:54:45 -0000 1.19 +++ yum-software-management-en.xml 22 Jul 2005 22:31:08 -0000 1.20 @@ -140,8 +140,7 @@ man yum -man yum.conf - +man yum.conf yum @@ -238,24 +237,23 @@ A repository is a prepared directory or Website that contains software packages and index files. - Software management utilities like yum + Software management utilities such as yum automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to - manually find and install new applications or updates: you may - use a single command to update all of the software that makes up - your system, or to search for new software by specifying - criteria. In each case the management utility connects to the - repositories that it is configured to use, and checks the - indexes that they provide to find the correct packages. + manually find and install new applications or updates. You may + use a single command to update all system software, or search + for new software by specifying criteria. In each case the + management utility connects to the configured repositories and + checks their indexes to find the correct packages. The package management utilities in &FC; are automatically - configured to use the network of repository servers maintained - by the &FP;. These repositories hold both the software included - with &FC;, and a large selection of additional software, known - as &FEX;. Third-party software developers also provide - repositories for their &FED; compatible packages. + configured to use the network of repositories maintained by the + &FP;. These repositories contain the software included with &FC; + and a large selection of additional software known as + &FEX;. Third-party software developers also provide repositories + for their &FED; compatible packages. From fedora-docs-commits at redhat.com Sat Jul 23 00:18:46 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 22 Jul 2005 20:18:46 -0400 Subject: yum-software-management yum-software-management-en.xml,1.20,1.21 Message-ID: <200507230018.j6N0IkW3027970@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27952 Modified Files: yum-software-management-en.xml Log Message: More style editing, through package arch section Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- yum-software-management-en.xml 22 Jul 2005 22:31:08 -0000 1.20 +++ yum-software-management-en.xml 23 Jul 2005 00:18:43 -0000 1.21 @@ -261,19 +261,20 @@ All of the software provided by the &FP; is Open Source - software, or and can therefore be downloaded and installed + software, and can therefore be downloaded and installed from the network of &FED; repositories without restrictions. - package groups, defined + package groups + defined - You may also manage related packages as sets by using the - package groups provided by the &FED; - repositories. Some third-party repositories add packages to - these groups, or provide their packages as additional groups. + You may also use the package groups + provided by the &FED; repositories to manage related packages as + sets. Some third-party repositories add packages to these + groups, or provide their packages as additional groups. @@ -282,74 +283,86 @@ To view a list of all of the available package groups for your - &FED; system, run the command yum - . + &FED; system, run the command yum + grouplist. - - - Using repositories ensures that you always receive the current - version of the software. If several versions of the same package - are available then your management utility automatically selects - the latest version. - - - - For all of these reasons you should only manually install - software when you are confident that there is no repository that - can currently provide it. If a piece of software on your system - is not available from a repository then you cannot automatically - find or install newer versions. You must keep that product - updated yourself. - - - - Manual Package Installation - + + + + + Use repositories to ensure that you always receive current + versions of software. If several versions of the same package + are available, your management utility automatically selects the + latest version. + + + + Installing Software not from a Repository + + Install software using manual methods only when you are + confident there is no repository which can currently provide + it. You may not be able to manage such software using &FED; + software management utilities. You may need to update that + software with manual methods. + The yum commands shown in this document use - repositories as package sources. Refer to + repositories as package sources. Refer to for details of - using yum to manually install software from - a package file. + using yum to install software from a + package file. - +
About Dependencies - dependencies, defined + dependencies + defined - You must consider package dependencies - when manually installing software. To avoid conflicts and - inconsistencies Linux distributions supply program library files - as separate packages to the applications that use their - functions. Many libraries and command-line utilities are used by - multiple applications. + Some of the files installed on a &FED; distribution are + libraries which may provide functions to + multiple applications. When an application requires a specific + library, the package which contains that library is a + dependency. To properly install a + package, &FED; must first satisfy its dependencies. The + dependency information for a RPM package is stored within the + RPM file. - Management tools like yum use the information - on dependencies stored within packages to ensure that all of the - requirements are met when you install an application. The - packages for any supporting software are automatically be - installed first, if they are not already present on your system. - If a new application has requirements that conflict with - existing software then the installation process safely aborts - without making any changes to your system. - - + The yum utility uses package dependency data + to ensure all its requirements are met during installation. The + yum utility automatically installs packages + for any required software not already present on your system. If + a new application has requirements that conflict with existing + software, yum aborts without making any + changes to your system. + + + + + + + + + + +
Understanding Package Names - packages, hardware compatibility + packages + hardware compatibility - packages, naming + packages + naming Each package file has a long name that indicates several key @@ -360,17 +373,6 @@ tsclient-0.132-4.i386.rpm - Use just the name of the package itself with - yum, except when it is necessary to specify - the exact version or type. For example, use - name-version to specify the exact version - of the application. The package listings provided by - yum itself use the format - name.architecture, to specify the type of - computer that the package is intended for. - - - These naming conventions are valid for the file shown above: @@ -383,8 +385,10 @@ Package name with version number: - tsclient-0.132 + tsclient-0.132-4 + + @@ -395,25 +399,38 @@ + Use only the name of the package with yum, + except when the exact version or type is necessary. When exactly is that required? I fixed the + sentence structure but the meaning is obscure here. + [PWF] For example, use + name-version to specify the exact version + of the application. The package listings provided by + yum use the format + name.architecture to specify the type of + computer for which the package is intended. + + + The hardware architecture is the minimum - type of machine required for that specific package. Packages for - run on any current Intel-compatible - computer. Packages for PowerPC machines, such as Apple Macs, are - indicated with . Packages specified as - have no architecture requirement. + type of machine required for that specific package. Packages + with architecture run on any current + Intel-compatible computer. Packages for PowerPC systems, such as + Apple Power Macintosh, are indicated with . + Packages for systems with 64-bit processors such as Opterons are + indicated with . Packages specified as + have no architecture requirement. Some software may be optimized for particular types of - Intel-compatible machine. For these products, separate packages - may be provided for , - , and - computers. A machine with at least an - Intel Pentium, VIA C3 or compatible CPU is an - . Computers with an Intel Pentium II and - above, or a current model of AMD chip, are - machines. 64-bit PCs use packages for - full 64-bit support. + Intel-compatible machine. Separate packages may be provided for + , , + and computers. A + machine with at least an Intel Pentium, VIA C3 or compatible CPU + may use packages. Computers with an Intel + Pentium Pro and above, or a current model of AMD chip, may use + packages.
From fedora-docs-commits at redhat.com Sat Jul 23 00:37:28 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Fri, 22 Jul 2005 20:37:28 -0400 Subject: securing-filesystems setfacl-en.xml,1.1,NONE Message-ID: <200507230037.j6N0bShu028949@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28930/securing-filesystems Removed Files: setfacl-en.xml Log Message: --- setfacl-en.xml DELETED --- From fedora-docs-commits at redhat.com Sat Jul 23 03:31:16 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Fri, 22 Jul 2005 23:31:16 -0400 Subject: release-notes/FC4 RELEASE-NOTES-en.xml, 1.11, 1.12 splash.xml, 1.10, 1.11 Message-ID: <200507230331.j6N3VGcU001513@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1494 Modified Files: RELEASE-NOTES-en.xml splash.xml Log Message: New section on patented software and the like. Forgot to commit this when I did all the updates to the posted version of the release notes. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-en.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- RELEASE-NOTES-en.xml 19 Jul 2005 20:41:03 -0000 1.11 +++ RELEASE-NOTES-en.xml 23 Jul 2005 03:31:13 -0000 1.12 @@ -37,7 +37,7 @@ - + Index: splash.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/splash.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- splash.xml 7 Jun 2005 19:55:45 -0000 1.10 +++ splash.xml 23 Jul 2005 03:31:13 -0000 1.11 @@ -177,6 +177,176 @@ +
+ MP3 Codecs and Other Patented or Closed Source Software + + This section is a brief explanation of why certain software is not + included in &FC; or &FEX;. This information was drawn directly + from the canonical wiki page: + + + http://fedoraproject.org/wiki/ForbiddenItems + + + A frequent question of the &FP; is why certain items are not + included in &FC; or &FEX;. This briefly explains some of the + reasons. + + + Other items, such as file systems support, requires community + participation. For more information, refer to http://fedoraproject.org/wiki/Wishlist + + + + NTFS + + + NTFS Support is not included in the &FC; kernel because of + patent concerns. Using a file system natively supported by + Linux such as ext3 is a better option. If you must share + files between Windows and Linux on a single system, use + FAT/FAT32 (vfat) instead. For sharing across a network, + Samba is a good option. + + + + + MP3 encode/decode functionality + + + MP3 support is not included in any &FC; application because + MP3 is heavily patented in several regions including the + United States. The patent holder is unwilling to give an + unrestricted patent grant, as required by the GPL. Other + platforms might have paid the royalty and/or included + proprietary software. Other Linux distributions not based in + a region affected by the patent might ship MP3 + decoders/encoders. However, &FC; cannot and does not ship + MP3 decoders/encoders in order to serve the goal of shipping + only free and open source software. Using other open source + formats such as Ogg Vorbis (a lossy codec that has better + quality than MP3) or FLAC (a lossless codec) is highly + recommended. + + + + + NVIDIA 3D drivers + + + The NVIDIA 3D drivers are closed source. &FC; does not + include proprietary binaries. Consider using an Intel or any + other manufacturer that supports open source cards with full + specifications and/or source code. + + + + + ATI 3D drivers + + + The ATI 3D drivers are closed source. &FC; does not include + proprietary binaries. Consider using an Intel or any other + manufacturer that supports open source cards with full + specifications and/or source code. + + + + + RealPlayer + + + RealPlayer is a closed source application. &FC; does not + include proprietary binaries. Consider using open source + codecs that do not have patent restrictions. + + + + + DVD video playback + + + DVD video playback (of CSS encrypted DVDs) may violate the + US DMCA (refer to http://en.wikipedia.org/wiki/DMCA) + because it may be considered circumventing an encryption + mechanism. Additionally, MPEG2 is a patented codec, so even + DVDs without encryption cannot be played. Consider using + open source unencrypted mediums such as Ogg Theora formats. + + + + + Mono + + + Mono packages are not currently included due to potential + legal issues. (Pending more input.) Applications can be + written in other languages that are open source, such as + Python, Perl, or Ruby. Java is cross-platform and GCJ is a + relatively mature open source implementation of it. These + are not direct one-to-one equivalents with .NET but might + serve your purpose. + + + + + Cryptology (mcrypt) + + + Some cryptology related packages such as mcrypt are not + included within &FC; due to US export restrictions. Consider + using non-restricted cryptographical methods instead. + + + + + szip + + + The szip license is too restrictive for inclusion in &FEX;. + Use other open source alternatives. + + + + + + In conclusion: + + + + If it is proprietary, it cannot be included in &FED;. + + + + + If it is legally encumbered, it cannot be included in &FED;. + + + + + If it violates US Federal law, it cannot be included in &FED;. + + + + + Of course, the logical followup is: "But I want to get foo and do + bar, how can I do one of the items listed above?" + + + The unofficial http://fedorafaq.org provides + useful answers on commonly asked questions. However, these are + completely unsupported by the &FP;. The &FP; recommends using free + and open source software alternatives whenever possible. + + + The binary only drivers can be acquired from the vendors. You can + find many interesting things with Google. + +
- + + + @@ -600,32 +602,35 @@ Package Versions - Only the newest version of each package is displayed and used by - yum, unless you specify an older version of a - package. + The yum utility only displays and uses the + newest version of each package, unless you specify an older + version. Downloads are Cached - Downloaded data files and packages are kept for reuse. You may - copy packages from the repository cache directories under - /var/cache/yum/, and use them elsewhere if - you wish. Removing a package from the cache does not affect the - copy of the software installed on your system. + The yum utility keeps Downloaded data files + and packages for reuse. You may copy packages from the + repository cache directories under + /var/cache/yum/, and use them elsewhere if + you wish. If you remove a package from the cache, you do not + affect the copy of the software installed on your system.
Installing New Software with <command>yum</command> - installing software with yum + installing software + software, installing - software, installing + software + installing To install the package tsclient, enter the - command: + command: su -c 'yum install tsclient' @@ -653,12 +658,15 @@ New Services Require Activation - Installing a service does not activate or start it. To - configure a new service to run on bootup, choose - DesktopSystem - Settings Server Settings - Services, or use the - chkconfig command-line utility. + When you install a service, &FED; does not activate or start + it. To configure a new service to run on bootup, choose + + Desktop + System Settings + Server Settings + Services + , or use the chkconfig + and service command-line utilities.
@@ -666,10 +674,12 @@
Updating Software with <command>yum</command> - updating software with yum + updating + software packages - software, updating + software + updating To update the tsclient package to the @@ -688,10 +698,9 @@ New Software Versions Require Reloading - If a piece of software is in use whilst it is updated then the - old version remains active until the software is next loaded. - Services are reloaded by restarting the service. Kernel - updates take effect the next time that the system is booted. + If a piece of software is in use when you update it, the old + version remains active until the software is restarted. Kernel + updates take effect when you reboot the system. @@ -712,8 +721,8 @@ Updating the Entire System - To update all of the packages that make up your &FED; system, - use the commands described in + To update all of the packages on your &FED; system, use the + commands described in . @@ -723,20 +732,21 @@
Removing Software with <command>yum</command> - removing software with yum + removing software - software, removing + software + removing To remove software, yum examines your system - for both the specified software, and any other software that - must also be removed in order to safely uninstall it. + for both the specified software, and any software which claims + it as a dependency. To remove the tsclient package from your - system the full command is: + system, use the command: su -c 'yum remove tsclient' @@ -765,14 +775,16 @@
Searching for Packages with <command>yum</command> - packages, locating + packages + locating - searching for packages + searching + for packages Use the search features of yum to find software - that is available from the defined repositories, or is already + that is available from the configured repositories, or already installed on your system. Searches automatically include both installed and available packages. @@ -782,16 +794,16 @@ The and options of - yum are not case-sensitive. For example, a - query for palmpilot will automatically find - PalmPilot packages. + yum are not case-sensitive. A query for + palmpilot automatically finds + PalmPilot packages. The format of the results depends upon the option. If the query - produces no information then no packages matching the criteria - have been found. + produces no information, there are no packages matching the + criteria.
@@ -799,8 +811,8 @@ To search for a specific package by name, use the - function. For example, to search for the - package tsclient the command would be: + function. To search for the package + tsclient, use the command: su -c 'yum list tsclient' @@ -813,8 +825,8 @@ To make your queries more specific, add other package - attributes. For example, to search for version 0.132 of the - application the command would be: + attributes. To search for version 0.132 of the application, use + the command: su -c 'yum list tsclient-0.132' @@ -830,10 +842,10 @@ - checks the names, descriptions, - summaries and listed package maintainers of all of the available - packages to find those that match. For example, to search for - all packages that relate to PalmPilots, type: + The option checks the names, + descriptions, summaries and listed package maintainers of all of + the available packages to find those that match. For example, to + search for all packages that relate to PalmPilots, type: su -c 'yum search PalmPilot' @@ -848,8 +860,8 @@ The function checks both the files included in the packages and the functions that the software provides. This option requires yum to - download and read much larger index files than other types of - search. + download and read much larger index files than with the + option. @@ -860,25 +872,25 @@ su -c 'yum provides libneon' - To search for all packages that either provide an MTA (Mail - Transport Agent) service, or include files with - mta in their name: + To search for all packages that either provide a MTA (Mail + Transport Agent) service, or include files with + mta in their name: su -c 'yum provides MTA' - For each command, enter the password for the - root account when - prompted. + For each command, at the prompt enter the password for the + root account. Wildcards and Regular Expressions You may use the standard wildcard characters in search - criteria: to represent any one character, - and to mean any characters. Use Perl or - Python regular expressions to carry out more complex queries. + criteria: to represent any one character, + and to mean zero or more characters. Use + Perl or Python regular expressions to carry out more complex + queries.
@@ -887,19 +899,19 @@ Understanding Matches - When carrying out a search yum shows all of - the packages that match your criteria. Packages must meet the - terms of the search exactly to be considered matches, unless you - have used wildcards or a regular expression. + Searches with yum show all of the packages + that match your criteria. Packages must meet the terms of the + search exactly to be considered matches, unless you use + wildcards or a regular expression. - For example, querying for shadowutils or - shadow-util would not produce the package - shadow-utils. This package would match and - be shown if the query was either - shadow-util? or - Shadow*. + For example, a search query for shadowutils + or shadow-util would not produce the + package shadow-utils. This package would + match and be shown if the query was either + shadow-util? or + Shadow*.
@@ -907,26 +919,27 @@
Updating Your System with <command>yum</command> - updating, full system + updating + full system - yum, updating full system + yum + updating full system - Use the option to upgrade all of the - software on your &FED; system to the latest version with one - operation. + Use the option to upgrade all of your + &FED; system software to the latest version with one operation. - To carry out a full system update, type this command: + To perform a full system update, type this command: su -c 'yum update' - Enter the root password - when prompted. + At the prompt, enter the root password.
@@ -936,16 +949,15 @@ The yum package supplied with &FC; includes - scripts to carry out full system updates every day. To activate - automatic daily updates, enter this command: + scripts to perform full system updates every day. To activate + automatic daily updates, enter this command: su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' - Enter the password for the - root account when - prompted. + At the prompt, enter the password for the + root account. @@ -953,12 +965,12 @@ There is no separate yum service that runs - on your system. The command given above enables the control - script /etc/rc.d/init.d/yum. This control - script activates the script - /etc/cron.daily/yum.cron, so that the - cron service will perform the system update - as one of the tasks that are automatically run each day. + on your system. The command given above enables the control + script /etc/rc.d/init.d/yum. This control + script activates the script + /etc/cron.daily/yum.cron, which causes + the cron service to perform the system + update automatically each day.
@@ -970,10 +982,12 @@ &FEX; - repositories, finding + repositories + finding - searching for repositories + searching + for repositories &FED; systems automatically use the &FP; repositories. These @@ -986,35 +1000,32 @@ You must manually configure &FED; 3 systems to use &FEX;, using - the instructions at: - http://fedora.redhat.com/projects/extras/. - Refer to this Website for additional packages for &FED; 1 and - &FED; 2: - http://www.fedora.us/. + the instructions at . For + additional packages for &FED; 1 and &FED; 2, refer to . - If the &FP; does not provide packages for a specific piece of - software, the manufacturer of the software may provide or - recommend a separate repository. Members of the community also - maintain repositories to provide packages for &FED; systems. - Third-party repositories provide information on their Websites. + If the &FP; does not provide a specific software package, the + manufacturer of the software may provide or recommend a separate + repository. Members of the community also maintain repositories to + provide packages for &FED; systems. Third-party repositories + provide information on their web sites.
Adding a Repository as a Package Source - repositories, adding to yum - - - repository definition files, installing + repositories + adding to yum To add an extra repository, place a definition file in the /etc/yum.repos.d/ directory on your system. Package providers make the definition files for their - repositories available on their Websites. + repositories available on their web sites. Definition File Extension @@ -1024,39 +1035,39 @@ - Adding a file to the definitions directory requires - root access. To copy - the definition file example.repo, type the - command: + You must have root + access to add a file to the definitions directory. To copy the + definition file example.repo, type this + command: su -c 'cp example.repo /etc/yum.repos.d/' - Enter the password for the - root account when - prompted. + At the prompt, enter the password for the + root account. The configuration file for each repository should include a - gpgkey setting to specify the location of the - public key that verifies the packages it provides. This public - key is automatically imported the first time that you install - software from the repository. If the configuration file provided - does not include this setting, refer to - . + gpgkey setting. This setting specifies the + location of a public key that verifies the packages provided by + that repository. This public key is automatically imported the + first time you install software from the repository. If the + configuration file provided does not include this setting, refer + to . Repositories and <application>up2date</application> Channels - On &FED; &FCLOCALVER; systems yum - repositories are automatically used as - up2date channels. Repositories must - be separately configured as channels on &FED; 3 and earlier - systems. + Starting with &FED; 4, yum repositories are + automatically used as up2date + channels. On &FED; 3 and earlier systems, you must manually + configure up2date to use these + channels. To do so, edit the + /etc/sysconfig/rhn/sources file.
@@ -1064,28 +1075,29 @@
Manually Authorizing Package Sources - public keys, adding + public keys + adding To manually add a public key to your rpm - keyring, use the feature of the - rpm utility. For example, to import the file - GPG-PUB-KEY.asc, type the following: + keyring, use the feature of the + rpm utility. To import the file + GPG-PUB-KEY.asc, type the following + command: su -c 'rpm --import GPG-PUB-KEY.asc' - Enter the password for the - root account when - prompted. + At the prompt, enter the password for the + root account. - You may also import public keys directly from a Website. For + You may also import public keys directly from a web site. For example, to import the file GPG-PUB-KEY.asc - on the website www.therepository.com - the command would be: + on the web site www.therepository.com + use this command: su -c 'rpm --import http://www.therepository.com/GPG-PUB-KEY.asc' @@ -1095,45 +1107,47 @@
Understanding Repository Compatibility - packages, software compatibility + packages + software compatibility - repositories, compatibility + repositories + compatibility - The &FEX; project provides packages that are built to the same - standards as the packages that are part of &FC;. Third-party - packages should be compatible with these official packages, - unless the provider specifically states otherwise. + The &FEX; project provides packages which are built to the same + standards as &FC; packages. Third-party packages should be + compatible with these official packages, unless the provider + specifically states otherwise. - Refer to the Website of the repository for information on - package compatibility before adding it as a package source. - Repositories often provide packages that are specifically - intended for use with packages that are supplied by other - repositories. In some cases separate third-party repository - providers may each offer different versions of the same - software, preventing those repositories from being safely used - together by your &FED; system. + Refer to the web site of the repository for information on + package compatibility before you add it as a package source. + Repositories often provide packages specifically intended for + use with packages supplied by other repositories. In some cases, + separate third-party repository providers may each offer + different versions of the same software. This situation may + prevent you from safely using those repositories together on + your &FED; system. - Packages that have been made for one version of &FED; are - usually not compatible with other versions of &FED;. The Website - of the provider should specifically state which versions of - &FED; they support. + Packages built for one version of &FED; are usually not + compatible with other versions of &FED;. The web site of the + provider should specifically state which versions of &FED; they + support. Old Versions of <command>yum</command> and Current Repositories The data format for repository indexes changed with version - 2.11 of yum. This was the version supplied - with &FED; 3. Repository providers should specify the versions - of &FED; that they support. To confirm that an unlabeled - repository is compatible with current versions of - yum, check that it has a sub-directory - called repo-data/. + 2.1 of yum. This was the version supplied + with &FED; 3. Repository providers should specify the versions + of &FED; that they support. To confirm that an unlabeled + repository is compatible with current versions of + yum, check that it has a sub-directory + called repodata/.
@@ -1145,53 +1159,65 @@ The yum system does not require any routine maintenance. To ensure that yum operations are - carried out at the best possible speed, disable or remove - repository definitions are no longer required. You may also clear - the files from the yum caches in order to - recover disk space. + carried out at optimal speed, disable or remove repository + definitions which you no longer require. You may also clear the + files from the yum caches in order to recover + disk space.
Disabling or Removing Package Sources - repositories, disabling in yum - - - repositories, removing from yum + repositories + disabling in yum - repository definition files, removing + repositories + removing from yum Set enable=0 in a definition file to prevent - yum using that repository. Any definition - file with this setting is ignored. + yum from using that repository. The + yum utility ignores any definition file with + this setting. To completely remove access to a repository: - - + + Delete the relevant file from - /etc/yum.repos.d/. + /etc/yum.repos.d/. - - + + Delete the cache directory from - /var/cache/yum/. + /var/cache/yum/. - - + + + + + + + + + + + + + +
Clearing the <command>yum</command> Caches - yum, cleaning caches + yum + cleaning caches By design, yum does not automatically delete - any of the packages or package data files that it downloads, so - that they may be reused in future operations. To purge the - header files, use the command: + any of the packages or package data files it downloads, so they + may be reused in future operations. To purge the header files, + use this command: su -c 'yum clean headers' @@ -1280,9 +1308,8 @@ su -c 'yum clean packages' - When using these commands, enter the password for the - root account when - prompted. + When using these commands, at the prompt, enter the password for + the root account. @@ -1290,8 +1317,8 @@ Package management operations download header files and - packages as required, automatically replacing any deleted - files needed for the operation. + packages as required, and automatically replace any deleted + files needed for the operation.
@@ -1302,10 +1329,13 @@
Manually Installing Software - installing software with yum (from a package) + installing software + from a package + software, installing from a package - software, installing from a package + software + installing from a package Use repositories and the standard yum commands @@ -1322,28 +1352,28 @@ You must ensure that the public key for the package source has been imported before installing a package without a repository. - Refer to + Refer to . - As an example, enter this command to install the package + Enter this command to install the package tsclient-0.132-4.i386.rpm: su -c 'yum localinstall tsclient-0.132-4.i386.rpm' - Enter the root password - when prompted. + At the prompt, enter the root password. - Dependencies Must Be Met + Meeting Dependencies You must ensure that all of the dependencies are already - installed on your system, as yum cannot + installed on your system,because yum cannot download additional packages to complete the installation when performing a operation. @@ -1353,103 +1383,101 @@
Using <command>yum</command> with a Proxy Server - proxy server, with yum + proxy server - yum, using a proxy server + yum + using with a proxy server - Repositories may be accessed through standard Web proxy servers. - If your system is connected to the Internet through a Web proxy - server, specify the details of the server in - /etc/yum.conf. The proxy + You may access Repositories through standard web proxy servers. If + your system is connected to the Internet through a web proxy + server, specify the proxy server details in + /etc/yum.conf. The setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and password, specify these by adding - proxy_username and - proxy_password settings. + and + settings. - For example, the settings below enable yum to - use the proxy server mycache.mydomain.com, - connecting to port 3128, with the username - yum-user and the password - qwerty. + The settings below enable yum to use the proxy + server mycache.mydomain.com, connecting + to port 3128, with the username yum-user and the password + qwerty. Configuration File Settings for Using A Proxy Server - - - + +# The proxy server - proxy server:port number +proxy=http://mycache.mydomain.com:3128 +# The account details for yum connections +proxy_username=yum-user +proxy_password=qwerty + Global Settings - Defining a proxy server in /etc/yum.conf - means that all users connect to the proxy - server with those details when using yum. + If you define a proxy server in + /etc/yum.conf, all + users connect to the proxy server with those details when using + yum. To enable proxy access for a specific user, add the lines in the - example box below to their shell profile. For the default + example box below to the user's shell profile. For the default bash shell, the profile is the file - .bash_profile. The settings below enable - yum to use the proxy server - mycache.mydomain.com, connecting to port - 3128. + ~/.bash_profile. The settings below enable + yum to use the proxy server mycache.mydomain.com, connecting + to port 3128. Profile Settings for Using a Proxy Server - - - + +# The Web proxy server used by this account +http_proxy="http://mycache.mydomain.com:3128" +export http_proxy + - If the proxy server requires a username and password then add - these to the URL. For example, to include the username - yum-user and the password - qwerty: + If the proxy server requires a username and password, add these to + the URL. To include the username + yum-user and the password + qwerty, add these settings: Profile Settings for a Secured Proxy Server - - - + +# The Web proxy server, with the username and password for this account +http_proxy="http://yum-user:qwerty at mycache.mydomain.com:3128" +export http_proxy + - <command>http_proxy</command> Variable with Other Utilities + The <option>http_proxy</option> Environment + Variable - The http_proxy variable is also used by - curl and other utilities. Although - yum itself may use - http_proxy in either upper-case or - lower-case, curl requires the name of the - variable to be in lower-case. + The http_proxy environment variable is also + used by curl and other utilities. Although + yum itself may use + http_proxy in either upper-case or + lower-case, curl requires the name of the + variable to be in lower-case.
From fedora-docs-commits at redhat.com Mon Jul 25 02:12:48 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 24 Jul 2005 22:12:48 -0400 Subject: yum-software-management yum-software-management-en.xml,1.23,1.24 Message-ID: <200507250212.j6P2Cmbt001696@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1679 Modified Files: yum-software-management-en.xml Log Message: A little further through the style wringer... Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- yum-software-management-en.xml 24 Jul 2005 17:28:24 -0000 1.23 +++ yum-software-management-en.xml 25 Jul 2005 02:12:45 -0000 1.24 @@ -207,15 +207,14 @@ defined - All of the software and documentation prepared for use with - &FED; is supplied in the form of files called RPM - packages. Each package is a compressed - archive containing product information, program files, icons, - documentation and management scripts. Management applications - use these files to safely locate, install, update and remove - software. For example, the &FED; installation process uses the - packages supplied with &FC; to build or upgrade a system to your - requirements. + &FED; software and documentation is supplied in the form of + files called RPM packages. Each package + is a compressed archive containing product information, program + files, icons, documentation and management scripts. Management + applications use these files to safely locate, install, update + and remove software. For example, the &FED; installation process + uses the packages supplied with &FC; to build or upgrade a + system to your requirements. @@ -237,7 +236,7 @@ A repository is a prepared directory or - Website that contains software packages and index files. + web site that contains software packages and index files. Software management utilities such as yum automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to @@ -249,24 +248,23 @@ - The package management utilities in &FC; are automatically - configured to use the network of repositories maintained by the - &FP;. These repositories contain the software included with &FC; - and a large selection of additional software known as - &FEX;. Third-party software developers also provide repositories - for their &FED; compatible packages. + The package management utilities in &FC; are already configured + to use the network of repositories maintained by the &FP;. These + repositories contain the software included with &FC; and a large + selection of additional software known as &FEX;. Third-party + software developers also provide repositories for their &FED; + compatible packages. All &FED; Packages are Open Source Software - All of the software provided by the &FP; is Open Source - software, and can therefore be downloaded and installed - from the network of &FED; repositories without restrictions. + All of the software provided by the &FP; is open source + software. You may download and install software from the &FP; + network of repositories on as many systems as desired. - package groups defined @@ -303,9 +301,8 @@ Install software using manual methods only when you are confident there is no repository which can currently provide - it. You may not be able to manage such software using &FED; - software management utilities. You may need to update that - software with manual methods. + it. You may have to manage that software with manual methods, + instead of with &FED; software management utilities. The yum commands shown in this document use @@ -367,8 +364,8 @@ Each package file has a long name that indicates several key - pieces of information. For example, this is the full name of a - package supplied with &FC;: + pieces of information. This is the full name of the + tsclient package supplied with &FC;: tsclient-0.132-4.i386.rpm @@ -385,8 +382,8 @@ - Package name with version number: - tsclient-0.132-4 + Package name with version and release numbers: + tsclient-0.132-4 @@ -395,7 +392,7 @@ Package name with hardware architecture: - tsclient.i386 + tsclient.i386 @@ -413,6 +410,11 @@ computer for which the package is intended. + + + + + The hardware architecture is the minimum type of machine required for that specific package. Packages From fedora-docs-commits at redhat.com Mon Jul 25 02:23:23 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Sun, 24 Jul 2005 22:23:23 -0400 Subject: yum-software-management yum-software-management-en.xml,1.24,1.25 Message-ID: <200507250223.j6P2NNmo001734@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1717 Modified Files: yum-software-management-en.xml Log Message: Trivial corrections for typos Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- yum-software-management-en.xml 25 Jul 2005 02:12:45 -0000 1.24 +++ yum-software-management-en.xml 25 Jul 2005 02:23:20 -0000 1.25 @@ -1375,7 +1375,7 @@ You must ensure that all of the dependencies are already - installed on your system,because yum cannot + installed on your system, because yum cannot download additional packages to complete the installation when performing a operation. @@ -1392,7 +1392,7 @@ using with a proxy server - You may access Repositories through standard web proxy servers. If + You may access repositories through standard web proxy servers. If your system is connected to the Internet through a web proxy server, specify the proxy server details in /etc/yum.conf. The From fedora-docs-commits at redhat.com Mon Jul 25 19:16:14 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Mon, 25 Jul 2005 15:16:14 -0400 Subject: yum-software-management yum-software-management-en.xml,1.25,1.26 Message-ID: <200507251916.j6PJGEto025885@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25868 Modified Files: yum-software-management-en.xml Log Message: Making the title all beta like and my local version in sync for more betas, change back when ready to publish final. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- yum-software-management-en.xml 25 Jul 2005 02:23:20 -0000 1.25 +++ yum-software-management-en.xml 25 Jul 2005 19:16:12 -0000 1.26 @@ -17,7 +17,8 @@
- Software Management with <command>yum</command> + Software Management with <command>yum</command> - + <emphasis>BETA DOCUMENT</emphasis> 2005 Stuart Ellis From fedora-docs-commits at redhat.com Mon Jul 25 19:51:21 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Mon, 25 Jul 2005 15:51:21 -0400 Subject: yum-software-management yum-software-management-en.xml,1.26,1.27 Message-ID: <200507251951.j6PJpL3j026263@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26246 Modified Files: yum-software-management-en.xml Log Message: Bumped reivsion to 0.6 following style edits Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- yum-software-management-en.xml 25 Jul 2005 19:16:12 -0000 1.26 +++ yum-software-management-en.xml 25 Jul 2005 19:51:19 -0000 1.27 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -51,6 +51,16 @@ + + 0.6 + 2005-07-25 + PaulWFrields + + + Edited for style and usage; BETA publication. + + + From fedora-docs-commits at redhat.com Mon Jul 25 21:58:01 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Mon, 25 Jul 2005 17:58:01 -0400 Subject: yum-software-management yum-software-management-en.xml,1.27,1.28 Message-ID: <200507252158.j6PLw1Kc029221@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29204 Modified Files: yum-software-management-en.xml Log Message: - Restructured "Understanding Package Names" - Style fixes Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- yum-software-management-en.xml 25 Jul 2005 19:51:19 -0000 1.27 +++ yum-software-management-en.xml 25 Jul 2005 21:57:58 -0000 1.28 @@ -17,8 +17,8 @@
- Software Management with <command>yum</command> - - <emphasis>BETA DOCUMENT</emphasis> + Software Management with <command>yum</command> - <emphasis>BETA + DOCUMENT</emphasis> 2005 Stuart Ellis @@ -52,14 +52,14 @@ - 0.6 - 2005-07-25 - PaulWFrields - - - Edited for style and usage; BETA publication. - - + 0.6 + 2005-07-25 + PaulWFrields + + + Edited for style and usage; BETA publication. + + @@ -166,6 +166,7 @@ + Other useful yum resources on the Internet include: @@ -174,7 +175,7 @@ - Web home page + Project web site @@ -215,27 +216,27 @@ About Packages packages - defined + defined &FED; software and documentation is supplied in the form of - files called RPM packages. Each package - is a compressed archive containing product information, program - files, icons, documentation and management scripts. Management - applications use these files to safely locate, install, update - and remove software. For example, the &FED; installation process - uses the packages supplied with &FC; to build or upgrade a - system to your requirements. + files called RPM packages. Each package + is a compressed archive containing product information, program + files, icons, documentation and management scripts. Management + applications use these files to safely locate, install, update + and remove software. For example, the &FED; installation process + uses the packages supplied with &FC; to build or upgrade a + system to your requirements. Packages also include a digital signature to prove their source. - Software management utilities verify this digital signature by - using a GPG public key. The - yum and rpm utilities - share a common keyring that stores all of - the public keys for approved package sources. The system - administrator configures these approved package sources. + Software management utilities verify this digital signature by + using a GPG public key. The + yum and rpm utilities + share a common keyring that stores all of + the public keys for approved package sources. The system + administrator configures these approved package sources.
@@ -243,7 +244,7 @@ About Repositories repositories - defined + defined A repository is a prepared directory or @@ -251,7 +252,7 @@ Software management utilities such as yum automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to - manually find and install new applications or updates. You may + manually find and install new applications or updates. You may use a single command to update all system software, or search for new software by specifying criteria. In each case the management utility connects to the configured repositories and @@ -260,11 +261,11 @@ The package management utilities in &FC; are already configured - to use the network of repositories maintained by the &FP;. These - repositories contain the software included with &FC; and a large - selection of additional software known as &FEX;. Third-party - software developers also provide repositories for their &FED; - compatible packages. + to use the network of repositories maintained by the &FP;. These + repositories contain the software included with &FC; and a large + selection of additional software known as &FEX;. Third-party + software developers also provide repositories for their &FED; + compatible packages. @@ -272,19 +273,19 @@ All of the software provided by the &FP; is open source - software. You may download and install software from the &FP; - network of repositories on as many systems as desired. + software. You may download and install software from the &FP; + network of repositories on as many systems as desired. package groups - defined + defined You may also use the package groups - provided by the &FED; repositories to manage related packages as - sets. Some third-party repositories add packages to these - groups, or provide their packages as additional groups. + provided by the &FED; repositories to manage related packages as + sets. Some third-party repositories add packages to these + groups, or provide their packages as additional groups. @@ -293,34 +294,34 @@ To view a list of all of the available package groups for your - &FED; system, run the command yum - grouplist. + &FED; system, run the command su -c 'yum + grouplist'. - - - + Use repositories to ensure that you always receive current - versions of software. If several versions of the same package - are available, your management utility automatically selects the - latest version. + versions of software. If several versions of the same package + are available, your management utility automatically selects the + latest version. - Installing Software not from a Repository - - Install software using manual methods only when you are - confident there is no repository which can currently provide - it. You may have to manage that software with manual methods, - instead of with &FED; software management utilities. - + Installing Software not from a Repository + + + Install software using manual methods only when you are + confident there is no repository which can currently provide + it. You may have to manage that software with manual methods, + instead of with &FED; software management utilities. + + The yum commands shown in this document use - repositories as package sources. Refer to + repositories as package sources. Refer to for details of - using yum to install software from a - package file. + using yum to install software from a + package file.
@@ -329,60 +330,51 @@ About Dependencies dependencies - defined + defined - Some of the files installed on a &FED; distribution are - libraries which may provide functions to - multiple applications. When an application requires a specific - library, the package which contains that library is a - dependency. To properly install a - package, &FED; must first satisfy its dependencies. The - dependency information for a RPM package is stored within the - RPM file. + Some of the files installed on a &FED; distribution are + libraries which may provide functions to + multiple applications. When an application requires a specific + library, the package which contains that library is a + dependency. To properly install a + package, &FED; must first satisfy its dependencies. The + dependency information for a RPM package is stored within the + RPM file. The yum utility uses package dependency data - to ensure all its requirements are met during installation. The - yum utility automatically installs packages - for any required software not already present on your system. If - a new application has requirements that conflict with existing - software, yum aborts without making any - changes to your system. - - - - - - - - - - - + to ensure that all of requirements for an application are met + during installation. It automatically installs the packages for + any dependencies not already present on your system. If a new + application has requirements that conflict with existing + software, yum aborts without making any + changes to your system. +
Understanding Package Names packages - hardware compatibility + hardware compatibility packages - naming + naming Each package file has a long name that indicates several key - pieces of information. This is the full name of the - tsclient package supplied with &FC;: + pieces of information. This is the full name of the + tsclient package supplied with &FC;: tsclient-0.132-4.i386.rpm - These naming conventions are valid for the file shown above: + Management utilities refer to packages with one of three + formats: @@ -394,7 +386,7 @@ Package name with version and release numbers: - tsclient-0.132-4 + tsclient-0.132-4 @@ -403,50 +395,111 @@ Package name with hardware architecture: - tsclient.i386 + tsclient.i386 - - - Use only the name of the package with yum, - except when the exact version or type is necessary. When exactly is that required? I fixed the - sentence structure but the meaning is obscure here. Tell the - reader the full story here. [PWF] For example, use - name-version to specify the exact version - of the application. The package listings provided by - yum use the format - name.architecture to specify the type of - computer for which the package is intended. - - - - The hardware architecture is the minimum - type of machine required for that specific package. Packages - with architecture run on any current - Intel-compatible computer. Packages for PowerPC systems, such as - Apple Power Macintosh, are indicated with . - Packages for systems with 64-bit processors such as Opterons are - indicated with . Packages specified as - have no architecture requirement. + For clarity, yum itself lists packages in the + format name.architecture. Repositories also + commonly store packages in separate directories by architecture. + In each case, the hardware architecture specified for the + package is the minimum type of machine + required to use the package. + + + + i386 + + + + Suitable for any current Intel-compatible computer + + + + + + + noarch + + + + Compatible with all computer architectures + + + + + + + ppc + + + + Suitable for PowerPC systems, such as Apple Power + Macintosh + + + + + + + x86_64 + + + + Suitable for 64-bit Intel-compatible processors, such as + Opterons + + + + + Some software may be optimized for particular types of - Intel-compatible machine. Separate packages may be provided for - , , - and computers. A - machine with at least an Intel Pentium, VIA C3 or compatible CPU - may use packages. Computers with an Intel - Pentium Pro and above, or a current model of AMD chip, may use - packages. + Intel-compatible machine. Separate packages may be provided for + , , + and computers. A + machine with at least an Intel Pentium, VIA C3 or compatible CPU + may use packages. Computers with an Intel + Pentium Pro and above, or a current model of AMD chip, may use + packages. + + + Use the short name of the package for yum + commands. This causes yum to automatically + select the most recent package in the repositories that matches + the hardware architecture of your computer. + + + + Specify a package with other name formats to override the + default behavior and force yum to use the + package that matches that version or architecture. Only override + yum when you know that the default package + selection has a bug or other fault that makes it unsuitable for + installation. + + + Package Names + + You may use any of the following formats to specify a package + in a yum operation: + name, + name.architecture, + name-version, + name-version-release, + name-version-release.architecture, + and + epoch:name-version-release.architecture. + +
@@ -479,13 +532,11 @@ &FC; also includes system-config-packages. To run this - application from the graphical interface, select - - Desktop - System Settings - Add/Remove Applications - . Unlike up2date and - yum, + application from the graphical interface, select + Desktop System + Settings Add/Remove + Applications . Unlike + up2date and yum, system-config-packages installs software packages from your &FC; installation discs only, and does not use repositories. This application is used on systems that do @@ -507,9 +558,9 @@ The up2date and - yum utilities ensure that you have the most - recent version of software packages. Other methods do not - guarantee that the packages are current. + yum utilities ensure that you have the most + recent version of software packages. Other methods do not + guarantee that the packages are current. @@ -521,26 +572,25 @@ software management - The yum utility may modify the software on your - system in three ways: + Use the yum utility to modify the software on + your system in three ways: - It may install new software from repositories or a package - file. + To install new software from repositories or a package file - It may update existing software on your system. + To update existing software on your system - It may remove unwanted software from your system. + To remove unwanted software from your system @@ -551,23 +601,11 @@ packages or package groups. Each section below gives some examples. - - Package Names - - You may use any of the following formats to specify a package in - a yum operation: name, - name.architecture, - name-version, - name-version-release, - name-version-release.architecture, and - epoch:name-version-release.architecture. - - + - To use the repositories yum downloads data - files from each of the configured repositories. On a slow - connection, it may take several seconds to download the required - files for each package. + yum downloads data files from each of the + configured repositories. On a slow connection, it may take several + seconds to download the required files for each package. @@ -581,9 +619,10 @@ Format of <command>yum</command> Transaction Reports + - This is an example of the transaction for installing - tsclient: + This is an example of the transaction for installing + tsclient: ============================================================================= @@ -605,10 +644,13 @@ - Review the list of changes, and then press y to - accept and begin the process. If you press N or - Enter, yum does not download - or change any packages. + Review the list of changes, and then press + y + to accept and begin the process. If you press + N + or + Enter + , yum does not download or change any packages. @@ -616,34 +658,34 @@ The yum utility only displays and uses the - newest version of each package, unless you specify an older - version. + newest version of each package, unless you specify an older + version. Downloads are Cached The yum utility keeps Downloaded data files - and packages for reuse. You may copy packages from the - repository cache directories under - /var/cache/yum/, and use them elsewhere if - you wish. If you remove a package from the cache, you do not - affect the copy of the software installed on your system. + and packages for reuse. You may copy packages from the + repository cache directories under + /var/cache/yum/, and use them elsewhere if + you wish. If you remove a package from the cache, you do not + affect the copy of the software installed on your system.
Installing New Software with <command>yum</command> - installing software - software, installing + installing software + software, installing software - installing + installing To install the package tsclient, enter the - command: + command: su -c 'yum install tsclient' @@ -672,14 +714,12 @@ When you install a service, &FED; does not activate or start - it. To configure a new service to run on bootup, choose - - Desktop - System Settings - Server Settings - Services - , or use the chkconfig - and service command-line utilities. + it. To configure a new service to run on bootup, choose + Desktop System + Settings Server Settings + Services , or use the + chkconfig and service + command-line utilities.
@@ -687,12 +727,12 @@
Updating Software with <command>yum</command> - updating - software packages + updating + software packages software - updating + updating To update the tsclient package to the @@ -712,8 +752,8 @@ If a piece of software is in use when you update it, the old - version remains active until the software is restarted. Kernel - updates take effect when you reboot the system. + version remains active until the software is restarted. Kernel + updates take effect when you reboot the system. @@ -735,7 +775,7 @@ To update all of the packages on your &FED; system, use the - commands described in + commands described in . @@ -749,7 +789,7 @@ software - removing + removing To remove software, yum examines your system @@ -807,9 +847,9 @@ The and options of - yum are not case-sensitive. A query for - palmpilot automatically finds - PalmPilot packages. + yum are not case-sensitive. A query for + palmpilot automatically finds + PalmPilot packages. @@ -824,8 +864,8 @@ To search for a specific package by name, use the - function. To search for the package - tsclient, use the command: + function. To search for the package + tsclient, use the command: su -c 'yum list tsclient' @@ -838,8 +878,8 @@ To make your queries more specific, add other package - attributes. To search for version 0.132 of the application, use - the command: + attributes. To search for version 0.132 of the application, use + the command: su -c 'yum list tsclient-0.132' @@ -856,9 +896,9 @@ The option checks the names, - descriptions, summaries and listed package maintainers of all of - the available packages to find those that match. For example, to - search for all packages that relate to PalmPilots, type: + descriptions, summaries and listed package maintainers of all of + the available packages to find those that match. For example, to + search for all packages that relate to PalmPilots, type: su -c 'yum search PalmPilot' @@ -886,8 +926,8 @@ To search for all packages that either provide a MTA (Mail - Transport Agent) service, or include files with - mta in their name: + Transport Agent) service, or include files with + mta in their name: su -c 'yum provides MTA' @@ -900,10 +940,10 @@ Wildcards and Regular Expressions You may use the standard wildcard characters in search - criteria: to represent any one character, - and to mean zero or more characters. Use - Perl or Python regular expressions to carry out more complex - queries. + criteria: to represent any one character, + and to mean zero or more characters. Use + Perl or Python regular expressions to carry out more complex + queries.
@@ -913,18 +953,18 @@ Searches with yum show all of the packages - that match your criteria. Packages must meet the terms of the - search exactly to be considered matches, unless you use - wildcards or a regular expression. + that match your criteria. Packages must meet the terms of the + search exactly to be considered matches, unless you use + wildcards or a regular expression. For example, a search query for shadowutils - or shadow-util would not produce the - package shadow-utils. This package would - match and be shown if the query was either - shadow-util? or - Shadow*. + or shadow-util would not produce the + package shadow-utils. This package would + match and be shown if the query was either + shadow-util? or + Shadow*. @@ -951,7 +991,8 @@ su -c 'yum update' - At the prompt, enter the root password. @@ -962,8 +1003,8 @@ The yum package supplied with &FC; includes - scripts to perform full system updates every day. To activate - automatic daily updates, enter this command: + scripts to perform full system updates every day. To activate + automatic daily updates, enter this command: su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' @@ -978,12 +1019,12 @@ There is no separate yum service that runs - on your system. The command given above enables the control - script /etc/rc.d/init.d/yum. This control - script activates the script - /etc/cron.daily/yum.cron, which causes - the cron service to perform the system - update automatically each day. + on your system. The command given above enables the control + script /etc/rc.d/init.d/yum. This control + script activates the script + /etc/cron.daily/yum.cron, which causes + the cron service to perform the system + update automatically each day. @@ -1013,9 +1054,11 @@ You must manually configure &FED; 3 systems to use &FEX;, using - the instructions at . For - additional packages for &FED; 1 and &FED; 2, refer to . @@ -1032,7 +1075,7 @@ Adding a Repository as a Package Source repositories - adding to yum + adding to yum To add an extra repository, place a definition file in the @@ -1049,9 +1092,9 @@ You must have root - access to add a file to the definitions directory. To copy the - definition file example.repo, type this - command: + access to add a file to the definitions directory. To copy the + definition file example.repo, type this + command: su -c 'cp example.repo /etc/yum.repos.d/' @@ -1063,12 +1106,12 @@ The configuration file for each repository should include a - gpgkey setting. This setting specifies the - location of a public key that verifies the packages provided by - that repository. This public key is automatically imported the - first time you install software from the repository. If the - configuration file provided does not include this setting, refer - to . + gpgkey setting. This setting specifies the + location of a public key that verifies the packages provided by + that repository. This public key is automatically imported the + first time you install software from the repository. If the + configuration file provided does not include this setting, refer + to . @@ -1076,11 +1119,11 @@ Starting with &FED; 4, yum repositories are - automatically used as up2date - channels. On &FED; 3 and earlier systems, you must manually - configure up2date to use these - channels. To do so, edit the - /etc/sysconfig/rhn/sources file. + automatically used as up2date + channels. On &FED; 3 and earlier systems, you must manually + configure up2date to use these + channels. To do so, edit the + /etc/sysconfig/rhn/sources file. @@ -1089,14 +1132,14 @@ Manually Authorizing Package Sources public keys - adding + adding To manually add a public key to your rpm - keyring, use the feature of the - rpm utility. To import the file - GPG-PUB-KEY.asc, type the following - command: + keyring, use the feature of the + rpm utility. To import the file + GPG-PUB-KEY.asc, type the following + command: su -c 'rpm --import GPG-PUB-KEY.asc' @@ -1121,46 +1164,46 @@ Understanding Repository Compatibility packages - software compatibility + software compatibility repositories - compatibility + compatibility The &FEX; project provides packages which are built to the same - standards as &FC; packages. Third-party packages should be - compatible with these official packages, unless the provider - specifically states otherwise. + standards as &FC; packages. Third-party packages should be + compatible with these official packages, unless the provider + specifically states otherwise. Refer to the web site of the repository for information on - package compatibility before you add it as a package source. - Repositories often provide packages specifically intended for - use with packages supplied by other repositories. In some cases, - separate third-party repository providers may each offer - different versions of the same software. This situation may - prevent you from safely using those repositories together on - your &FED; system. + package compatibility before you add it as a package source. + Repositories often provide packages specifically intended for + use with packages supplied by other repositories. In some cases, + separate third-party repository providers may each offer + different versions of the same software. This situation may + prevent you from safely using those repositories together on + your &FED; system. Packages built for one version of &FED; are usually not - compatible with other versions of &FED;. The web site of the - provider should specifically state which versions of &FED; they - support. + compatible with other versions of &FED;. The web site of the + provider should specifically state which versions of &FED; they + support. Old Versions of <command>yum</command> and Current Repositories The data format for repository indexes changed with version - 2.1 of yum. This was the version supplied - with &FED; 3. Repository providers should specify the versions - of &FED; that they support. To confirm that an unlabeled - repository is compatible with current versions of - yum, check that it has a sub-directory - called repodata/. + 2.1 of yum. This was the version supplied + with &FED; 3. Repository providers should specify the versions + of &FED; that they support. To confirm that an unlabeled + repository is compatible with current versions of + yum, check that it has a sub-directory + called repodata/. @@ -1182,17 +1225,17 @@ Disabling or Removing Package Sources repositories - disabling in yum + disabling in yum repositories - removing from yum + removing from yum Set enable=0 in a definition file to prevent - yum from using that repository. The - yum utility ignores any definition file with - this setting. + yum from using that repository. The + yum utility ignores any definition file with + this setting. @@ -1202,17 +1245,16 @@ Delete the relevant file from - /etc/yum.repos.d/. + /etc/yum.repos.d/. Delete the cache directory from - /var/cache/yum/. + /var/cache/yum/. - @@ -1221,7 +1263,6 @@ - -
Clearing the <command>yum</command> Caches yum - cleaning caches + cleaning caches By design, yum does not automatically delete - any of the packages or package data files it downloads, so they - may be reused in future operations. To purge the header files, - use this command: + any of the packages or package data files it downloads, so they + may be reused in future operations. To purge the header files, + use this command: su -c 'yum clean headers' @@ -1322,7 +1362,7 @@ When using these commands, at the prompt, enter the password for - the root account. + the root account. @@ -1330,8 +1370,8 @@ Package management operations download header files and - packages as required, and automatically replace any deleted - files needed for the operation. + packages as required, and automatically replace any deleted + files needed for the operation.
@@ -1377,7 +1417,8 @@ su -c 'yum localinstall tsclient-0.132-4.i386.rpm' - At the prompt, enter the root password. @@ -1409,18 +1450,19 @@ /etc/yum.conf. The setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and - password, specify these by adding - and - settings. + password, specify these by adding + and settings. The settings below enable yum to use the proxy - server mycache.mydomain.com, connecting - to port 3128, with the username yum-user and the password - qwerty. + server + mycache.mydomain.com, + connecting to port 3128, with the username + yum-user and the + password qwerty. @@ -1439,9 +1481,9 @@ If you define a proxy server in - /etc/yum.conf, all - users connect to the proxy server with those details when using - yum. + /etc/yum.conf, all + users connect to the proxy server with those details when using + yum. @@ -1450,9 +1492,10 @@ example box below to the user's shell profile. For the default bash shell, the profile is the file ~/.bash_profile. The settings below enable - yum to use the proxy server mycache.mydomain.com, connecting - to port 3128. + yum to use the proxy server + mycache.mydomain.com, + connecting to port 3128. @@ -1467,8 +1510,8 @@ If the proxy server requires a username and password, add these to the URL. To include the username - yum-user and the password - qwerty, add these settings: + yum-user and the + password qwerty, add these settings: @@ -1481,16 +1524,15 @@ - The <option>http_proxy</option> Environment - Variable + The <option>http_proxy</option> Environment Variable The http_proxy environment variable is also - used by curl and other utilities. Although - yum itself may use - http_proxy in either upper-case or - lower-case, curl requires the name of the - variable to be in lower-case. + used by curl and other utilities. Although + yum itself may use + http_proxy in either upper-case or + lower-case, curl requires the name of the + variable to be in lower-case. From fedora-docs-commits at redhat.com Tue Jul 26 03:50:00 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Mon, 25 Jul 2005 23:50:00 -0400 Subject: hardening hardening-tutorial-en.xml, NONE, 1.1 Makefile, 1.1, 1.2 fedora-hardening-guide-en.xml, 1.1, NONE Message-ID: <200507260350.j6Q3o0eS004471@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/hardening In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4454 Modified Files: Makefile Added Files: hardening-tutorial-en.xml Removed Files: fedora-hardening-guide-en.xml Log Message: Updating to use new Makefile, renamed file and tutorial to match scope of document and FDP, other standardization changes. --- NEW FILE hardening-tutorial-en.xml --- %FEDORA-ENTITIES-EN; ]> &FC; &FCLOCALVER; Hardening Tutorial 2005 &FORMAL-RHI; Charles Heselton Heselton Charles &LEGALNOTICE; Introduction &DRAFTNOTICE; This tutorial is a basic walk-through of how to harden a basic install of &FC;. Many of the actions and principles discussed here will apply to many different linux distributions. However, for the purpose of this tutorial we will be regarding &FC;, specifically. Document Scope While describing the techniques and tools used in this tutorial, it is the goal of the author to present both the Graphical User Interface (GUI) tools, and the more traditional command line (CLI) tools that are available in FC3. Many users will have customized the appearance of their desktop (if running one), panels, menus, etc. This guide makes direction based on the default install and configuration of &FC;. The locations of items, menus, commands, etc. may differ from your actual experience. Intended Audience This document is intended for use by all &FC; users. However, there is a focus for home or small-business users. Enterprise deployments of Fedora will want to make some different considerations such as centralized syslog storage, unified (central) user authentication, etc. Most of the principles discussed will apply, however there are some enterprise applications which are outside the scope of this document. Initial Steps &DRAFTNOTICE; Package Installation Considerations This section will not go into the actual process of installing packages, that falls under the scope of the Installation Guide. However, there are some important things to consider, in regards to security, when you are installing &FC; and selecting your packages for installation, and when you are installing new packages on an already built system. Package Selections During Install When you are first installing your &FC; system, take careful consideration of the packages that you are installing. Know what type of system you are building before you build it. Fedora offers a "system role" method of choosing packages, which can be customized to remove or not install certain packages, and install others that may not be designated as part of that particular role. A good approach would be to, first, draw out a plan of what your system is to be used for, and what services you will want to offer (if any). You can then make an educated decision about what installation type you want to start with. Fedora offers the following in terms of installation types: Personal Desktop Workstation Server Custom You can then check the "Select specific packages" to modify your installation, or use the Add and Remove Progams GUI utility, or the yum command line utility, to install any additional packages required for your needs. Package Considerations for Installation of New Software If you are updating, or adding to, a system that is already installed with &FC;, then there are some other considerations that need to be made. When installing a new package, you should check the integrity of the package. Most reliable sources will provide a signed checksum file for a package file. You can use gpg or md5sum to verify the checksum provided, depending on the digital signature provided. gpg is a utility which allows you to manage digital signatures. These signatures allow you to digitally sign or encrypt data (including text messages or files). For more details on gpg visit the GNU gpg website at http://www.gnupg.org. md5sum is a utility which is based off of the MD5 algorithm. This utility can be used to create a digital signature of a file, which can then be compared to the MD5 checksum downloaded with the software package. For more details on the MD5 hashing algorithm, and associated utilities, you can visit the MD5 website at http://www.fourmilab.ch/md5/. The actual source of the package must come into consideration as well. If you are downloading new packages from fedora.redhat.com, the package and checksum should be fairly trustworthy. However, if you are downloading the package from www.myanonymoussoftwaresite.com, you may want to try to find another source for the package, or further verify the integrity of the site. You can find a brief description of how to verify a downloaded file with the provided checksum in the following two sections. <command>gpg</command> usage example Verifying a file with gpg is a method of verifying a file's integrity with a digital signature. In porder for this to work, you must have the signer's public key, or digital signature, on your local keyring. If you are totally lost at this point, you should go back and read the documentation on the GNUpg site, linked above. For this example, we're going to download and test a kernel image from ftp://ftp.kernel.org. As just stated, we need to get the key for the Linux Kernel Archives. However, first we need to make sure that our gpg comfiguration is complete. Start by issuing the following command to see if our home configuration directory exists or not. (If you have never used gpg, this directory will not exist.) ls -d ~/.gnupg If your directory exists, you will see something along the lines of the following: /home/charlie/.gnupg Of course, unless your username happens to be "charlie", this part of the path will be something different. If your directory does not exist, then you will see something like this: ls: /home/charlie/.gnupg: No such file or directory ... and you will need to create that directory ... mkdir ~/.gnupg Next, you will need to create your own keys, which will also initialize your gpg public and private keyrings. gpg --gen-key You will be prompted with the following: gpg (GnuPG) 1.2.6; Copyright (C) 2004 Free Software Foundation, Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the file COPYING for details. Please select what kind of key you want: (1) DSA and ElGamal (default) (2) DSA (sign only) (4) RSA (sign only) Your selection? Option one (1) is the option you should choose if you ever might want to encrypt anything. The other two options only allow you to sign. After you make your selection, you will be asked a series of questions about yourself (name, email, etc.), and you will be asked for a passphrase. Once the key has been created, you will be prompted with your new gpg fingerprint: public and secret key created and signed. key marked as ultimately trusted. pub 1024D/834AA506 2005-04-08 Bogus (Bogus key) <bogus at foo.com> Key fingerprint = 8F0F CDA0 1682 58B2 F38D 31AF CD8A 6FD5 834A A506 sub 1024g/0F43BE0D 2005-04-08 If you have never used gpg before, you may also receive messages regarding the creation of your public and private keyrings. Now that you have your keyrings in place, you need to add the Linux Kernel Archive public key to your key ring. This process is described in detail at the following URL: http://www.kernel.org/signature.html However, the process is summarized in one simple step for you below: gpg --keyserver wwwkeys.pgp.net --recv-keys 0x517D0F0E When you downloaded the kernel file, you should have also downloaded a linux-2.x.x.x.tar.gz.sign file. This file contains the signature of the file you downloaded that was created with the Archive public key. In order to get that warm and fuzzy when we verify the file. We will also want to sign the key we just downloaded. gpg --lsign-key 517D0F0E pub 1024D/517D0F0E created: 2000-10-10 expires: never trust: -/- sub 4096g/E50A8F2A created: 2000-10-10 expires: never (1). Linux Kernel Archives Verification Key <ftpadmin at kernel.org> pub 1024D/517D0F0E created: 2000-10-10 expires: never trust: -/- Primary key fingerprint: C75D C40A 11D7 AF88 9981 ED5B C86B A06A 517D 0F0E Linux Kernel Archives Verification Key <ftpadmin at kernel.org> How carefully have you verified the key you are about to sign actually belongs to the person named above? If you don't know what to answer, enter "0". (0) I will not answer. (default) (1) I have not checked at all. (2) I have done casual checking. (3) I have done very careful checking. Your selection? (enter '?' for more information): 2 Are you really sure that you want to sign this key with your key: "Tuxxer (Tuxxer) <tuxxer at cox.net>" (F1E11EA1) I have checked this key casually. Really sign? y Option two (2) in the dialog described above is a good selection if you are somewhat familiar with the person or group owning the key. Now on to the downloading and verifying. The download process is outlined below: ftp ftp.kernel.org Connected to ftp.kernel.org (204.152.191.37). 220 Welcome to ftp.kernel.org. Name (ftp.kernel.org:charlie): anonymous 331 Please specify the password. Password: 230- Welcome to the 230- LINUX KERNEL ARCHIVES 230- ftp.kernel.org 230- < ... snip kernel.org banner stuff ... > 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> cd /pub/linux/kernel/v2.6 250 Directory successfully changed. ftp>ls linux-2.6.11* 227 Entering Passive Mode (204,152,191,37,71,78) 150 Here comes the directory listing. < ... snip older versions listing ... > -rw-r--r-- 1 536 536 37099602 Apr 07 19:21 linux-2.6.11.7.tar.bz2 -rw-r--r-- 1 536 536 248 Apr 07 19:21 linux-2.6.11.7.tar.bz2.sign -rw-r--r-- 1 536 536 46585077 Apr 07 19:21 linux-2.6.11.7.tar.gz -rw-r--r-- 1 536 536 248 Apr 07 19:21 linux-2.6.11.7.tar.gz.sign -rw-r--r-- 1 536 536 248 Apr 07 19:21 linux-2.6.11.7.tar.sign 226 Directory send OK. ftp> prompt Interactive mode off. At the time of this writing, the 2.6.11.7 kernel was the most recent. There may be a more recent version when you read this document. ftp> mget linux-2.6.11.7.tar.gz linux-2.6.11.7.tar.gz.sign local: linux-2.6.11.7.tar.gz remote: linux-2.6.11.7.tar.gz 227 Entering Passive Mode (204,152,191,37,170,43) 150 Opening BINARY mode data connection for linux-2.6.11.7.tar.gz (46585077 bytes). 226 File send OK. 46585077 bytes received in 89.7 secs (5.1e+02 Kbytes/sec) local: linux-2.6.11.7.tar.gz.sign remote: linux-2.6.11.7.tar.gz.sign 227 Entering Passive Mode (204,152,191,37,84,119) 150 Opening BINARY mode data connection for linux-2.6.11.7.tar.gz.sign (248 bytes). 226 File send OK. 248 bytes received in 0.00102 secs (2.4e+02 Kbytes/sec) ftp> bye 221 Goodbye. Now that we have all that ftp stuff out of the way, we can verify the file that has just been downloaded. Since you have already gone through the trouble of creating your keyring, and signing the Linux Kernel Archive's key, this is a easy as the single command below. gpg --verify linux-2.6.11.7.tar.gz.sign linux-2.6.11.7.tar.gz gpg: Signature made Thu 07 Apr 2005 12:30:06 PM PDT using DSA key ID 517D0F0E gpg: Good signature from "Linux Kernel Archives Verification Key <ftpadmin at kernel.org>" gpg: checking the trustdb gpg: checking at depth 0 signed=7 ot(-/q/n/m/f/u)=0/0/0/0/0/2 gpg: checking at depth 1 signed=16 ot(-/q/n/m/f/u)=7/0/0/0/0/0 gpg: next trustdb check due at 2005-09-29 The line "gpg: Good signature from ... " indicates that the signatures is valid, and the file is verified. <command>md5sum</command> usage example The md5sum command is used to get an MD5 checksum from a file, or line/section of text, which can then be compared to a supplied checksum to verify the integrity of the file you are downloading. Start by downloading the file. For this example, we are using the first disk image of the Fedora Core 3 install. ftp download.fedora.redhat.com Trying 66.187.224.20... Connected to download.fedora.redhat.com (66.187.224.20). 220 Fedora FTP server ready. All transfers are logged. Name (download.fedora.redhat.com:charlie): anonymous 331 Please specify the password. Password: 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> cd /pub/fedora/linux/core/3/i386/iso/ 250 Directory successfully changed. ftp> ls 227 Entering Passive Mode (66,187,224,20,49,191) 150 Here comes the directory listing. -rw-r--r-- 1 ftp ftp 2466410496 Nov 03 22:18 FC3-i386-DVD.iso -rw-r--r-- 1 ftp ftp 589832192 Nov 03 22:11 FC3-i386-SRPMS-disc1.iso -rw-r--r-- 1 ftp ftp 589844480 Nov 03 22:12 FC3-i386-SRPMS-disc2.iso -rw-r--r-- 1 ftp ftp 589815808 Nov 03 22:13 FC3-i386-SRPMS-disc3.iso -rw-r--r-- 1 ftp ftp 589817856 Nov 03 22:15 FC3-i386-SRPMS-disc4.iso -rw-r--r-- 1 ftp ftp 646987776 Nov 03 22:05 FC3-i386-disc1.iso -rw-r--r-- 1 ftp ftp 668520448 Nov 03 22:07 FC3-i386-disc2.iso -rw-r--r-- 1 ftp ftp 667498496 Nov 03 22:08 FC3-i386-disc3.iso -rw-r--r-- 1 ftp ftp 404764672 Nov 03 22:10 FC3-i386-disc4.iso -rw-r--r-- 2 ftp ftp 79908864 Nov 03 21:59 FC3-i386-rescuecd.iso -rw-r--r-- 1 ftp ftp 791 Nov 03 23:00 MD5SUM 226 Directory send OK. ftp> get FC3-i386-disc1.iso ftp> get MD5SUM After you have the file downloaded, verify the checksum by issuing the following command: md5sum FC3-i386-disc1.iso This will output something similar to the following: db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso You can then grep the MD5SUM file you should have downloaded for the correct checksum: grep 'FC3-i386-disc1.iso' MD5SUM db8c7254beeb4f6b891d1ed3f689b412 FC3-i386-disc1.iso If the hexadecimal number in the first column matches the hexadecimal number output by the md5sum command, then you can be assured that the file you downloaded is an unmodified version of the file that was posted. Configuring and Using <command>sudo</command> Using the sudo utility allows a user to run another command or tool as if they were logged on as root. If you're doing something that requires the access of the root user, this is the best method for elevating your privileges. The file that sudo uses as its configuration file is /etc/sudoers. This file allows you to set up command, host, and user aliases that are allowed through sudo, and which users are allowed to run them, from which host, etc. For more information on the details of the sudoers file and how to configure it, take a look at the sudoers man page. If you add the lines below to the /etc/sudoers file, it will allow your user account access to command(s) specified by the 'Cmnd_Alias' when you use the sudo command. You will have to type your password for each command. Cmnd_Alias HARD = "gpg", "md5sum", "sudo", "yum", "rpm", "find", "pkill", "iptables", "umask", "chkconfig", "grep" yourusername ALL = HARD The commands selected for this example should provide all of the appropriate priveleges required by the instructions in this guide. If you would like a more complete configuration for your implementation of sudo, please consult the man page or the online documentation. For more information on how to configure sudo, you can view the manpage and other documentation at the link below. http://www.courtesan.com/sudo/man/sudo.html http://www.linuxhelp.net/guides/sudo/ Identifying system role and usage &DRAFTNOTICE; As we have already mentioned, one important thing to do initially is to identify what your system will be used for, what services you will need, and how many users will be using your system. Here are some things to consider: Will you be using your new &FC; system for Internet and email only? Will you be serving web/email/ftp content? Will your system act as a firewall for your home or office network which will do Network Address Translation (NAT'ing)? Once you have considered all of these things in regards to your new &FC; system, you can make intelligent decisions about to secure your system. For the scope of this guide, it is assumed that you will be securing a workstation which will be used for web surfing, email, office documents, and the like. It is also assumed that there will be one primary user for this system. GUI: Updates with <application>up2date</application> Make sure that you have all of the most current updates. There are many times that a package will be released with a distribution release and then a vulnerability with that version will be posted after the release of the distribution. While there is a lag between notification, and patching, the distribution "owner" will usually release a patch or updated version shortly. This means that if you are installing a system after it's initial release, it may be outdated. &FC; provides a couple of different ways of accomplishing this. The GUI utility is called up2date. After you've first installed your new &FC; system, it should automatically try to connect to the &RHN; to determine if it's applications are up to date or not. Most likely, they will not be up to date. This is indicated by the red exclamation point icon in the upper right hand corner of the screen, on the Gnome panel. Clicking on the icon will bring up the &RHN; Alert Notification Tool dialog. This will show you any products that are currently installed on your system that need to be updated. Click the "Launch up2date" button to launch the actual update application. Follow the instructions in the subsequent dialogs to update your system. If your system is up to date, you will receive a notification that indicates this. Otherwise, the up2date program will download the necessary packages and install them for you. CLI: Updates with <command>yum</command> &DRAFTNOTICE; The most convenient CLI tool that comes with &FC; is yum. Yum will not automatically check to see if your applications and packages are up to date, since the default functionality relies on the GUI tools. It can, however, be configured to do so. By issuing the following command: sudo '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' you will start the service, and configure it to start at runlevels 3, 4, and 5. If you are running a "headless" system, or if you are running in command line only mode, one of the first things that you will want to do will be to run yum. Use the following command to check for any available updates: sudo 'yum check-update' This will check for any package updates, and dependencies. Ultimately, this is not a necessary step, but I like to run it to see what updates are available, if any, before actually updating. Then, to install any updates found, you will need to run the following command: sudo 'yum update' This will automatically download any pending package or application updates, including kernel updates. Then once all of the updates packages have been downloaded, you will be prompted to continue with the transaction (or installation process). The first time you run yum, you will be asked to install the gpg key, unless you have already disabled file signature checking in yum.conf. The simplest way to do this is to use the key installed when installing the operating system. Issue the following command to accomplish this: sudo "rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora" Once you have the key installed, you will be able to verify the packages you download and install by using yum. Note If there are any unresolved dependencies, you will be asked if you want to download and install the dependencies. Most of the time, you should do this. Tip If you have received any critical updates, like a kernel update, you will want to reboot your system after the update is complete. You can find more information on keeping your system up to date at following link: http://fedora.redhat.com/docs/updates/index.html Disabling unnecessary services &DRAFTNOTICE; GUI: Service Configuration To get to the GUI tool to edit the default services, select Menu->System Settings->Server Settings->Services. This will bring up the Service configuration dialog. Access Note You should run this utility (and all other GUI utilities) as a normal user, unless otherwise specified. When doing so, you will be prompted for the root password. Type it in the dialog to continue. For each service listed, the Service Configuration utility will display a short description about the service you have highlighted in the upper-right pane, and the current status and process ID (PID) of the service, if it is running. The services that you can safely disable will depend upon the role of your system. For example, if you are planning to run a web server, you will not want to disable the httpd service. The list below is a good starting place. These services can be disabled for the role we have chosen, that of a home workstation: aep1000 - load and unload AEP1000/AEP2000 coprocessor driver. bcm5820 - Hardware cryptographic accelerator support - BCM5820 Cryptonet driver. chargen - An xinetd internal service which generates characters. chargen-udp - This is the udp version. daytime - An internal xinetd service which gets the current system time. daytime-udp - This is the udp version. echo - An xinetd internal service which echo's characters back to clients. echo-udp - This is the udp version. httpd - Apache is a World Wide Web server. It is used to serve HTML files and CGI. irda - Infrared data link (for PDAs and such) ktalk - KDE version of the talk server. lisa - Provides information about hosts on your network. mysqld - MySQL database server. named - named (BIND) is a Domain Name Server (DNS) that is used to resolve host names to IP addresses. netplugd - netplugd is a daemon for managing non-static network interfaces. nfs - This service provides NFS server functionality. nfslock - This service provides NFS file locking functionality. nscd - This is a daemon which handles passwd and group lookups for running programs and cache the results for the next query. ntpd - ntpd is the NTPv4 daemon. pcmcia - PCMCIA support is usually to support things like ethernet and modems in laptops. rsync - allows remote file synchronization saslauthd - saslauthd is a server process which handles plaintext authentication requests on behalf of the cyrus-sasl library. services - An internal xinetd service, listing active services. sgi_fam - FAM is a file monitoring daemon. smartd - Self Monitoring and Reporting Technology (SMART) Daemon. snmpd - Simple Network Management Protocol (SNMP) Daemon. snmptrapd - Simple Network Management Protocol (SNMP) Trap Daemon. squid - Squid - Internet Object Cache. time - An RFC 868 time server. time-udp - This is the udp version. tux - The TUX threaded kernel-based http server. vncserver - Starts and stops vncserver. used to provide remote X administration services. winbind - Starts and stops the Samba winbind daemon. ypbind - This is a daemon which runs on NIS/YP clients and binds them to a NIS domain. yppasswdd - yppasswdd is the RPC server that lets users change their passwords in the presence of NIS (a.k.a. YP). ypserv - ypserv is an implementation of the standard NIS/YP networking protocol. ypxfrd - ypxfrd should be started in addition to ypserv to accelerate transferring yp maps. yum - Enable daily run of yum, a program updater. (This will depend on your environment.) If you include yum in your list of services to disable here, then you will be disabling the automated updates you would have configured in earlier sections of this overview. Certain users may have specific reasons for not wanting to run automated updates every night. Most users will want to leave this enabled, if you are disabling it, you should know exactly why. Once you have chosen the services that you want to disable for your application, you can do so by unchecking the check box next to the name of the service you are disabling. Once you have deselected all of the services you want to disable, be sure to click the Save button, so that your changes are committed. The process needs to be done for all 3 multi user runlevels (3, 4, 5). The GUI utility defaults to runlevel 5, so you will have to manually select runlevels 3 and 4 to enable/disable service there. You may also want to check runlevel 2, as there are certain services that may be considered "critical" that will be started at that runlevel. Important Be sure to stop the service you are disabling, if it is running. This will both prevent you from having to reboot your system, as well as give you an immediate indication of what effect not having that particular service running will have on your system. CLI: Service Configuration Note: The following commands will need to be run as root. There are a number of ways to tackle service control from the command line. One of the simplest is to use chkconfig. The following command will show you the all of the services that are enabled to run at runlevel 5: sudo '/sbin/chkconfig --list | awk '/5:on/ { print $1 }' | sort' If you are running in command line only mode (runlevel 3), theoretically, you could disable all of these services. However, this could cause problems if you were to ever run in GUI mode. So, focus on the ones that I have listed above in the GUI section. Take this list of services, and put it into a series of commands that can be run either from the command line directly, or in a script. The easiest way will be to put the list of services in a file, however you could list all of the services individually in the for loop. This might be the better option if you were running it directly from the command line. To put the list of services in a file, issue the command above, and redirect the output to a file: sudo '/sbin/chkconfig --list | awk '/[35]:on/ { print $1 }' | sort >> serviceslist.txt' This will capture all of the services that are designated to start at either runlevel 3 or runlevel 5. Then, edit the serviceslist.txt file to only disable the services you want to disable. An example serviceslist.txt file might look like this: acpid anacron apmd autofs cpuspeed crond cups cups-config-daemon gpm haldaemon httpd iptables irqbalance kudzu lm_sensors mDNSResponder messagebus microcode_ctl netfs network nfslock nifd portmap readahead readahead_early rhnsd rpcgssd rpcidmapd rpcsvcgssd smartd smb vncserver xfs xinetd Once you've edited the serviceslist.txt file, put the following into a text file: for SERVICE in `cat serviceslist.txt` ;do /sbin/chkconfig --level 35 ${SERVICE} off done ...and give it executable permissions: sudo chmod u+x script.sh Execute the script by issuing the following command: sudo ./script.sh This will disable the services you have selected for runlevels 3 and 5, which are multi-user runlevels: level 3 for command line only, and level 5 for X, or GUI, mode. Disabling or Deleting Unnecessary Users and Groups &DRAFTNOTICE; Once you've disabled all of the services you have determined to be unnecessary for your implementation, you will need to do the same thing for your users and groups. Warning! Unmanaged users (unused users, users without passwords, etc.) can be a vector for attack. Without proper management of all of these "system" and "service" accounts, they could be easily compromised, and used to bring further harm to your system. Remember the list of services that you disabled? Most of those services will have their own user. This is a good thing if you are intending to use those services, because that means that there is some chroot, or "jail environment", that is built into the application for that service. However, if you're not going to use those services, there is no reason to have those users lying around. For the most part, the user accounts that are associated with a service should be removed when the service is removed. However, the following steps will be necessary if a service or package is simply disabled, as described above, as opposed to completely removed. GUI: Disabling unnecessary users Start by selecting Menu->System Setting->Users and Groups. This will bring up the User Manager. Authorization If you are running this as a normal user (as you should be), then you will have to type in the root password in the administrative privilege dialog box. By default, the User Manager will filter all of the "default" and/or "system" users. These are the user account that need to be scrutinized. To view the users you want to disable, select Preferences->Filter System users and Groups. This will disable the default filter and you will be able to view the system users you want to disable. In order to disable a user, you will need to select the user, then click Properties. This will show you the details of the user's account. The first tab in the User Properties dialog will be the User Data tab. Here you will be presented with options such as "username", "user full name", etc. At the bottom of the tab will be the user's default shell. If this is not already /sbin/nologin, change it to that shell. Next, select the "Account Info" tab. You will be presented with two (2) check boxes here. The first is for account expiration period, the second is for "locking" the user account's password. Click both of these boxes so that they are checked. In the "Account Expiration" section, put today's date. Click the OK button, and move on to the next user. The following are some of the service related user accounts that you might want to disable, depending on your requirements: news - news server user operator gopher games squid - squid proxy cache daemon user. named - BIND (DNS Server) user. mysql - MySQLd user. ncsd - NCSD daemon user. ntp - ntp client user. apache - Apache/HTTPD user. smmsp - Sendmail mail queue user. Your usage will vary. If you are using certain publicly available services (such as a web server), you may not want to disable some of the user accounts mentioned here (like apache). A good rule of thumb is, that if you are disabling a service, and there is a user associated with that service, you will want to disable the user as well. Securing the File System &DRAFTNOTICE; Securing the file system basically translates to securing files. Some might consider selection of the file system type to be important, but for the scope of this document, it is assumed that you will be dealing with a base installation of &FC;. Given that assumption, most files will have "reasonable" permission already set. However, it never hurts to be sure. Searching for insecure files Basic File Permissions Introduction &FC; (and most other Unices) separates access control on files and directories according to three characteristics: user, group, and other. There is always exactly one owner, any number of members of the group, and everyone else. A quick explanation of Unix permissions: Ownership - Which user(s) and group(s) retain(s) control of the permission settings of the node and parent of the node Permissions - Bits capable of being set or reset to allow certain types of access to it. Permissions for directories may have a different meaning than the same set of permissions on files. Read: To be able to view contents of a file To be able to read a directory Write: To be able to add to or change a file To be able to delete or move files in a directory Execute: To be able to run a binary program or shell script To be able to search in a directory, combined with read permission Save Text Attribute: (For directories) The "sticky bit" also has a different meaning when applied to directories than when applied to files. If the sticky bit is set on a directory, then a user may only delete files that the he owns or for which he has explicit write permission granted, even when he has write access to the directory. This is designed for directories like /tmp, which are world-writable, but where it may not be desirable to allow any user to delete files at will. The sticky bit is seen as a t in a long directory listing. SUID Attribute: (For Files) This describes set-user-id permissions on the file. When the set user ID access mode is set in the owner permissions, and the file is executable, processes which run it are granted access to system resources based on the user who owns the file, as opposed to the user who created the process. This is the cause of many "buffer overflow" exploits. SGID Attribute: (For Files) If set in the group permissions, this bit controls the "set group id" status of a file. This behaves the same way as SUID, except the group is affected instead. The file must be executable for this to have any effect. SGID Attribute: (For directories) If you set the SGID bit on a directory (with chmod g+s directory), files created in that directory will have their group set to the directory's group. You - The owner of the file Group - The group you belong to Everyone - Anyone on the system that is not the owner or a member of the group This is a fairly high level discussion of linux file permissions. A slightly more indepth discussion can be found here: http://www.tldp.org/LDP/intro-linux/html/sect_03_04.html Finding world-writable files Unfortunately, there is no Fedora-specific tool (or GUI tool, for that matter) which raises the "Big Red Flag" and says: /THIS/FILE/IN/THIS/PATH has world writable permissions. ANYONE can write to this file!!! There is, however, a very simple (although not very timely) way of doing this with the *NIX find command. The lines below can be copied to a command line and then executed to find any world writable files and directories. sudo 'find / \( -type d -o -type f \) -perm +002 | tee world-writable-files.txt' You may be surprised at how many files are world-writable "out of the box". But you'll have to examine the list carefully, making sure that files that are listed are not links, or devices, or other special files. The command line above will only return normal directories and files. So if you have device (i.e. /dev/foo) files in your list, they are most likely marker files for devices that don't exist, or aren't in use on your system. Finding SetUID/SetGID files You should also check for setUID/setGID files and directories. SetUID/setGID files are files that can be executed with permissions greater than that of the user running the program. Often, this can be exploited, and may still leave backdoors into your system, even after patching. Again, there is no Fedora-specific tool which will help us identify these files, however find can also solve this problem. Use the find command line string below to pipe all of the setUID/setGID files into a file. find / -type f \( -perm -04000 -o -perm -02000 \) | tee -a setuid-files.txt You are likely to see many normal programs in this list, however, if you have just installed your system, and have not yet connected it to a network, it would be safe to consider this entire list of files as trusted. If you have connected this system to a network and/or have not just installed your system, you will want to carefully review the list of files, to make sure that there is nothing "odd" in the list. Insecure files summary Once you have obtained the list(s) of world-writable files and directories, you will want to save those lists in a secure place. Make a copy of the lists on a floppy, or other secure location, so you have them to reference, if needed. If you are using gpg, or have installed the md5 utility, you will want to run a checksum of your file, or digitally sign it, so that in the event you need to reference that file, you are able to verify that it has not been tampered with. You will also want to periodically re-check your file system to make sure that no new files with the above permissions issues have been introduced into your system, that you are unaware of. To accomplish this, you can copy the following script, which combines the above commands, and run it from the cron tab on a regular basis. #!/bin/bash #simple script to check for world writable files and setUID/setGID files. # baseline world-writable files list BL_WWF='/SCRIPTS/security/harden/world-writable-files.txt' #baseline setuid files list BL_SUID='/SCRIPTS/security/harden/setuid-files.txt' TODAY=`date +%y%m%d` printf "Checking the file system for world-writable files ..... " find / \( -type d -o -type f \) -perm +002 > /tmp/${TODAY}-wwf.txt printf " done.\n" printf "Checking the file system for setUID/GID files ..... " find / -type f \( -perm -04000 -o -perm -02000 \) > /tmp/${TODAY}-suid.txt printf " done.\n" diff ${BL_WWF} /tmp/${TODAY}-wwf.txt > /tmp/${TODAY}-wwf.diff diff ${BL_SUID} /tmp/${TODAY}-suid.txt > /tmp/${TODAY}-suid.diff printf "Changed world-writable files:\n" cat /tmp/${TODAY}-wwf.diff | mail -s "World Writable Files for ${TODAY}" charlie at localhost printf "Changed setUID/GID files:\n" cat /tmp/${TODAY}-suid.diff | mail -s "setU/GID Files for ${TODAY}" charlie at localhost This may take a few minutes depending upon the size of your file system. For example, on a file system spanning multiple drives, and totaling approximately 160GB, it could take as long as 10 minutes. To run the script from the crontab, enter a line like the following into the cron: 0 0 * * * /SCRIPTS/security/harden/check_files.sh This will run the script every night at midnight. You will want to make adjustments for your own application. Verifying packages with <command>rpm</command> The rpm command can be used to verify the packages that you have installed. This should be done regularly. Verifying a package compares information about the installed files in the package with information about the files taken from the package metadata stored in the rpm database. Among other things, verifying compares the size, MD5 sum, permissions, type, owner and group of each file. Any discrepancies are displayed. Files that were not installed from the package will be silently ignored. There are a number of options that you can implement at the command line, however, they are mostly to disable features that you would most likely want. You can do this type of verification by issuing the following command: rpm -Va This will verify each installed package as described above, and output something similar to the following: .....UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/lxdialog/msgbox.c .....UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/lxdialog/yesno.c .M...UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/mkuboot.sh .....UG. /lib/modules/2.6.9-1.724_FC3/build/scripts/mkversion S.5....T c /etc/pam.d/system-auth S.5....T /usr/share/texmf/web2c/amstex.fmt S.5....T /usr/share/texmf/web2c/bamstex.fmt There may be file identifiers, like the 'c' in the middle of the line for the /etc/pam.d/system-auth. This index can indicate any of the following: c - configuration file. d - documentation file. g - the file contents are not included in the package payload l - license file. r - readme file. The indicators in the left column indicate the test success or failure, and if the test failed, the reason for the failure. The alphanumeric indicator can indicate any of the following: S - file Size differs M - Mode differs (includes permissions and file type) 5 - MD5 sum differs D - Device major/minor number mismatch L - readLink(2) path mismatch U - User ownership differs G - Group ownership differs T - mTime differs Most of the time the errors seen here will be relatively benign, especially if you have yum configured to update packages automatically. However you should verify changes that you don't recognize. Configuration File Verification If you are running any types of network services, i.e. web, mail, ftp, etc., you should periodically verify your configuration files. It is a good idea to have an external backup (floppy, CD, etc.) in case something happens to your working config. Once you have completed either the base configuration, or an update to an existing configuration, save your files to your chosen secure location. You may even consider running the tool md5sum against each configuration file as an extra measure. This will help to ensure that your configuration files haven't been tampered with. md5sum example md5sum /etc/httpd/conf/httpd.conf >> /dev/fd0/conf_files_checksums.md5 The above example makes the assumption that you will be saving your md5 checksum list to a floppy, and the your floppy is already mounted. If you don't know how to mount a floppy, the following command should work: mount -t vfat /dev/fd0 /mnt/floppy You can also find more information on md5sum, and a more complete example in the previous section: . Setting the default umask The default UMASK is the file permissions mask that establishes the level of permissions used for creating the default permissions on files. The mask is the "mirror image" of the actual permissions that you want. For example, if you want files created with permissions of 755, or -rwxr-xr-x, you would want your umask to be 022. In order to set this globally, you will need to edit this parameter in the /etc/bashrc file. However, the default implementation with &FC; is fairly secure, employing the idea of what RedHat calls "User Private Groups". So, if you want to change this parameter, you should know exactly what you are doing and why. To change the umask for a single session, you can use the umask utility as shown below. umask 0022 The above command will change the default umask to 022. (This should already be the default and you can test this by issuing the command umask at the command line as root.) File System Security Summary: Where to go from here? The actions discussed here will put you on the road to file system security. However, you may find that there are some other things which are handy to have to help ensure the security of your files. One type of tool that you may want to look into is called a System Integrity Verifier (SIV). This is a program which will scan your system and keep track of any changes to your files, or file system, based on a security policy that you design. Some examples of this might be Tripwire or AIDE. You can find out more about these products at the links below. http://sourceforge.net/projects/tripwire/ http://www.cs.tut.fi/~rammer/aide.html Securing User Accounts &DRAFTNOTICE; Disabling Unnecessary Users Disabling unnecessary users can stop possible attacks by limiting the avenues that an attacker can use to penetrate your system. The procedure has already been discussed in . Limiting root logins There are a number of ways to limit how root can login to your system. When making changes to your system, you must be mindful of how root could access your system. The most secure practice is to limit root to su logins only. GUI: Limiting root As alluded to in earlier sections, where GUI configurations were discussed, as long as you are logged in as a normal user, you will be prompted for the root password if you are attempting to administer any system-wide services that require root access. From time to time, there will be an application or program that does not ask for root authentication when attempting to run. If you believe that an application should run as root, and it does not ask for the root password, you may be better off running it from a terminal with the su. CLI: Limiting root Unfortunately, the command line isn't so forgiving. Unless you are starting a GUI application that requires root permissions, you will not be prompted for the root password if attempting to execute a command that requires root permissions. You will just get a "Permission Denied" error. One of the easiest ways to utilize the su capability, is with the utility called sudo. Aside from enabling and using sudo, one of the first things to disable is root's direct access via SSH. If you plan not to use SSH for remote access to your system, then you can disable SSH completely as described in . However, if you ARE planning to use SSH, then you will want to limit direct access as root. "Direct access" means that you login to the system as root, instead of SSH'ing as a normal user, then su'ing to root (or using sudo, which will be discussed later). Unfortunately, there isn't yet a Fedora GUI tool for editing SSH configuration. So choose your favorite editor (this may actually be a GUI editor, but there is no specific tool for ssh configuration). Go to the line that reads: PermitRoot yes And change it to read: PermitRoot no Application Security Note While you are editing the sshd_config file, you may want to disable the SSH1 protocol by changing the line that reads: Protocol 2,1 to read: Protocol 2 This forces the client to use the SSH2 protocol, which can help to discourage attacks that SSH1 is vulnerable to. Then, either reboot your system, or issue the command pkill -1 sshd. The pkill command will force sshd to re-read it's configuration file, it will also kill any existing connections, including your own if you're making these changes through an ssh session. A more graceful way to simply make sshd reread it's config file would be with the following command: sudo '/sbin/service sshd reload' This will force users to login as a normal user account and then su to root, or utilize sudo. Verifying and Correcting System user shells System users, such as bin, sys, nobody, lp, etc. should not have valid shells &FC; offers the /bin/false and the /bin/nologin shell for these users. To verify the shells in use by your system accounts, you can use the User Manager utility. Select System Settings->Users and Groups. You will be prompted for the root password, if you are logged in as a normal user. Then the utility will open. If you do not see any of the systems users, make sure that you do not have them filtered (this is the default behavior). Select Preferences->Filter System Users and Groups from the menu and ensure that it is NOT checked. Then, you can scroll through the list of users to make sure that all of your system users have the /bin/false or /bin/nologin shells. There are some users which will have a special shell, like the shutdown or halt users. These special shells can be left alone. Password Security and PAM Configuration Password strength and security is one of the weakest points in a system's security posture. This is mainly because password strength depends on us humans. One way that you can help to enforce more secure passwords is by editing the PAM configuration. PAM stands for Pluggable Authentication Modules, and is a good way of setting password and authentication settings for many different services on your &FC; system. All or most of the files that configure PAM settings for different services are located in the /etc/pam.d/ directory. The one that we want to focus on for increasing password strength is the system-auth file. This file contains configuration information for your general system authentication. The file /usr/share/doc/pam-0.77/txts/README.pam_cracklib contains some information regarding the configuration options for this file. One option described in this file is the minlen= option. This is the option that specifies the minimum number of characters in a password. A password with 7 characters, even a "strong" password, yeilds only a maximum of [still figuring this number] character combinations, which can be cracked rather easily by today's brute force methods. Increasing the minimum length to 8 characters ups the number of combinations to [still figuring this number too]. Most security guides will advise a password of at least 8 characters, however, 12-16 characters is considered ",very secure. Other important options are the dcredit=, ucredit=, lcredit=, and ocredit= options. These options specify how many characters should be digits, uppercase, lowercase, and special characters, respectively. In order to ensure a strong password, all of these options should be set to at least one. The difok= option specifies how many characters can be the same between the "old" password and the "new" password when changing passwords. For example, if your old password was password, and you had the difok= setting set to 4, the "new" password passways would fail, whereas pastels would succeed. tcp_wrappers and Firewall Configuration <application>tcp_wrappers</application> Configuration tcp_wrappers is a method of limiting the connections that can be made to your system - sort of like the "poor man's firewall". tcp_wrappers will allow or deny a connection based on the source IP address and the service that that IP address is attempting to connect to. The version of tcp_wrappers that comes with &FC; does not support the "enhanced" functionality, however with a proper implementation of iptables you can get a lot more granular in your network defense. The <filename>hosts.deny</filename> file. The basic tcp_wrappers configuration consists of two files: /etc/hosts.allow and /etc/hosts.deny. The hosts.deny is the easier of the two to configure. An example is below. # Example hosts.deny file configuration # Deny all hosts unless specified in the allow file ALL:ALL As indicated by the example, the best practice is to deny all hosts attempting to make a connection to your system, unless they are specifically allowed in the hosts.allow file. The <filename>hosts.allow</filename> file. The hosts.allow file is only slightly more complex in this implementation, than the hosts.deny file. Let's assume for example, that you were running a web server on your workstation and you wanted every system in your local network to be able to connect to it, but you only wanted to be able to manage the web server from one other workstation. You hosts.allow file might look something like the following: # Example hosts.allow file configuration # Allow every system in the local network to connect to # the web server httpd:10.0.0. # Only allow the administration workstation to ssh to the # server for configuration and administration sshd:10.0.0.192 This would satisfy the requirements as specified above. If there was a service that you wanted anyone and everyone to be able to connect to, you might include a line like the following: # Allow any system to make DNS queries named:all There is more information on tcp_wrappers at the links below. They may mention features which are not implemented in the &FC; implementation, but they will give you an idea of how tcp_wrappers can be configured, and its purpose. http://www.cert.org/security-improvement/implementations/i041.07.html http://www.stanford.edu/group/itss-ccs/security/unix/tcpwrappers.html Firewall/IPTables Configuration The default &FC; firewall configuration utility is somewhat limited at this point in time. However, it should function well enough for most home or small office users. During the install you will be asked if you want to enable the firewall, and what services you will want enabled (if any). If you disabled the firewall during the install, or if you are working with a previously installed system and are not sure whether the firewall was enabled, you can check the security level by selecting Applications->System Settings->Security Level. This will bring up the system-config-securitylevel utility. This utility will allow you to view or change the firewall settings. It will also allow you to change the SELinux settings, however that discussion is currently outside of the scope of this document. If you are familiar enough with the applications that you need to allow to your system, then you can specify specific ports in the text area provided in the utility's dialog. The format for adding ports should match the following: 445:tcp, 135:tcp, 137:udp, 138:udp, 139:udp The example above would allow NetBIOS communications to your system. The utility currently does not support entry of port ranges. So, if your are going to use the default Fedora utility, you will need to specify each port specifically as exemplified above. If you have need for more granular control over your firewall, you may consider a utility such as Firestarter. Or do some reading on the configuration of iptables. Conclusion As stated in the introduction and the scope of this document, this is not meant to be the end-all-be-all document for security, or even Fedora security. However, it can be a guide to specific tasks that will help to accomplish a couple of things. One, it gives you guidance on how to accomplish specific tasks to make your Fedora system more secure. It also can act as a guide to get you thinking about security. To stay as secure as possible, explore tools and opportunities outside of the Fedora utilities. This will help you to see the breadth of things that are out there to help you secure your system. Learn, learn, learn. As threats become more mature, so must the user. The more you read and learn about your system and your chosen operating system, the more savvy, and more secure as a user you will become. Bibliography and References http://www.tldp.org/LDP/intro-linux/html/sect_03_04.html http://www.linuxhelp.net/guides/sudo/ http://www.brandonhutchinson.com/Hardening_Fedora.html http://www.linuxsecurity.com/docs/LDP/Security-HOWTO/file-security.html http://security.linux.com/security/04/09/20/1555239.shtml?tid=35 http://lists.samba.org/archive/samba-technical/2002-November/025702.html http://www.puschitz.com/SecuringLinux.shtml http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam-6.html#ss6.3 http://openskills.info/infobox.php?IDbox=1092&boxtype=distro Index: Makefile =================================================================== RCS file: /cvs/docs/hardening/Makefile,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Makefile 17 May 2005 02:02:13 -0000 1.1 +++ Makefile 26 Jul 2005 03:49:57 -0000 1.2 @@ -1,29 +1,30 @@ ############################################################################### # Makefile for RHLP docs project # Created by: Tammy Fox -# Last edited by: Tammy Fox +# Last edited by: Tommy Reynolds # WARNING: need passivetex 1.24 for pdf generation to work # License: GPL # Copyright 2003 Tammy Fox, Red Hat, Inc. +# Copyright 2005 Tommy Reynolds, MegaCoder.com ############################################################################### -XSLPDF = ../xsl/main-pdf.xsl -XSLHTML = ../xsl/main-html.xsl -LANG = en -#DOCNAME = fedora-hardening-guide-$(LANG) -DOCNAME = fedora-hardening-guide-$(LANG) -XMLFILE = $(DOCNAME).xml +XSLPDF = ../docs-common/xsl/main-pdf.xsl +XSLHTML = ../docs-common/xsl/main-html.xsl +XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl +LANG = en +DOCNAME = hardening-tutorial-$(LANG) +XMLFILE = $(DOCNAME).xml +XMLEXTRAFILES = ###################################################### -html: - @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE) - @mkdir -p $(DOCNAME)/stylesheet-images - @cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images - @cp ../css/fedora.css $(DOCNAME) - -pdf-%: - @xmlto pdf -x $(XSLPDF) $(XMLFILE) +include ../docs-common/Makefile.common ###################################################### -clean: - @rm -rfv *.html *.pdf *.tex $(DOCNAME) +# If you want to add additional steps to any of the +# targets defined in "Makefile.common", be sure to use +# a double-colon in your rule here. For example, to +# print the message "FINISHED AT LAST" after building +# the HTML document version, uncomment the following +# line: +#${DOCNAME}/index.html:: +# echo FINISHED AT LAST --- fedora-hardening-guide-en.xml DELETED --- From fedora-docs-commits at redhat.com Tue Jul 26 08:37:17 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 26 Jul 2005 04:37:17 -0400 Subject: hardening hardening-tutorial-en.xml,1.1,1.2 Message-ID: <200507260837.j6Q8bH0S011577@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/hardening In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11560 Modified Files: hardening-tutorial-en.xml Log Message: Mainly formatting, this allows for more odular use of sections; some style and writing changes included. Index: hardening-tutorial-en.xml =================================================================== RCS file: /cvs/docs/hardening/hardening-tutorial-en.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- hardening-tutorial-en.xml 26 Jul 2005 03:49:57 -0000 1.1 +++ hardening-tutorial-en.xml 26 Jul 2005 08:37:14 -0000 1.2 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + @@ -15,7 +15,7 @@ - &FC; &FCLOCALVER; Hardening Tutorial + &FC; &FCLOCALVER; Hardening Tutorial - <emphasis>RC Document</emphasis> 2005 &FORMAL-RHI; @@ -28,6 +28,32 @@ &LEGALNOTICE; + + + 0.2 + 2005-04-26 + Charles Heselton + + + Latest build made available for import into cvs.fedora.redhat.com + + + + + 0.3 + 2005-07-26 + Karsten Wade + + + Changes made are wide, including title, structural, stylistic, + Documentation Project generic usage guidelines, writing editorial, + technical, format. Changes are checked into CVS in stages with + descriptive logs to help make contextual sense of the 'cvs diff + -u'. Made available as RC. + + + + @@ -35,73 +61,79 @@ &DRAFTNOTICE; - This tutorial is a basic walk-through of how to harden a basic install - of &FC;. Many of the actions and principles discussed here will apply - to many different linux distributions. However, for the purpose of this - tutorial we will be regarding &FC;, specifically. + This tutorial is a walk-through of how to harden an install + of &FC;. Many of the actions and principles discussed here apply + to many different Linux distributions. This tutorial focuses on how to + perform these actions using &FC;. - +
Document Scope - While describing the techniques and tools used in this tutorial, it is - the goal of the author to present both the Graphical User Interface (GUI) tools, and the - more traditional command line (CLI) tools that are available in - FC3. + This tutorial has a goal of presenting both the graphical user interface + (GUI) tools and the more traditional command line (CLI) tools that are + available in &FC;. - Many users will have customized the appearance of their desktop (if running - one), panels, menus, etc. This guide makes direction based on the default - install and configuration of &FC;. The locations of items, menus, - commands, etc. may differ from your actual experience. + Many users have customized the appearance of their desktop (if running + one), panels, menus, etc. This tutorial provides directions based on + the default install and configuration of &FC;. The locations of items, + menus, commands, and so forth may differ from your actual experience. - +
- +
Intended Audience - This document is intended for use by all &FC; users. However, there is a - focus for home or small-business users. Enterprise deployments of Fedora - will want to make some different considerations such as centralized syslog - storage, unified (central) user authentication, etc. Most of the - principles discussed will apply, however there are some enterprise - applications which are outside the scope of this document. + This document is intended for use by all &FC; users. However, there + is a focus for home or small-business users. Enterprise deployments + of &FED; want to make different considerations, such as centralized + syslog storage, unified (central) user authentication, etc. Most of + the principles discussed still apply, however there are some + enterprise applications which are outside the scope of this document. - +
- + Initial Steps &DRAFTNOTICE; - +
Package Installation Considerations - This section will not go into the actual process of installing packages, - that falls under the scope of the Installation Guide. However, there - are some important things to consider, in regards to security, when you are installing &FC; - and selecting your packages for installation, and when you are - installing new packages on an already built system. + This section does not go into the actual process of installing packages. + Refer to the &IG; for new installations, and the + documentation at http://fedora.redhat.com/docs + for more information on updating systems and installing packages. + + + However, there are some important things to consider in regards to + security when you are selecting packages during installation or for + adding to an existing system. - +
Package Selections During Install - When you are first installing your &FC; system, take careful - consideration of the packages that you are installing. Know what type - of system you are building before you build it. Fedora offers a - "system role" method of choosing packages, which can be customized to + When you are first installing your &FC; system, carefully + consider of the packages that you are installing. Know what type + of system you are building before you build it. &FC; offers a + system role method of choosing packages, which can be customized to remove or not install certain packages, and install others that may not be - designated as part of that particular role. A good approach would be to, - first, draw out a plan of what your system is to be used for, and what - services you will want to offer (if any). You can then make an - educated decision about what installation type you want to start - with. Fedora offers the following in terms of installation types: + designated as part of that particular role. + + + A good approach is to draw out a plan of what your system is to be + used for and what services you will want to offer (if any). Then make + an educated decision about what installation type you want to start + with. Fedora offers the following installation types: @@ -118,34 +150,37 @@ yum command line utility, to install any additional packages required for your needs. - +
- +
Package Considerations for Installation of New Software If you are updating, or adding to, a system that is already - installed with &FC;, then there are some other considerations that + installed with &FC;, then there are some other considerations that need to be made. - When installing a new package, you should check the integrity of the - package. Most reliable sources will provide a signed checksum file - for a package file. You can use gpg or - md5sum to verify the checksum provided, - depending on the digital signature provided. - gpg is a utility which allows you to manage digital - signatures. These signatures allow you to digitally sign or encrypt - data (including text messages or files). For more details on - gpg visit the GNU gpg website at http://www.gnupg.org. - md5sum is a utility which is based off of the MD5 - algorithm. This utility can be used to create a digital signature of - a file, which can then be compared to the MD5 checksum downloaded with - the software package. For more details on the MD5 hashing algorithm, - and associated utilities, you can visit the MD5 website at http://www.fourmilab.ch/md5/. + When installing a new package, you should check the integrity of the + package. Most reliable sources provide a signed checksum file for a + package file. You can use gpg or + md5sum to verify the checksum provided, + depending on the digital signature provided. + + + GnuPGgpg is a utility that allows you to manage + digital signatures. These signatures allow you to digitally sign or + encrypt data (including text messages or files). For more details + on gpg visit the GNU gpg website at http://www.gnupg.org. + md5sum is a utility which is based off of the MD5 + algorithm. This utility can be used to create a digital signature + of a file, which can then be compared to the MD5 checksum downloaded + with the software package. For more details on the MD5 hashing + algorithm, and associated utilities, you can visit the MD5 website + at http://www.fourmilab.ch/md5/. @@ -159,7 +194,7 @@ two sections. - +
<command>gpg</command> usage example @@ -372,9 +407,9 @@ The line "gpg: Good signature from ... " indicates that the signatures is valid, and the file is verified. - +
- +
<command>md5sum</command> usage example The md5sum command is used to get an MD5 checksum @@ -444,11 +479,11 @@ then you can be assured that the file you downloaded is an unmodified version of the file that was posted. - - - +
+
+
- +
Configuring and Using <command>sudo</command> Using the sudo utility allows a user to run another @@ -502,9 +537,9 @@ - +
- +
Identifying system role and usage &DRAFTNOTICE; @@ -532,9 +567,9 @@ and the like. It is also assumed that there will be one primary user for this system. - +
- +
GUI: Updates with <application>up2date</application> @@ -566,9 +601,9 @@ system is up to date, you will receive a notification that indicates this. Otherwise, the up2date program will download the necessary packages and install them for you. - +
- +
CLI: Updates with <command>yum</command> &DRAFTNOTICE; @@ -651,12 +686,12 @@ http://fedora.redhat.com/docs/updates/index.html - +
- +
Disabling unnecessary services &DRAFTNOTICE; - +
GUI: Service Configuration To get to the GUI tool to edit the default services, select @@ -765,9 +800,9 @@ have on your system. - +
- +
CLI: Service Configuration Note: @@ -885,10 +920,10 @@ which are multi-user runlevels: level 3 for command line only, and level 5 for X, or GUI, mode. - - +
+
- +
Disabling or Deleting Unnecessary Users and Groups &DRAFTNOTICE; @@ -919,7 +954,7 @@ removed. - +
GUI: Disabling unnecessary users @@ -982,11 +1017,11 @@ a service, and there is a user associated with that service, you will want to disable the user as well. - - +
+
- + Securing the File System &DRAFTNOTICE; @@ -998,9 +1033,9 @@ "reasonable" permission already set. However, it never hurts to be sure. - +
Searching for insecure files - +
Basic File Permissions Introduction &FC; (and most other Unices) separates access control on files and directories according to three characteristics: user, group, @@ -1100,9 +1135,9 @@ http://www.tldp.org/LDP/intro-linux/html/sect_03_04.html - +
- +
Finding world-writable files Unfortunately, there is no Fedora-specific tool (or GUI tool, for that @@ -1133,8 +1168,8 @@ likely marker files for devices that don't exist, or aren't in use on your system. - - +
+
Finding SetUID/SetGID files @@ -1164,8 +1199,8 @@ of files, to make sure that there is nothing "odd" in the list. - - +
+
Insecure files summary @@ -1236,10 +1271,10 @@ This will run the script every night at midnight. You will want to make adjustments for your own application. - - +
+
- +
Verifying packages with <command>rpm</command> @@ -1311,9 +1346,9 @@ especially if you have yum configured to update packages automatically. However you should verify changes that you don't recognize. - +
- +
Configuration File Verification If you are running any types of network services, i.e. web, mail, ftp, @@ -1344,9 +1379,9 @@ You can also find more information on md5sum, and a more complete example in the previous section: . - +
- +
Setting the default umask @@ -1377,9 +1412,9 @@ umask at the command line as root.) - +
- +
File System Security Summary: Where to go from here? @@ -1400,14 +1435,14 @@ http://sourceforge.net/projects/tripwire/ http://www.cs.tut.fi/~rammer/aide.html - +
- + Securing User Accounts &DRAFTNOTICE; - +
Disabling Unnecessary Users Disabling unnecessary users can stop possible attacks by @@ -1416,9 +1451,9 @@ linkend="userconfig-gui">. - +
- +
Limiting root logins @@ -1428,7 +1463,7 @@ su logins only. - +
GUI: Limiting root As alluded to in earlier sections, where GUI configurations were @@ -1441,9 +1476,9 @@ password, you may be better off running it from a terminal with the su. - +
- +
CLI: Limiting root Unfortunately, the command line isn't so forgiving. Unless you are @@ -1527,10 +1562,10 @@ This will force users to login as a normal user account and then su to root, or utilize sudo. - - +
+
- +
Verifying and Correcting System user shells System users, such as bin, sys, nobody, lp, etc. should not have valid @@ -1555,9 +1590,9 @@ There are some users which will have a special shell, like the shutdown or halt users. These special shells can be left alone. - +
- +
Password Security and PAM Configuration @@ -1615,12 +1650,12 @@ setting set to 4, the "new" password passways would fail, whereas pastels would succeed. - +
- + tcp_wrappers and Firewall Configuration - +
<application>tcp_wrappers</application> Configuration tcp_wrappers is a method of limiting the @@ -1634,7 +1669,7 @@ more granular in your network defense. - +
The <filename>hosts.deny</filename> file. The basic tcp_wrappers configuration consists @@ -1657,8 +1692,8 @@ attempting to make a connection to your system, unless they are specifically allowed in the hosts.allow file. - - +
+
The <filename>hosts.allow</filename> file. The hosts.allow file is only slightly more @@ -1718,10 +1753,10 @@ - - +
+
- +
Firewall/IPTables Configuration The default &FC; firewall configuration utility is @@ -1762,7 +1797,7 @@ consider a utility such as Firestarter. Or do some reading on the configuration of iptables. - +
@@ -1787,7 +1822,7 @@ - + Bibliography and References From fedora-docs-commits at redhat.com Tue Jul 26 21:07:09 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 26 Jul 2005 17:07:09 -0400 Subject: release-notes/FC4 RELEASE-NOTES-en.xml, 1.12, 1.13 splash.xml, 1.11, 1.12 Message-ID: <200507262107.j6QL7AnT032571@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32540 Modified Files: RELEASE-NOTES-en.xml splash.xml Log Message: Better wording, close to project goal. Index: RELEASE-NOTES-en.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/RELEASE-NOTES-en.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- RELEASE-NOTES-en.xml 23 Jul 2005 03:31:13 -0000 1.12 +++ RELEASE-NOTES-en.xml 26 Jul 2005 21:07:06 -0000 1.13 @@ -37,7 +37,7 @@ - + Index: splash.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/splash.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- splash.xml 23 Jul 2005 03:31:13 -0000 1.11 +++ splash.xml 26 Jul 2005 21:07:06 -0000 1.12 @@ -339,8 +339,8 @@ The unofficial http://fedorafaq.org provides useful answers on commonly asked questions. However, these are - completely unsupported by the &FP;. The &FP; recommends using free - and open source software alternatives whenever possible. + completely unsupported by the &FP;. The &FP; encourages using free + and open source software.. The binary only drivers can be acquired from the vendors. You can From fedora-docs-commits at redhat.com Tue Jul 26 21:27:26 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Tue, 26 Jul 2005 17:27:26 -0400 Subject: release-notes/FC4 splash.xml,1.12,1.13 Message-ID: <200507262127.j6QLRQ8Z032748@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/release-notes/FC4 In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32731 Modified Files: splash.xml Log Message: What's a period more or less. Index: splash.xml =================================================================== RCS file: /cvs/docs/release-notes/FC4/splash.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- splash.xml 26 Jul 2005 21:07:06 -0000 1.12 +++ splash.xml 26 Jul 2005 21:27:23 -0000 1.13 @@ -340,7 +340,7 @@ url="http://fedorafaq.org">http://fedorafaq.org provides useful answers on commonly asked questions. However, these are completely unsupported by the &FP;. The &FP; encourages using free - and open source software.. + and open source software. The binary only drivers can be acquired from the vendors. You can From fedora-docs-commits at redhat.com Tue Jul 26 23:29:21 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Tue, 26 Jul 2005 19:29:21 -0400 Subject: yum-software-management yum-software-management-en.xml,1.28,1.29 Message-ID: <200507262329.j6QNTL1u002782@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2765 Modified Files: yum-software-management-en.xml Log Message: - Clarify wording on effect of purging caches - Explicitly list Fedora repositories - Amended explanation of use of wildcards in searches Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- yum-software-management-en.xml 25 Jul 2005 21:57:58 -0000 1.28 +++ yum-software-management-en.xml 26 Jul 2005 23:29:18 -0000 1.29 @@ -261,13 +261,27 @@ The package management utilities in &FC; are already configured - to use the network of repositories maintained by the &FP;. These - repositories contain the software included with &FC; and a large - selection of additional software known as &FEX;. Third-party - software developers also provide repositories for their &FED; - compatible packages. + to use a network of servers that provide three repositories: + + + + The packages that make up &FC;, as it is released on disc + + + + + Updated versions of &FC; software + + + + + A large selection of additional software, known as &FEX; + + + + All &FED; Packages are Open Source Software @@ -277,6 +291,13 @@ network of repositories on as many systems as desired. + + + Third-party software developers also provide repositories for + their &FED; compatible packages. To learn how to configure your + &FED; system to use third-party repositories, read + . + package groups defined @@ -373,8 +394,8 @@ tsclient-0.132-4.i386.rpm - Management utilities refer to packages with one of three - formats: + Management utilities commonly refer to packages with one of + three formats: @@ -603,18 +624,11 @@ - yum downloads data files from each of the - configured repositories. On a slow connection, it may take several - seconds to download the required files for each package. - - - During operation, yum first determines the best set of actions to produce the required result, and displays the transaction for you to approve. The yum utility - may prompt you to approve installation, update, or removal of - additional packages in addition to the package that you specified. - These actions may be necessary to resolve software dependencies. + may prompt you to approve the installation, update, or removal of + additional packages, in order to resolve software dependencies. @@ -877,20 +891,29 @@ - To make your queries more specific, add other package - attributes. To search for version 0.132 of the application, use - the command: + To make your queries more precise, specify packages with a name + that include other attributes, such as version or hardware + architecture. To search for version 0.132 of the application, + use the command: su -c 'yum list tsclient-0.132' + + Valid Package Attributes + + + Refer to for information + on package name formats and the attributes that they include. + +
Advanced Searches - If you do not know the name of the package, use either the + If you do not know the name of the package, use the or options. @@ -936,14 +959,27 @@ For each command, at the prompt enter the password for the root account. + + + Use the standard wildcard characters to run any search option + without a complete name: to represent any one + character, and to mean zero or more + characters. Always add the escape character () + before wildcards. + + + + To all packages with names that begin with + tsc, type: + + +su -c 'yum list tsc\*' + - Wildcards and Regular Expressions + Regular Expressions - You may use the standard wildcard characters in search - criteria: to represent any one character, - and to mean zero or more characters. Use - Perl or Python regular expressions to carry out more complex - queries. + Use Perl or Python regular expressions to carry out more + complex queries.
@@ -963,8 +999,8 @@ or shadow-util would not produce the package shadow-utils. This package would match and be shown if the query was either - shadow-util? or - Shadow*. + shadow-util\? or + Shadow\*. @@ -1345,10 +1381,10 @@ cleaning caches - By design, yum does not automatically delete - any of the packages or package data files it downloads, so they - may be reused in future operations. To purge the header files, - use this command: + By default, yum retains the packages or + package data files that it downloads, so they may be reused in + future operations without being downloaded again. To purge the + header files, use this command: su -c 'yum clean headers' @@ -1365,15 +1401,11 @@ the root account. - - Purged Files - - - Package management operations download header files and - packages as required, and automatically replace any deleted - files needed for the operation. - - + + Purging cached files causes those files to downloaded again the + next time that they are required. This increases the amount of + time required to complete the operation. + From fedora-docs-commits at redhat.com Wed Jul 27 21:27:34 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Wed, 27 Jul 2005 17:27:34 -0400 Subject: yum-software-management yum-software-management-en.xml,1.29,1.30 Message-ID: <200507272127.j6RLRZx7002754@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2737 Modified Files: yum-software-management-en.xml Log Message: - Revised section on Repository Compatibility. - Style fix in Advanced Search section. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- yum-software-management-en.xml 26 Jul 2005 23:29:18 -0000 1.29 +++ yum-software-management-en.xml 27 Jul 2005 21:27:32 -0000 1.30 @@ -679,7 +679,7 @@ Downloads are Cached - The yum utility keeps Downloaded data files + The yum utility keeps downloaded data files and packages for reuse. You may copy packages from the repository cache directories under /var/cache/yum/, and use them elsewhere if @@ -915,6 +915,8 @@ If you do not know the name of the package, use the or options. + Alternatively, you may use wild cards and regular expressions + with any yum search option. @@ -962,8 +964,8 @@ Use the standard wildcard characters to run any search option - without a complete name: to represent any one - character, and to mean zero or more + with a partial word or name: to represent any + one character, and to mean zero or more characters. Always add the escape character () before wildcards. @@ -1207,23 +1209,31 @@ compatibility - The &FEX; project provides packages which are built to the same - standards as &FC; packages. Third-party packages should be - compatible with these official packages, unless the provider + The &FEX; repository provides packages which are built to the + same standards as &FC; packages. Third-party packages should be + compatible with these &FP; packages, unless the provider specifically states otherwise. - Refer to the web site of the repository for information on + Always read the web site of the repository for information on package compatibility before you add it as a package source. - Repositories often provide packages specifically intended for - use with packages supplied by other repositories. In some cases, - separate third-party repository providers may each offer - different versions of the same software. This situation may - prevent you from safely using those repositories together on - your &FED; system. + Separate repository providers may offer different and + incompatible versions of the same software. In some cases, + third-party repositories may also include alternative packages + for software provided by &FP; repositories that are not + compatible with other &FED; packages. + + Incompatible Repositories + + + If you use incompatible repositories yum + operations may fail. + + + Packages built for one version of &FED; are usually not compatible with other versions of &FED;. The web site of the @@ -1381,10 +1391,10 @@ cleaning caches - By default, yum retains the packages or + By default, yum retains the packages and package data files that it downloads, so they may be reused in future operations without being downloaded again. To purge the - header files, use this command: + package data files, use this command: su -c 'yum clean headers' From fedora-docs-commits at redhat.com Thu Jul 28 00:54:18 2005 From: fedora-docs-commits at redhat.com (Karsten Wade (kwade)) Date: Wed, 27 Jul 2005 20:54:18 -0400 Subject: yum-software-management yum-software-management-en.xml,1.30,1.31 Message-ID: <200507280054.j6S0sIrs008007@cvs-int.fedora.redhat.com> Author: kwade Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7990 Modified Files: yum-software-management-en.xml Log Message: Bumping date for beta publication. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- yum-software-management-en.xml 27 Jul 2005 21:27:32 -0000 1.30 +++ yum-software-management-en.xml 28 Jul 2005 00:54:16 -0000 1.31 @@ -4,7 +4,7 @@ %FEDORA-ENTITIES-EN; - + From fedora-docs-commits at redhat.com Thu Jul 28 22:03:19 2005 From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss)) Date: Thu, 28 Jul 2005 18:03:19 -0400 Subject: yum-software-management yum-software-management-en.xml,1.31,1.32 Message-ID: <200507282203.j6SM3J4X006930@cvs-int.fedora.redhat.com> Author: elliss Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5817 Modified Files: yum-software-management-en.xml Log Message: - Added note that package removal does not remove config and data files. - Amended package operation description to hopefully clarify metadata download - Added example of GPG key import. Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- yum-software-management-en.xml 28 Jul 2005 00:54:16 -0000 1.31 +++ yum-software-management-en.xml 28 Jul 2005 22:03:12 -0000 1.32 @@ -98,7 +98,7 @@ linkend="sn-software-management-concepts"/> before using yum for the first time. Experienced Linux users should start with - . + . @@ -254,9 +254,7 @@ these repositories. This method frees you from having to manually find and install new applications or updates. You may use a single command to update all system software, or search - for new software by specifying criteria. In each case the - management utility connects to the configured repositories and - checks their indexes to find the correct packages. + for new software by specifying criteria. @@ -391,7 +389,7 @@ tsclient package supplied with &FC;: -tsclient-0.132-4.i386.rpm +tsclient-0.132-6.i386.rpm Management utilities commonly refer to packages with one of @@ -407,7 +405,7 @@ Package name with version and release numbers: - tsclient-0.132-4 + tsclient-0.132-6 @@ -624,11 +622,19 @@ - During operation, yum first determines the best - set of actions to produce the required result, and displays the - transaction for you to approve. The yum utility - may prompt you to approve the installation, update, or removal of - additional packages, in order to resolve software dependencies. + For each operation, yum downloads the latest + package information from the configured repositories. If your + system uses a slow network connection yum may + require several seconds to download the repository indexes and the + header files for each package. + + + + The yum utility searches these data files to + determine the best set of actions to produce the required result, + and displays the transaction for you to approve. The transaction + may include the installation, update, or removal of additional + packages, in order to resolve software dependencies. @@ -676,6 +682,41 @@ version. + + + The yum utility imports the repository public + key if it is not already installed on the rpm + keyring. + + + + Format of <command>yum</command> Public Key Import + + + This is an example of the public key import: + + + +" +Is this ok [y/N]: +]]> + + + + + + Check the public key, and then press + y + to import the key and authorize the key for use. If you press + N + or + Enter + , yum stops without installing any packages. + Downloads are Cached @@ -766,8 +807,9 @@ If a piece of software is in use when you update it, the old - version remains active until the software is restarted. Kernel - updates take effect when you reboot the system. + version remains active until the application or service is + restarted. Kernel updates take effect when you reboot the + system. @@ -808,7 +850,8 @@ To remove software, yum examines your system for both the specified software, and any software which claims - it as a dependency. + it as a dependency. The transaction to remove the software + deletes both the software and the dependencies. @@ -836,6 +879,16 @@ root account when prompted. + + + Data and Settings are Retained + + + The removal process leaves configuration files and data in + place. If you reinstall removed software the new installation + uses the original configuration files. + + @@ -915,8 +968,9 @@ If you do not know the name of the package, use the or options. - Alternatively, you may use wild cards and regular expressions - with any yum search option. + Alternatively, use wild cards or regular expressions with any + yum search option to broaden the search + critieria. @@ -1147,7 +1201,7 @@ gpgkey setting. This setting specifies the location of a public key that verifies the packages provided by that repository. This public key is automatically imported the - first time you install software from the repository. If the + first time that you install software from the repository. If the configuration file provided does not include this setting, refer to . From fedora-docs-commits at redhat.com Fri Jul 29 15:00:18 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Fri, 29 Jul 2005 11:00:18 -0400 Subject: securing-filesystems sn-introduction.xml,NONE,1.1 Message-ID: <200507291500.j6TF0IiY031243@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31227/securing-filesystems Added Files: sn-introduction.xml Log Message: Initial commit to the Fedora Docs repository. --- NEW FILE sn-introduction.xml --- Introduction
Intended Audience This document is intended for all end-users of the fedora distribution. However it is my intention to present, as effectively as possible, this topic so that the following experienced audience can readily acquire valuable relevant information from this document as well: System Administrators Security Practitioners Power Users
Current Version The most current version of this document can be accessed at the following location: http://www.domain.com/docs/current/something.html This document is built from the following sources: Remote Development Versioning &doccvs; Local Development Identification &docsysid;
Revision History &REVID; 2005-07-18 TRJ Imported into fedora-docs CVS. Altered document outline. Added the character device content. 0.2 2005-05-13 TRJ Bugzilla submission. Received bugid: &BUG-NUM;. Altered inclusive nature of the document title. 0.1 2005-05-04 TRJ Initial draft for fedora-docs
Feedback Have you found some missing information, missing links, or missing characters? Maybe you just have some comments and/or suggestions about this document? Mail it to the author of this document at the following address: &author.mail; Whenever possible please utilize the authors GnuPG key for these communications: KeyID: 1024D/57BF9042 2004-12-26 Thomas R. Jones ( IEEE Computer Society Account) <thomasjones@computer.org> Fingerprint: 5264 BCA1 6059 57A8 58E5 7F04 A11E 5C13 57BF 9042
Legal Information &LEGALNOTICE-CONTENT;
System Requirements List requirements: materials, knowledge.
Document Conventions The following typographic and usage conventions occur in this document: Typographic and usage conventions Text typeMeaning Quoted text Quotes from people, quoted computer output. terminal view Literal computer input and output captured from the terminal, usually rendered with a light grey background. command Name of a command that can be entered on the command line. VARIABLE Name of a variable or pointer to content of a variable, as in $VARNAME. Option to a command, as in the option to the ls command. argument Argument to a command, as in read man ls. command arguments Command synopsis or general usage, on a separated line. filename Name of a file or directory, for example Change to the /usr/bin directory. Key Keys to hit on the keyboard, such as type Q to quit. Button Graphical button to click, like the OK button. Menu Choice Choice to select from a graphical menu, for instance: Select Help About Mozilla in your browser. Terminology Important term or concept: The Linux kernel is the heart of the system. See ????? link to related subject within this guide. The authors site Clickable link to an external web resource.
From fedora-docs-commits at redhat.com Fri Jul 29 15:03:28 2005 From: fedora-docs-commits at redhat.com (Thomas R. Jones (trjones)) Date: Fri, 29 Jul 2005 11:03:28 -0400 Subject: securing-filesystems securing-filesystems-en.xml,1.1,1.2 Message-ID: <200507291503.j6TF3SfM032368@cvs-int.fedora.redhat.com> Author: trjones Update of /cvs/docs/securing-filesystems In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32351/securing-filesystems Modified Files: securing-filesystems-en.xml Log Message: Structural changes of the document model. Index: securing-filesystems-en.xml =================================================================== RCS file: /cvs/docs/securing-filesystems/securing-filesystems-en.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- securing-filesystems-en.xml 24 Jul 2005 00:08:23 -0000 1.1 +++ securing-filesystems-en.xml 29 Jul 2005 15:02:56 -0000 1.2 @@ -1,7 +1,7 @@ - + @@ -12,52 +12,51 @@ - + - - + + - - + + %FEDORA-ENTITIES-EN; - + - - - + - + Access Control List"> acl"> ACL"> ThomasR. Jones"> - thomasjones@computer.org"> + thomasjones at computer.org"> Extended Attributes"> EA"> + Filesystem Hierarchy Standard"> + FHS"> POSIX"> - - + + - - - - - - - - - - - - - - + + + + + + + + + + + + + ]> @@ -65,93 +64,90 @@ &docpubid; - Implementing effective filesystem permissions and access controls in Fedora + + Implementing effective filesystem permissions and access controls in Fedora + &author;&author.mail; - + - This document provides a review of the concept and implementation of traditional - permissions, various access control methodologies, techniques and models to develop - effective safeguards to secure the filesystems of Fedora. + This document provides a review of the concept and implementation of + traditional permissions, various access control methodologies, techniques + and models to develop effective safeguards to secure the filesystems of + Fedora. &DRAFTNOTICE; - + - - + + - - &pr-introduction; - - - - - - &ch-standards_compliance; - - - + + &sn-introduction; + + + - - &ch-basic_characteristics; - - - - - - &ch-laying_foundation; - - - - - - &ch-understanding_access_control; - - - - - - &ch-introducing_access_control; - - - + + &ch-constitutes_filesystem; + + + + + + &ch-permissions; + + + + + + &ch-access_control; + + + - - &ch-introducing_extended_attributes; - - - - - - &ch-supplemental_packages; - - - + + &ch-extended_attributes; + + + + + + &ch-access_control_lists; + + + + + + + - - &ch-case_studies; - - - + + &ch-case_studies; + + + - + &ap-annotated_filesystem; - - - + + + - + &ap-glossary_of_terminology; - - + + - - &ap-bibliography; + + &ap-bibliography; - + \ No newline at end of file From fedora-docs-commits at redhat.com Fri Jul 29 17:47:47 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 29 Jul 2005 13:47:47 -0400 Subject: docs-common/css fedora.css,1.5,1.6 Message-ID: <200507291747.j6THlleh004208@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/css In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4191 Modified Files: fedora.css Log Message: Heading and admonition color changes to provide new Fedora branded feel Index: fedora.css =================================================================== RCS file: /cvs/docs/docs-common/css/fedora.css,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- fedora.css 18 May 2005 02:05:51 -0000 1.5 +++ fedora.css 29 Jul 2005 17:47:45 -0000 1.6 @@ -39,8 +39,8 @@ div.note table, div.tip table, div.important table, div.caution table, div.warning table { width: 95%; - border: 2px solid #B0C4DE; - background-color: #F0F8FF; + border: 2px solid #D0D0B0; + background-color: #FAF9E0; color: #000000; /* padding inside table area */ padding: 0.5em; @@ -72,7 +72,7 @@ h1, h2, h3, h4 { font-family: luxi sans,sans-serif; - color: #990000; + color: #172e56; font-weight: bold; } h1 { From fedora-docs-commits at redhat.com Sat Jul 30 01:44:17 2005 From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields)) Date: Fri, 29 Jul 2005 21:44:17 -0400 Subject: docs-common/css fedora.css,1.6,1.7 Message-ID: <200507300144.j6U1iK74011333@cvs-int.fedora.redhat.com> Author: pfrields Update of /cvs/docs/docs-common/css In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11316 Modified Files: fedora.css Log Message: Better agreement with the official web site color scheme Index: fedora.css =================================================================== RCS file: /cvs/docs/docs-common/css/fedora.css,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- fedora.css 29 Jul 2005 17:47:45 -0000 1.6 +++ fedora.css 30 Jul 2005 01:44:15 -0000 1.7 @@ -72,21 +72,31 @@ h1, h2, h3, h4 { font-family: luxi sans,sans-serif; - color: #172e56; + color: #22437f; font-weight: bold; } h1 { font-size: 1.75em; } - + h2 { font-size: 1.25em; } - + h3 { font-size: 1.1em; } +a:link { + color: #900; +} +a:visited { + color: #48468f; +} +a:hover { + color: #f20; +} + code.screen, pre.screen { font-family: monospace; font-size: 1em;