Sallar
RedhatEnterpriseLinux Blog
How to Removing Software /RPM
To remove a package, issue the following
command:
rpm -e
<packagename>
Notice that this time, only <packagename> is used, not the full name of the file used to
install the software. When this command is issued, the RPM database is searched
for the files associated with this package, and they are removed.
If multiple versions of a package are
installed, such as the kernel, the package version can also be specified to
make sure the correct version is removed:
rpm -e
<packagename>-<version>-<release>
How to Updating Software/ RPM
If an RPM package is already installed, it can
be updated to a newer version. With RPM, there isn’t the concept of using a
different file or set of files to perform a software upgrade. The same RPM file
or files used to install a program can be used to update the program as well.
To update to a newer version of a package
already installed:
rpm -Uvh
<packagename>-<version>-<release>.<arch>.rpm
How to Install a New Kernel RPM
There is a -i
argument to RPM to install packages,
but it is more convenient to use –U
when installing and upgrading software
because -U installs or upgrades the package depending on
whether or not it is already installed. However, there is an exception: installing
a new kernel. When installing a new kernel, you should keep the current kernel installed
in case the new kernel does not work with the system’s hardware, does not
perform as well as the current kernel, or causes other problems. When you use
the –U argument
to RPM, the older version of the software package is no longer available.
Installing RPM Package Software
Installing
an RPM package can be done via the command line or a graphical program. Because
some systems such as servers do not always have a graphical desktop installed,
it is important to learn at least the basics of how to use the command-line
version of RPM. The command is simple to remember: It is the rpm
command.
Before
installing any software, confirm that it was packaged by a trusted source and
has not been altered since the trusted source built it. This process is done by
checking the GPG signature of the package.
Subscribe to:
Posts (RSS)
