.rpm files; DNF operates on top of RPM and resolves dependencies automatically.

DNF commands generally require root privileges — prepend
sudo or run as root when performing installs, updates, or removals.RPM vs DNF — quick comparison
Common DNF operations (cheat sheet)
Searching for packages
Usednf search to locate packages in enabled repositories. It performs word-based matching by default:
web or server. Example output might include:
Installing, reinstalling, and removing packages
Install a package from enabled repositories:.rpm file, prefer installing it with DNF so dependencies are resolved for you:
dnf autoremove to purge orphaned dependencies that are no longer required:
Checking for updates and applying them
Check for available updates without applying them:Reboot after kernel updates or other critical system updates when prompted to ensure the running system uses the new components.
Listing packages
List all packages (installed and available from enabled repos):dnf list output (truncated):
Example: Installing and removing Apache HTTP Server (httpd)
Search to verify the package is available:dnf info output:
httpd is up-to-date, running an update will indicate there is nothing to do:
Managing package groups
DNF supports installing/removing predefined groups (environment groups and comps). This is useful for installing a set of related packages like container toolchains, development environments, or server roles. List groups:Summary
DNF is the recommended day-to-day package manager for Red Hat–based systems. It:- Installs and removes packages from repositories.
- Resolves and installs dependencies automatically.
- Updates packages and the system.
- Manages predefined package groups.
- Uses RPM under the hood to perform low-level package operations.