Shulou(Shulou.com)06/01 Report--

This article will explain in detail the example analysis of rpm, yum and source code under Linux. Xiaobian thinks it is quite practical, so share it with you as a reference. I hope you can gain something after reading this article.

Chapter 1: The Last Day

Source package installation is slower than RPM package installation because RPM packages are system and platform specific, often a

The program will provide a lot of RPM package format, users choose the appropriate RPM package directly installed according to the system situation, and the source package is equivalent to

General purpose, can be used in multiple systems, so you need to run the configure script to detect the environment and generate the corresponding installation information.

1.1 Advantages of source code installation

1. Complete documentation

2, because you can locate the code, so debug is convenient

3, native compatibility is the best (because it is compiled natively, as long as the compilation passes, there is no dependence on various libraries)

1.2 Disadvantages of source code installation

1. Compilation trouble

2, lack of automatic dependency management, software upgrade trouble

1.3 installation process

1.3.1 Unpacking source packages tar files: source packages are usually archived using tar tools and then compressed using gunzip or bzip2,

Suffix format will be separated

For.tar.gz and.tar.bz2, respectively, decompression methods:

tar -zxvf FileName.tar.gztar -jxvf FileName.tar.bz2

1.3.2 Switching to the decompressed directory

cd /unzipped directory

1.3.3 Preparation for compilation: Before starting the service installation, you need to execute the configure script, which will automatically perform the current system.

A series of evaluations, such as source files, software dependency libraries, compilers, assemblers, connector checks, etc., and, if necessary,

The-prefix parameter can be used to specify the installation path of the program, and when the script checks that the system environment meets the requirements, it will be installed when

Create a Makefile file under the previous directory.

./ configure -prefix=/usr/local/program

1.3.4 Generating the installer: The Makefile generated in the previous step will save the installation rules with system environment dependencies. Next,

You need to use the make command to compile all dependencies using the appropriate SHELL according to the rules provided in the Makefile file

The source code, and then the make command will generate a final executable installer.

make compile

1.3.5 Install Service Programs: If the-prefix parameter is not used in the configure script phase, the program is generally defaulted

Install to/usr/local/bin directory.

make install

1.3.6 Clean up temporary files (optional):

make clean

1.3.7 Uninstall Service Program Command (Required)

make uninstall

1.3.8 Viewing Installation Information

The whereis command locates executable files, source code files, and help files in the file system. of these documents

Properties should belong to source code, binary files, or help files.

For example, whereas Java

whereis [-bmsu] [BMS directory name-f ] filename

-b Search for binary parts of files.

-m Search the manual section of the document.

-s Search for the source part of the file.

-u Files without documentation

The-B, -M, and-S flags can be used to change or restrict where the whereis command searches. Because the program has to run

Faster and uses the chdir subroutine, so pathnames given with-M, -S, and-B flag directory lists must be complete;

For example, they must start with a/(slash).

-B Same as-b, but adds the directory to search. Change or restrict where the whereis command searches for binaries.

-M Same as-m, but adds the directory to search. Change or qualify the location of the whereis command search manual section.

-S Same as-s, but adds directories to search. Change or qualify where the whereis command searches for sources.

-f Terminates the last-M, -S, or-B directory list concurrent file name start position signal.

(iv)[Parameters][Documents]

-c compressed file

-x extract files

-t See what files are in the archive

-z compressed or decompressed with Gzip

-j compressed or decompressed with bzip2

-v Display information about compression or decompression process

-f destination file name

-P retains original permissions and attributes

-p Use absolute path compression

-C specifies the directory to extract

Chapter 2 RPM Package Installation

For an rpm packet, there are "-" and ". "Constituent, basically composed of the following parts:

* Package name * version information * release version number * platform, when noarch appears, it means that the software is compatible with the platform.

2.1 Common usage 1

2.1.1 Installation

rpm -i Package files to install

rpm -iv Package files to install (shows installation details)

rpm -ivh Package files to be installed (shows installation details and progress)

2.1.2 Upgrade

rpm -U Package files that need to be upgraded

rpm -Uvh Package files to be upgraded (shows upgrade details and progress)

2.1.3 Unloading

rpm -e packages to uninstall

Note: If other programs depend on the package to be uninstalled, the system will prompt that it cannot be deleted. If it needs to be deleted forcibly, add--nodeps,

Forcefully removes, but may cause software that depends on it to fail to function.

2.1.4 View installed

rpm -qa

2.1.5 Viewing Specified Packages

rpm -qa |grep "Name of software or package"

2.2 Common Method 2

2.2.1 The first type: inquiry for service information of installed software

1. Query the installed software in the system

rpm -qa

2. Query which software package an installed file belongs to;

rpm -qf Absolute path to filename

3. Query where the installed software packages are installed;

Software name definition is:rpm package after removing platform information and suffix information

rpm -ql Software name

4. Query information about an installed package

rpm -qi Software name

5. Check the configuration file of the installed software;

rpm -qc software name

6. View a document that has installed software. Installation location:

rpm -qd Software name

7. Check the packages and files on which the installed software depends;

rpm -qR Software name

2.2.2 The second type: query for information about uninstalled software packages

1. View the purpose, version and other information of a software package;

rpm -qpi rpm file

2. View the files contained in a software package;

rpm -qpl rpm file

3. View the location of the package's documentation;

rpm -qpd rpm file

4. View the configuration file of a software package;

rpm -qpc rpm file

5. View the dependencies of a package

rpm -qpR rpm file

2.2.3 [Options] [Parameters]:

-a: Query all packages

-e: Delete the specified package

-f: Query the suite that owns the specified file;

-h or--hash: Displays progress information

-i: Display package details

-i or--install: Installs the specified package

-l: Displays the file list of the package

-p: Query the specified RPM package

-q: Use query mode

-U or--upgrade: Upgrade the specified package

-v: Display instruction execution process;

-vv: Detailed display of instruction execution process, easy to debug.

Common command combinations:

-ivh: installation shows installation progress--install--verbose--hash

-Uvh: Upgrade package--Update;

-qpl: List file information in RPM package [Query Package list];

-qpi: List RPM package description information [Query Package install package(s)];

-qf: Find which RPM package the specified file belongs to [Query File];

-Va: Verify all RPM packages, find missing files [View Lost];

-e: Delete package

--force forced operations such as forced deletion;

--requires Shows the dependencies of the package;

--nodeps Ignore dependencies and continue

Chapter 3: The Last Day

3.1 installation process

1, Install: yum install software

2. Upgrade: yum update software

3. Remove: yum remove software

4. View: yum info software

5. Search software: yum search software

6. View dependencies: yum deplist software

7. View installed software: yum list installed

3.2[Options] [Parameters]:

-e Silent execution

-t Ignore errors

-R[min] Set wait time

-Y auto answer yes

check-update Check for updatable packages

clean all Clear all

The requested URL/var/cache/was not found on this server.

clean headers Clear rpm headers

clean oldheaders Clean old rpm headers

deplist List package dependencies

listInstallable and updatable RPM packages

list installed installed packages

list extras Packages installed and not in the repository

info Installable and updatable RPM package information

info installed information about installed packages (-qa parameter similar)

install[RPM package] Installation package

localinstall Installs local RPM packages

update[RPM package] update package

upgrade system

search[keywords] Search package

provides[keyword] Search for specific package filenames

reinstall[RPM package] Reinstall package

repolist Displays the configuration of the repository

resolvedep specifies dependencies

remove[RPM package] uninstall package

About "Linux rpm, yum and source code three installation methods of example analysis" This article is shared here, I hope the above content can be of some help to everyone, so that you can learn more knowledge, if you think the article is good, please share it to let more people see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.