2. Software Management Concepts
2.1. About Packages
CentOS software and documentation is supplied in the form of files called RPM packages. Each package is a compressed archive containing product information, program files, icons, documentation and management scripts. Management applications use these files to safely locate, install, update and remove software. For example, the CentOS installation process uses the packages supplied with CentOS to build or upgrade a system to your requirements.
Packages also include a digital signature to prove their source. Software management utilities verify this digital signature by using a GPG public key. The yum and rpm utilities share a common keyring that stores all of the public keys for approved package sources. The system administrator configures these approved package sources.
2.2. About Repositories
A repository is a prepared directory or web site that contains software packages and index files. Software management utilities such as yum automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to manually find and install new applications or updates. You may use a single command to update all system software, or search for new software by specifying criteria.
The package management utilities in CentOS are already configured to use a network of servers that provide several repositories:
*
[base] (AKA [os]) - The packages that make up CentOS, as it is released on the ISOs. It is enabled by default.
*
[updates] - Updated packages to [base] released after the CentOS ISOs. This will be Security, BugFix, or Enhancements to the [base] software. It is enabled by default.
*
[addons] - Contains packages required in order to build the main Distribution or packages produced by SRPMS built in the main Distribution, but not included in the main Redhat package tree (mysql-server in CentOS-3.x falls into this category). Packages contained in the addons repository should be considered essentially a part of the core distribution, but may not be in the upstream Package tree. It is enabled by default.
*
[contrib] - Packages contributed by the CentOS Users, which do not overlap with any of the core Distribution packages. These packages have not been tested by the CentOS developers, and may not track upstream version releases very closely. It is disabled by default.
*
[centosplus] - Packages contributed by CentOS Developers and the Users. These packages might replace rpm's included in the core Distribution. You should understand the implications of enabling and using packages from this repository. It is diabled by default
*
[csgfs] - Packages that make up the Cluster Suite and Global File System. It is disabled by default.
*
[extras] - Packages built and maintained by the CentOS developers that add functionality to the core distribution. These packages have undergone some basic testing, should track upstream release versions fairly closely and will never replace any core distribution package. It is enabled by default.
*
[testing] - Packages that are being tested proir to release, you should not use this repository except for a specific reason. It is disabled by default.
[Note] All CentOS Packages are Open Source Software
All of the software provided by the CentOS Project is open source software. You may download and install software from the CentOS Project network of repositories on as many systems as desired.
Third-party software developers also provide repositories for their CentOS compatible packages. To learn how to configure your CentOS system to use third-party repositories, read Section 7, “Using Other Software Repositories”.
You may also use the package groups provided by the CentOS repositories to manage related packages as sets. Some third-party repositories add packages to these groups, or provide their packages as additional groups.
[Note] Available Package Groups
To view a list of all of the available package groups for your CentOS system, run the command su -c 'yum grouplist'.
Use repositories to ensure that you always receive current versions of software. If several versions of the same package are available, your management utility automatically selects the latest version.
[Caution] Installing Software not from a Repository
Install software using manual methods only when you are confident there is no repository which can currently provide it. You may have to manage that software with manual methods, instead of with CentOS software management utilities.
The yum commands shown in this document use repositories as package sources. Refer to Section 9, “Manually Installing Software” for details of using yum to install software from a package file.
2.3. About Dependencies
Some of the files installed on a CentOS distribution are libraries which may provide functions to multiple applications. When an application requires a specific library, the package which contains that library is a dependency. To properly install a package, CentOS must first satisfy its dependencies. The dependency information for a RPM package is stored within the RPM file.
The yum utility uses package dependency data to ensure that all of requirements for an application are met during installation. It automatically installs the packages for any dependencies not already present on your system. If a new application has requirements that conflict with existing software, yum aborts without making any changes to your system.
2.4. Understanding Package Names
Each package file has a long name that indicates several key pieces of information. This is the full name of the tsclient package supplied with CentOS:
tsclient-0.132-4.i386.rpm
Management utilities commonly refer to packages with one of three formats:
*
Package name: tsclient
*
Package name with version and release numbers: tsclient-0.132-4
*
Package name with hardware architecture: tsclient.i386
For clarity, yum lists packages in the format name.architecture. Repositories also commonly store packages in separate directories by architecture. In each case, the hardware architecture specified for the package is the minimum type of machine required to use the package.
i386
Suitable for any current Intel®-compatible computer
noarch
Compatible with all computer architectures
ppc
Suitable for PowerPC systems, such as Apple® Power Macintosh or IBM® PowerPC
ia64
Suitable for Intel® Itanium2 processors.
s390 or s390x
Suitable for IBM® S390 or S390x Processors.
alpha
Suitable for DEC® alpha Processors (now owned by Hewlitt Packard®).
sparc
Suitable for Sun Microsystems® sparc Processors.
x86_64
Suitable for 64-bit Intel-compatible processors, such as AMD® Opteron or Intel® Xeon Processors
Some software may be optimized for particular types of Intel-compatible machine. Separate packages may be provided for i386, i586, i686 and x86_64 computers. A machine with at least an Intel® Pentium, VIA® C3 or compatible CPU may use i586 packages. Computers with an Intel® Pentium Pro® and above, or a current model of AMD® chip, may use i686 packages.
Use the short name of the package for yum commands. This causes yum to automatically select the most recent package in the repositories that matches the hardware architecture of your computer.
Specify a package with other name formats to override the default behavior and force yum to use the package that matches that version or architecture. Only override yum when you know that the default package selection has a bug or other fault that makes it unsuitable for installation.
[Tip] Package Names
You may use any of the following formats to specify a package in a yum operation: name, name.architecture, name-version, name-version-release, name-version-release.architecture, and epoch:name-version-release.architecture.
唉～～～接下去，两天没来了吧
The example commands for CentOS package groups use the MySQL Database group.
[Important] Avoid Logging in with the Root Account
You do not need to log in with the root account in order to manage your CentOS system. All of the commands shown in this tutorial that require root access will prompt you for the root password. The example terminal commands use su -c to provide this facility.
1.4. Additional Resources
The yum utility has features and options not discussed in this document. Read the man pages for yum(8) and yum.conf(5) to learn more, using the following commands:
man yum
man yum.conf
Other useful yum resources on the Internet include:
Project web site
http://linux.duke.edu/projects/yum/ Users mailing list
https://lists.dulug.duke.edu/mailman/listinfo/yum/ Development mailing list
https://lists.dulug.duke.edu/pipermail/yum-devel/
本文档中大多数范例使用了软件包 tsclient，它位于 centos里面。tsclient 软件包提供了一个用于远程桌面连接的应用程序。如果您成功安装了它，可以选择菜单 Applications → Internet → Terminal Server Client。要使用例子，只需把 tsclient 替换为相关的软件包名称。
relaaxx 于 2008-01-14 20:35:24发表:
1. Introduction
1.1. Purpose
This document presents basic concepts of software management on CentOS systems. It outlines the major functions of yum, the recommended software management tool for CentOS.
1.2. Audience
This document is intended for CentOS users of all levels of experience.
1.3. Using This Document
This document is a reference for using yum. You may wish to read some or all of the sections, depending upon your needs and level of experience. If you are a new user, read the Section 2, “Software Management Concepts” before using yum for the first time. Experienced Linux users should start with Section 4, “Managing Software with yum”.
Previous Versions of CentOS
This document describes the configuration of yum on CentOS 4 systems. You must perform the additional step noted in Section 7.2, “Manually Authorizing Package Sources” to enable yum on CentOS 3.
Most of the examples in this document use the package tsclient, which is included with CentOS. The tsclient package provides an application for remote desktop access. If you install it successfully you may start the application by choosing Applications->Internet->Terminal Server Client. To use the examples, substitute the name of the relevant package for tsclient.
[ 本帖最后由 relaaxx 于 2008-1-14 20:51 编辑 ]
relaaxx 于 2008-01-14 20:32:25发表:
现在红联原创好象好少，我争取把这个centos的Managing Software with yum译完，算是支持下红联
1. Introduction
1.1. Purpose
1.2. Audience
1.3. Using This Document
1.4. Additional Resources
2. Software Management Concepts
2.1. About Packages
2.2. About Repositories
2.3. About Dependencies
2.4. Understanding Package Names
3. Software Management Tools in CentOS
4. Managing Software with yum
4.1. Installing New Software with yum
4.2. Updating Software with yum
4.3. Removing Software with yum
5. Searching for Packages with yum
5.1. Searching by Package Name and Attributes
5.2. Advanced Searches
5.3. Understanding Matches
6. Updating Your System with yum
6.1. Automatically Updating Your System
7. Using Other Software Repositories
7.1. Adding a Repository as a Package Source
7.2. Manually Authorizing Package Sources
7.3. Understanding Repository Compatibility
8. Maintaining yum
8.1. Disabling or Removing Package Sources
8.2. Clearing the yum Caches
8.3. Using yum Plugins
9. Manually Installing Software
10. Using yum with a Proxy Server
11. Acknowledgements
Index
hudome 于 2011-08-31 14:18:04发表:
楼主你写的太高深了，一般人看不懂哇～！
relaaxx 于 2008-01-17 19:19:28发表:
不加精，不译了(5ty(
relaaxx 于 2008-01-17 19:17:41发表:
2. Software Management Concepts
2.1. About Packages
CentOS software and documentation is supplied in the form of files called RPM packages. Each package is a compressed archive containing product information, program files, icons, documentation and management scripts. Management applications use these files to safely locate, install, update and remove software. For example, the CentOS installation process uses the packages supplied with CentOS to build or upgrade a system to your requirements.
Packages also include a digital signature to prove their source. Software management utilities verify this digital signature by using a GPG public key. The yum and rpm utilities share a common keyring that stores all of the public keys for approved package sources. The system administrator configures these approved package sources.
2.2. About Repositories
A repository is a prepared directory or web site that contains software packages and index files. Software management utilities such as yum automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to manually find and install new applications or updates. You may use a single command to update all system software, or search for new software by specifying criteria.
The package management utilities in CentOS are already configured to use a network of servers that provide several repositories:
*
[base] (AKA [os]) - The packages that make up CentOS, as it is released on the ISOs. It is enabled by default.
*
[updates] - Updated packages to [base] released after the CentOS ISOs. This will be Security, BugFix, or Enhancements to the [base] software. It is enabled by default.
*
[addons] - Contains packages required in order to build the main Distribution or packages produced by SRPMS built in the main Distribution, but not included in the main Redhat package tree (mysql-server in CentOS-3.x falls into this category). Packages contained in the addons repository should be considered essentially a part of the core distribution, but may not be in the upstream Package tree. It is enabled by default.
*
[contrib] - Packages contributed by the CentOS Users, which do not overlap with any of the core Distribution packages. These packages have not been tested by the CentOS developers, and may not track upstream version releases very closely. It is disabled by default.
*
[centosplus] - Packages contributed by CentOS Developers and the Users. These packages might replace rpm's included in the core Distribution. You should understand the implications of enabling and using packages from this repository. It is diabled by default
*
[csgfs] - Packages that make up the Cluster Suite and Global File System. It is disabled by default.
*
[extras] - Packages built and maintained by the CentOS developers that add functionality to the core distribution. These packages have undergone some basic testing, should track upstream release versions fairly closely and will never replace any core distribution package. It is enabled by default.
*
[testing] - Packages that are being tested proir to release, you should not use this repository except for a specific reason. It is disabled by default.
[Note] All CentOS Packages are Open Source Software
All of the software provided by the CentOS Project is open source software. You may download and install software from the CentOS Project network of repositories on as many systems as desired.
Third-party software developers also provide repositories for their CentOS compatible packages. To learn how to configure your CentOS system to use third-party repositories, read Section 7, “Using Other Software Repositories”.
You may also use the package groups provided by the CentOS repositories to manage related packages as sets. Some third-party repositories add packages to these groups, or provide their packages as additional groups.
[Note] Available Package Groups
To view a list of all of the available package groups for your CentOS system, run the command su -c 'yum grouplist'.
Use repositories to ensure that you always receive current versions of software. If several versions of the same package are available, your management utility automatically selects the latest version.
[Caution] Installing Software not from a Repository
Install software using manual methods only when you are confident there is no repository which can currently provide it. You may have to manage that software with manual methods, instead of with CentOS software management utilities.
The yum commands shown in this document use repositories as package sources. Refer to Section 9, “Manually Installing Software” for details of using yum to install software from a package file.
2.3. About Dependencies
Some of the files installed on a CentOS distribution are libraries which may provide functions to multiple applications. When an application requires a specific library, the package which contains that library is a dependency. To properly install a package, CentOS must first satisfy its dependencies. The dependency information for a RPM package is stored within the RPM file.
The yum utility uses package dependency data to ensure that all of requirements for an application are met during installation. It automatically installs the packages for any dependencies not already present on your system. If a new application has requirements that conflict with existing software, yum aborts without making any changes to your system.
2.4. Understanding Package Names
Each package file has a long name that indicates several key pieces of information. This is the full name of the tsclient package supplied with CentOS:
tsclient-0.132-4.i386.rpm
Management utilities commonly refer to packages with one of three formats:
*
Package name: tsclient
*
Package name with version and release numbers: tsclient-0.132-4
*
Package name with hardware architecture: tsclient.i386
For clarity, yum lists packages in the format name.architecture. Repositories also commonly store packages in separate directories by architecture. In each case, the hardware architecture specified for the package is the minimum type of machine required to use the package.
i386
Suitable for any current Intel®-compatible computer
noarch
Compatible with all computer architectures
ppc
Suitable for PowerPC systems, such as Apple® Power Macintosh or IBM® PowerPC
ia64
Suitable for Intel® Itanium2 processors.
s390 or s390x
Suitable for IBM® S390 or S390x Processors.
alpha
Suitable for DEC® alpha Processors (now owned by Hewlitt Packard®).
sparc
Suitable for Sun Microsystems® sparc Processors.
x86_64
Suitable for 64-bit Intel-compatible processors, such as AMD® Opteron or Intel® Xeon Processors
Some software may be optimized for particular types of Intel-compatible machine. Separate packages may be provided for i386, i586, i686 and x86_64 computers. A machine with at least an Intel® Pentium, VIA® C3 or compatible CPU may use i586 packages. Computers with an Intel® Pentium Pro® and above, or a current model of AMD® chip, may use i686 packages.
Use the short name of the package for yum commands. This causes yum to automatically select the most recent package in the repositories that matches the hardware architecture of your computer.
Specify a package with other name formats to override the default behavior and force yum to use the package that matches that version or architecture. Only override yum when you know that the default package selection has a bug or other fault that makes it unsuitable for installation.
[Tip] Package Names
You may use any of the following formats to specify a package in a yum operation: name, name.architecture, name-version, name-version-release, name-version-release.architecture, and epoch:name-version-release.architecture.
relaaxx 于 2008-01-17 19:14:47发表:
centos 软件组的操作范例使用了 MySQL Database 组。
[重要] 避免以 root 帐号登录
您不需要以 root 登录，当是仍然可以管理您的centos 系统。本文档中包含的所有操作，如果需要 root 权限，会提示您输入 root 的密码。例子使用 su -c 命令实现了这种功能。
1.4. 附加资源
本文档没有介绍 yum 工具的某些特性和选项。阅读 man 手册页的 yum(8) 和 yum.conf(5) 来学习它们，只要这样：
man yum
man yum.conf
互联网上其他有用的 yum 资源还有：
项目网站
http://linux.duke.edu/projects/yum/
用户的邮件列表
https://lists.dulug.duke.edu/mailman/listinfo/yum/
开发的邮件列表
https://lists.dulug.duke.edu/pipermail/yum-devel/
relaaxx 于 2008-01-17 19:10:33发表:
唉～～～接下去，两天没来了吧
The example commands for CentOS package groups use the MySQL Database group.
[Important] Avoid Logging in with the Root Account
You do not need to log in with the root account in order to manage your CentOS system. All of the commands shown in this tutorial that require root access will prompt you for the root password. The example terminal commands use su -c to provide this facility.
1.4. Additional Resources
The yum utility has features and options not discussed in this document. Read the man pages for yum(8) and yum.conf(5) to learn more, using the following commands:
man yum
man yum.conf
Other useful yum resources on the Internet include:
Project web site
http://linux.duke.edu/projects/yum/
Users mailing list
https://lists.dulug.duke.edu/mailman/listinfo/yum/
Development mailing list
https://lists.dulug.duke.edu/pipermail/yum-devel/
relaaxx 于 2008-01-14 20:52:28发表:
1. 介绍
1.1. 目的
这个文档记述了centos系统中软件管理的基本内容。文档包括了centos推荐使用的软件管理工具 yum 的主要功能。
1.2. 读者
本文档适于水平不同的所有 centos用户。
1.3. 使用本文档
本文档是使用yum的一份参考。您可以有选择地阅读或者全文阅读，这取决于您的要求和水平。如果您是一个新手，可以在第一次使用 yum 之前先阅读第2节 “软件管理概念”。有经验的 Linux 用户可以从 第 4 节 “使用 yum 管理软件” 开始。
早先版本的centos
这份文档描述的 yum 的配置适用于centos4系统。您必须按照 第 7.2 节 “手动认证软件来源” 中的步骤才能启用 yum。
本文档中大多数范例使用了软件包 tsclient，它位于 centos里面。tsclient 软件包提供了一个用于远程桌面连接的应用程序。如果您成功安装了它，可以选择菜单 Applications → Internet → Terminal Server Client。要使用例子，只需把 tsclient 替换为相关的软件包名称。
relaaxx 于 2008-01-14 20:35:24发表:
1. Introduction
1.1. Purpose
This document presents basic concepts of software management on CentOS systems. It outlines the major functions of yum, the recommended software management tool for CentOS.
1.2. Audience
This document is intended for CentOS users of all levels of experience.
1.3. Using This Document
This document is a reference for using yum. You may wish to read some or all of the sections, depending upon your needs and level of experience. If you are a new user, read the Section 2, “Software Management Concepts” before using yum for the first time. Experienced Linux users should start with Section 4, “Managing Software with yum”.
Previous Versions of CentOS
This document describes the configuration of yum on CentOS 4 systems. You must perform the additional step noted in Section 7.2, “Manually Authorizing Package Sources” to enable yum on CentOS 3.
Most of the examples in this document use the package tsclient, which is included with CentOS. The tsclient package provides an application for remote desktop access. If you install it successfully you may start the application by choosing Applications->Internet->Terminal Server Client. To use the examples, substitute the name of the relevant package for tsclient.
[ 本帖最后由 relaaxx 于 2008-1-14 20:51 编辑 ]
relaaxx 于 2008-01-14 20:32:25发表:
现在红联原创好象好少，我争取把这个centos的Managing Software with yum译完，算是支持下红联
relaaxx 于 2008-01-14 20:27:38发表:
自己留位，打字好累
relaaxx 于 2008-01-14 20:26:41发表:
1. 介绍
1.1. 目的
1.2. 读者
1.3. 本文档的用法
1.4. 附加资源
2. 软件管理概念
2.1. 关于软件包
2.2. 关于仓库
2.3. 关于依赖关系
2.4. 理解软件包名称
3. centos 中的软件管理工具
4. 使用 yum 管理软件
4.1. 使用 yum 安装新软件
4.2. 使用 yum 更新软件
4.3. 使用 yum 移除软件
5. 使用 yum 搜索软件
5.1. 通过软件名和属性搜索
5.2. 高级搜索
5.3. 理解匹配
6. 使用 yum 更新您的系统
6.1. 自动更新您的系统
7. 使用其他软件仓库
7.1. 添加仓库作为软件来源
7.2. 手动认证软件来源
7.3. 理解仓库相容性
8. 维护 yum
8.1. 禁用或删除软件来源
8.2. 清空 yum 缓存
8.3使用yum plugins
9. 手动安装软件
10. 使用 yum有代理服务器
11. 感谢
索引
Totoobo 于 2008-01-14 20:24:00发表:
要是中文好些，英文看起来费力些
relaaxx 于 2008-01-14 20:14:18发表:
1. Introduction
1.1. Purpose
1.2. Audience
1.3. Using This Document
1.4. Additional Resources
2. Software Management Concepts
2.1. About Packages
2.2. About Repositories
2.3. About Dependencies
2.4. Understanding Package Names
3. Software Management Tools in CentOS
4. Managing Software with yum
4.1. Installing New Software with yum
4.2. Updating Software with yum
4.3. Removing Software with yum
5. Searching for Packages with yum
5.1. Searching by Package Name and Attributes
5.2. Advanced Searches
5.3. Understanding Matches
6. Updating Your System with yum
6.1. Automatically Updating Your System
7. Using Other Software Repositories
7.1. Adding a Repository as a Package Source
7.2. Manually Authorizing Package Sources
7.3. Understanding Repository Compatibility
8. Maintaining yum
8.1. Disabling or Removing Package Sources
8.2. Clearing the yum Caches
8.3. Using yum Plugins
9. Manually Installing Software
10. Using yum with a Proxy Server
11. Acknowledgements
Index
[ 本帖最后由 relaaxx 于 2008-1-14 20:27 编辑 ]