- Learning Red Hat Linux, 2nd Edition
- Preface
- Organization of This Book
- Sources of Information
- Conventions Used in This Book
- How to Contact Us
- Acknowledgments
- 1. Why Run Linux?
- 2. Preparing to Install Red Hat Linux
- 3. Installing Red Hat Linux
- Installing the Operating System and Applications
- Start the Installation
- Creating a Boot Floppy
- Boot the Installation Program
- Understanding the Installer’s User Interface
- Use Virtual Consoles to Monitor the Installation
- Choose the Installation Language
- Select the Keyboard Type
- Select the Mouse Type
- Select the Installation Type
- Create Partitions
- Configure the Boot Loader
- Configure Networking
- Configure the Language
- Configure the System Clock
- Configure User Accounts and Authentication
- Selecting Packages
- Configure Video
- Installing the Packages
- Create a Boot Floppy
- Complete the Video Configuration
- Complete the Installation
- Logging In
- Getting Help
- 4. How Linux Works
- 5. Using the GNOME Desktop
- 6. Using the KDE Desktop
- 7. Conquering the bash Shell
- 8. Using the RPM Package Manager
- 9. Configuring and Administering Linux
- 10. Connecting to the Internet
- 11. Setting Up a Networked Workstation
- 12. Setting Up Internet Services
- 13. Advanced Shell Usage and Shell Scripts
- A. Linux Directory Tree
- B. Principal Linux Files
- C. Managing the Boot Process
- D. Installing and Configuring X
- E. Linux CommandQuick Reference
- Glossary
- Index
- Colophon
- Preface
This chapter explains the RPM Package Manager (RPM), a tool that facilitates installing, uninstalling, and upgrading software for your Red Hat Linux system. The chapter explains how to use RPM to find the package associated with an application and quickly and easily install the package. It also explains how to use RPM to upgrade packages and query the status of installed packages.
An RPM package (or more simply, an RPM or a package) is a file that contains executable programs, scripts, documentation, and other files needed by an application or software unit. RPM packages are generally named using a convention that lets you determine the name of the package, the version of the software, the release number of the software, and the system architecture for which the application is intended. Figure 8-1 shows how the components of a package name are arranged.
-
No Comment