• Updating the scrollkeeper database: If an .omf file is being installed, the scrollkeeper database (used to index docbook documentation) needs to be updated:

Interaction with urpmi and rpmdrake

Sometimes it"s necessary to warn the user about some particular care that should be taken when upgrading or installing a specific version of a package. rpmdrake-2.1.3-11mdk and above supports this: it searches in rpms for text files named README. install.urpmi , README.update.urpmi or README.urpmi , and displays them.

README.install.urpmi is displayed only for installed packages; README.update.urpmi only for upgraded packages; README.urpmi is displayed in both cases.

ROSA Package Groups

Each package must belong to one of the RPM groups used by ROSA.

Licenses

For questions regarding licenses for packaged software, please refer to the Licensing policy .

Alternative: check install

A very easy way to build RPMs for personal use is to install the checkinstall package; compile from source as usual (./configure && make && sudo make install), but just replace the make install step by checkinstall . This automates building an RPM, and is very simple to use. The advantage is that you don't ever have to bypass the package manager when compiling from source. (However, it's probably A Good Idea to build RPMs "properly" as described above, if you intend to distribute them to others.)

When a buyer tries to assemble a computer from components on his own or simply choose a hard drive for a PC, he often encounters the concept of "RPM". What is it and is it important? RPM is not just important, but one of the key parameters of a hard drive that must be considered first of all when choosing. Let's take a closer look at what RPM is.

concept

The abbreviation RPM (Rounds per minute) literally translates into Russian as "Revolutions per minute". This unit denotes a hard drive, but the concept itself does not say anything to the average user. The RPM of a hard drive plays a role in system performance, and the higher the rotation speed, the faster the entire system will work. Most often, this parameter is indicated in the characteristics of the hard drive, and between two hard drives it is advisable to choose the one with the higher RPM.

If you take two disks that are identical in all respects, but with different spindle speeds, you can immediately notice a significant difference in system performance.

What is a spindle?

A hard drive consists of several sealed round platters that are stacked on top of each other and covered with a layer of ferromagnetic material. There is also a reading head in the housing. These plates rotate during operation using a spindle - a special rotating shaft. This shaft is driven by an electric motor. When the plates rotate, the reading heads do not touch the surface of the discs, but are located as close as possible to them. As a result, with the help of the heads it is possible to write and read information from solid media - disks.

For thousands of hours, the spindle stably rotates the plates at a tremendous speed, so this element must be reliable. Due to the absence of direct physical contact between the spindle and the disk, information can be written and erased on the latter. It is believed that on average one disk can be written and erased information 100 thousand times.

This is what the hard drive spindles look like. Of course, they may differ depending on the device model and manufacturer.

So, we found out that this is RPM. The parameter determines at what speed the plates can rotate during normal operation. In turn, this allows you to understand how quickly the computer system can get information from the hard disk when accessing it. The higher the speed, the faster the data exchange between the system and the disk will be.

How it works?

To understand more precisely what it is - RPM, you need to understand the principle of operation of the device itself. When certain information is requested, the head unit jumps to the requested track. This requires a certain time to search (Seek latency). After the reading heads move to the desired sector, it is necessary to wait for the discs to rotate so that the desired area is under the reading head. This period of time is called the rotation delay. It is this parameter that depends on the speed of rotation of the spindle, and the higher it is, the lower the delay for rotation.

Both delays (for spindle movement and disk rotation) determine the speed of system access to data. Many benchmark programs calculate this parameter and display it below the "Access to data time" lines. This allows you to determine the actual speed of the disk. This parameter directly affects the performance of the entire system. Today there are many powerful laptops that are equipped with powerful graphics cards and processors, a large amount of RAM. But at the same time, together with good hardware, very slow hard drives with a rotation speed of 5400 rpm are used. As a result, all these powerful components do not work at full capacity due to the slow speed of data access. So the RPM of the disk is important on a par with the frequency of the processor and the bus width of the video card.

Impact of RPM HDD on performance

Winchesters (as hard drives are often called) can be in LFF and SFF formats. To put it simply, one type of disk has a 2.5-inch format, the other has a 3.5-inch format. The first is often used in laptops and servers, the second - in conventional system units. It is this type of hard drive that most often has a high spindle speed - 7200 rpm. In such models, the half-turn time is 4.2 ms, and the average seek time is 8.5 ms. Therefore, the data access time will be 12.7 ms.

Note that most desktop computers use SATA hard drives. 7200 RPM is the standard speed for these models. There are also 5400 RPM drives, but they are not recommended for use on modern systems, although they are cheaper. There are also 10000 RPM discs - in such models, search and rotation delays are about 3 ms. Such devices are most often used on gaming computers, but even they can be called outdated. Modern desktop PCs and laptops are increasingly using SSD drives, which work in a completely different way. We will talk about this a little later.

Non-standard RPM setting

There are also models on the market with a spindle speed of 15,000 rpm. As you may have guessed, the latency is even lower there - about 2 ms, and the average seek time is 3.8 ms. This allows you to provide access to data in 5.8 ms. Therefore, disks with a large RPM have a low search time for the desired information, thereby ensuring a fast exchange between the information store and the system.

However, it is important to note that when accessing large data, the performance difference between disks with high and low RPM parameters will not be significant, since there will be no information access delays at all.

How to know the spindle speed?

Determining this parameter is as easy as shelling pears - it is always indicated on a sticker on the device itself. It is enough to open the case of your system unit and look at the sticker. There may be many obscure options, but there is always one of the following lines:

1. RPM HDD: 5400.
2. RPM: 7200
3. RPM: 10000

If the hard drive is hidden under the laptop case, which is quite difficult to open, then you can use a special hardware testing program.

The following are popular:

1. crystalmark.
2. Aida64.
3. Speccy.

They are available for download from the Internet for free. By running one of these programs, you can quickly find information about the storage device. There will be displayed in detail the parameters of the hard disk. We are primarily interested in the "Rotation Rate" line and the value opposite it. In the Russian version of the Aida64 program, on the left side, click on "Data storage" - "Windows data storage", then in the upper part you need to select the hard drive, after which information about it will appear below, including the line "Rotational speed".

Disadvantages of high speed

Of course, with a high RPM, the performance of the system as a whole is ensured, but there are also disadvantages. The faster the spindle rotates, the more the disk itself heats up, and it works noisier. Also, such hard drives consume more electricity. However, modern technology makes it possible to set the RPM and reduce power consumption and noise by reducing the spindle speed. In this case, performance losses are compensated by a special data caching algorithm.

SSD as an alternative

In the development of modern computer platforms, the use of hard drives with platters and a spindle is abandoned. Today, solid-state drives are used, in which there are no moving parts at all. The "innards" of these drives are microcircuits on the board. Such devices work like ordinary flash drives, but the performance and data access speed in them is very high and far exceeds the performance of HDD standard disks. In addition, they do not make noise, are very light and consume little energy. The high price is the only drawback. 7200 RPM at 1 TB will cost less than a 128 or 256 GB SSD.

If we draw an analogy, then the difference between an SSD and an HDD is about the same as the difference between a regular DVD and a flash drive. They have already moved away from disks, and today only flash drives are mainly used.

Conclusion

When choosing a hard drive in the first place, it is important to consider the performance parameter, which is determined by the spindle speed in the first place. Unfortunately, most users look at disk capacity, although this is not the most important thing. It is better to give preference to a hard drive with a capacity of 500 GB and a spindle speed of 7200 rpm than to choose a 1 TB drive with an RPM 5400 parameter. In general, today we need to move away from using such systems, since SSD drives are superior to outdated HDD devices in everything .

*.RPM - files similar to Windows SFX archives and installers.
As a rule, they contain collected source texts of programs that are easy to edit.
The source code of the package itself is assembled with the .SRPM extension at the user's command.

Operations with packages from the console are performed by the RPM command.
I remind you:
help can be obtained by typing "rpm --help" or "rpm -?"; and the detailed manual is "man rpm"
(to exit the manual and return to the terminal, you need to press "q" ).

Here it is proposed to familiarize yourself first with the description of the programs themselves for installing packages
(the main one is rpm) followed by a list of commands and options for that program.

On the Linux operating system, there are three ways to install software:

• Traditional.
• From RPM packages.
• From packages containing source code.

Let's take a look at all three methods.

This method lies in the fact that the program is distributed not in assembled form, but in the form of source texts. This method is called traditional because it was the first way to install software before RPM or similar (apt-get) came along.

Usually, source text distributed in the archive. Usually the file containing the source text has a double extension: for example, tar.gz or tar.bz2. This means that this file is compressed by two archivers: first tar and then gzip.

You need to unpack the archive according to the stack principle: first with an external archiver, and then with an internal one. Let's assume that prg-2.00.tar.gz is the filename of our archive. To unpack it, you need to enter the commands:

gunzip prg-2.00.tar.gz
tar xvf prg-2.00.tar

The first command will unpack the prg-2.00.tar file, which we will specify as one of the arguments in the second command. The x option of the tar program means that we need to extract the files from the archive (the c option is create). You can specify the v parameter at your own discretion, it provides more information when the program is running.
The last parameter f is required when working with files.
The tar program was originally designed to work with tape tapes, so we need to use the f option to tell the program that we need to work with files.
If the external extension is not gz, but bz or bz2, then instead of the first command you need to enter the commands (respectively):

bunzip prg-2.00.tar.bz
bunzip2 prg-2.00.tar.bz2

Then, as in the first case, you need to run the tar command (with the same parameters).

Sometimes source files have only one tgz extension. In this case, you only need to enter one command:

tar xzf prg-2.00.tgz

The z option means extracting files using the gzunzip unpacker. This extension is usually given to archive files created with the tar program and passed through the gzip archiver's filter.

The next step is the actual installation of the program. After the successful completion of the first stage (unpacking), go to the directory containing the source texts. This is usually a directory<имя_программы-версия>:

cd prg-2.00

. /configure
make
make install

The first command configures the installer to work with your system. This program also checks if the program being installed can run on your system. If the program is not possible,
you will see a corresponding message and the installation process will be interrupted.

This usually happens when one of the libraries required by the new program is not installed on your system. To continue with the installation, you must install the required library and try re-typing the ./configure command. After successful completion of the ./configure program, a Makefile will be created, which will contain the necessary parameters (paths to libraries, path to install the program) for the make program.

The second command (make) "builds" the program. At this stage, the program is compiled, that is, binary executable files are created from source texts.

The third command, make install, installs the program and help files in the appropriate directories. Programs are usually installed in the /usr/bin directory, but this depends on the contents of the Makefile configuration file.

After the program has been successfully installed, you can run it after reading the documentation for this program.

Software installation on Red Hat and Mandrake distributions is done using the rpm program. RPM (Red Hat Package Manager) is Red Hat's package manager. Although it has "Red Hat" in the name, it is fully intended to operate as an open packaging system available for anyone to use. It allows users to take the source code for new software and package it in source and binary form so that the binaries can be easily installed and tracked and the source code is easily
built. This system also maintains a database of all packages and their files, which can be used to check packages and query information about files and/or packages.

Unlike the familiar InstallShield wizards that are used to install programs for Windows, RPM packages (files with the .rpm extension) are not executable files, that is, programs. Packages contain files (as in an archive) that need to be installed, as well as various information about this package: which package is required for this package to work, which package conflicts with, information about the developer, as well as information indicating what actions to take when installing this package, such as which directories to create. The RPM package manager is used in many Linux distributions(Red Hat, Mandrake, ASP, Black Cat) and is quite easy and flexible to use, which makes it popular.

For example, for the package software-1.0-I.i386.rpm the following takes place: software - name;

1.0 - program version;
1 - package release;
i386 - Intel 386 platform.

Usually, the package file name contains its name, version, release, platform. The last four characters - ".rpm" - an indication that this file is a package. Linux has no such thing as an extension or file type.

Note the difference between the software version and package release. The version indicated in the package name is the version of the software contained in it. The version number is set by the program's author, who is usually not the package's manufacturer.
The version number characterizes and refers to the software. As for the release number, it characterizes the package itself - it indicates the number of the existing version of the package. In some cases, even if not changed software may need to be repackaged.

With the name and version of the program, I think everything is clear. But the architecture is a little more complicated. The most "universal" packages are packages designed for the Intel 386 architecture. This program should
run on any Intel processor starting with 80386DX (or compatible). But if you have an 80486 processor, a package designed to work with the 80586 architecture (Pentium) will most likely not install on your system.
Typically, the following designations are used for CISC architecture processors (with the x86 instruction set):

i386 - Intel 80368DX;
i586 - Intel Pentium (MMX), AMD K5 (K6);
i686 - Intel PPro, Celeron, PII, RSH, PIV.

In the simplest case, the package installation command looks like this:

rpm -i<пакет>

Before installing a program, RPM will check the package's dependencies, that is, whether you have other packages installed on your system that the new program needs or conflicts with. If all required
packages (or the program does not need any additional packages at all), and also, if the new program does not conflict with any already installed package, the RPM manager will install the program.
Otherwise, you will receive a message that the program needs some additional package to work, or the program conflicts with an already installed package.

If you need an additional package, just install it. But if the program conflicts with an already installed package, then you will need to choose which package you need more: already installed or new.

When installing the program, I recommend specifying two additional parameters: h and v. The first tells the program to display a status bar for the installation process, and the second displays additional messages. The status bar will be displayed as # symbols. Given these two parameters, the installation command becomes a little more complicated:

rpm -ihv software-1.0-1.i386.rpm

Installation can be performed not only from a local disk, but also via FTP:

To remove a package, use the command:

rpm -e<пакет>

Once again, remember that when installing or removing packages, keep in mind that some packages may require other packages to be present on the system - this is called a package dependency. Therefore, sometimes you won't be able to install a certain package until you have installed all the packages that are required for it to work. When uninstalling a program, the package manager also checks for dependencies between packages. If the package being removed is needed by some other packages, you will not be able to remove it.

To skip dependency checking, use the --nodeps option.
This is sometimes useful. For example, you have postfix installed and you need to install sendmail. Both programs are used to send mail.

However, many mail programs require an MTA agent (Mail Transfer Agent) - a program for sending mail (postfix or sendmail).
Therefore, you cannot uninstall the postfix program using the -e option.
You can't install sendmail without uninstalling postfix either, because the packages conflict with each other. In this case, the command will help you:

rpm -e -nodeps postfix

After such a removal, other programs that need the MTA cannot work normally, so you need to install the sendmail program (or another MTA) right away. In this case, you need to install the program, as usual, using the -i parameter.

The -U option is used to update programs. I recommend using it when installing programs too, because if the package being installed has already been installed, then it will be updated, and if not, it will simply install a new package. To see a text indicator when installing packages, use the h option. Command to update the package:

rpm -Uhv<пакет>

For example:

rpm -Uhv software-1.1-4.i386.rpm

The text indicator will be displayed as # symbols. You can view all installed packages with the command:

rpm -qa I less

If you need to know if a particular package is installed, run the command:

rpm-qa | grep package_name

You can view general information about a package with the command:

rpm -qi package

and information about the files that are included in the package:

rpm -ql package

The RPM package manager is a powerful tool for performing operations on packages - creating, installing, updating, deleting. However, the command line interface may not appeal to everyone, and especially to a novice administrator. There are also graphical (under X Window) implementations of the package manager - for example, kpackage from KDE, gnorpm and others.
I recommend using the gnorpm program, which has an intuitive GUI. RPM is more suitable for creating new packages, as well as updating a large number of packages. For installing one or two packages, it is better and more convenient to use gnorpm.

Functions of the gnorpm program:

Installing packages.
Removing packages.
Get information about a package.
Checking the package.
Search for a package in the RPM database.

To install a package, click the "Install" button. If there is an installation CD in the CD-ROM drive, then in the window that appears you will see a list of packages not yet installed in the system.

If the package is not listed or you want to install a package that is not included in the distribution, click the Add button and add the packages you want to install to the list. Click on the "Inquiry" button to get information about the package.

If the package is not installed yet and you have enough disk space to install it, click on the "Install" button. After that, the package will be checked for dependency satisfaction: does this package require the presence of any uninstalled package and does it conflict with already installed packages. If everything is in order, you will see the package installation status window.

You can find a package using the Search operation. To do this, click on the "Search" button on the gnorpm toolbar or execute the menu command Operations -> Search. In the window that opens, you can set the search criteria and click on the "Search" button.

KDE comes with a graphical user interface program that manages packages, kpackage. Its functions are similar to the gnorpm program. Which of these programs to use is a matter of taste and habit.

Also worth mentioning is the APT program. The APT program is a software package management system. APT was originally developed for Debian Linux. Now included with some Red Hat compatibles
distributions (for example, apt-get and is included with AltLinux, but you will not find it in Red Hat Linux). Apt-get is used to manage packages. The format for invoking the apt-get program is as follows:

apt-get [options] [commands] [package. . .]

The Linux distribution Mandrake includes own remedy package management - rpmdrake. By the tenth version of the distribution, it has changed a bit. Now it consists of three parts:

/usr/sbin/edit-urpm-media - package source manager (I have already said what sources are, so we will not dwell on this);
rpmdrake - package manager;
rpmdrake-remove is a package removal manager.
You can launch any of the parts from the K menu: System | Setting | Packages.

Sometimes RPM packages do not contain compiled versions of programs, but their source code. This is indicated by the word src instead of the name of the architecture. To install such a package, enter:

rpm --rebuild software-2.00-1.src.rpm

Of course, instead of software-2.00-l.src.rpm, you need to specify the real file name. Before a program is installed, its source code will be compiled and then the program will be installed.

GENERAL OPTIONS.

These options can be used in all operating modes.

"-vv" Output a lot of debug information.

"--quiet" Output as few messages as possible - usually only error messages are displayed.

"--help" Print more detailed than usual help about using rpm.

"--version" Print a single line containing the version number of the rpm used.

"--rcfile<список-файлов>" Each of the files from colon-separated<списка-файлов>rpm is read sequentially for configuration information.
Default<список-файлов>looks like /usr/lib/rpm/rpmrc:/etc/rpmrc:~/.rpmrc.
Only the first row must exist in this list; all tildes will be replaced by the value of $HOME.

"--root<каталог>"Use for all operations file system rooted in<каталог>.
Note that this means that the database will also be read and modified under<каталог>, and all pre and post scripts will be executed after chroot() in<каталог>.

"--dbpath<путь>" Use the RPM database in<путь>.

"--justdb" Update only the database, not the file system.

"--ftpproxy , --httpproxy " Use as an FTP or HTTP proxy.

"--ftpport<порт>, --httpport<порт>" Use<порт>as FTP or HTTP proxy server port.

"--pipe " Redirects rpm output to command input .

Database maintenance:

rpm -i [--initdb]

rpm -i [--rebuilddb]

DATABASE REBUILDING OPTIONS.

The general form of the RPM database rebuild command is:
rpm --rebuilddb
To build a new database:
rpm --initdb
This mode only supports two options, --dbpath and --root.

launch
rpm --showrc
prints out the values ​​that rpm will use for all options that can be set in rpmrc files.

Assembly:
rpm [-b|t] +
rpm [--rebuild] +
rpm [--tarbuild] +

OPTIONS FOR BUILDING (BUILDING) PACKAGES.

The general form of the rpm package build command looks like this:
rpm -O [build-options] +
The -bfR argument is used if a spec file is used to build the package. If rpmfR is to extract this file from a gzip (or compress) archive, the -tfR argument is used. After the first argument, the next (OfR) is specified, indicating which assembly and packaging steps should be performed. This is one of:

"-bp" Execute the "%prep" stage of the spec file. This usually involves unpacking the sources and applying patches to them.

"-bl" Perform "list check". In the "%files" section of the spec file, macros are expanded and the listed files are checked for existence.

"-bc" Execute the "%build" stage of the spec file (after executing the %prep stage). It usually boils down to doing some equivalent of "make".

"-bi" Execute the "%install" stage of the spec file (after executing the %prep and %build stages). It usually boils down to doing some equivalent
"make install".

"-bb" Build a binary package (previously executing the %prep, %build and %install stages).

"-bs" Build only the source package (after running the %prep, %build and %install stages).

"-ba" Build binary (RPM) and source (SRPM) packages (after running %prep, %build and %install stages).

The following options can also be used:

"--short-circuit" Execute the specified stage directly, skipping the previous ones. Can only be used with -bc and -bi.

"--timecheck" Set age for "timecheck" (0 to disable). This value can also be set by defining the "_timecheck" macro.
The timecheck value determines the maximum age (in seconds) of files to be packaged. All files older than this age will be warned.

"--clean" Remove the build tree after the packages have been built.

"--rmsource" Remove sources and spec file after build (can be used separately, eg "rpm --rmsource foo.spec").

"--test" Do not execute any build steps. Useful for testing spec files.

"--sign" Embed a PGP signature in the package. This signature can be used to verify the integrity and origin of the package. See section
PGP SIGNATURES for PGP options.

"--buildroot<каталог>" Use directory<каталог>as the root for building packages.

"--target<платформа>" When building a package, interpret<платформа>as arch-vendor-os
and set the _target, _target_arch and _target_os macros accordingly.

"--buildarch " Build package for architecture regardless of architecture
build system. This option is deprecated, in RPM 3.0 the --target option should be used instead.

"--buildos " Build a package for the operating system ignoring
the architecture of the system on which the assembly is performed. This option is deprecated, in RPM 3.0 the --target option should be used instead.

REBUILD AND RECOMPILATE OPTIONS.

There are two other ways to start rpm:

rpm --recompile<файл_исходного_пакета>+"

rpm --rebuild<файл_исходного_пакета>+"

When called in this way, rpm installs the specified source package and executes %prep, %build, and %install. In addition, --rebuild builds a new binary package. After the build is complete, the tree used for the build is removed (as with the --clean option), the sources themselves, and the spec file.

SIGNATURE EXISTING RPM.

rpm --resign<файл_бинарного_пакета>+ This option generates and inserts new signatures into the specified packages.
All existing signatures from packages are removed.

rpm --addsign<файл_бинарного_пакета>+ This option generates and adds new signatures to the specified packages.
All existing package signatures are preserved.

PGP SIGNATURES.

In order to use the signing feature, rpm must be configured to run PGP and must be able to find a public key ring with an RPM key in it. By default, rpm uses the PGP defaults to find keyrings (observing PGPPATH).
If your key rings are not located where PGP expects them to be, you must set the "_pgp_path" macro to the directory containing your key rings.

If you want to be able to sign the packages you create, you also need to create your own public/private key pair (see the PGP documentation). In addition to the above macro, you also need to configure the macros

"_signature" Signature type. Currently only pgp is supported.

"_pgp_name" The name of the "user", whose keys you want to use to sign your packages.

When building packages, you add to command line the --sign option. You will be asked for a password and your package will be assembled and signed.

For example, in order to use PGP to sign packages as the user "John Doe " from key rings located in /etc/rpm/.pgp, you must include

"%_signature"
pgp
"%_pgp_name"
/etc/rpm/.pgp
"%_pgp_name"
John Doe "

in the macro configuration file. Use /etc/rpm/macros for system wide and ~/.rpmmacros for user configuration.

Maintenance of installed packages:

rpm [--install] [install-options] [package-file]+
rpm [--eshen|-F] [install-options] [package-file]+
rpm [--uninstall|-e] [uninstall-options] [package]+
rpm [--verify|-V] [verify-options] [package]+

INSTALLATION AND UPDATE OPTIONS.

The general form of the rpm install command looks like this:
rpm -i [install-options]<файл_пакета>+
This command installs new packages.

The general form of the rpm update command looks like this:
rpm -U [install-options]<файл_пакета>+
This command updates installed packages. This command works exactly like the install command, except that all other package versions are removed from the system.

rpm [-F|--eshen] [install-options]<файл_пакета>+
Such a command updates packages, but only if earlier versions of those packages exist on the system.
Job allowed<файл_пакета>as ftp or http style URL. In this case, before installation, the file will be obtained from the server specified in the URL.

"--force" Same as a combination of --replacepkgs, --replacefiles, and --oldpackage.

"-h, --hash" Display 50 "#" characters as the archive with the package is unpacked. Used with -v for prettierness.

"--oldpackage" Allows you to replace a new package with an older one when upgrading (roll back).

"--percent" Display the percentage of completion as the archive with the package is unpacked. Designed to make it easier to use rpm from other utilities.

"--replacefiles" Install packages even if they overwrite files from other already installed packages.

"--replacepkgs" Install packages even if some of them are already installed on the system.

"--allfiles" Install or update all files specified as "missingok", even if they already exist.

"--nodeps" Don't check dependencies before installing or updating a package.

"--noscripts" Do not execute pre- and post-installation scripts.

"--notriggers" Do not execute trigger scripts set to install this package.

"--ignoresize" Don't check the file system for enough free space before installing this package.

"--excludepath<путь>"Do not install files whose names begin with<путь>.

"--excludedocs" Do not install any files marked as documentation files (includes manuals and texinfo documents).

"--includedocs" Install documentation files. This is the default behavior.

"--test" Don't install the package, just test the installability and report any problems.

"--ignorearch" Install or upgrade even if the architectures of the binary RPM and the machine do not match.

"--ignoreos" Install or upgrade even if the operating systems of the binary RPM and the machine do not match.

"--prefix<путь>" Set installation prefix to<путь>for relocatable packages.

"--relocate<старый_путь>=<новый_путь>" For relocatable packages: converts files that should have been installed to<старый_путь>in<новый_путь>.

"--badreloc" For use with --relocate. Performs a relocation even if the package is not relocatable.

"--noorder" Do not reorder the list of packages to be installed. Usually the list is reordered to satisfy dependencies.

Request:
rpm [--query] [query-options]
rpm [--querytags]

REQUEST OPTIONS.

The general form of the rpm query (inspection) command looks like this:
rpm -q [query-options]
You can set the format in which information about the package will be displayed. This is done using the --queryformat option followed by a format string.

Request formats are a modified version of the standard printf(3) formatting. The format consists of static strings (which may include standard C escape sequences for newlines, tabs, and other special characters) and formats like those used in printf(3). Since rpm already knows the types of the data to be output, the type specifiers must be omitted and replaced by the tag names (keys) of the headers to be output, enclosed in (). The RPMTAG_ part of the tag name may be omitted.

Alternate output formats can be specified by adding :typetag to the tag name. The currently supported types are octal, date, shescape, perms, fflags, and depflags.

For example, to display only the names of loaded packages, you can use %(NAME) as a format string. You can use %-30(NAME)%(DISTRIBUTION) to display package names and distribution information in two columns.

When run with the --querytags argument, rpm will list all the tags it knows about.

There are two sets of options for a query - package selection and information selection.

Package selection options:

"<название_пакета>" Requesting an installed package called<название_пакета>.

"-a, --all" Query all installed packages.

"--whatrequires " Query all packages that require for proper functioning.

"--whatprovides " Query all packages that provide service.

"-f<файл>, --file<файл>" Request the package that owns a file<файл>.

"-g<группа>, --group<группа>" Request packages from a group<группа>.

"-p<файл_пакета>" Requesting an (uninstalled) package<файл_пакета>.
File<файл_пакета>can be given as ftp or http style URL; in this case, the package header will be retrieved from the specified server.

"--specfile "Parse and Query as if it were a package. While not all information (such as file lists) is available, this type of query allows rpm to be used to extract information from spec files without having to write a spec file parser.

"--querybynumber " Query directly database entry number . Useful for debugging purposes.

"--triggeredby<имя_пакета>" Query all packages containing trigger scripts activated by the package<имя_пакета>.

Information selection options:

"-i"
Displays information about the package, including name, version, and description. Uses --queryformat if one is given.

"-R, --requires" Print a list of packages that this package depends on.

"--provides" Lists the services and libraries provided by this package.

"--changelog" Displays the change log for this package.

"-l, --list" Displays a list of files included in the given package.

"-s, --state" Print the state of the files in the package (implies -l).

Each file can be in one of the following states: normal, not installed, or replaced.

"-d, --docfiles" List only documentation files (implies -l).

"-c, --configfiles" List configuration files only (implies -l).

"--scripts" Output package-specific scripts used as part of the install/uninstall processes, if any.

"--triggers, --triggerscripts" Show all trigger scripts, if any, contained in the package.

"--dump" Dump file information like this: path size mtime md5sum mode owner group isconfig isdoc rdev symlink.
This option must be used in conjunction with at least one of -l, -c, -d.

"--last" Orders the list of packages by installation time, with the most recent packages at the top of the list.

"--filesbypkg" Shows all files in each package.

"--triggerscripts" Shows all trigger scripts for the selected packages.

VERIFICATION OPTIONS.

The general form of the rpm verification command looks like this:
rpm -V|-y|--verify [verify-options]
During the package verification process, information about the package's installed files is compared with information from the original package and from the RPM database. Verification checks the size, MD5 checksum, permissions, type, owner, and group of each file, among others. All discrepancies are reported. The options for selecting packages are the same as for requesting (inspecting) packages.

Files that were not installed from the package (for example, documentation files that were excluded from the installation process with the "--excludedocs" option) are silently ignored.

Options that can be used in the verification process:

"--nofiles" Ignore missing files.

"--nomd5" Ignore MD5 checksum errors.
"--nopgp" Ignore PGP signing errors.

The output format is an eight-character string, possibly a "c" indicating a configuration file, and the file name. Each of the eight characters represents the result of comparing one of the file's attributes with the value stored in the RPM database. The dot indicates that the test passed. The following symbols indicate some test errors:

"5" MD5 checksum.

"S" File size.

"L" Symlink.

"T" Modification time.

"D" device.

"U" Owner.

"G" Group.

"M" Permissions (includes permissions and file type).

SIGNATURE VERIFICATION

The general form of the RPM signature verification command looks like this:
rpm --checksig<файл_с_пакетом>+
This command verifies the PGP signature embedded in the package to verify the integrity and origin of the package.
PGP configuration information is read from configuration files. See the PGP SIGNING section for more details.

UNINSTALLATION OPTIONS

The general form of the rpm uninstall command looks like this:
rpm -e<название_пакета>+

"--allmatches" Remove all versions of a package that match<название_пакета>Usually if<название_пакета>responds to multiple packets, issued
error message and deletion is not performed.

"--noscripts" Do not execute pre- and post-installation scripts.

"--notriggers" Do not execute trigger scripts set to remove this package.

"--nodeps" Don't check dependencies before removing packages.

"--test" Don't delete, just pretend :) Useful in combination with the -vv option.

Miscellaneous:
rpm [--showrc]
rpm [--setperms] [package]+
rpm [--setgids] [package]+

FTP/HTTP OPTIONS.

rpm contains simple FTP clients and HTTP to make it easier to install and explore packages available over the Internet. Package files to install,
updates and requests can be specified as ftp or http style URLs:
ftp:// :@hostname: /path/to/package.rpm
If part Omitted, the password will be prompted (once for each user/hostname pair). If neither , nor Not specified, anonymous ftp will be used. Passive (PASV) transfer over FTP is used in all cases.

Rpm allows you to use the following options with ftp URLs:

"--ftpproxy " System will be used as a proxy for all transfers, allowing FTP connections to be made through a firewall that uses the proxy to reach the outside world. This option can also be set by setting the _ftpproxy macro.

"--ftpport " Specifies the TCP port number to use for FTP connections instead of the default port.
This option can also be set by setting the _ftpport macro.

Rpm allows you to use the following options with http URLs:

"--httpproxy " System will be used as a proxy for all forwarding, allowing HTTP connections to be made through a firewall that uses the proxy to reach the outside world. This option can also be set by setting the _httpproxy macro.

"--httpport " Specifies the TCP port number to use for HTTP connections instead of the default port.
This option can also be specified by setting the _httpport macro.

Prepared by Dvoe4nik85

Sooner or later, we have to install software from non-official repositories. Not all packages are there, and not always there are the newest versions of newly released programs. Very often, developers post packages for the most popular distributions on their official website. Usually these are deb and rpm. The latter is a little less common, but if you're using a Red Hat-based distribution, this is the package format you need. Also on the net you can often find libraries and other components that are not in the repositories in the form of packages.

Previously, we have already considered the installation deb packages in Ubuntu. And in this article, the installation of rpm packages in linux will be analyzed in detail.

RPM or RPM Package Manager is package manager, used in Linux distributions based on Red Hat. The file format of this package manager has the same name.

This format is not very different from the same Deb. You can see their detailed comparison in the article what. Here, I’ll just note that the rpm file is a regular cpio archive that contains the program files themselves, as well as metadata describing where they need to be installed. The database of all installed packages is located in the /var/lib/rpm directory. Of the features, it can be noted that rpm does not support recommended packages, as well as either-or format dependencies.

To manage packages, as well as in Debian systems, there is a console, low-level utility with the same name - rpm. We will consider it further in the article. Different systems use different package managers, for example Red Hat uses Yum, Fedora uses DNF, and OpenSUSE uses zypper, but rpm will work on all of these systems.

Installing RPM Packages on Linux

Let's first look at the syntax of the rpm utility itself:

$ rpm -option mode package

The utility can work in one of the modes:

• -q- request, obtaining information;
• -i- installation;
• -V- checking packages;
• -U- update;
• -e- removal.

Consider only the most interesting program options that we will need in this article:

• -v- show detailed information;
• -h- display status bar;
• --force- perform an action forcibly;
• --nodeps- do not check dependencies;
• --replacefiles- replace all old files with new ones without warning;
• -i- get information about the package;
• -l- list of package files;

Now that you already have an idea how to work with this utility, installing the rpm package on Linux can be considered. The simplest installation command would look like this:

sudo rpm -i packagename.rpm

To work with the command current directory, there must be a folder with the package. Here we set the install mode and pass the package file. Upon successful installation, the utility will not display anything, if an error occurs, you will know about it.

To view more detailed information during the installation process, use the -v option:

sudo rpm -iv packagename.rpm

You can also enable the display of the bar status during the installation process:

sudo rpm -ivh packagename.rpm

To check if a package is installed, we already need to use query mode:

sudo rpm -q packagename

You can also immediately remove the package if it is not needed:

sudo rpm -e packagename

But rpm, like dpkg, has one major drawback. The program cannot resolve dependencies. If the required package does not exist in the system, you will simply receive an error message and the package will not be installed.

For automatic download dependencies during rpm linux installation, you need to use the distribution's package manager. Let's look at a few commands for the most popular RPM distributions. On RedHat and other distributions that use Yum, use this command:

sudo yum --nogpgcheck localinstall packagename.rpm

The first option disables the GPG key check, and the second says that we will install a local package. On Fedora, dnf makes things even easier:

sudo dnf install packagename.rpm

The Zypper package manager and OpenSUSE do just as well:

sudo zypper install packagename.rpm

This is how it is very easy to install rpm with dependencies. But not everyone likes to work in the console, many new users want to use GUI to solve all problems, including this one. Next, we will look at several of these utilities.

Installing RPM file in GUI

If you are using OpenSUSE, this is very easy to do. The YaST universal system configurator, among other things, allows you to install rpm packages. You can do it with file manager by selecting the item context menu for the file, open with Yast or by running the command:

yast2 -i packagename.rpm

On Fedora, you can use the distribution's application manager for the same purpose. There used to be a few more universal utilities to solve this problem, but now they are all outdated.

conclusions

Now you know how to install an rpm file in Linux. In fact, it is very simple and there is even not only one way, but several. Although there are a bit less graphical utilities here than in Ubuntu. But console utilities are completely enough. If you have any questions, ask in the comments!

The most interesting:

Distance from the TV depending on the diagonal ... bad choice ...

How to make a closed VKontakte group How to make a private VKontakte group

How to find out if a mobile phone is being tapped How to find out a mobile phone for wiretapping