The Yum Foundation for Linux

Yum(full name isYellow Dogupdater, Modified)is one inFedoraand theRedHatas wellCentOSin theShellFront-end package manager. At first it was byYellow DogThe developer of this releaseTerra Softresearch and development, withpythonwritten, and later by Duke University's[email protected]The development team has made improvements, hence the name.

          yum rpm package management, which can be downloaded automatically from the specified server rpm package and install, and install all dependent packages at once,　No need to cumbersome to download, install. yum Multiple repositories can be configured at the same time (Repository) , concise configuration file ( /etc/ yum.conf rpm rpm database consistency.

CentOS The default is already installed Yum, no additional installation is required. You can use the #rpm –qa yum to view the installed yum versions.

a.yum configuration file

yum The configuration file is divided into two parts: main and repository main generally located in /etc/yum.conf repository /etc/yum.repos.d/ Span style= "font-family: ' The song Body '; , and with .repo suffix end, each repo

Main the configuration options in

[Main]

cachedir=/var/cache/yum/$basearch/$releasever Cache Directory

keepcache=0 If the package is retained after installation is complete, the default 0 reserved

debuglevel=2 Debug Information Output Level

Logfile=/var/log/yum.log Yum the log file

exactarch=1 1 install only packages that match the system architecture

Obsoletes=1 Check RPM the bag was abandoned .

gpgcheck=1 whether to GPG Checksum

Plugins=1 whether to enable plugin default 1 Allow

installonly_limit=5 the number of installation package limits at one time

Bugtracker_url=http://bugs.centos.org/set_project.php?

Project_id=19&ref=http://bugs.centos.org/bug_report_page.php?category=yum Bug Trace Path

Distroverpkg=centos-release

Warehouse Configuration

[Repositoryid] for the current system Yum speaking, this Repositoryid used to uniquely identify this Repository point, so that it must be unique;

name= current warehouse description information;

baseurl=url://path/to/repository/ indicate Repository , typically a file server that outputs a Repository ;

Enabled={1|0} whether this warehouse can be used

Gpgcheck={1|0} whether to validate the package

Gpgkey=url://path/to/keyfile indicate Gpgkey file path;        

cost= indicates the current Repository the access cost, which defaults to + ;

Second, Yum Command

Yum [options] [command] [package ...]

command is one of:

* Installpackage1 [Package2] [...] Package Installation: If a package has multiple versions in different warehouses, the latest version is installed by default, and if you are installing the specified version:installpackage-version ...

*update [Package1] [package2][...] Package Upgrade

* Update-to [Package1] [Package2] [...]

* Check-update check which upgrades are available

* upgrade [Package1] [Package2] [...]

* Upgrade-to [Package1] [Package2] [...]

* Distribution-synchronization [Package1] [Package2] [...]

* Remove |erase package1 [Package2] [...] Uninstall , all packages that depend on the package being uninstalled will be uninstalled

* List [...]

* Info [...] Brief information about the query program

* provides | Whatprovides Feature1 [Feature2] [...]

* Clean [packages | metadata | expire-cache | rpmdb | plugins | all] clean up the cache

* Makecache Cache Creation , automatically connect to every available warehouse, download it without data, and create it as a cache

* Groupinstall group1 [group2] [...] Install package Group

* Groupupdate group1 [group2] [...] Upgrade Package Groups

* grouplist [hidden] [Groupwildcard] [...] List all package groups

* Groupremove group1 [group2] [...] Uninstalling a package group

* GroupInfo group1 [...] Show specified package group details

* Search string1 [string2] [...] search for the specified keyword in the package name and sumary Information

* Shell [filename]

* RESOLVEDEP DEP1 [DEP2] [...]

*localinstall Rpmfile1 [Rpmfile2] [...] Install or upgrade the local package files, which may be dependent on some packages in the warehouse, for installing package files that do not exist in the warehouse ;

* localupdate rpmfile1[rpmfile2] [...] Upgrading a local package file

(Maintained forlegacy reasons Only-use update)

* Reinstall Package1 [Package2] [...] Reinstall (overwrite installation)

* Downgrade Package1 [Package2] [...] Package Demotion

* Deplist Package1 [Package2] [...]

* repolist [all|enabled|disabled] list all available warehouses that have been configured

* Version [all | installed | available | group-* | nogroups* |grouplist | groupinfo]

*history[info|list|packages-list|packages-info|summary|addon-info|redo|undo|rollback|new|sync|stats]

* Load-transaction [Txfile]

* Check

* Help [command]

Yum available options for the command:

- y: The auto answer is " Yes "

--disablerepo=: temporarily disables a file that is configured and enabled in the profile Repository ;

--enablerepo= : Temporarily enables a specified Repo ;

--nogpgcheck: do not check the package;

Yum has built-in variables for storing information about the current platform;

(1) $raleasever: The major version number of the current OS release;

For example, for CentOS 6.6 x86_64, the major version number is 6;

(2) $arch: Platform

i386, i486

(3) $basearch: Basic Platforms such as i686, i586, i486 and i386 The foundation platform is the same as i386;

(4) $YUM 0-$YUM 9

This article is from the "10031868" blog, please be sure to keep this source http://10041868.blog.51cto.com/10031868/1631622

The Yum Foundation for Linux