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

This article will explain in detail how to build your first yum source, the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

Yum source is like a treasure house, there are many rpm packages in it, who wants to go to it to get things as long as the specified path, so how do we build our own warehouse?

YUM building

The client sets up its own YUM source

Environment: using local ISO as YUM source

1. Mount ISO

Mount / dev/cdrom / mnt/cdrom-o loop\\ We first need to mount the ISO image. Mount is the mount command.

2. Establish a YUM source

Cd / etc/yum.repos.d/

Vi my.repo

Note: the name must end with repo, and the system will automatically recognize this file suffix.

3. The my.repo content defines the name of the Yum source as follows

[my-source]

Comment name=abc to the YUM source

YUM source location (can support FTP/HTTP, etc.) baseurl= file:///mnt/cdrom

Whether to enable this YUM source. 0 is not enabled, 1 is enabled=1 enabled

Whether the gpg secret key detection function supports. 0: no, 1: allow gpgcheck=0.

Specify the path and name of the gpg key gpgkey= file:///etc/pki/rpm-gpg/RPM-GPG-Test

4. Test

Yum repolist

Yum search xxx

Yum install xxx-y

When there are multiple yum sources, you can configure priority to determine which source has the highest priority (CentOS)

# yum install yum-plugin-priorities-y

Add to the source configuration file of yum

Priority=N [Number1-99, the lower the number, the higher the priority]

The plug-in for priorities is installed in / etc/yum/pluginconf.d, and the configuration file is priorities.conf

If priority is set, it should be noted that when priority 1 (highest priority) exists software and other priorities also exist, only priority 1 shall prevail. If there is a new version of this software at low priority, but no new version for high priority (such as using ISO as repo), the software will not be updated.

RPM: RedHat Package Manage (RedHat package Management)

RPM is a binary software package, users can install the software directly.

The composition of RPM generally consists of four parts.

1. Software name

two。 Software version number

3. Architecture [i686 ~ x86 ~ 64 ~ # noarch]

4. Suffix name [rpm (binary package) / src.rpm (source code package)]

Characteristics of RPM

1. Binaries do not need to compile the software and then install

two。 You can adjust the src.rpm package again and generate binary software

3. It is very convenient to control, query and uninstall the software.

4. Software package association processing is not intelligent

Command: rpm

Function: install RPM software with suffix

Syntax format: rpm

Option usage-I: install package-v: display installation information during installation-h: use "#" as a progress bar to show installation progress-e: delete package-U: upgrade package, if the upgraded package does not exist, then install-F: upgrade package, if the upgraded package does not exist Then abandon the upgrade-nodeps: ignore the associated package of the package-force: force installation, ignore errors / prompts and other information

Options:

-Q: query. Query options have many secondary parameters.

1)-qa: query all currently installed software packages on the local system

2)-qf: query a file / directory generated by which software package is installed

3)-ql: query the installation path of a software package

4)-qi: query the details of the specified software package

5)-- whatrequires: query the associated package of the specified software package

6)-- whatprovides: query which software package a module belongs to

7)-qR: query which modules are required for the specified software to work properly

8)-qd: query help documentation only

9)-qc: find the configuration document

10)-Q-- scripts: query the script for installing / removing software packages

11)-Q-- changelog: displays information about package changes

-qlp: displays the information of the specified software package

-- root: specify the installation directory of the software

-V: verify that the installed software option is in use

If no information appears when using-V, it means that all files installed by the software have not been modified or other actions. If the relevant information appears, it means that some aspect has been modified.

Its information code indicates

Option usage-V represents 5:MD5 checksumS: file size L:Symbolic link (connection symbol) T: file modification time D: device U: file owner G: file group M: file permissions and types on how to build your first yum source is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to 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.