mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-12 01:40:10 +08:00
20131108-1 选题
This commit is contained in:
DeadFire
parent
8824fac58d
commit
ce44c883f0
98
sources/How to monitor system temperature on Linux.md
Normal file
98
sources/How to monitor system temperature on Linux.md
Normal file
@ -0,0 +1,98 @@
|
||||
How to monitor system temperature on Linux
|
||||
================================================================================
|
||||
In most cases, you are not supposed to be worried about the temperature of your computer. Barring manufacturing defects, hardware is designed so that its temperature does not exceed maximum operating temperature. But even without any hardware fault, overheating can occur due to various software issues, e.g., buggy graphics card driver, misconfigured fan control program, malfunctioning CPU frequency scaling daemon, etc.
|
||||
|
||||
Overheating may become serious enough to cause permanent damage on your hardware. So watch out for any overheating issue in your system. Even better, have temperature monitoring system in place, so that you will be alerted if system temperature suddenly goes up.
|
||||
|
||||
In this tutorial, I will describe **how to monitor system temperature on Linux**.
|
||||
|
||||
There are several user space tools on Linux, which allow you to check and monitor temperature of various system components.
|
||||
|
||||
[lm-sensors][1] is a software tool that draws from hardware embedded sensors to monitor temperatures, voltage, humidity and fans. [hddtemp][2] is a tool that can measure the temperature of hard drives from [S.M.A.R.T.][3] readings. [psensor][4] is a graphical front-end for temperature monitoring, which visualizes temperature readings from CPUs, NVidia/ATI/AMD GPUs, hard disks, etc.
|
||||
|
||||
In the following, I will describe how to set up psensor to monitor the temperature of CPUs and hard drives.
|
||||
|
||||
### Install psensor on Linux Desktop ###
|
||||
|
||||
psensor can visualize system temperature based on the information obtained from other tools such as lm-sensors and hddtemp. Thus you need to install psensor along with those prerequisites.
|
||||
|
||||
To install psensor on Debian or Ubuntu:
|
||||
|
||||
$ sudo apt-get install lm-sensors hddtemp psensor
|
||||
|
||||
To install psensor on Fedora:
|
||||
|
||||
$ sudo yum install lm_sensors hddtemp
|
||||
$ sudo yum install gcc gtk3-devel GConf2-devel lm_sensors-devel cppcheck libatasmart-devel libcurl-devel json-c-devel libmicrohttpd-devel help2man libnotify-devel libgtop2-devel make
|
||||
$ wget http://wpitchoune.net/psensor/files/psensor-0.8.0.3.tar.gz
|
||||
$ tar xvfvz psensor-0.8.0.3.tar.gz
|
||||
$ cd psensor-0.8.0.3
|
||||
$ ./configure
|
||||
$ make
|
||||
$ sudo make install
|
||||
|
||||
Due to the requirement for GTK3 libraries, psensor is not compatible with the GNOME 2 desktop of CentOS or RHEL 6.
|
||||
|
||||
### Configure psensor on Linux ###
|
||||
|
||||
Before launching psensor, you need to configure lm_sensors and hddtemp first.
|
||||
|
||||
#### lm_sensors configuration ####
|
||||
|
||||
To configure lm_sensors, run the following command. Choose YES to every question.
|
||||
|
||||
$ sudo sensors-detect
|
||||
|
||||
This command will probe for and detect embedded sensors in your hardware (including CPUs, memory controllers, I/O chips), and automatically determine which driver modules need to be loaded to check temperature on your system.
|
||||
|
||||
Once sensor probing is completed, you will be asked to add detected driver module(s) to /etc configuration, so they can be loaded automatically upon boot.
|
||||
|
||||
On Debian or Ubuntu, detected driver modules will be added to /etc/modules. On Fedora, the driver information will be added to /etc/sysconfig/lm_sensors.
|
||||
|
||||
Next, proceed to load necessary modules as follows.
|
||||
|
||||
On Ubuntu:
|
||||
|
||||
$ sudo service module-init-tools start
|
||||
|
||||
On Debian:
|
||||
|
||||
$ sudo /etc/init.d/kmod start
|
||||
|
||||
On Fedora:
|
||||
|
||||
$ sudo service lm_sensors start
|
||||
|
||||
#### hddtemp configuration ####
|
||||
|
||||
You also need to launch hddtemp which monitors the temperature of hard drives.
|
||||
|
||||
Run the following command to launch hddtemp as a daemon. Replace “/dev/sda” with the disk drive to monitor on your system.
|
||||
|
||||
$ sudo hddtemp -d /dev/sda
|
||||
|
||||
### Monitor System Temperature with psensor ###
|
||||
|
||||
To start monitoring temperature with psensor, simply run:
|
||||
|
||||
$ psensor
|
||||
|
||||
The psensor window will show a list of available sensors, and visualize temperature readings from these sensors. You can selectively enable or disable each sensor.
|
||||
|
||||
[][5]
|
||||
|
||||
Optionally, you can set an alarm level for each sensor, so that you can be notified when the temperature from a sensor exceeds a threshold.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://xmodulo.com/2013/11/monitor-system-temperature-linux.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://lm-sensors.org/
|
||||
[2]:http://www.guzu.net/linux/hddtemp.php
|
||||
[3]:http://en.wikipedia.org/wiki/S.M.A.R.T.
|
||||
[4]:http://wpitchoune.net/blog/psensor/
|
||||
[5]:http://www.flickr.com/photos/xmodulo/10719475225/
|
||||
@ -0,0 +1,447 @@
|
||||
Package Management Using YUM In Red Hat Linux
|
||||
================================================================================
|
||||
|
||||
|
||||
**Yum** is a utility provided in RHEL based systems to install,remove and search packages. It can do lot more than just installing and removing and that’s what I will demonstrate in this article.
|
||||
|
||||
Yum installs the package dependencies automatically, for example yum install httpd will install https apache server and it’s required dependencies automatically. Something that is not that easy while installing through rpm. with rpm you have to download all the required dependencies and then install accordingly.
|
||||
|
||||
The yum utility fetches the package information from a hosted repository (usually by the OS vendor). A repository is basically a collection of rpm’s that are supposed to work on a particular architecture. For example there would be a separate repository for 32 and 64 bit systems, and same goes with RHEL Version 5 and Version 6. You can host your local repository and configure yum to search,install packages from the local repository. In the following examples I will show you some other stuff we can do with yum rather than install and remove but for the sake of understanding I will use httpd package for exempts on my Amazon EC2 RHEL 6.4 server.
|
||||
|
||||
### Search package from repository ###
|
||||
|
||||
# yum search httpd
|
||||
|
||||
Loaded plugins: amazon-id, rhui-lb, security
|
||||
=============================================== N/S Matched: httpd ==========
|
||||
httpd.x86_64 : Apache HTTP Server
|
||||
httpd-devel.i686 : Development interfaces for the Apache HTTP server
|
||||
httpd-devel.x86_64 : Development interfaces for the Apache HTTP server
|
||||
httpd-manual.noarch : Documentation for the Apache HTTP server
|
||||
httpd-tools.x86_64 : Tools for use with the Apache HTTP Server
|
||||
mod_dav_svn.x86_64 : Apache httpd module for Subversion server
|
||||
mod_dnssd.x86_64 : An Apache HTTPD module which adds Zeroconf support
|
||||
|
||||
For a more detailed output use the below command:
|
||||
|
||||
# yum provides httpd
|
||||
|
||||
Loaded plugins: amazon-id, rhui-lb, security
|
||||
httpd-2.2.15-26.el6.x86_64 : Apache HTTP Server
|
||||
Repo : rhui-REGION-rhel-server-releases
|
||||
Matched from:
|
||||
|
||||
**yum provides */httpd** Searches in yum packages to find the package that contains a httpd.
|
||||
|
||||
### Provide a list of all Package Groups. ###
|
||||
|
||||
# yum grouplist
|
||||
|
||||
The above command will show you the installed and available package group. You can install an individual package group with group install option. For example we will install package group PHP Support. This package group contains the required php packages.
|
||||
|
||||
# yum groupinstall PHP Support
|
||||
|
||||
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
|
||||
Setting up Group Process
|
||||
Warning: Group Support does not exist.
|
||||
Resolving Dependencies
|
||||
–> Running transaction check
|
||||
—> Package php.x86_64 0:5.3.3-23.el6_4 will be installed
|
||||
–> Processing Dependency: php-common(x86-64) = 5.3.3-23.el6_4 for package: php-5.3.3-23.el6_4.x86_64
|
||||
–> Processing Dependency: php-cli(x86-64) = 5.3.3-23.el6_4 for package: php-5.3.3-23.el6_4.x86_64
|
||||
—> Package php-gd.x86_64 0:5.3.3-23.el6_4 will be installed
|
||||
–> Processing Dependency: libXpm.so.4()(64bit) for package: php-gd-5.3.3-23.el6_4.x86_64
|
||||
—> Package php-pdo.x86_64 0:5.3.3-23.el6_4 will be installed
|
||||
—> Package php-pear.noarch 1:1.9.4-4.el6 will be installed
|
||||
—> Package php-xml.x86_64 0:5.3.3-23.el6_4 will be installed
|
||||
–> Running transaction check
|
||||
—> Package libXpm.x86_64 0:3.5.10-2.el6 will be installed
|
||||
—> Package php-cli.x86_64 0:5.3.3-23.el6_4 will be installed
|
||||
—> Package php-common.x86_64 0:5.3.3-23.el6_4 will be installed
|
||||
–> Finished Dependency Resolution
|
||||
|
||||
Dependencies Resolved
|
||||
|
||||
=====================================================================
|
||||
Package Arch Version Repository Size
|
||||
=====================================================================
|
||||
Installing:
|
||||
php x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 1.1 M
|
||||
php-gd x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 106 k
|
||||
php-pdo x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 75 k
|
||||
php-pear noarch 1:1.9.4-4.el6 rhui-REGION-rhel-server-releases 393 k
|
||||
php-xml x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 103 k
|
||||
Installing for dependencies:
|
||||
libXpm x86_64 3.5.10-2.el6 rhui-REGION-rhel-server-releases 51 k
|
||||
php-cli x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 2.2 M
|
||||
php-common x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 524 k
|
||||
|
||||
Transaction Summary
|
||||
========================================================================
|
||||
Install 8 Package(s)
|
||||
|
||||
Total download size: 4.5 M
|
||||
Installed size: 16 M
|
||||
Is this ok [y/N]: y
|
||||
|
||||
Downloading Packages:
|
||||
(1/8): libXpm-3.5.10-2.el6.x86_64.rpm | 51 kB 00:00
|
||||
(2/8): php-5.3.3-23.el6_4.x86_64.rpm | 1.1 MB 00:00
|
||||
(3/8): php-cli-5.3.3-23.el6_4.x86_64.rpm | 2.2 MB 00:00
|
||||
(4/8): php-common-5.3.3-23.el6_4.x86_64.rpm | 524 kB 00:00
|
||||
(5/8): php-gd-5.3.3-23.el6_4.x86_64.rpm | 106 kB 00:00
|
||||
(6/8): php-pdo-5.3.3-23.el6_4.x86_64.rpm | 75 kB 00:00
|
||||
(7/8): php-pear-1.9.4-4.el6.noarch.rpm | 393 kB 00:00
|
||||
(8/8): php-xml-5.3.3-23.el6_4.x86_64.rpm | 103 kB 00:00
|
||||
———————————————————————-
|
||||
Total 2.9 MB/s | 4.5 MB 00:01
|
||||
Running rpm_check_debug
|
||||
Running Transaction Test
|
||||
Transaction Test Succeeded
|
||||
Running Transaction
|
||||
Installing : php-common-5.3.3-23.el6_4.x86_64 1/8
|
||||
Installing : php-cli-5.3.3-23.el6_4.x86_64 2/8
|
||||
Installing : libXpm-3.5.10-2.el6.x86_64 3/8
|
||||
Installing : php-gd-5.3.3-23.el6_4.x86_64 4/8
|
||||
Installing : 1:php-pear-1.9.4-4.el6.noarch 5/8
|
||||
Installing : php-5.3.3-23.el6_4.x86_64 6/8
|
||||
Installing : php-xml-5.3.3-23.el6_4.x86_64 7/8
|
||||
Installing : php-pdo-5.3.3-23.el6_4.x86_64 8/8
|
||||
Verifying : 1:php-pear-1.9.4-4.el6.noarch 1/8
|
||||
Verifying : php-xml-5.3.3-23.el6_4.x86_64 2/8
|
||||
Verifying : php-common-5.3.3-23.el6_4.x86_64 3/8
|
||||
Verifying : libXpm-3.5.10-2.el6.x86_64 4/8
|
||||
Verifying : php-cli-5.3.3-23.el6_4.x86_64 5/8
|
||||
Verifying : php-5.3.3-23.el6_4.x86_64 6/8
|
||||
Verifying : php-pdo-5.3.3-23.el6_4.x86_64 7/8
|
||||
Verifying : php-gd-5.3.3-23.el6_4.x86_64 8/8
|
||||
|
||||
Installed:
|
||||
php.x86_64 0:5.3.3-23.el6_4 php-gd.x86_64 0:5.3.3-23.el6_4 php-pdo.x86_64 0:5.3.3-23.el6_4
|
||||
php-pear.noarch 1:1.9.4-4.el6 php-xml.x86_64 0:5.3.3-23.el6_4
|
||||
|
||||
Dependency Installed:
|
||||
libXpm.x86_64 0:3.5.10-2.el6 php-cli.x86_64 0:5.3.3-23.el6_4 php-common.x86_64 0:5.3.3-23.el6_4
|
||||
|
||||
Complete!
|
||||
|
||||
### Install package using YUM ###
|
||||
|
||||
A package can be installed using yum install command as below:
|
||||
|
||||
# yum install httpd
|
||||
|
||||
Loaded plugins: amazon-id, rhui-lb, security
|
||||
Setting up Install Process
|
||||
Resolving Dependencies
|
||||
–> Running transaction check
|
||||
—> Package httpd.x86_64 0:2.2.15-29.el6_4 will be installed
|
||||
–> Processing Dependency: httpd-tools = 2.2.15-29.el6_4 for package: httpd-2.2.15-29.el6_4.x86_64
|
||||
–> Processing Dependency: apr-util-ldap for package: httpd-2.2.15-29.el6_4.x86_64
|
||||
–> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.2.15-29.el6_4.x86_64
|
||||
–> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.2.15-29.el6_4.x86_64
|
||||
–> Running transaction check
|
||||
—> Package apr.x86_64 0:1.3.9-5.el6_2 will be installed
|
||||
—> Package apr-util.x86_64 0:1.3.9-3.el6_0.1 will be installed
|
||||
—> Package apr-util-ldap.x86_64 0:1.3.9-3.el6_0.1 will be installed
|
||||
—> Package httpd-tools.x86_64 0:2.2.15-29.el6_4 will be installed
|
||||
–> Finished Dependency Resolution
|
||||
|
||||
Dependencies Resolved
|
||||
|
||||
=============================================================================
|
||||
Package Arch Version Repository Size
|
||||
=============================================================================
|
||||
Installing:
|
||||
httpd x86_64 2.2.15-29.el6_4 rhui-REGION-rhel-server-releases 821 k
|
||||
Installing for dependencies:
|
||||
apr x86_64 1.3.9-5.el6_2 rhui-REGION-rhel-server-releases 123 k
|
||||
apr-util x86_64 1.3.9-3.el6_0.1 rhui-REGION-rhel-server-releases 87 k
|
||||
apr-util-ldap x86_64 1.3.9-3.el6_0.1 rhui-REGION-rhel-server-releases 15 k
|
||||
httpd-tools x86_64 2.2.15-29.el6_4 rhui-REGION-rhel-server-releases 73 k
|
||||
|
||||
Transaction Summary
|
||||
==============================================================================
|
||||
Install 5 Package(s)
|
||||
|
||||
Total download size: 1.1 M
|
||||
Installed size: 3.6 M
|
||||
Is this ok [y/N]: y
|
||||
|
||||
As you can see yum added additional packages with httpd installation. This is called the dependency resolution done by yum.
|
||||
|
||||
If you want yum not to prompt for the [y/N] option. Use **yum install -y httpd**
|
||||
|
||||
**Update an existing package using yum update command.**
|
||||
|
||||
# yum update httpd
|
||||
Loaded plugins: amazon-id, rhui-lb, security
|
||||
Setting up Update Process
|
||||
No Packages marked for Update
|
||||
|
||||
That means the httpd package is the latest version in the yum’s repository.
|
||||
|
||||
**Update all packages on the server.**
|
||||
|
||||
# yum update
|
||||
|
||||
the above command will update all the packages including kernel package to the latest version that means your OS will be updated to the latest provided by RHEL.
|
||||
|
||||
### Download RPM without installing ###
|
||||
|
||||
Use yum to download RPM package from RHN or CentOS repository without installing it. You have to install a plugin for yum first to have yum download the rpm only. The utility name is yum-downloadonly and can be installed through yum as below:
|
||||
|
||||
# yum install yum-downloadonly
|
||||
Loaded plugins: amazon-id, rhui-lb, security
|
||||
Setting up Install Process
|
||||
Resolving Dependencies
|
||||
–> Running transaction check
|
||||
—> Package yum-plugin-downloadonly.noarch 0:1.1.30-14.el6 will be installed
|
||||
–> Finished Dependency Resolution
|
||||
|
||||
Dependencies Resolved
|
||||
|
||||
===========================================================================
|
||||
Package Arch Version Repository Size
|
||||
===========================================================================
|
||||
Installing:
|
||||
yum-plugin-downloadonly noarch 1.1.30-14.el6 rhui-REGION-rhel-server-releases 20 k
|
||||
|
||||
Transaction Summary
|
||||
===========================================================================
|
||||
Install 1 Package(s)
|
||||
|
||||
Total download size: 20 k
|
||||
Installed size: 21 k
|
||||
Is this ok [y/N]: y
|
||||
Downloading Packages:
|
||||
yum-plugin-downloadonly-1.1.30-14.el6.noarch.rpm | 20 kB 00:00
|
||||
Running rpm_check_debug
|
||||
Running Transaction Test
|
||||
Transaction Test Succeeded
|
||||
Running Transaction
|
||||
Installing : yum-plugin-downloadonly-1.1.30-14.el6.noarch 1/1
|
||||
Verifying : yum-plugin-downloadonly-1.1.30-14.el6.noarch 1/1
|
||||
|
||||
Installed:
|
||||
yum-plugin-downloadonly.noarch 0:1.1.30-14.el6
|
||||
|
||||
Complete!
|
||||
|
||||
Now you can just download a package from repository without installing it by using this command:
|
||||
|
||||
# yum install httpd-devel –downloadonly
|
||||
|
||||
By default packages are downloaded to **/var/cache/yum/<arch\>** directory but you can download them a specified location by adding another option to yum command
|
||||
|
||||
# yum install httpd-devel –downloadonly –downloaddir=/opt
|
||||
|
||||
If you have a rpm of a package but you don’t have the dependencies and you do not know where to get that. you can still have yum to install that rpm and get the required dependencies from the repository. Let’s install the httpd-devel-2.2.15-29.el6_4.x86_64 RPM that we just downloaded.
|
||||
|
||||
# yum localinstall /opt/httpd-devel-2.2.15-29.el6_4.x86_64.rpm
|
||||
|
||||
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
|
||||
Setting up Local Package Process
|
||||
Examining /opt/httpd-devel-2.2.15-29.el6_4.x86_64.rpm: httpd-devel-2.2.15-29.el6_4.x86_64
|
||||
Marking /opt/httpd-devel-2.2.15-29.el6_4.x86_64.rpm to be installed
|
||||
Resolving Dependencies
|
||||
–> Running transaction check
|
||||
—> Package httpd-devel.x86_64 0:2.2.15-29.el6_4 will be installed
|
||||
–> Processing Dependency: apr-devel for package: httpd-devel-2.2.15-29.el6_4.x86_64
|
||||
–> Processing Dependency: apr-util-devel for package: httpd-devel-2.2.15-29.el6_4.x86_64
|
||||
–> Running transaction check
|
||||
—> Package apr-devel.x86_64 0:1.3.9-5.el6_2 will be installed
|
||||
—> Package apr-util-devel.x86_64 0:1.3.9-3.el6_0.1 will be installed
|
||||
–> Processing Dependency: openldap-devel for package: apr-util-devel-1.3.9-3.el6_0.1.x86_64
|
||||
–> Processing Dependency: expat-devel for package: apr-util-devel-1.3.9-3.el6_0.1.x86_64
|
||||
–> Processing Dependency: db4-devel for package: apr-util-devel-1.3.9-3.el6_0.1.x86_64
|
||||
–> Running transaction check
|
||||
—> Package db4-devel.x86_64 0:4.7.25-18.el6_4 will be installed
|
||||
–> Processing Dependency: db4-cxx = 4.7.25-18.el6_4 for package: db4-devel-4.7.25-18.el6_4.x86_64
|
||||
–> Processing Dependency: db4 = 4.7.25-18.el6_4 for package: db4-devel-4.7.25-18.el6_4.x86_64
|
||||
–> Processing Dependency: libdb_cxx-4.7.so()(64bit) for package: db4-devel-4.7.25-18.el6_4.x86_64
|
||||
—> Package expat-devel.x86_64 0:2.0.1-11.el6_2 will be installed
|
||||
—> Package openldap-devel.x86_64 0:2.4.23-32.el6_4.1 will be installed
|
||||
–> Processing Dependency: cyrus-sasl-devel >= 2.1 for package: openldap-devel-2.4.23-32.el6_4.1.x86_64
|
||||
–> Running transaction check
|
||||
—> Package cyrus-sasl-devel.x86_64 0:2.1.23-13.el6_3.1 will be installed
|
||||
—> Package db4.x86_64 0:4.7.25-17.el6 will be updated
|
||||
–> Processing Dependency: db4 = 4.7.25-17.el6 for package: db4-utils-4.7.25-17.el6.x86_64
|
||||
—> Package db4.x86_64 0:4.7.25-18.el6_4 will be an update
|
||||
—> Package db4-cxx.x86_64 0:4.7.25-18.el6_4 will be installed
|
||||
–> Running transaction check
|
||||
—> Package db4-utils.x86_64 0:4.7.25-17.el6 will be updated
|
||||
—> Package db4-utils.x86_64 0:4.7.25-18.el6_4 will be an update
|
||||
–> Finished Dependency Resolution
|
||||
|
||||
Dependencies Resolved
|
||||
|
||||
=============================================================================
|
||||
Package Arch Version Repository Size
|
||||
=============================================================================
|
||||
Installing:
|
||||
httpd-devel x86_64 2.2.15-29.el6_4 /httpd-devel-2.2.15-29.el6_4.x86_64 526 k
|
||||
Installing for dependencies:
|
||||
apr-devel x86_64 1.3.9-5.el6_2 rhui-REGION-rhel-server-releases 176 k
|
||||
apr-util-devel x86_64 1.3.9-3.el6_0.1 rhui-REGION-rhel-server-releases 69 k
|
||||
cyrus-sasl-devel x86_64 2.1.23-13.el6_3.1 rhui-REGION-rhel-server-releases 302 k
|
||||
db4-cxx x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 588 k
|
||||
db4-devel x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 6.6 M
|
||||
expat-devel x86_64 2.0.1-11.el6_2 rhui-REGION-rhel-server-releases 120 k
|
||||
openldap-devel x86_64 2.4.23-32.el6_4.1 rhui-REGION-rhel-server-releases 1.1 M
|
||||
Updating for dependencies:
|
||||
db4 x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 563 k
|
||||
db4-utils x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 130 k
|
||||
|
||||
Transaction Summary
|
||||
=======================================================================
|
||||
Install 8 Package(s)
|
||||
Upgrade 2 Package(s)
|
||||
|
||||
Total size: 10 M
|
||||
Is this ok [y/N]: y
|
||||
Downloading Packages:
|
||||
Running rpm_check_debug
|
||||
Running Transaction Test
|
||||
Transaction Test Succeeded
|
||||
Running Transaction
|
||||
Updating : db4-4.7.25-18.el6_4.x86_64 1/12
|
||||
Installing : apr-devel-1.3.9-5.el6_2.x86_64 2/12
|
||||
Installing : expat-devel-2.0.1-11.el6_2.x86_64 3/12
|
||||
Installing : db4-cxx-4.7.25-18.el6_4.x86_64 4/12
|
||||
Installing : db4-devel-4.7.25-18.el6_4.x86_64 5/12
|
||||
Installing : cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64 6/12
|
||||
Installing : openldap-devel-2.4.23-32.el6_4.1.x86_64 7/12
|
||||
Installing : apr-util-devel-1.3.9-3.el6_0.1.x86_64 8/12
|
||||
Installing : httpd-devel-2.2.15-29.el6_4.x86_64 9/12
|
||||
Updating : db4-utils-4.7.25-18.el6_4.x86_64 10/12
|
||||
Cleanup : db4-utils-4.7.25-17.el6.x86_64 11/12
|
||||
Cleanup : db4-4.7.25-17.el6.x86_64 12/12
|
||||
Verifying : apr-devel-1.3.9-5.el6_2.x86_64 1/12
|
||||
Verifying : cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64 2/12
|
||||
Verifying : apr-util-devel-1.3.9-3.el6_0.1.x86_64 3/12
|
||||
Verifying : db4-cxx-4.7.25-18.el6_4.x86_64 4/12
|
||||
Verifying : httpd-devel-2.2.15-29.el6_4.x86_64 5/12
|
||||
Verifying : openldap-devel-2.4.23-32.el6_4.1.x86_64 6/12
|
||||
Verifying : expat-devel-2.0.1-11.el6_2.x86_64 7/12
|
||||
Verifying : db4-devel-4.7.25-18.el6_4.x86_64 8/12
|
||||
Verifying : db4-4.7.25-18.el6_4.x86_64 9/12
|
||||
Verifying : db4-utils-4.7.25-18.el6_4.x86_64 10/12
|
||||
Verifying : db4-4.7.25-17.el6.x86_64 11/12
|
||||
Verifying : db4-utils-4.7.25-17.el6.x86_64 12/12
|
||||
|
||||
Installed:
|
||||
httpd-devel.x86_64 0:2.2.15-29.el6_4
|
||||
|
||||
Dependency Installed:
|
||||
apr-devel.x86_64 0:1.3.9-5.el6_2 apr-util-devel.x86_64 0:1.3.9-3.el6_0.1
|
||||
cyrus-sasl-devel.x86_64 0:2.1.23-13.el6_3.1 db4-cxx.x86_64 0:4.7.25-18.el6_4
|
||||
db4-devel.x86_64 0:4.7.25-18.el6_4 expat-devel.x86_64 0:2.0.1-11.el6_2
|
||||
openldap-devel.x86_64 0:2.4.23-32.el6_4.1
|
||||
|
||||
Dependency Updated:
|
||||
db4.x86_64 0:4.7.25-18.el6_4 db4-utils.x86_64 0:4.7.25-18.el6_4
|
||||
|
||||
Complete!
|
||||
|
||||
### Removing packages using yum. ###
|
||||
|
||||
yum remove Remove a package.
|
||||
|
||||
# yum remove httpd
|
||||
Failed to set locale, defaulting to C
|
||||
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
|
||||
Setting up Remove Process
|
||||
Resolving Dependencies
|
||||
–> Running transaction check
|
||||
—> Package httpd.x86_64 0:2.2.15-29.el6_4 will be erased
|
||||
–> Processing Dependency: httpd-mmn = 20051115 for package: php-5.3.3-23.el6_4.x86_64
|
||||
–> Processing Dependency: httpd = 2.2.15-29.el6_4 for package: httpd-devel-2.2.15-29.el6_4.x86_64
|
||||
–> Running transaction check
|
||||
—> Package httpd-devel.x86_64 0:2.2.15-29.el6_4 will be erased
|
||||
—> Package php.x86_64 0:5.3.3-23.el6_4 will be erased
|
||||
–> Finished Dependency Resolution
|
||||
|
||||
Dependencies Resolved
|
||||
|
||||
========================================================================
|
||||
Package Arch Version Repository Size
|
||||
========================================================================
|
||||
Removing:
|
||||
httpd x86_64 2.2.15-29.el6_4 @rhui-REGION-rhel-server-releases 2.9 M
|
||||
Removing for dependencies:
|
||||
httpd-devel x86_64 2.2.15-29.el6_4 @/httpd-devel-2.2.15-29.el6_4.x86_64 526 k
|
||||
php x86_64 5.3.3-23.el6_4 @rhui-REGION-rhel-server-releases 3.5 M
|
||||
|
||||
Transaction Summary
|
||||
==========================================================================
|
||||
Remove 3 Package(s)
|
||||
|
||||
Installed size: 7.0 M
|
||||
Is this ok [y/N]: y
|
||||
Downloading Packages:
|
||||
Running rpm_check_debug
|
||||
Running Transaction Test
|
||||
Transaction Test Succeeded
|
||||
Running Transaction
|
||||
Erasing : httpd-devel-2.2.15-29.el6_4.x86_64 1/3
|
||||
Erasing : php-5.3.3-23.el6_4.x86_64 2/3
|
||||
Erasing : httpd-2.2.15-29.el6_4.x86_64 3/3
|
||||
Verifying : httpd-2.2.15-29.el6_4.x86_64 1/3
|
||||
Verifying : httpd-devel-2.2.15-29.el6_4.x86_64 2/3
|
||||
Verifying : php-5.3.3-23.el6_4.x86_64 3/3
|
||||
|
||||
Removed:
|
||||
httpd.x86_64 0:2.2.15-29.el6_4
|
||||
|
||||
Dependency Removed:
|
||||
httpd-devel.x86_64 0:2.2.15-29.el6_4 php.x86_64 0:5.3.3-23.el6_4
|
||||
|
||||
Complete!
|
||||
|
||||
### List all installed packages ###
|
||||
|
||||
If you want to list all the installed packages then you can use yum list installed command. This is useful in combination with grep or to check whether a specific package has been installed. This is similar to query installed packages with rpm -qa command.
|
||||
|
||||
# yum list installed
|
||||
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
|
||||
Installed Packages
|
||||
ConsoleKit.x86_64 0.4.1-3.el6 @koji-override-0/$releasever
|
||||
ConsoleKit-libs.x86_64 0.4.1-3.el6 @koji-override-0/$releasever
|
||||
MAKEDEV.x86_64 3.24-6.el6 @koji-override-0/$releasever
|
||||
PyYAML.x86_64 3.10-3.1.el6 @koji-override-0/$releasever
|
||||
Red_Hat_Enterprise_Linux-Release_Notes-6-en-US.noarch
|
||||
4-2.el6 @koji-override-0/$releasever
|
||||
SDL.x86_64 1.2.14-3.el6 @koji-override-0/$releasever
|
||||
abrt.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
abrt-addon-ccpp.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
abrt-addon-kerneloops.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
abrt-addon-python.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
abrt-cli.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
abrt-libs.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
abrt-tui.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
|
||||
acl.x86_64 2.2.49-6.el6 @koji-override-0/$releasever
|
||||
acpid.x86_64 1.0.10-2.1.el6 @koji-override-0/$releasever
|
||||
aic94xx-firmware.noarch 30-2.el6 @koji-override-0/$releasever
|
||||
.
|
||||
.
|
||||
Output Truncated.
|
||||
|
||||
### List the available repository from which packages are being queried, installed and updated. ###
|
||||
|
||||
# yum repolist
|
||||
|
||||
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
|
||||
repo id repo name status
|
||||
rhui-REGION-client-config-server-6 Red Hat Update Infrastructure 2.0 Client Configuration Server 6 4
|
||||
rhui-REGION-rhel-server-releases Red Hat Enterprise Linux Server 6 (RPMs) 10994
|
||||
rhui-REGION-rhel-server-releases-optional Red Hat Enterprise Linux Server 6 Optional (RPMs) 6250
|
||||
repolist: 17248
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://linoxide.com/linux-command/package-management-yum-redhat-linux/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
@ -0,0 +1,38 @@
|
||||
Linux Desktop In The Enterprise: Ubuntu Vs. Windows
|
||||
================================================================================
|
||||
The "year of the Linux desktop" has been prophesied by Linux supporters almost every year for the last decade. This was once a lofty goal in the Microsoft-dominated enterprise, but times are changing. Linux has grown into a formidable competitor in the smartphone and cloud computing markets, which has caught Microsoft off guard. More importantly, Google, IBM, Red Hat, Facebook, and Netflix have made huge investments into Linux innovations.
|
||||
|
||||
Now, with shrinking technology budgets and rising Microsoft licensing fees, it's time for IT to seriously consider desktop Linux deployment as an alternative to Windows. The timing for this couldn't be better: Windows 8.1 was just released, as was the latest version of Ubuntu, 13.10. Windows XP has just five months of support left, so companies need to make the switch to something new. Ubuntu may just have what companies need to support their desktop OS needs. I'll look at various considerations for making the Linux desktop switch, including training and support, as well as potential complications.
|
||||
|
||||
I know that Ubuntu has lost some of the favor it once enjoyed in the open source community. Canonical, the creators of Ubuntu, have made some unpopular choices, including changing the display manager -- the base component of the graphical interface in Linux-- to the internally developed Mir instead of Wayland. However, Ubuntu remains completely open source and offers the most painless install of any Linux distribution or even Windows version, for that matter. Canonical also offers paid support, which may be needed in enterprise environments.
|
||||
|
||||
There has always been the argument that end users will need retraining if they switch over to a new desktop interface. Microsoft's controversial decision to overhaul the familiar interface for Windows 8.1 now requires just as much training as switching to Linux. Ubuntu's Unity desktop has evolved into a user friendly interface that is arguably more easily understood by end users than Windows 8.1.
|
||||
|
||||
For example, compare how a user shuts down the system in each operating system. In all recent versions of Ubuntu, it starts with one click in the right corner of the screen, where the symbol for on-off is located. A menu drops down and one more click shuts down the machine. Windows 8.1 requires a right-click on the Start button, where a menu drops down allowing for a shutdown. This was a vast improvement over Windows 8, which required a trip to the charms bar, but still not as obvious as an icon located directly on the screen.
|
||||
|
||||
End-user training for applications is a less complex task nowadays, thanks to the Windows versions of many popular open source applications. Users may already be familiar with Firefox, LibreOffice, Pidgin, and VLC Media Player on Windows. Commercial applications used in business, such as Skype and Adobe Acrobat, function just like their Windows equivalents. Cloud-based applications such as Google Drive or Microsoft Office 365 work well on Ubuntu.
|
||||
|
||||
Legacy Windows applications can be accessed through the familiar Citrix client or open source RDP clients. Companies also can use open source virtualization products such as VirtualBox to run the most stubborn legacy Windows applications.
|
||||
|
||||
On the support front, many technicians will remember the earlier days of Linux when hardware support was extremely limited. That simply is not the case anymore.
|
||||
|
||||
Linux hardware support is oftentimes better than the latest versions of Windows. Many hardware vendors have been dropping driver support for newer versions of Windows. The open source drivers in Linux can be kept up to date by anyone in the developer community, so a lot of older hardware is fully supported in the latest versions of Ubuntu. This fact, plus Ubuntu's lower system requirements, will allow companies to extend the life of hardware once destined for the recycling bin.
|
||||
|
||||
While there are upsides to a Linux desktop replacement program, there are some potential difficulties companies should consider. While many technicians have already been using Linux or will be motivated by the prospect of learning new skills, there also will be technicians who have spent a lot of time developing a comfort level managing Windows and may be reluctant to embrace the change.
|
||||
|
||||
Citing salary trends is one way to address this potential issue. The salaries of positions with Linux skills requirements are rising at nearly double the rate of other technical professionals, according to Dice.
|
||||
|
||||
Companies under stringent compliance requirements may have difficulties switching over to Linux. For example, HIPAA requires encryption that meets FIPS-140-2 requirements. Most open source encryption projects do not have sponsors to get them through the NIST certification to meet this requirement. Open source may actually be more secure than proprietary software because of the number of people that have reviewed the source code, but surprisingly that doesn't matter in the world of compliance.
|
||||
|
||||
Businesses need to understand their compliance requirements and develop a plan for training IT staff before deciding to move forward with a full conversion. But overall, Ubuntu Linux has matured into a viable alternative to proprietary operating systems in the enterprise. The effort companies put into a Linux desktop replacement program will be worth the savings in licensing fees. Next year may finally be the “year of the Linux desktop.”
|
||||
|
||||
|
||||
> Joseph Granneman has more than 20 years of technology experience, primarily focused in health care information technology. He is CIO for Rockford Orthopedic Associates in Rockford, Ill., and an active independent author, presenter and professor in the health care information technology and information security fields. Granneman has been active in many standards groups, including developing the early frameworks for Health Information Exchange as part of the Health Information Security and Privacy Security Working Group for Illinois. He was also a volunteer for the Certification Commission for Health Information Technology (CCHIT) Security Working Group, which developed the information security standards for ARRA certification of electronic medical records.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.networkcomputing.com/data-networking-management/linux-desktop-in-the-enterprise-ubuntu-v/240163564
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
Loading…
Reference in New Issue
Block a user