Author: elliss

Update of /cvs/docs/rpm-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18943

Modified Files: rpm-guide-advanced-packaging-en.xml rpm-guide-creating-rpms-en.xml rpm-guide-development-tools-en.xml rpm-guide-extra-packaging-tools-en.xml rpm-guide-intro-packaging-en.xml rpm-guide-intro-rpm-en.xml rpm-guide-management-software-en.xml rpm-guide-online-resources-en.xml rpm-guide-other-linuxes-en.xml rpm-guide-other-os-en.xml rpm-guide-packaging-guidelines-en.xml rpm-guide-programming-c-en.xml rpm-guide-programming-perl-en.xml rpm-guide-programming-python-en.xml rpm-guide-rpm-evolution-en.xml rpm-guide-rpmbuild-en.xml rpm-guide-scripting-en.xml rpm-guide-specfiles-en.xml rpm-guide-transactions-en.xml rpm-guide-using-rpm-db-en.xml rpm-guide-using-rpm-en.xml Log Message:

- Bulk replaced product names with entities - Replaced SuSE with SUSE to match current brand name

Index: rpm-guide-advanced-packaging-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-advanced-packaging-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-advanced-packaging-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-advanced-packaging-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -77,7 +77,7 @@ <para> Chapter 6 covers more on dependencies. The Obsoletes dependencies are usually only used when a package is renamed, such as the - apache package becoming the httpd package, starting in Red Hat + apache package becoming the httpd package, starting in &RH; Linux 8.0. The httpd package obsoletes the apache package. </para> <para> @@ -1196,7 +1196,7 @@ <title>Creating Relocatable Packages</title> <para> A relocatable package allows a user to specify where to install - the package. For example, if you build a package for Red Hat + the package. For example, if you build a package for &RH; Linux, the normal directory for binary executable programs is /usr/bin. Other versions of Linux, though, may place executable programs into /opt/bin, for example. If your package forces the @@ -1688,7 +1688,7 @@ different locations than originally planned. This is very useful when working with more than one version of Linux, or with other operating systems. For example, most Linux commands are stored in - /usr/bin, at least for Red Hat Linux. Other Linux distributions, + /usr/bin, at least for &RHL;. Other Linux distributions, or other operating systems may specify that programs added to the original set should be stored in /opt/bin and not /usr/bin, for example. Making your package relocatable helps users in these

Index: rpm-guide-creating-rpms-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-creating-rpms-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-creating-rpms-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-creating-rpms-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -388,7 +388,7 @@ command (GNU C Compiler) instead. The options passed to the C compiler may differ depending on the architecture of the system. Other commands may exist but be located in different - locations. SuSE Linux, for example, puts a lot of programs in + locations. SUSE Linux, for example, puts a lot of programs in /opt. </para> <para> @@ -749,14 +749,14 @@ noarch </para> <para> - By default, Red Hat Linux systems expect RPMs to be built in the + By default, &RHL; systems expect RPMs to be built in the /usr/src/redhat directory. </para> <para> Note </para> <para> - This directory is obviously specific to Red Hat Linux. On other + This directory is obviously specific to &RHL;. On other Linux distributions, you'll likely see other directories. </para> <para> @@ -1629,7 +1629,7 @@ <para> In this case, you see some file sizes and times differ. These differences can be explained by the fact that the original package - was compiled on a different system and older version of Red Hat + was compiled on a different system and older version of &RH; Linux than the version compiled locally. </para> <para>

Index: rpm-guide-development-tools-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-development-tools-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-development-tools-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-development-tools-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -61,7 +61,7 @@ </para> <para> You may not have installed any of these editors, but all are - available as part of Red Hat Linux. You can install vi, emacs, + available as part of &RHL;. You can install vi, emacs, gedit, kedit, or kate from the packages that come with your Linux distribution. </para> @@ -109,7 +109,7 @@ <sect1> <title>Integrated Development Environments for C Programming</title> <para> - If you want more of a graphical environment, Red Hat Linux ships + If you want more of a graphical environment, &RHL; ships with KDevelop, an IDE for C and C++ programming. </para> <para> @@ -126,7 +126,7 @@ <para> The Eclipse IDE, while mostly used for Java development, has a C and C++ mode called CDT, for C/C++ Development Tools. Eclipse is - important because Red Hat provides an RPM-building plug-in to + important because &RH; provides an RPM-building plug-in to Eclipse. </para> <para>

Index: rpm-guide-extra-packaging-tools-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-extra-packaging-tools-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-extra-packaging-tools-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-extra-packaging-tools-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -83,7 +83,7 @@ IMproved, or VIM (www.vim.org). VIM is the standard vi implementation (meaning that when you type vi at the command prompt, the program you really are running is vim) on many Linux - distributions, including Red Hat Linux. It is also freely + distributions, including &RHL;. It is also freely available for most other Unixes and even for non-Unix systems such as Microsoft Windows. </para> @@ -118,7 +118,7 @@ The spec.vim file that provides VIM with an understanding of spec-file syntax is bundled with newer versions of VIM, or it can be downloaded from the Internet. Most RPM-based Linux - distributions, including Red Hat Linux, ship this file with VIM + distributions, including &RHL;, ship this file with VIM as part of their distribution and even automatically configure VIM to load this syntax file any time an RPM spec file is being edited. When using VIM on a system that does not automatically @@ -213,7 +213,7 @@ &lt;your@email.address&gt;" </para> <para> - The preceding format is what Red Hat's developers use for Red + The preceding format is what &RH;'s developers use for Red Hat Linux spec files and results in a %changelog entry that looks like the following, with the user name and e-mail address changed to protect the innocent: @@ -350,7 +350,7 @@ License. </para> <para> - Red Hat Linux includes RPMs of both GNU Emacs and XEmacs as part + &RHL; includes RPMs of both GNU Emacs and XEmacs as part of the distribution, and most other Linux distributions will include one or both as well. </para> @@ -360,7 +360,7 @@ files that add new commands and functions. Stig Bj��rlykke has written a mode, rpm-spec-mode.el, which works with both GNU Emacs and with XEmacs to add many functions, making it easier to - use when editing RPM spec files. Red Hat Linux includes and + use when editing RPM spec files. &RHL; includes and enables this mode in both GNU Emacs and XEmacs, as do many other Linux distributions. </para> @@ -705,14 +705,14 @@ listing what entries are valid for various fields in the RPM header, such as the Vendor and Packager fields. By default, Red Hat Linux ships with this configuration file set to validate - packages to make sure they are suitable for Red Hat Linux; if + packages to make sure they are suitable for &RHL;; if packaging for a different distribution, this file might need to be modified. </para> <para> Once rpmlint has been installed and configured, it can be run against RPMs. For example, rpmlint helps with creating packages, - such as tin (a popular Usenet client) for Red Hat Linux, since + such as tin (a popular Usenet client) for &RHL;, since it is not included with the distribution. After preparing a tin spec file, then building RPMs from that file, you can typically double-check them using rpmlint. @@ -986,7 +986,7 @@ </para> <para> This rpm2cpio command is bundled with RPM and is installed on - most RPM-based Linux distributions, including Red Hat Linux. + most RPM-based Linux distributions, including &RHL;. However, it is less useful on systems that do not come with RPM, such as Solaris. This "standard" implementation of rpm2cpio is written in C, and so must be compiled before it can be used.

Index: rpm-guide-intro-packaging-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-packaging-en.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- rpm-guide-intro-packaging-en.xml 26 Oct 2005 00:49:38 -0000 1.3 +++ rpm-guide-intro-packaging-en.xml 31 Oct 2005 23:18:20 -0000 1.4 @@ -400,9 +400,9 @@ </para> <note> <title>Change of Name</title> -<!-- SE: Don't replace "Red Hat" with an entity here: we don't want the text to change --> +<!-- SE: Don't replace "&RH;" with an entity here: we don't want the text to change --> <para> - RPM was originally called Red Hat Package Manager. After + RPM was originally called &RH; Package Manager. After adoption by other Linux distributions, the name has changed to simply the RPM Package Manager. The RPM initials remain the same.

Index: rpm-guide-intro-rpm-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-rpm-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-intro-rpm-en.xml 25 Oct 2005 00:32:57 -0000 1.2 +++ rpm-guide-intro-rpm-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -26,7 +26,7 @@ Several package managers are available for Linux to track and manipulate the applications installed on the system. The most widely used of these Linux package managers is the RPM Package Manager - (formerly the Red Hat Package Manager), or RPM for short, the + (formerly the &RH; Package Manager), or RPM for short, the subject of this book </para> <para> @@ -167,7 +167,7 @@ related applications, but what was really needed was installation and uninstallation on an application-by-application basis. </para> -<!-- SE: Note that "Red Hat" should not replaced by entities when part of abbreviations --> +<!-- SE: Note that "&RH;" should not replaced by entities when part of abbreviations --> <para> In late 1993, Rik Faith, Doug Hoffman, and Kevin Martin began releasing the first public betas of the BOGUS Linux distribution. @@ -175,8 +175,8 @@ (<command>pms</command>) software that was used with it for installation and uninstallation of all software on an application-by-application basis. Shortly thereafter, in the - summer of 1994, the first public betas of Red Hat Commercial Linux - were released. &RH; initially used Red Hat Software Program + summer of 1994, the first public betas of &RH; Commercial Linux + were released. &RH; initially used &RH; Software Program Packages (RPP) as the basis of its Linux distribution. Like <command>pms</command>, RPP was a system-management tool that allowed for easy installation and uninstallation of applications. @@ -212,7 +212,7 @@ RPP-based distributions, &RH; looked closely at both their own RPP software and other software such as BOGUS's <command>pms</command> software. Developers at &RH;, particularly Marc Ewing and Erik - Troan, set out to develop what they initially called the Red Hat + Troan, set out to develop what they initially called the &RH; Package Manager (RPM). Based on experiences with earlier Linux packaging software and knowledge about packaging tools used on other platforms, &RH; had several design goals in mind when they @@ -528,7 +528,7 @@ <para> The BOGUS distribution's <command>pms</command> packaging system introduced the use of pristine source code to prepare packages. - With Red Hat's early RPP package system and other similar early + With &RH;'s early RPP package system and other similar early efforts, software packagers would compile software manually, then run commands to produce a package of that compiled software. Any changes made to the application's original source

Index: rpm-guide-management-software-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-management-software-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-management-software-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-management-software-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -56,15 +56,15 @@ As you start to search for RPM packages on the Internet, you���ll find thousands of packages available. Many of these packages are built specifically for various Linux distributions, such as - Conectiva, SuSE, Red Hat, or Mandrake. In many cases, the Linux + Conectiva, SUSE, &RH;, or Mandrake. In many cases, the Linux distribution won���t matter, but in general it's best to download - packages built for your version of Linux, such as Red Hat. + packages built for your version of Linux, such as &RH;. </para> <para> Note </para> <para> - Although the examples in this book assume Red Hat Linux as a base, + Although the examples in this book assume &RHL; as a base, just about everything applies to all versions of Linux that use the RPM system, unless noted otherwise. </para> @@ -294,10 +294,10 @@ that 364 packages are found; there are lots of e-mail clients available for Linux! That number, however, is slightly misleading. Some of the packages found are prepared for the - distribution I am running (Red Hat Linux version 7.2), but + distribution I am running (&RHL; version 7.2), but others are not. Result #364, for example, appears to be the Polish(ed) Linux Distribution 1.0 package of sylpheed, the same - software offered to me packaged for my Red Hat Linux version 7.2 + software offered to me packaged for my &RHL; version 7.2 system in Result #2. </para> <para> @@ -641,7 +641,7 @@ </entry> <entry> <para> - Edwin Chan's Red Hat RPMs + Edwin Chan's &RH; RPMs </para> </entry> </row> @@ -725,33 +725,33 @@ Figure 8-3: Installing RPM files with Nautilus. </para> <para> - When you install RPMs with Nautilus, it really runs the Red Hat + When you install RPMs with Nautilus, it really runs the &RH; Package Management tool. </para> <para> Note </para> <para> - Nautilus only supports RPM functionality starting with Red Hat + Nautilus only supports RPM functionality starting with &RH; Linux 8.0. This functionality may not be supported in other versions of Linux. </para> </sect2> <sect2> - <title>Red Hat Package Management</title> + <title>&RH; Package Management</title> <para> The redhat-config-packages application (say that three times - fast) comes new with Red Hat Linux 8.0. You can use the Python + fast) comes new with &RHL; 8.0. You can use the Python program in this package to manage the packages that come with - Red Hat Linux, using an interface that is very similar to the - Red Hat Linux installation program. This similarity may make it + &RHL;, using an interface that is very similar to the + &RHL; installation program. This similarity may make it easier for many users to manage their packages, although I found the program a bit short on explanations. </para> <para> To run this program, you first have to do a bit of searching to find it. It appears under the System Settings menu from the main - Red Hat Start menu under the default Bluecurve desktop. Select + &RH; Start menu under the default Bluecurve desktop. Select the Packages choice to launch this program. You can also start the program from the command line with the following command: </para> @@ -761,7 +761,7 @@ <para> This program takes a long time to read in all the information and start up. Once started, the interface provides the same - categories and much the same look as the Red Hat Linux + categories and much the same look as the &RHL; installer, as shown in Figure 8-4. </para> <para> @@ -773,7 +773,7 @@ <para> The packages tool divides the packages into groups. Inside each group, the packages are divided into two sets: standard and - extra packages. (Red Hat places the packages into these + extra packages. (&RH; places the packages into these categories, striving to make a reasonable division among the many packages that come with Linux.) If you click the check box for a group, the tool will queue up all the standard packages @@ -1284,7 +1284,7 @@ repository. In addition, they support wild cards and directory accesses, so a command such as install ftp://ftp.redhat.com/pub/redhat/linux/updates/current/* can be - used to install all errata for the current release of Red Hat + used to install all errata for the current release of &RH; Linux. </para> <para> @@ -1294,7 +1294,7 @@ auto, AutoRPM consults the configuration file /etc/autorpm.conf to decide what to do. By default, /etc/autorpm.d/autorpm.conf is configured to download, but not automatically install, all - errata for the release of Red Hat Linux running on the local + errata for the release of &RHL; running on the local system. Editing this file makes it possible to use AutoRPM to download all errata ��� or errata for other Linux distributions ��� or to install errata automatically once downloaded. @@ -1337,8 +1337,8 @@ /etc/autoupdate.d/autoupdate.conf. By default, AutoUpdate provides several additional configuration files pre-defined for downloading updates for the most popular RPM-based Linux - distributions (Red Hat Linux, Mandrake Linux, Caldera/SCO - OpenLinux, and SuSE Linux). The autoupdate.conf file can be + distributions (&RHL;, Mandrake Linux, Caldera/SCO + OpenLinux, and SUSE Linux). The autoupdate.conf file can be modified to configure AutoUpdate to install software automatically. </para> @@ -1453,31 +1453,31 @@ </para> </sect2> <sect2> - <title>The Red Hat Network and up2date</title> + <title>The &RHN; and up2date</title> <para> Some vendors of RPM-based Linux distributions also provide utilities that can help with management of the distributions - they create. Red Hat has created two complementary products, the - Red Hat Network (RHN) and up2date, which together provide much - the same functionality for managing Red Hat Linux installations + they create. &RH; has created two complementary products, the + &RHN; (RHN) and up2date, which together provide much + the same functionality for managing &RHL; installations as tools such as AutoUpdate and AutoRPM, as well as offering more advanced features. </para> <para> - Red Hat Network is a subscription-based service offered by Red - Hat Red Hat Network makes software available for installation + &RHN; is a subscription-based service offered by Red + Hat &RHN; makes software available for installation via the network. (A free evaluation is also available.) After - registering machines with Red Hat Network, administrators can + registering machines with &RHN;, administrators can pull updates or new software for installation to those registered machines. In addition, administrators have access to a Web-based administrative console from which they can view the systems they manage and can push software out to those systems. </para> <para> - Red Hat offers two tiers of access to Red Hat Network. Basic - Service subscriptions to Red Hat Network provide the ability to + &RH; offers two tiers of access to &RHN;. Basic + Service subscriptions to &RHN; provide the ability to manage single systems. Multiple machines can be subscribed by - the same administrator for Basic Service level Red Hat Network + the same administrator for Basic Service level &RHN; access, but they must all be managed independently. The administrator must push out errata to each machine separately. Workgroup Service subscriptions provide the same functionality @@ -1491,22 +1491,22 @@ administrators. </para> <para> - When using Red Hat Network to manage machines with Workgroup - Service subscriptions, Red Hat also offers two optional - services: Red Hat Network Proxy Server and Red Hat Network - Satellite. The Red Hat Network Proxy Server is, as its name - suggests, a proxy server for the Red Hat Network. Using it, - errata pushed out via Red Hat Network is downloaded by the + When using &RHN; to manage machines with Workgroup + Service subscriptions, &RH; also offers two optional + services: &RHN; Proxy Server and &RHN; + Satellite. The &RHN; Proxy Server is, as its name + suggests, a proxy server for the &RHN;. Using it, + errata pushed out via &RHN; is downloaded by the organization (only once) to a central server in-house. All - machines in that organization subscribed to Red Hat Network get + machines in that organization subscribed to &RHN; get their updated software from that in-house proxy server, significantly reducing the network bandwidth requirements needed to keep large organizations up to date. </para> <para> - In addition, the Red Hat Network Proxy Server can be used to + In addition, the &RHN; Proxy Server can be used to provide all subscribed machines with software not provided with - Red Hat Linux. Custom ���channels��� of supplemental software + &RHL;. Custom ���channels��� of supplemental software can be created on the Proxy Server, and machines can be subscribed to those channels as desired. Using this feature, different departments in the organization with different @@ -1518,38 +1518,38 @@ get only software that desktop machines need. </para> <para> - The Red Hat Network is normally centrally administered through - Red Hat. Machines subscribed to the Red Hat Network have a - system profile on file with Red Hat that details the system���s + The &RHN; is normally centrally administered through + &RH;. Machines subscribed to the &RHN; have a + system profile on file with &RH; that details the system���s essential configuration information (what software is installed on it, what CPU architecture it contains, and so forth) needed to determine which software errata are appropriate for that system. Similarly, the Web console through which machines - subscribed to Red Hat Network can be administered is also - located on a Red Hat server. Customers wishing to use Red Hat + subscribed to &RHN; can be administered is also + located on a &RH; server. Customers wishing to use &RH; Network services, but not wanting the dependency upon Internet - access to Red Hat, can create an in-house Red Hat Network by - using the Red Hat Network Satellite. This solution is often + access to &RH;, can create an in-house &RHN; by + using the &RHN; Satellite. This solution is often practical for customers who need to keep system information confidential or for customers whose systems are not able to access the Internet. </para> <para> - Red Hat provides several interfaces for administering machines - subscribed to the Red Hat Network. A Web-management console is + &RH; provides several interfaces for administering machines + subscribed to the &RHN;. A Web-management console is available at https://rhn.redhat.com/. Administrators of machines - subscribed to any level of the Red Hat Network can simply log + subscribed to any level of the &RHN; can simply log into this Web site and perform a variety of package-management operations from their Web browsers. In addition to viewing other things, administrators can see what software is currently - installed, select and install Red Hat Linux errata or new + installed, select and install &RHL; errata or new software, or schedule a time for automatic installation of Red Hat Linux errata. </para> <para> - When using Red Hat Network, rhnsd is a client-side daemon that + When using &RHN;, rhnsd is a client-side daemon that should be run on subscribed systems. It periodically launches a - helper utility, rhn_check, which connects to the Red Hat Network + helper utility, rhn_check, which connects to the &RHN; servers and checks for any actions (such as a scheduled installation of errata) that an administrator has selected in the Web console. If any actions have been scheduled for that @@ -1559,11 +1559,11 @@ every hour if necessary. </para> <para> - In addition, Red Hat provides client-side tools that can be used - in a more interactive fashion to connect to the Red Hat Network + In addition, &RH; provides client-side tools that can be used + in a more interactive fashion to connect to the &RHN; from subscribed systems. The up2date program provides a graphical and command-line tool that can be used to install - packages from Red Hat Network servers. When installing a new + packages from &RHN; servers. When installing a new package, up2date automatically installs any necessary dependencies the package requires, making it a very convenient tool for adding software to the system. up2date can also be run @@ -1721,7 +1721,7 @@ <entry> <para> Update the list of installed packages associated with - this computer in the Red Hat Network database + this computer in the &RHN; database </para> </entry> </row> @@ -1810,9 +1810,9 @@ <sect2> <title>Current</title> <para> - The up2date command, the Red Hat Network client software, is - open-source software released by Red Hat under the terms of the - GNU GPL. Red Hat Network Proxy Server and Red Hat Network + The up2date command, the &RHN; client software, is + open-source software released by &RH; under the terms of the + GNU GPL. &RHN; Proxy Server and &RHN; Satellite, the server applications with which up2date interacts, are not freely available, open-source applications. For this reason, an effort is underway to develop servers available under @@ -1823,7 +1823,7 @@ <para> The current server can be downloaded from http://current.tigris.org. Although not yet as functional as Red - Hat Network Proxy Server or Red Hat Network Satellite, current + Hat Network Proxy Server or &RHN; Satellite, current can already be used to create a RPM repository from which up2date-using clients can retrieve and install software. More advanced features, such as support for multiple ���channels��� @@ -1834,7 +1834,7 @@ <title>urpmi and RpmDrake</title> <para> Mandrake provides a set of software similar to the combination - of up2date and Red Hat Network or current that can be used with + of up2date and &RHN; or current that can be used with the Mandrake Linux distribution. Links to the source code for the Mandrake applications can be found at www.linux-mandrake.com/cooker/urpmi.html. This suite of @@ -1893,7 +1893,7 @@ The Debian Project (www.debian.org/) is a nonprofit volunteer group that develops a Linux distribution, Debian GNU/Linux. The group uses a different package format, dpkg, which was developed - independently of and simultaneous to Red Hat���s creation of + independently of and simultaneous to &RH;���s creation of RPM. The two formats, dpkg and RPM, are very similar in terms of utility and functionality. In addition to having created a package format, the Debian Project later developed a collection @@ -1904,7 +1904,7 @@ </para> <para> In many respects, Debian���s implementation of apt is very - similar to the functionality provided by Red Hat���s up2date/Red + similar to the functionality provided by &RH;���s up2date/Red Hat Network products or Mandrake���s urpmi software. On Debian systems, apt is a client tool used to select and install new software packages or to update existing packages already @@ -1935,8 +1935,8 @@ necessary utilities that can be used to make any RPM repository apt-capable. By creating apt-capable servers using apt4rpm and then installing apt-rpm on the client systems, any RPM-based - distribution, such as Red Hat Linux, Mandrake Linux, Caldera/SCO - OpenLinux, or SuSE Linux, can then be easily managed using apt. + distribution, such as &RHL;, Mandrake Linux, Caldera/SCO + OpenLinux, or SUSE Linux, can then be easily managed using apt. </para> <para> Note @@ -1949,7 +1949,7 @@ Administrators managing multiple dispersed machines as well as those used to Debian administration often find it useful to configure their machines to use apt; its dependency tracking is - far better than any other tool, except for Red Hat���s + far better than any other tool, except for &RH;���s up2date/RHN combination. To use apt, administrators must install it on their machines and have access to an apt-capable RPM repository for the distribution they use. Several public FTP @@ -1969,7 +1969,7 @@ Once apt and libapt RPMs are installed, the sources.list file in /etc/apt needs to be modified to reference the apt-capable software site that will be used. For example, to configure a - machine to access the apt-capable Red Hat Linux 7.2 software + machine to access the apt-capable &RHL; 7.2 software distributed by the Tuxfamily.org server, the /etc/apt/sources.list file needs to list: </para> @@ -1981,8 +1981,8 @@ os </para> <para> - These two lines, respectively, access the Red Hat Linux 7.2 and - Red Hat Linux 7.2 errata RPMs being served by the system + These two lines, respectively, access the &RHL; 7.2 and + &RHL; 7.2 errata RPMs being served by the system apt-rpm.tuxfamily.org. If you also want access to source RPMs, the following lines are necessary as well. </para> @@ -2084,7 +2084,7 @@ it installs any RPM files you double-click. </para> <para> - Red Hat Linux 8 comes with a new package-management tool available + &RHL; 8 comes with a new package-management tool available from the System Settings menu. Be careful with this tool, though, as it automatically installs--and removes--dependent packages. </para> @@ -2096,7 +2096,7 @@ <para> The Debian GNU/Linux apt system provides many of the same capabilities as RPM, along with the network-updating capabilities - of up2date and the Red Hat Network. You can use special apt + of up2date and the &RHN;. You can use special apt packages that adapt apt for RPM-based Linux distributions and get the best of both the RPM system and the apt system. </para>

Index: rpm-guide-online-resources-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-online-resources-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-online-resources-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-online-resources-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -315,7 +315,7 @@ </entry> <entry> <para> - Edwin Chan's Red Hat RPMs + Edwin Chan's &RH; RPMs </para> </entry> </row>

Index: rpm-guide-other-linuxes-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-other-linuxes-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-other-linuxes-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-other-linuxes-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -1,7 +1,7 @@ <!-- $Id: -->

<chapter id="ch-other-linuxes"> - <title>Using RPM on Non-Red Hat Linuxes</title> + <title>Using RPM on Non-&RHL;es</title> <para> This chapter covers: </para> @@ -35,7 +35,7 @@ <para> Although its name was originally the Red Hat Package Manager, RPM has been adopted by most major Linux distributions. With this - adoption, RPM has moved from its Red Hat roots, and RPM now stands + adoption, RPM has moved from its &RH; roots, and RPM now stands for the RPM Package Manager. </para> <para> @@ -78,7 +78,7 @@ <sect2> <title>Dealing with RPM versions</title> <para> - Red Hat Linux 8.0 ships with RPM version 4.1. Other + &RHL; 8.0 ships with RPM version 4.1. Other distributions of Linux ship with other versions of RPM. Thus, one of the first commands you can run on another Linux distribution is the rpm --version command, to see what RPM @@ -166,7 +166,7 @@ Start with the simple case and make certain that you haven���t failed to install a necessary RPM that provides the right dependency. In most cases, you can download a vendor-specific - package from your Linux vendor, such as www.suse.com for SuSE + package from your Linux vendor, such as www.suse.com for SUSE Linux. Most Linux vendors provide HTTP or FTP sites with a large set of packages created for their distributions. If such a distribution-specific package solves a dependency issue, this is @@ -212,7 +212,7 @@ </para> <para> This naming scheme of a base package and base-devel is used for - Red Hat Linux packages, but may not be used for other vendor + &RHL; packages, but may not be used for other vendor packages. In any case, you can solve this type of dependency by finding the relevant base packages that the package you are trying to install depends on. Consult the manuals that come with @@ -293,7 +293,7 @@ For example, a set of Build Root Policy (brp) helper scripts are run at the end of the %install section in an RPM. These scripts perform tasks such as compressing man pages. The Mandrake brp - scripts use bzip2 compression. Red Hat brp scripts use gzip + scripts use bzip2 compression. &RH; brp scripts use gzip compression. This is one case where rebuilding an RPM and then installing may work best. </para> @@ -339,12 +339,12 @@ One way to help make vendor-specific packages, or to see which RPM macros are defined on a given Linux distribution, is to look for an RPM that contains the distribution-specific RPM - configuration. For example, on Red Hat Linux systems, the Red + configuration. For example, on &RHL; systems, the Red Hat RPM configuration is defined by the redhat-rpm-config package. </para> <para> - You can list the files in this package to see where Red Hat + You can list the files in this package to see where &RH; defines macros specific to their Linux distribution. </para> <para> @@ -396,7 +396,7 @@ These files, such as /usr/lib/rpm/redhat/macros, show you what is specific to a given Linux distribution. You can then look at the macros defined in these files to identify settings for a - particular distribution, in this case, Red Hat. Armed with this + particular distribution, in this case, &RH;. Armed with this knowledge, you can better create portable RPM spec files. </para> </sect2> @@ -540,7 +540,7 @@ $ more /etc/redhat-release </para> <para> - Red Hat Linux release 8.0 (Psyche) + &RHL; release 8.0 (Psyche) </para> <para> For packages, the convention is vendor-release for a package @@ -768,7 +768,7 @@ <sect3> <title>Dealing with Signatures</title> <para> - With SuSE Linux, or any Linux based on UnitedLinux 1.0, the + With SUSE Linux, or any Linux based on UnitedLinux 1.0, the RPM packages are signed with OpenPGP version 4, not 3, as used in RPM 4.1. This means that you must use some other, non-RPM means to extract the signatures from an RPM package, and then

Index: rpm-guide-other-os-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-other-os-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-other-os-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-other-os-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -426,7 +426,7 @@ <title>Running RPM on Windows</title> <para> The version of RPM for Windows requires cygwin, originally the - Cygnus port of many Unix tools to Windows. Now part of Red Hat, + Cygnus port of many Unix tools to Windows. Now part of &RH;, you can download the cygwin environment from the main cygwin site. </para> @@ -964,7 +964,7 @@ install. </para> <para> - On an operating system that is based on RPM, such as Red Hat + On an operating system that is based on RPM, such as &RH; Linux, all packages (except for some bootstrapping code) are installed with RPM. That means nearly everything on the system is defined in the RPM database. The RPM database then has a @@ -1410,11 +1410,11 @@ settings. </para> <para> - In most cases the _topdir setting on Red Hat Linux systems map + In most cases the _topdir setting on &RHL; systems map to the /usr/src/redhat directory. Your system may not even have a /usr/src directory. Also you may not want to build RPMs in a redhat directory, which may cause confusion if you are building - on a non-Red Hat Linux system. + on a non-&RHL; system. </para> <para> Cross Reference

Index: rpm-guide-packaging-guidelines-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-packaging-guidelines-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-packaging-guidelines-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-packaging-guidelines-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -474,7 +474,7 @@ <para> Using tools can help speed up the RPM-making process, as well as give you a head start in learning how RPMs work. - RPM-building tools such as the Red Hat plugin for the Eclipse + RPM-building tools such as the &RH; plugin for the Eclipse Integrated Development Environment have proven really helpful. </para> <para> @@ -628,7 +628,7 @@ <para> Packages are categorized into groups. These group names, while not always the best, appear in the graphical tools such as the - Red Hat package manager. If your application is a Linux shell + &RH; package manager. If your application is a Linux shell program, then users will expect to find it in the System Environment/Shells group and not the Development/Languages or System Environment/Daemons groups. This is a rather small

Index: rpm-guide-programming-c-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-c-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-programming-c-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-programming-c-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -108,14 +108,14 @@ <para> At the very least, you���ll need a C compiler, gcc, and a text editor. The easiest way to get the C compiler is to install the - packages grouped under Software Development with the Red Hat + packages grouped under Software Development with the &RH; package management tool. </para> <para> Cross Reference </para> <para> - See Chapter 8 for more on the Red Hat package management tool. + See Chapter 8 for more on the &RH; package management tool. </para> <para> The gcc package requires a number of capabilities. Make sure you @@ -143,7 +143,7 @@ <para> To program with the RPM library, you need to install the rpm-devel package. You must have a version of rpm-devel that - matches your version of the rpm package. If you have Red Hat + matches your version of the rpm package. If you have &RH; Linux, your installation CDs will also have the version of the RPM development package that corresponds to your system. </para> @@ -165,7 +165,7 @@ of Linux. </para> <para> - The package you need is rpm-devel. If you installed Red Hat + The package you need is rpm-devel. If you installed &RH; Linux 8.0, the package is rpm-devel-4.1-1.06. This package includes header files, documentation, and libraries. </para>

Index: rpm-guide-programming-perl-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-perl-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-programming-perl-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-programming-perl-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -82,12 +82,12 @@ A number of Perl RPM modules are available. No one module provides all the features you need, although with time, the Perl modules will consolidate into a few modules that most everyone uses. As of - this writing, the RPM2 module, by Chip Turner of Red Hat, provides + this writing, the RPM2 module, by Chip Turner of &RH;, provides the most recent approach to working with the RPM system from Perl. This chapter covers the RPM2 module. </para> <para> - Red Hat Linux 8.0 comes with a perl-RPM2 package, which you need + &RHL; 8.0 comes with a perl-RPM2 package, which you need to install to use this module. Otherwise, you can download the module from www.cpan.org. Install this module, as well as the perl module, which provides the Perl language interpreter. Once you @@ -98,11 +98,11 @@ Note </para> <para> - The version of the perl-RPM2 package that ships with Red Hat Linux + The version of the perl-RPM2 package that ships with &RHL; 8.0 has a bug in that it will not open package files that were - created with the version of rpm that ships with Red Hat Linux 8.0. + created with the version of rpm that ships with &RHL; 8.0. That is, the Perl module cannot read package files that ship with - Red Hat Linux. You can read older package files, though. This + &RHL;. You can read older package files, though. This problem only affects attempts to read .rpm files, not installed packages. The bug is related to reading signed packages but not having the GPG keys in the keyring. The latest version on @@ -942,7 +942,7 @@ upon. </para> <para> - Vendor: Red Hat, Inc., http://www.xfree86.org + Vendor: &FORMAL-RHI;, http://www.xfree86.org </para> <para> Size: 30552239 @@ -1057,7 +1057,7 @@ $ ./rpmdate.pl kernel </para> <para> - kernel-2.4.18-14 Red Hat, Inc. Sat Oct 5 12:29:58 2002 + kernel-2.4.18-14 &FORMAL-RHI; Sat Oct 5 12:29:58 2002 </para> </sect3> <sect3>

Index: rpm-guide-programming-python-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-python-en.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- rpm-guide-programming-python-en.xml 26 Oct 2005 01:54:11 -0000 1.3 +++ rpm-guide-programming-python-en.xml 31 Oct 2005 23:18:20 -0000 1.4 @@ -82,7 +82,7 @@ <para> *PyGTK is a binding between Python and the GTK+ toolkit used by the GNOME desktop, one of two main desktop environments for - Linux. (KDE is the other main desktop environment.) The Red Hat + Linux. (KDE is the other main desktop environment.) The &RH; redhat-config-packages program uses PyGTK and sports a very good-looking user interface. </para> @@ -273,10 +273,10 @@ Note </para> <para> - The code examples in this chapter follow the Red Hat conventions + The code examples in this chapter follow the &RH; conventions for naming variables, such as ts for a transaction set. This is to make it easier to read the Python examples in the RPM sources, - along with Red Hat installer programs written in Python. + along with &RH; installer programs written in Python. </para> <para> You will need a transaction set in just about every Python script @@ -335,7 +335,7 @@ </para> <para> This example uses the rpmdb-redhat package, which holds a - database of all Red Hat Linux packages. The explicit call to + database of all &RHL; packages. The explicit call to openDB opens the RPM database. In most Python scripts, though, you do not want to call openDB. Instead, a transaction set will open the database as needed. @@ -2212,8 +2212,8 @@ <para> You can use a check callback to automatically bring in packages that are required into a transaction set. You can - bring in packages from the Red Hat RPM database package, which - contains a database of all Red Hat packages, the rpmdb-redhat + bring in packages from the &RH; RPM database package, which + contains a database of all &RH; packages, the rpmdb-redhat package. You can open the database from this package by using the trick described previously for opening transactions to more than one RPM database at a time. Simply set the _dbpath @@ -3005,7 +3005,7 @@ <title>Where to Go from Here</title> <para> The RPM bindings for Python are documented along with the C - programming API. On a Red Hat Linux system, look in the file + programming API. On a &RHL; system, look in the file /usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html to see the start of the Python-specific documentation. </para> @@ -3025,7 +3025,7 @@ To learn more about programming in Python, install the python-docs package. The python-docs package has a large set of online documentation for Python, including the official Python Tutorial. - With Red Hat Linux, start at + With &RHL;, start at /usr/share/doc/python-docs-2.2.1/html/tut/tut.html. </para> <para>

Index: rpm-guide-rpm-evolution-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-rpm-evolution-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-rpm-evolution-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-rpm-evolution-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -23,14 +23,14 @@ </para> <para> RPM 3.0.5 is the final release of the 3.x series of RPM. It was the - release of RPM shipped with Red Hat Linux 6.2 and older releases. It + release of RPM shipped with &RHL; 6.2 and older releases. It is still in wide use by other vendors as well. Cobalt���s Linux distributions use an RPM implementation version based on RPM 3.0.5, - for example. (Red Hat Linux was upgraded to RPM 4 via an errata.) + for example. (&RHL; was upgraded to RPM 4 via an errata.) </para> <para> - RPM 4.0.4 was used with the 7.x releases of Red Hat Linux, and RPM - 4.1 first shipped with Red Hat Linux 8.0. Packages produced + RPM 4.0.4 was used with the 7.x releases of &RHL;, and RPM + 4.1 first shipped with &RHL; 8.0. Packages produced targeting RPM 3.0.5 should work with nearly all implementations of RPM still in use today. Packages produced targeting RPM 4.0.4 or RPM 4.1 will work only with recent RPM implementations.

Index: rpm-guide-rpmbuild-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-rpmbuild-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-rpmbuild-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-rpmbuild-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -360,7 +360,7 @@ cpu-vendor-os </para> <para> - For example, i686-redhat-linux specifies a 686 CPU with Red Hat + For example, i686-redhat-linux specifies a 686 CPU with &RH; Linux. Other CPUs include ppc for PowerPC and sparc for Sun SPARC. </para> @@ -731,14 +731,14 @@ For example, you can use the rpm -i command to install a source RPM. This installs the sources provided by the source RPM, not the actual application. Normally, when you install a source RPM on a - Red Hat Linux system, the package gets installed into + &RHL; system, the package gets installed into /usr/src/redhat. </para> <para> Note </para> <para> - This directory is obviously specific to Red Hat Linux. On other + This directory is obviously specific to &RHL;. On other Linux distributions, you'll likely see directories such as /usr/src/OpenLinux for SCO (formerly Caldera) OpenLinux. </para> @@ -1078,11 +1078,11 @@ <para> Often, source RPMs are abbreviated as SRPMs. In fact, if you see a directory named SRPM or SRPMS, chances are the directory holds - source RPMs. (Red Hat uses this convention for its Linux + source RPMs. (&RH; uses this convention for its Linux distributions.) </para> <para> - The SRPMS directories on Red Hat CD-ROMs or on the Red Hat FTP + The SRPMS directories on &RH; CD-ROMs or on the &RH; FTP Internet site, ftp.redhat.com, indicate directories that hold source RPMs. </para> @@ -1136,7 +1136,7 @@ compatible with the OpenPGP Internet standard as defined in RFC 2440. It started when a number of developers wanted a free implementation. One such free implementation, GPG, allows Linux - vendors such as Red Hat to include PGP in their products. So, in + vendors such as &RH; to include PGP in their products. So, in a sense, GPG provides PGP. </para> <para> @@ -1263,13 +1263,13 @@ Email address: please_no_spam@nospam.com </para> <para> - Comment: Example for Red Hat RPM Guide + Comment: Example for &RH; RPM Guide </para> <para> You selected this USER-ID: </para> <para> - "Eric Foster-Johnson (Example for Red Hat RPM Guide) + "Eric Foster-Johnson (Example for &RH; RPM Guide) &lt;erc@no_spam.com&gt;" </para> <para> @@ -1317,7 +1317,7 @@ <para/> <para> pub 1024D/01681C24 2002-11-05 Eric Foster-Johnson (Example for - Red Hat RPM + &RH; RPM </para> <para> Guide) &lt;please_no_spam@nospam.com&gt; @@ -1585,7 +1585,7 @@ built and </para> <para> - signed by Red Hat, Inc. using `rpm -K' using the GNU GPG + signed by &FORMAL-RHI; using `rpm -K' using the GNU GPG package. </para> <para> @@ -1680,7 +1680,7 @@ </para> <para> This example shows an error message when trying to verify the - key. Then, after importing the Red Hat public key, the + key. Then, after importing the &RH; public key, the verification works. </para> <para> @@ -1716,11 +1716,11 @@ </para> </sect2> <sect2> - <title>Getting the Red Hat public key</title> + <title>Getting the &RH; public key</title> <para> - Strangely enough, the Red Hat public key is not installed when - you install Red Hat Linux 8.0. If you need the key, the Red Hat - public key is available on the root directory of all Red Hat + Strangely enough, the &RH; public key is not installed when + you install &RHL; 8.0. If you need the key, the &RH; + public key is available on the root directory of all &RH; Linux CD-ROMs, as shown in the following listing: </para> <para> @@ -1737,7 +1737,7 @@ Note </para> <para> - You can also download this key file from the Red Hat FTP site, + You can also download this key file from the &RH; FTP site, at ftp://ftp.redhat.com/pub/redhat/linux/8.0/en/os/i386/. </para> </sect2>

Index: rpm-guide-scripting-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-scripting-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-scripting-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-scripting-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -925,7 +925,7 @@ Name : perl-XML-Dumper Relocations: /usr </para> <para> - Version : 0.4 Vendor: Red Hat, Inc. + Version : 0.4 Vendor: &FORMAL-RHI; </para> <para> Release : 22 Build Date: Tue 06 Aug 2002 01:53:30 PM CDT @@ -945,7 +945,7 @@ fd372689897da07a </para> <para> - Packager : Red Hat, Inc. + Packager : &FORMAL-RHI; &lt;http://bugzilla.redhat.com/bugzilla%3E; </para> <para>

Index: rpm-guide-specfiles-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-specfiles-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-specfiles-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-specfiles-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -293,7 +293,7 @@ <para> These directories are the default directories. See Chapter 21 for changing RPM default values. In addition, these are the - defaults for Red Hat Linux. See Chapters 19 and 20 for + defaults for &RHL;. See Chapters 19 and 20 for discussions on other versions of Linux and other non-Linux operating systems, respectively. </para> @@ -439,13 +439,13 @@ </para> <para> The Distribution: directive is used by Linux distribution - vendors such as Red Hat to identify that the package is part + vendors such as &RH; to identify that the package is part of a given distribution, or was built for a particular distribution. Most packages created outside of the Linux vendors don���t provide this directive. </para> <para> - Distribution: Red Hat Linux + Distribution: &RHL; </para> <para> The Icon: directive names an icon file stored in the RPM. The @@ -2214,7 +2214,7 @@ </para> <para> The example directories shown above come from the standard RPM - macro file, /usr/lib/rpm/macros, instead of the Red Hat-specific + macro file, /usr/lib/rpm/macros, instead of the &RH;-specific file, /usr/lib/rpm/redhat/macros, which holds: </para> <para/>

Index: rpm-guide-transactions-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-transactions-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-transactions-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-transactions-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -360,7 +360,7 @@ can query for packages installed when you installed or upgraded your version of Linux. First, query for the transaction ID of a package you know was installed with the - Linux distribution, such as setup on a Red Hat system: + Linux distribution, such as setup on a &RH; system: </para> <para> $ rpm -q --qf "%-20{NAME} %-20{INSTALLTID}\n" setup @@ -450,7 +450,7 @@ </para> <para> This example shows just a few of the packages installed when - the Red Hat Linux was installed. + the &RHL; was installed. </para> <para> With these options, you can find the transaction IDs for given @@ -547,7 +547,7 @@ Note </para> <para> - The up2date name comes from the Red Hat service for keeping a + The up2date name comes from the &RH; service for keeping a system up to date with regard to package versions. </para> <para>

Index: rpm-guide-using-rpm-db-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-db-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-using-rpm-db-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-using-rpm-db-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -481,7 +481,7 @@ </entry> <entry> <para> - Red Hat application, usually for configuring your + &RH; application, usually for configuring your system </para> </entry> @@ -763,7 +763,7 @@ Name : tcsh Relocations: (not relocateable) </para> <para> - Version : 6.10 Vendor: Red Hat, Inc. + Version : 6.10 Vendor: &FORMAL-RHI; </para> <para> Release : 6 Build Date: Sun 24 Jun 2001 10:45:29 @@ -785,7 +785,7 @@ Size : 764000 License: distributable </para> <para> - Packager : Red Hat, Inc. + Packager : &FORMAL-RHI; &lt;http://bugzilla.redhat.com/bugzilla%3E; </para> <para> @@ -1839,7 +1839,7 @@ Name : grep Relocations: /usr </para> <para> - Version : 2.5.1 Vendor: Red Hat, + Version : 2.5.1 Vendor: &RH;, </para> <para> Inc. @@ -1869,7 +1869,7 @@ Signature : DSA/SHA1, Tue 03 Sep 2002 04:17:47 PM CDT, Key ID </para> <para> - 219180cddb42a60ePackager : Red Hat, Inc. + 219180cddb42a60ePackager : &FORMAL-RHI; </para> <para> &lt;http://bugzilla.redhat.com/bugzilla%3E; @@ -3502,7 +3502,7 @@ <para> If what you���ve seen so far isn���t enough, the rpm command supports a number of extra queries, mostly of use to developers - at Red Hat. + at &RH;. </para> <para> Table 5-7 summarizes these extra queries.

Index: rpm-guide-using-rpm-en.xml =================================================================== RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- rpm-guide-using-rpm-en.xml 26 Oct 2005 01:54:11 -0000 1.2 +++ rpm-guide-using-rpm-en.xml 31 Oct 2005 23:18:20 -0000 1.3 @@ -754,7 +754,7 @@ packages are obviously interrelated. From the name eruby-libs, you can guess that the package will be in a file with a name like eruby-libs-0.9.8-2.i386.rpm. (I cheated and used the - actual package on the Red Hat installation CDs.) + actual package on the &RH; installation CDs.) </para> <para> But you can see how the version numbers of the two files, and @@ -971,10 +971,10 @@ </para> <para> Note that when you purchase an upgraded version of Linux, such - as Red Hat Linux, all the packages with the product should be + as &RHL;, all the packages with the product should be properly aligned with each other as to versions. This alignment problem is an issue that the Linux vendors, such as - Red Hat, need to take care of. The main problems occur when + &RH;, need to take care of. The main problems occur when you need packages beyond those offered with your Linux distribution. </para> @@ -1037,10 +1037,10 @@ </para> <para> The --aid option depends on a separate package that contains - an RPM database with all packages installed. For Red Hat + an RPM database with all packages installed. For &RH; Linux, this package is rpmdb-redhat. This separate database, built as if all packages were installed (all packages that - come with Red Hat Linux in this case), allows the rpm command + come with &RHL; in this case), allows the rpm command to search for which packages would solve dependencies. </para> </sect3> @@ -1973,7 +1973,7 @@ Separate each file name with a colon. </para> <para> - With Red Hat Linux, the default set of initialization files are: + With &RHL;, the default set of initialization files are: </para> <para> /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc