Configuration·LPIC-1
Repositories, and verifying what is installed
A package manager is only as good as the sources it reads, and only useful if you can tell whether what it installed is still what is on disk. This guide shows where both families configure repositories - including Debian's newer deb822 format - and then deliberately damages a binary to watch rpm -V catch it.
101: Installation and Packages Guide 7 of 33 Intermediate
- PlatformsUbuntu 26.04 LTS + AlmaLinux 10.2
- TimeAbout 15 min
- RPM packagingrpm 4.19.1.1, dnf 4.20.0
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| LPIC1-A01 | 192.168.0.76 | Ubuntu 26.04 LTS | Debian-family host - dpkg and apt, which objective 102.4 names | 2 Core | 4 GB | 50 GB |
| LPIC1-B01 | 192.168.0.77 | AlmaLinux 10.2 | RPM-family host - rpm and dnf, which objective 102.5 names | 2 Core | 4 GB | 50 GB |
This guide includes
Use this because a package manager is only as good as the sources it reads. This matters because rpm -V compares the disk against the package - so an altered binary can be proved altered, and then proved restored.
- finding where the repositories are configured, in two formats
- proving a package's files are unchanged
- breaking one on purpose, and reading what the check reports
- putting it back with a reinstall
Before you start
- dpkg-and-rpm-the-low-level-tools
-
Where the repositories are configured
-
Proving a package's files are unchanged
-
Now break it on purpose
-
Putting it back