There are three ways to install the software, the first is to install the source code (source installation need to manually install the software, installation directory, you also need to install after compiling), more complicated steps. The second is RPM installation, rpm install a bit like windows system panel, will establish a unified database files, detailed records and information software automatically analyzes the dependencies, but need to manually install the dependent packages, if you rely on when installing a package there are other packages depend on the package, you have to rely on after this package back to the previous installation dependencies installed. Only the successful installation of all dependencies to install the package was originally to be installed. The third is mounted yum, which one is the most convenient installation, can automatically install dependencies. It said more above, in fact, the difference between the rpm and yum is the dependency problem. Let's introduce common package commands.
-
RPM Red Hat Package Manager
-
Yum repositories
A, RPM Red Hat Package Manager
RPM (Red-Hat Package Manager). rpm was originally Red Hat Linux distributions designed to manage the Linux program suite, because it is easy to follow and powerful GPL rules, so popular. Gradually adopted by other distributions. Appear RPM package management, so that Linux is easy to install, upgrade, indirectly, to enhance the applicability of Linux.
format:
rpm [options]
Options:
- A query for all packages.
- B < completion stage > < Kits profiles > + or - T < completion stage > < Kits profiles > + setting completion stage of the packaging kit, kit and specify the file name of the file.
- C configuration profile list only, with parameters to be present " - L" parameter.
- D text file list only, with parameters to be present " - L" parameter.
- E < package file > or - ERASE <package file> delete the specified package.
- f < file > + queries suite has a specified file.
- H, or - listed hash mark kit installation.
- i Display information kit.
- I <Kits file > , or - the install <package file> Install specific software packages.
- L displays a list of files suite.
- the p- < package file > + query specified RPM package file.
- q use inquiry mode, when faced with any problem, rpm command will first ask the user.
- R & lt kit display-related information.
- S file status displays, parameters to be present with " - L" parameter.
- the U- < package file > or - upgrade <package file> specified upgrade kit files.
- V display process execution instruction.
- VV instruction execution process is shown in detail, to facilitate troubleshooting.
- addsign < package file > + specified in the package plus new signature verification.
- AllFiles install all the files.
- allmatches delete files in line with the specified package contains.
- When badreloc error occurs, reconfigure the file.
- buildroot <root> is set to produce kits to be used as the root directory.
- ChangeLog display changes Suite.
- checksig <package file> + signature verification testing of the suite.
- After completion of clean packaging kit, remove the directory created in the packaging process.
- dbpath <Database Directory> is set RPM For storage directory database.
- dump displays the authentication information for each file. This parameter is required with the "-l" parameter.
- When excludedocs mounting kit, not the installation files.
- EXCLUDEPATH <exclude directory> ignores all the files in the specified directory.
- Force forced replacement kit or file.
- ftpproxy <host name or IP address> Specify the FTP proxy server.
- ftpport <communications port> communication port set FTP server or a proxy server.
- Help online help.
- HttpProxy <host name or IP address> Specifies the HTTP proxy server.
-httpport <communications port> HTTP server, or a communication port provided by the proxy server.
- ignorearch kit does not verify the correctness of the configuration profile.
- ignoreos kit does not verify the correctness of the configuration profile.
- does not check whether enough disk space before ignoresize installation.
- When includedocs mounting kit, together with the installation files.
- initdb confirmed the correct database can be used.
- justdb update the database, if not change any files.
- nobulid does not perform any stage of completion.
- nodeps interrelatedness kit does not validate profiles.
- nofiles properties file does not validate.
- nogpg skip all the GPG signature verification.
- nomd5 without using MD5 and a coding size and confirm the correctness of the file.
- nopgp skip all the PGP signature verification.
- Noorder not rearrange the order of installation kit, in order to satisfy its association between each other.
- noscripts not perform any installation Script files.
- notriggers any Script files within the kit package does not execute.
- oldpackage upgrade to an older version of the suite.
- shows the percentage of completion when mounting kit percent.
- pipe <execution instruction> create a channel, the output data into the input execution instruction.
- prefix <destination directory> If re-configuration file, put the file into the specified directory.
- the Provides compatible query of the kit provided.
- queryformat <file header format> header file provided representation.
- querytags lists may be used to tag file header format.
- rcfile <profile> Use the specified configuration file.
- rebulid <package file> installation kit original code, reproduces the binary kit.
- rebuliddb based on existing databases, a database rebuild.
- RECOMPILE <profile Kits> and the effect of this parameter designated "--rebulid" similar parameters, do not produce package file.
- RELOCATE <original directory> = <new directory> would have put the files in the original directory to change into the new directory.
- ReplaceFiles forced displacement file.
- replacepkgs forced replacement kit.
-The kit requires inquiry required degree of compatibility.
- resing <package file> + delete existing certification, re-produce the signature authentication.
- After rmsource complete suite of packaging, delete the original code.
- rmsource <file> delete the original code and the specified file.
- root <root> is set to be used as the root directory.
- scripts listed Script variable installation kit.
- permission setperms settings file.
- Owner setugids settings files and their group.
- Short-Circuit skip directly specify the steps to complete the stage.
- Sign generate PGP or GPG signatures certified.
- target = <mounting platform> + generated mounting platform disposed kit.
- the Test only for testing, not really mount kit.
- timecheck <Check seconds> seconds timer is provided to check the time.
- triggeredby <package file> query packager of the suite.
- the Triggers display package Script files in the package.
- effects and designated verify this parameter "-q" the same parameters.
- Version display version information.
- whatprovides <Features> Query compatible suite on the functional properties of the specified offer.
- whatrequires <Features> Query The suite of features required for a specified degree of compatibility.
Commonly used commands:
Two, Yum source installation
the y- UM source installation needs to configure yum source to be installed
