dnf Updates and Transaction History
Covers the "install and update software packages" objective and the one dnf feature that can rescue a task: every transaction is logged and most can be undone. It also settles a question worth settling - RHEL 10 has no modularity at all, so the module streams in RHEL 8 and 9 study material do not exist here.
Managing Software Guide 16 of 67 Intermediate
- OSRHEL 10.0
- Kernel6.12.0-55.9.1.el10_0
- dnf4.20.0
- Flatpak1.16.0
- TimeAbout 13 min
dnf update and dnf upgrade are the same command. On this machine the local mirror matches the installed versions, so check-update correctly reports nothing - the exit status is the part to read.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| RHCSA-A01 | 192.168.0.31 | RHEL 10.0 | Practice node (graded) - spare /dev/sda | 2 Core | 4 GB | 50 GB + 15 GB |
This guide includes
Use this when an update has to be checked, applied or undone. This matters because dnf keeps a transaction log you can roll back - and modularity, which older material spends pages on, does not exist on RHEL 10.
- checking for updates, and reading the exit code that says whether any exist
- reading the transaction log
- undoing a transaction
- clearing orphans and the cache
- confirming that modularity does not exist on RHEL 10 at all
Before you start
- A working repository.
- The session installs and removes
treeand clears the dnf cache.
-
Checking for updates
-
The transaction log
-
Undoing a transaction
-
Orphans and the cache
-
Modularity does not exist on RHEL 10