What is .rpm? — CompTIA Definition

Overview

RPM stands for RedHat Package Manager and is one of the most widely used package management systems in the Linux ecosystem. The .rpm file format is a standardized way to distribute, install, and manage software on RPM-based Linux distributions such as RedHat Enterprise Linux (RHEL), CentOS, Fedora, and openSUSE. RPM simplifies software management by handling dependencies, version control, and system integration automatically.

How RPM Works

An RPM file is a binary archive that contains:

Compiled binaries – The executable program files ready to run on the target system
Configuration files – Default settings and initialization files for the application
Documentation – Man pages, README files, and help documentation
Metadata – Package information including name, version, dependencies, architecture, and checksums
Installation scripts – Pre-installation and post-installation scripts that execute during package setup

When an RPM package is installed, the package manager reads the metadata, checks for dependencies, verifies digital signatures, and extracts files to their designated locations on the filesystem. The system maintains a database of all installed packages, enabling users to query, update, or remove software with a single command.

RPM File Naming Convention

RPM filenames follow a standardized format: name-version-release.architecture.rpm

For example: httpd-2.4.37-43.el8.x86_64.rpm

name – Package name (httpd)
version – Software version (2.4.37)
release – RPM release number and distribution tag (43.el8)
architecture – Target processor architecture: x86_64, i686, aarch64, ppc64le, etc.

Key Components and Concepts

Dependency Management

RPM handles package dependencies automatically. When installing a package, the system checks if required libraries or other packages are already installed. If dependencies are missing, the package manager can either warn the user or automatically fetch and install them, depending on the tool used (yum or dnf).

Digital Signatures and Verification

RPM packages can be digitally signed using GPG keys to verify authenticity and integrity. Before installation, the system can validate that the package comes from a trusted source and hasn't been tampered with. This is critical for security in production environments.

Version and Release Numbers

The version number indicates the upstream software version, while the release number tracks RPM-specific iterations. A single software version may have multiple RPM releases as maintainers make packaging improvements or security patches.

Architecture-Specific Packages

RPM files are compiled for specific processor architectures. Installing the wrong architecture (trying to install a 32-bit package on a 64-bit system) will fail. The noarch (no architecture) designation is used for packages containing only scripts or platform-independent content.

Working with RPM Files

Installation

RPM packages can be installed using command-line tools:

rpm -i package.rpm – Install a package
rpm -U package.rpm – Upgrade an existing package
rpm -F package.rpm – Freshen (upgrade only if already installed)

Higher-level tools like yum and dnf provide dependency resolution and access to configured repositories.

Querying Installed Packages

Users can query the RPM database to find installed software:

rpm -qa – List all installed packages
rpm -qi package-name – Show detailed information about a specific package
rpm -ql package-name – List all files installed by a package

Removal

rpm -e package-name removes a package, with options to check for dependent packages that would break.

RPM-Based Distributions

Major Linux distributions using RPM include:

RedHat Enterprise Linux (RHEL) – Commercial, enterprise-focused distribution
CentOS/Rocky Linux – Free, community-supported RHEL alternatives
Fedora – Community-driven, cutting-edge distribution
openSUSE – Community-supported distribution with its own variant called Zypper
Amazon Linux – AWS's custom RPM-based distribution

RPM vs Other Package Managers

Different Linux families use different package managers. Debian-based systems (Ubuntu, Debian) use DEB packages and apt/dpkg tools. Alpine uses APK packages. Understanding which package format your distribution uses is essential for system administration. RPM is particularly dominant in enterprise Linux environments, making it critical knowledge for infrastructure professionals.

Best Practices

Verify GPG signatures before installing packages from external sources
Use dependency-aware tools like yum or dnf rather than raw rpm commands in production
Maintain updated package repositories to access security patches and bug fixes
Understand package conflicts before forcing installation with the --force flag
Keep backups of critical configurations in case package updates overwrite custom settings
Test updates in non-production before deploying to critical systems

Common Use Cases

System Administration: Installing and managing server software, libraries, and utilities across enterprise Linux deployments.

Software Distribution: Developers package applications as RPMs to simplify deployment for end users.

Patch Management: Security updates and bug fixes are distributed as RPM updates through configured repositories.

Dependency Resolution: Complex applications requiring multiple libraries can be packaged with all dependencies automatically managed.

Example Workflow

A system administrator needs to install Apache web server on a CentOS system. Rather than downloading and compiling from source, they use: yum install httpd. The yum tool queries its configured repositories, finds the latest httpd RPM package, checks dependencies (like openssl and apr), downloads all necessary packages, verifies signatures, and installs them. The system database is updated, and the service can be started immediately.