RPMs aren’t just for automotive aficionados. They're also Red Hat’s answer to the establishment’s EXE files.
Linux 101 installments are intended to bring IT professionals unacquainted with Linux up to speed quickly on the alternative operating system's more basic features and uses.
Like many Linux commands and applications, RPM accepts arguments and flags, adding to its usefulness. These arguments (like many Linux arguments) dictate to RPM the nature of the request made—allowing user modification and control.
With the above arguments, there can be a great many variations. For example, you can install with verbose output only using the -Iv combination, or you can upgrade with both verbose information and hash marks using -Uvh. (We'll look at the U argument in a minute.)
With the arguments in this short list, you can install with a command similar to this one:
RPM -ivh this_package-1.1.RPMwhich would install this_package-1.1 with verbose output and hash marks indicating the installation's progress.
RPM -q this_packagewould report the following information:
this_package-1.1.
Should you want to upgrade this_package-1.1 to this_package-1.2, run RPM with the upgrade argument like this:
RPM -Uvh this_package-1.2
Upgrading with RPM allows you to extend the verbose and hash arguments as if installing.
The complete command looks like this:
RPM -e this_package
The Red Hat Package Management system is a well-designed, fully functional, user-friendly method of managing applications and programs within the Linux environment. The RPM technology was unique to Red Hat Linux, but it is also now used with many other distributions, such as Mandrake, Caldera, and SuSE.
If you'd like to share your opinion, please post a comment at the bottom of this page.