May 23, 2021 That's what Linux should learn
Prior to the release of RPM (Red Hat Package Manager), software to install in a Linux system could only be installed as a source package. E arly installation of programs in Linux systems is a very difficult and patient thing, and most service programs only provide source code, require operators to compile their own code and solve many software dependencies, so to install a service program, operations personnel need to have a wealth of knowledge, skills, and even good patience. And in the installation, upgrade, uninstall service programs should also take into account the dependencies of other programs, libraries, so in the verification, installation, uninstall, query, upgrade and other management software operations are very difficult.
The RPM mechanism is designed to address these issues. R PM is a bit like a control panel in a Windows system, created a unified database file that records software information in detail and automatically analyzes dependencies. T he advantages of RPM are now recognized by the public and are not limited to Red Hat systems. Table 1-1 is a commonly used RPM package command that currently does not need to be remembered, and a rough mix of "face familiarity" is sufficient.
Table 1-1 Common RPM package commands
The command format rpm -ivh filename for installing the .rpm
Upgrade the command format of the software rpm -Uvh filename .rpm
Uninstall the software's command format rpm -e filename .rpm
The command format rpm -qpi filename for querying software description information .rpm
The command format rpm -qpl filename, which lists the software file information.rpm
The query file belongs to which RPM command format rpm -qf filename belongs