Logotype
web hosting
GEEKS
-
-
Providers
Recommended Shared Hosting Providers
Browse allRecommended Dedicated Hosting Providers
Browse allRecommended VPS Hosting Providers
Browse allRecommended Reseller Hosting Providers
Browse allRecommended Cloud Hosting Providers
Browse allRecommended Wordpress Hosting Providers
Browse all - Reviews
- Guides
- Tools
- Blog
- contact us
-
Providers
- login / Register Submit review
Skip to content
Category: EPEL
How to Install EPEL Yum Repository on Linux CentOS 7 / RHEL 7
Epel yum repository is an open source centos yum repository or rpm repository for developers and system administrators to perform the installation of RPM packages via yum on their virtual private server (VPS) or dedicated server.
EPEL yum repository is redhat yum repository for CentOS and additional yum repository for the existing CentOS repository.
It provides 100 % high quality software packages for Linux distributions, including RHEL (Red Hat Enterprise Linux), CentOS and Debian, and all packages maintained by Fedora repo team.
1. Prepare EPEL repository for RHEL 7/CentOS 7 64 bit (epel centos 7/epel rhel 7) :
# sudo rpm --import https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-7 # # sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-9.noarch.rpm
Example :
# sudo rpm --import https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-7 # sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-9.noarch.rpm Retrieving https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-9.noarch.rpm Preparing... ################################# [100%] Updating / installing... 1:epel-release-7-9 ################################# [100%]
In CentOS 7, an alternative way to install the EPEL repo is by using the command yum :
# sudo yum install epel-release -y
2. Command to verify that the EPEL repository is enabled.
# sudo yum repolist
Sample output :
# sudo yum repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.linode.com * epel: ftp.osuosl.org * extras: mirrors.linode.com * updates: mirrors.linode.com repo id repo name status base/7/x86_64 CentOS-7 - Base 9,363 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 11,046 extras/7/x86_64 CentOS-7 - Extras 200 nginx/x86_64 nginx repo 41 updates/7/x86_64 CentOS-7 - Updates 438 varnish-4.1/x86_64 Varnish Cache 4.1 for Enterprise Linux 31 repolist: 21,119
3. Install httpd package using epel repo option –enablerepo=epel :
# sudo yum --enablerepo=epel install httpd
How to Enable EPEL and Remi Repository into CentOS 6
EPEL stand for Extra Packages for Enterprise Linux. EPEL repository is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Enterprise Linux(OEL). Remi repository is a yum repository maintained by a French dude – Remi Collet. This post describe the basic steps to prepare and install the additional CentOS packages with EPEL and Remi Repository into CentOS 6.
EPEL Repository
rpm --import https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-6 rpm -Uvh https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
Remi Repository
rpm --import http://rpms.famillecollet.com/RPM-GPG-KEY-remi rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm
Example :
[root@centos6 ~]# rpm --import https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-6 [root@centos6 ~]# rpm -Uvh https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm Retrieving https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
[root@centos6 ~]# rpm --import http://rpms.famillecollet.com/RPM-GPG-KEY-remi [root@centos6 ~]# rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm Retrieving http://rpms.famillecollet.com/enterprise/remi-release-6.rpm Preparing... ########################################### [100%] 1:remi-release ########################################### [100%]
Example of EPEl and Remi repo usage :
[root@centos6 ~]# yum --enablerepo=epel install httpd -y
[root@centos6 ~]# yum --enablerepo=remi install httpd -y
How to Install and Configure 389 LDAP Directory Server on CentOS 6.5
A directory server provides a centralized directory service for your organization. It is alternative to windows active directory. This post will describes how to install and configure 389 LDAP Directory Server with a basic Lightweight Directory Access Protocol (LDAP) directory implementation. 389 Directory Server was formerly known as the Fedora Directory Server and it is an enterprise-class open source LDAP. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project.
Steps to Install and Configure 389 LDAP Directory Server
TCP and Files system Tuning :
a) Decrease the time default value for tcp_keepalive_time connection. Edit the /etc/sysctl.conf file and add the following lines to the bottom of sysctl.conf ”
[root@ldap ~]# echo "net.ipv4.tcp_keepalive_time = 300" >> /etc/sysctl.conf b) Increase number of local system ports available by editing this parameter in the /etc/sysctl.conf file :
[root@ldap ~]# echo "net.ipv4.ip_local_port_range = 1024 65000" >> /etc/sysctl.conf
c) Increase the file descriptors by running these commands:
[root@ldap ~]# echo "64000" > /proc/sys/fs/file-max [root@ldap-05 ~]# echo "fs.file-max = 64000" >> /etc/sysctl.conf
d) Increase ulimit in /etc/profile :
[root@ldap ~]# echo "ulimit -n 8192" >> /etc/profile
389 Installation :
1. Prepare EPEL Repository on CentOS 6 :
How to Prepare EPEL Repository on CentOS 6
What packages and versions are available in EPEL?
You can take a look on any of the available EPEL mirrors from our mirror list
Alternately, you can browse the package set using repoview:
2. Configure hostname, FQDN and host file has been configured correctly :
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.0.5 ldap.ehowstuff.local
3. Make sure selinux is disabled :
Disable SELinux on CentOS 6.5
4. Install the 389 Directory Server packages :
[root@ldap ~]# yum install 389-ds -y
5. Fix Error: command ‘getsebool httpd_can_connect_ldap’ failed – output [getsebool: SELinux is disabled :
[root@ldap ~]# mkdir ~/bin [root@ldap ~]# vi ~/bin/getsebool
#!/bin/sh echo on exit 0
[root@ldap ~]# vi ~/bin/setsebool
#!/bin/sh exit 0
[root@ldap ~]# chmod +x ~/bin/*sebool
6. Run setup script to start configure the ldap service :
[root@ldap ~]# PATH=~/bin:$PATH setup-ds-admin.pl
==============================================================================
This program will set up the 389 Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
Would you like to continue with set up? [yes]:
==============================================================================
Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
389 Directory Server system tuning analysis version 23-FEBRUARY-2012.
NOTICE : System is x86_64-unknown-linux2.6.32-431.el6.x86_64 (1 processor).
Would you like to continue? [yes]:
==============================================================================
Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
Choose a setup type [2]:
==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
.
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly. If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:
General.FullMachineName=your.hostname.domain.name
Computer name [ldap.ehowstuff.local]:
WARNING: There are problems with the hostname.
Hostname 'ldap.ehowstuff.local' is valid, but none of the IP addresses
resolve back to ldap.ehowstuff.local
- address 192.168.0.5 resolves to host centos6.5.ehowstuff.local
Please check the spelling of the hostname and/or your network configuration.
If you proceed with this hostname, you may encounter problems.
Do you want to proceed with hostname 'ldap.ehowstuff.local'? [no]: yes
==============================================================================
The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
System User [nobody]:
System Group [nobody]:
==============================================================================
Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
.(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
Do you want to register this software with an existing
configuration directory server? [no]:
==============================================================================
Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
Configuration directory server
administrator ID [admin]:
Password:
Password (confirm):
==============================================================================
The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
Administration Domain [ehowstuff.local]:
==============================================================================
The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
Directory server network port [389]:
==============================================================================
Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
Directory server identifier [ldap]:
==============================================================================
The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
Suffix [dc=ehowstuff, dc=local]:
==============================================================================
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.
Directory Manager DN [cn=Directory Manager]:
Password:
Password (confirm):
==============================================================================
The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
Administration port [9830]:
==============================================================================
The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
Are you ready to set up your servers? [yes]:
Creating directory server . . .
Warning: Hostname ldap.ehowstuff.local is valid, but none of the IP addresses
resolve back to ldap.ehowstuff.local
address 192.168.0.5 resolves to host centos6.5.ehowstuff.local
Your new DS instance 'ldap' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server reconfiguration . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
Starting admin server . . .
output: Starting dirsrv-admin:
output: [ OK ]
The admin server was successfully started.
Admin server was successfully reconfigured and started.
Exiting . . .
Log file is '/tmp/setupGwS8hs.log'
7. Start dirsrv and dirsrv-admin service :
[root@ldap ~]# /etc/init.d/dirsrv start [root@ldap ~]# /etc/init.d/dirsrv-admin start
8. Make dirsrv and dirsrv-admin service auto start at boot :
[root@ldap ~]# chkconfig dirsrv on [root@ldap ~]# chkconfig dirsrv-admin on
9. Configure Iptables to allow server listen on port 22, 389 and 9830 :
# Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 9830 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT
Restart iptables to take effect the changes :
[root@ldap ~]# service iptables restart iptables: Applying firewall rules: [ OK ]
10. Verify port listen by the server using netstat :
[root@ldap ~]# netstat -plunt | grep LISTEN tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1083/rpcbind tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 1125/perl tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1116/sshd tcp 0 0 0.0.0.0:9830 0.0.0.0:* LISTEN 1508/httpd.worker tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1126/php-fpm tcp 0 0 :::8140 :::* LISTEN 1161/httpd tcp 0 0 :::111 :::* LISTEN 1083/rpcbind tcp 0 0 :::80 :::* LISTEN 1161/httpd tcp 0 0 :::22 :::* LISTEN 1116/sshd tcp 0 0 :::443 :::* LISTEN 1161/httpd tcp 0 0 :::8443 :::* LISTEN 1161/httpd tcp 0 0 :::389 :::* LISTEN 1391/./ns-slapd
11. Verify port listen by the server and opened by iptables firewall :
[root@ldap ~]# iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:389 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:9830 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) target prot opt source destination REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) target prot opt source destination
How to Install and Configure 389 LDAP Directory Server on CentOS 6.4
389 Directory Server is an enterprise-class open source Lightweight Directory Access Protocol (LDAP) server for Linux and based on Fedora Directory Server. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project. This steps has been tested on CentOS 6.4 x86_64 and may work on other version of CentOS as well.
2. Install 389-ds file :
[root@centos64 ~]# yum install 389-ds -y
3. Enable SELINUX :
[root@centos64 ~]# sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Mode from config file: enforcing Policy version: 24 Policy from config file: targeted
4. Configure hostname, FQDN and host file has been configured correctly :
[root@centos64 ~]# hostname centos64.ehowstuff.local
[root@centos64 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.2.64 centos64.ehowstuff.local centos64
5. To install 389 LDAP, run the configuration script :
[root@centos64 ~]# /usr/sbin/setup-ds-admin.pl
==============================================================================
This program will set up the 389 Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
Would you like to continue with set up? [yes]:
==============================================================================
Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
389 Directory Server system tuning analysis version 23-FEBRUARY-2012.
NOTICE : System is x86_64-unknown-linux2.6.32-358.2.1.el6.x86_64 (2 processors).
NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes). This may cause temporary server congestion from lost
client connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
WARNING : The warning messages above should be reviewed before proceeding.
Would you like to continue? [no]: yes
==============================================================================
Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
Choose a setup type [2]:
==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
.
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly. If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:
General.FullMachineName=your.hostname.domain.name
Computer name [centos64.ehowstuff.local]:
==============================================================================
The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
System User [nobody]:
System Group [nobody]:
==============================================================================
Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
.(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
Do you want to register this software with an existing
configuration directory server? [no]:
==============================================================================
Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
Configuration directory server
administrator ID [admin]:
Password:
Password (confirm):
==============================================================================
The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
Administration Domain [ehowstuff.local]:
==============================================================================
The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
Directory server network port [389]:
==============================================================================
Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
Directory server identifier [centos64]:
==============================================================================
The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
Suffix [dc=ehowstuff, dc=local]:
==============================================================================
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.
Directory Manager DN [cn=Directory Manager]:
Password:
Password (confirm):
==============================================================================
The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
Administration port [9830]:
==============================================================================
The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
Are you ready to set up your servers? [yes]:
Creating directory server . . .
Your new DS instance 'centos64' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server creation . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
Starting admin server . . .
output: Starting dirsrv-admin:
output: [ OK ]
The admin server was successfully started.
Admin server was successfully created, configured, and started.
Exiting . . .
Log file is '/tmp/setupDJucbG.log'
6. Start dirsrv and dirsrv-admin service :
[root@centos64 ~]# /etc/init.d/dirsrv start
Starting dirsrv:
centos64... [ OK ]
[root@centos64 ~]# /etc/init.d/dirsrv-admin start
Starting dirsrv-admin:
[ OK ]
7. Make dirsrv and dirsrv-admin service auto start at boot :
[root@centos64 ~]# chkconfig dirsrv on [root@centos64 ~]# chkconfig dirsrv-admin on
8. Check dirsrv and dirsrv-admin service status :
[root@centos64 ~]# /etc/init.d/dirsrv-admin status dirsrv-admin (pid 1409) is running... [root@centos64 ~]# /etc/init.d/dirsrv status dirsrv centos64 (pid 1317) is running...
How to Configure EPEL Repository on CentOS 6.4 x86_64
EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. By using EPEL repository you can install some other third party software such as nagios, or bugzilla, phpmyadmin, or any other standard open source software just using yum command. These repositories are not officially supported by CentOS, but this repository provide much more current versions of popular PHP or MySQL applications. This post describe how you can prepare EPEL Repository on CentOS 6.4 x86_64.
1. Download and import the GPG keys for EPEL software packages:
[root@centos64 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-6 [root@centos64 ~]# rpm --import RPM-GPG-KEY-EPEL-6 [root@centos64 ~]# rm -f RPM-GPG-KEY-EPEL-6
2. Download and install EPEL repository for 64-bit CentOS :
[root@centos64 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/6/x86_64/epel-release-6-8.noarch.rpm [root@centos64 ~]# rpm -ivh epel-release-6-8.noarch.rpm Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
Alternately, you can browse other version of EPEL package set using repoview:
How to Setup phpMyAdmin on CentOS 6.3 using EPEL Repository
This post will covers the steps to install phpMyAdmin to operate MySQL from Web browser. phpMyAdmin is a free software tool written in PHP intended to handle the administration of MySQL over the World Wide Web. It can manage a whole MySQL server (needs a super-user) as well as a single database. phpMyAdmin supports a wide range of operations with MySQL. The most frequently used operations are supported by the user interface (managing databases, tables, fields, relations, indexes, users, permissions, etc), while you still have the ability to directly execute any SQL statement.
Prerequisites :
How to Configure EPEL Repository on CentOS 6.3
How to Install Httpd on CentOS 6.3
How to Install and Securing MySQL Database Server on CentOS 6.3
1. Install phpmyadmin :
[root@centos63 ~]# yum --enablerepo=epel install phpMyAdmin php-mysql php-mcrypt -y
Examples :
[root@centos63 ~]# yum --enablerepo=epel install phpMyAdmin php-mysql php-mcrypt -y Loaded plugins: fastestmirror, presto Loading mirror speeds from cached hostfile * base: mirror.issp.co.th * epel: mirror.nus.edu.sg * extras: mirror.issp.co.th * updates: mirror.issp.co.th Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package php-mcrypt.i686 0:5.3.3-1.el6 will be installed --> Processing Dependency: php-api = 20090626 for package: php-mcrypt-5.3.3-1.el6.i686 --> Processing Dependency: libmcrypt.so.4 for package: php-mcrypt-5.3.3-1.el6.i686 ---> Package php-mysql.i686 0:5.3.3-14.el6_3 will be installed --> Processing Dependency: php-pdo for package: php-mysql-5.3.3-14.el6_3.i686 ---> Package phpMyAdmin.noarch 0:3.5.1-1.el6 will be installed --> Processing Dependency: php-mbstring >= 5.2.0 for package: phpMyAdmin-3.5.1-1.el6.noarch --> Processing Dependency: php-gd >= 5.2.0 for package: phpMyAdmin-3.5.1-1.el6.noarch --> Processing Dependency: php >= 5.2.0 for package: phpMyAdmin-3.5.1-1.el6.noarch --> Processing Dependency: php-php-gettext for package: phpMyAdmin-3.5.1-1.el6.noarch --> Running transaction check ---> Package libmcrypt.i686 0:2.5.8-9.el6 will be installed ---> Package php.i686 0:5.3.3-14.el6_3 will be installed --> Processing Dependency: php-cli = 5.3.3-14.el6_3 for package: php-5.3.3-14.el6_3.i686 ---> Package php-common.i686 0:5.3.3-14.el6_3 will be installed ---> Package php-gd.i686 0:5.3.3-14.el6_3 will be installed --> Processing Dependency: libpng12.so.0(PNG12_0) for package: php-gd-5.3.3-14.el6_3.i686 --> Processing Dependency: libpng12.so.0 for package: php-gd-5.3.3-14.el6_3.i686 --> Processing Dependency: libjpeg.so.62 for package: php-gd-5.3.3-14.el6_3.i686 --> Processing Dependency: libfreetype.so.6 for package: php-gd-5.3.3-14.el6_3.i686 --> Processing Dependency: libXpm.so.4 for package: php-gd-5.3.3-14.el6_3.i686 --> Processing Dependency: libX11.so.6 for package: php-gd-5.3.3-14.el6_3.i686 ---> Package php-mbstring.i686 0:5.3.3-14.el6_3 will be installed ---> Package php-pdo.i686 0:5.3.3-14.el6_3 will be installed ---> Package php-php-gettext.noarch 0:1.0.11-3.el6 will be installed --> Running transaction check ---> Package freetype.i686 0:2.3.11-6.el6_2.9 will be installed ---> Package libX11.i686 0:1.3-2.el6 will be installed --> Processing Dependency: libX11-common = 1.3-2.el6 for package: libX11-1.3-2.el6.i686 --> Processing Dependency: libxcb.so.1 for package: libX11-1.3-2.el6.i686 ---> Package libXpm.i686 0:3.5.8-2.el6 will be installed ---> Package libjpeg.i686 0:6b-46.el6 will be installed ---> Package libpng.i686 2:1.2.49-1.el6_2 will be installed ---> Package php-cli.i686 0:5.3.3-14.el6_3 will be installed --> Running transaction check ---> Package libX11-common.noarch 0:1.3-2.el6 will be installed ---> Package libxcb.i686 0:1.5-1.el6 will be installed --> Processing Dependency: libXau.so.6 for package: libxcb-1.5-1.el6.i686 --> Running transaction check ---> Package libXau.i686 0:1.0.5-1.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ==================================================================================================== Package Arch Version Repository Size ==================================================================================================== Installing: php-mcrypt i686 5.3.3-1.el6 epel 18 k php-mysql i686 5.3.3-14.el6_3 updates 77 k phpMyAdmin noarch 3.5.1-1.el6 epel 4.2 M Installing for dependencies: freetype i686 2.3.11-6.el6_2.9 CentOS6.3-Repository 363 k libX11 i686 1.3-2.el6 CentOS6.3-Repository 585 k libX11-common noarch 1.3-2.el6 CentOS6.3-Repository 188 k libXau i686 1.0.5-1.el6 CentOS6.3-Repository 22 k libXpm i686 3.5.8-2.el6 CentOS6.3-Repository 58 k libjpeg i686 6b-46.el6 CentOS6.3-Repository 133 k libmcrypt i686 2.5.8-9.el6 epel 94 k libpng i686 2:1.2.49-1.el6_2 CentOS6.3-Repository 184 k libxcb i686 1.5-1.el6 CentOS6.3-Repository 104 k php i686 5.3.3-14.el6_3 updates 1.1 M php-cli i686 5.3.3-14.el6_3 updates 2.2 M php-common i686 5.3.3-14.el6_3 updates 523 k php-gd i686 5.3.3-14.el6_3 updates 103 k php-mbstring i686 5.3.3-14.el6_3 updates 453 k php-pdo i686 5.3.3-14.el6_3 updates 72 k php-php-gettext noarch 1.0.11-3.el6 epel 21 k Transaction Summary ==================================================================================================== Install 19 Package(s) Total download size: 10 M Installed size: 38 M Downloading Packages: Setting up and reading Presto delta metadata updates/prestodelta | 72 kB 00:00 Processing delta metadata Package(s) data still to download: 10 M (1/19): libmcrypt-2.5.8-9.el6.i686.rpm | 94 kB 00:00 (2/19): php-5.3.3-14.el6_3.i686.rpm | 1.1 MB 00:09 (3/19): php-cli-5.3.3-14.el6_3.i686.rpm | 2.2 MB 00:19 (4/19): php-common-5.3.3-14.el6_3.i686.rpm | 523 kB 00:04 (5/19): php-gd-5.3.3-14.el6_3.i686.rpm | 103 kB 00:00 (6/19): php-mbstring-5.3.3-14.el6_3.i686.rpm | 453 kB 00:04 (7/19): php-mcrypt-5.3.3-1.el6.i686.rpm | 18 kB 00:00 (8/19): php-mysql-5.3.3-14.el6_3.i686.rpm | 77 kB 00:00 (9/19): php-pdo-5.3.3-14.el6_3.i686.rpm | 72 kB 00:00 (10/19): php-php-gettext-1.0.11-3.el6.noarch.rpm | 21 kB 00:00 (11/19): phpMyAdmin-3.5.1-1.el6.noarch.rpm | 4.2 MB 00:36 ---------------------------------------------------------------------------------------------------- Total 135 kB/s | 10 MB 01:19 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : php-common-5.3.3-14.el6_3.i686 1/19 Installing : libX11-common-1.3-2.el6.noarch 2/19 Installing : php-mbstring-5.3.3-14.el6_3.i686 3/19 Installing : php-php-gettext-1.0.11-3.el6.noarch 4/19 Installing : php-cli-5.3.3-14.el6_3.i686 5/19 Installing : php-5.3.3-14.el6_3.i686 6/19 Installing : php-pdo-5.3.3-14.el6_3.i686 7/19 Installing : php-mysql-5.3.3-14.el6_3.i686 8/19 Installing : libmcrypt-2.5.8-9.el6.i686 9/19 Installing : php-mcrypt-5.3.3-1.el6.i686 10/19 Installing : libjpeg-6b-46.el6.i686 11/19 Installing : 2:libpng-1.2.49-1.el6_2.i686 12/19 Installing : libXau-1.0.5-1.el6.i686 13/19 Installing : libxcb-1.5-1.el6.i686 14/19 Installing : libX11-1.3-2.el6.i686 15/19 Installing : libXpm-3.5.8-2.el6.i686 16/19 Installing : freetype-2.3.11-6.el6_2.9.i686 17/19 Installing : php-gd-5.3.3-14.el6_3.i686 18/19 Installing : phpMyAdmin-3.5.1-1.el6.noarch 19/19 Verifying : freetype-2.3.11-6.el6_2.9.i686 1/19 Verifying : php-5.3.3-14.el6_3.i686 2/19 Verifying : php-cli-5.3.3-14.el6_3.i686 3/19 Verifying : libXau-1.0.5-1.el6.i686 4/19 Verifying : php-common-5.3.3-14.el6_3.i686 5/19 Verifying : php-mbstring-5.3.3-14.el6_3.i686 6/19 Verifying : libXpm-3.5.8-2.el6.i686 7/19 Verifying : 2:libpng-1.2.49-1.el6_2.i686 8/19 Verifying : libxcb-1.5-1.el6.i686 9/19 Verifying : phpMyAdmin-3.5.1-1.el6.noarch 10/19 Verifying : libX11-1.3-2.el6.i686 11/19 Verifying : php-php-gettext-1.0.11-3.el6.noarch 12/19 Verifying : php-gd-5.3.3-14.el6_3.i686 13/19 Verifying : libjpeg-6b-46.el6.i686 14/19 Verifying : libX11-common-1.3-2.el6.noarch 15/19 Verifying : php-mysql-5.3.3-14.el6_3.i686 16/19 Verifying : php-pdo-5.3.3-14.el6_3.i686 17/19 Verifying : php-mcrypt-5.3.3-1.el6.i686 18/19 Verifying : libmcrypt-2.5.8-9.el6.i686 19/19 Installed: php-mcrypt.i686 0:5.3.3-1.el6 php-mysql.i686 0:5.3.3-14.el6_3 phpMyAdmin.noarch 0:3.5.1-1.el6 Dependency Installed: freetype.i686 0:2.3.11-6.el6_2.9 libX11.i686 0:1.3-2.el6 libX11-common.noarch 0:1.3-2.el6 libXau.i686 0:1.0.5-1.el6 libXpm.i686 0:3.5.8-2.el6 libjpeg.i686 0:6b-46.el6 libmcrypt.i686 0:2.5.8-9.el6 libpng.i686 2:1.2.49-1.el6_2 libxcb.i686 0:1.5-1.el6 php.i686 0:5.3.3-14.el6_3 php-cli.i686 0:5.3.3-14.el6_3 php-common.i686 0:5.3.3-14.el6_3 php-gd.i686 0:5.3.3-14.el6_3 php-mbstring.i686 0:5.3.3-14.el6_3 php-pdo.i686 0:5.3.3-14.el6_3 php-php-gettext.noarch 0:1.0.11-3.el6 Complete!
2. on Line 14 or 15, add IP address you permit. In this case i have added 192.168.1.0/24 and i’m using apache 2.2 :
[root@centos63 ~]# vi /etc/httpd/conf.d/phpMyAdmin.conf
<Directory /usr/share/phpMyAdmin/>
<IfModule mod_authz_core.c>
# Apache 2.4
<RequireAny>
Require ip 127.0.0.1
Require ip ::1
</RequireAny>
</IfModule>
<IfModule !mod_authz_core.c>
# Apache 2.2
Order Deny,Allow
Deny from All
Allow from 127.0.0.1 192.168.1.0/24
Allow from ::1
</IfModule>
</Directory>
3. Reload or restart apache httpd :
[root@centos63 ~]# /etc/rc.d/init.d/httpd reload Reloading httpd:
How to Configure EPEL Repository on CentOS 6.3
This post will covers on how to install and configure the Extra Packages for Enterprise Linux (EPEL) repository on CentOS 6.3. EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. To install the repository, you can follow this steps :
1. First, we download and import the GPG keys for EPEL software packages:
[root@centos63 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-6 [root@centos63 ~]# rpm --import RPM-GPG-KEY-EPEL-6 [root@centos63 ~]# rm -f RPM-GPG-KEY-EPEL-6
2. Download EPEL repository for 32-bit CentOS :
[root@centos63 ~]# wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-7.noarch.rpm
3. Install EPEL repository on 32-bit CentOS :
[root@centos63 ~]# rpm -ivh epel-release-6-7.noarch.rpm Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
4. You can start install and use epel the repository to install the software packages, input yum command like follows :
[root@centos63 ~]# yum --enablerepo=epel install phpmyadmin -y
How to Install 389 Directory Server on CentOS 6.2
This post will show you the quick steps to install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server. This post assumed that your CentOS server has been completely installed with minimum packages and the hostname and FQDN also has been configured correctly. Please make sure that you have configured EPEL repository on your CentOS 6.2 server.
Prerequisites :
How to Setup Local Yum Repository from CD-ROM/DVD-ROM image on CentOS 6.2
How to Install and Configure EPEL Repository on CentOS 6.2
Simply run this command to install 389 Directory Server on linux CentOS 6.2 server :
[root@centos62 ~]# yum install 389-ds openldap-clients -y
Examples :
[root@centos62 ~]# yum install 389-ds openldap-clients -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.ipserverone.com * epel: ftp.cuhk.edu.hk * extras: centos.ipserverone.com * updates: centos.ipserverone.com Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed --> Processing Dependency: 389-ds-console for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-ds-console-doc for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-admin-console-doc for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-admin-console for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-admin for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: idm-console-framework for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-1.el6.noarch --> Processing Dependency: 389-console for package: 389-ds-1.2.2-1.el6.noarch ---> Package openldap-clients.i686 0:2.4.23-20.el6 will be installed --> Running transaction check ---> Package 389-admin.i686 0:1.1.25-1.el6 will be installed --> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: nss-tools for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: policycoreutils-python for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: libicudata.so.42 for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: perl(CGI) for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: libadminutil.so.0 for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: libadmsslutil.so.0 for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: libicui18n.so.42 for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: mod_nss for package: 389-admin-1.1.25-1.el6.i686 --> Processing Dependency: libicuuc.so.42 for package: 389-admin-1.1.25-1.el6.i686 ---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed ---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed ---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed --> Processing Dependency: java >= 1:1.6.0 for package: 389-console-1.1.7-1.el6.noarch --> Processing Dependency: jpackage-utils for package: 389-console-1.1.7-1.el6.noarch ---> Package 389-ds-base.i686 0:1.2.9.14-1.el6_2.2 will be installed --> Processing Dependency: 389-ds-base-libs = 1.2.9.14-1.el6_2.2 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: cyrus-sasl-md5 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: libnetsnmpmibs.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: cyrus-sasl-gssapi for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: libnetsnmphelpers.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: libnetsnmpagent.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: libnetsnmp.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: libslapd.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 --> Processing Dependency: libsvrcore.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686 ---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed ---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed ---> Package 389-dsgw.i686 0:1.1.7-2.el6 will be installed ---> Package idm-console-framework.noarch 0:1.1.7-2.el6 will be installed --> Processing Dependency: jss >= 4.2 for package: idm-console-framework-1.1.7-2.el6.noarch --> Processing Dependency: ldapjdk for package: idm-console-framework-1.1.7-2.el6.noarch --> Running transaction check ---> Package 389-adminutil.i686 0:1.1.14-2.el6 will be installed ---> Package 389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2 will be installed ---> Package cyrus-sasl-gssapi.i686 0:2.1.23-13.el6 will be installed ---> Package cyrus-sasl-md5.i686 0:2.1.23-13.el6 will be installed ---> Package java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2 will be installed --> Processing Dependency: tzdata-java for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686 --> Processing Dependency: rhino for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686 --> Processing Dependency: libgif.so.4 for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686 ---> Package jpackage-utils.noarch 0:1.7.5-3.12.el6 will be installed ---> Package jss.i686 0:4.2.6-20.el6 will be installed ---> Package ldapjdk.i686 0:4.18-6.el6 will be installed --> Processing Dependency: libgcj_bc.so.1 for package: ldapjdk-4.18-6.el6.i686 --> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686 --> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686 ---> Package libicu.i686 0:4.2.1-9.1.el6_2 will be installed ---> Package mod_nss.i686 0:1.0.8-13.el6 will be installed ---> Package net-snmp-libs.i686 1:5.5-37.el6_2.1 will be installed --> Processing Dependency: libsensors.so.4 for package: 1:net-snmp-libs-5.5-37.el6_2.1.i686 ---> Package nss-tools.i686 0:3.13.1-7.el6_2 will be installed --> Processing Dependency: nss = 3.13.1-7.el6_2 for package: nss-tools-3.13.1-7.el6_2.i686 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.13) for package: nss-tools-3.13.1-7.el6_2.i686 --> Processing Dependency: libnss3.so(NSS_3.13) for package: nss-tools-3.13.1-7.el6_2.i686 ---> Package perl-CGI.i686 0:3.51-119.el6_1.1 will be installed ---> Package perl-Mozilla-LDAP.i686 0:1.5.3-4.el6 will be installed ---> Package policycoreutils-python.i686 0:2.0.83-19.21.el6_2 will be installed --> Processing Dependency: policycoreutils = 2.0.83-19.21.el6_2 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686 --> Processing Dependency: audit-libs-python >= 1.4.2-1 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686 --> Processing Dependency: libsemanage-python >= 2.0.43-4 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686 --> Processing Dependency: setools-libs-python for package: policycoreutils-python-2.0.83-19.21.el6_2.i686 --> Processing Dependency: libcgroup for package: policycoreutils-python-2.0.83-19.21.el6_2.i686 ---> Package svrcore.i686 0:4.0.4-5.1.el6 will be installed --> Running transaction check ---> Package audit-libs-python.i686 0:2.1.3-3.el6 will be installed ---> Package giflib.i686 0:4.1.6-3.1.el6 will be installed ---> Package java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6 will be installed --> Processing Dependency: sinjdoc for package: java-1.5.0-gcj-1.5.0.0-29.1.el6.i686 ---> Package libcgroup.i686 0:0.37-3.el6 will be installed ---> Package libgcj.i686 0:4.4.6-3.el6 will be installed --> Processing Dependency: zip >= 2.1 for package: libgcj-4.4.6-3.el6.i686 ---> Package libsemanage-python.i686 0:2.0.43-4.1.el6 will be installed ---> Package lm_sensors-libs.i686 0:3.1.1-10.el6 will be installed ---> Package nss.i686 0:3.12.10-17.el6_2 will be updated --> Processing Dependency: nss = 3.12.10-17.el6_2 for package: nss-sysinit-3.12.10-17.el6_2.i686 ---> Package nss.i686 0:3.13.1-7.el6_2 will be an update --> Processing Dependency: nspr >= 4.8.9 for package: nss-3.13.1-7.el6_2.i686 ---> Package nss-util.i686 0:3.12.10-2.el6 will be updated ---> Package nss-util.i686 0:3.13.1-3.el6_2 will be an update ---> Package policycoreutils.i686 0:2.0.83-19.18.el6 will be updated ---> Package policycoreutils.i686 0:2.0.83-19.21.el6_2 will be an update ---> Package rhino.noarch 0:1.7-0.7.r2.2.el6 will be installed --> Processing Dependency: jline for package: rhino-1.7-0.7.r2.2.el6.noarch ---> Package setools-libs-python.i686 0:3.3.7-4.el6 will be installed --> Processing Dependency: setools-libs = 3.3.7-4.el6 for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libapol.so.4 for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libsefs.so.4 for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libpoldiff.so.1 for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libseaudit.so.4(VERS_4.2) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libseaudit.so.4 for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libapol.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libqpol.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libqpol.so.1 for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libsefs.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libpoldiff.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libapol.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libqpol.so.1(VERS_1.4) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libseaudit.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libpoldiff.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686 --> Processing Dependency: libqpol.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686 ---> Package tzdata-java.noarch 0:2011n-2.el6 will be installed --> Running transaction check ---> Package jline.noarch 0:0.9.94-0.8.el6 will be installed ---> Package nspr.i686 0:4.8.8-3.el6 will be updated ---> Package nspr.i686 0:4.8.9-3.el6_2 will be an update ---> Package nss-sysinit.i686 0:3.12.10-17.el6_2 will be updated ---> Package nss-sysinit.i686 0:3.13.1-7.el6_2 will be an update ---> Package setools-libs.i686 0:3.3.7-4.el6 will be installed ---> Package sinjdoc.i686 0:0.5-9.1.el6 will be installed --> Processing Dependency: java_cup >= 0.10 for package: sinjdoc-0.5-9.1.el6.i686 ---> Package zip.i686 0:3.0-1.el6 will be installed --> Running transaction check ---> Package java_cup.i686 1:0.10k-5.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ==================================================================================================== Package Arch Version Repository Size ==================================================================================================== Installing: 389-ds noarch 1.2.2-1.el6 epel 9.9 k openldap-clients i686 2.4.23-20.el6 CentOS6.2-Repository 155 k Installing for dependencies: 389-admin i686 1.1.25-1.el6 epel 341 k 389-admin-console noarch 1.1.8-1.el6 epel 202 k 389-admin-console-doc noarch 1.1.8-1.el6 epel 43 k 389-adminutil i686 1.1.14-2.el6 epel 64 k 389-console noarch 1.1.7-1.el6 epel 72 k 389-ds-base i686 1.2.9.14-1.el6_2.2 updates 1.4 M 389-ds-base-libs i686 1.2.9.14-1.el6_2.2 updates 369 k 389-ds-console noarch 1.2.6-1.el6 epel 1.4 M 389-ds-console-doc noarch 1.2.6-1.el6 epel 55 k 389-dsgw i686 1.1.7-2.el6 epel 460 k audit-libs-python i686 2.1.3-3.el6 CentOS6.2-Repository 56 k cyrus-sasl-gssapi i686 2.1.23-13.el6 CentOS6.2-Repository 33 k cyrus-sasl-md5 i686 2.1.23-13.el6 CentOS6.2-Repository 46 k giflib i686 4.1.6-3.1.el6 CentOS6.2-Repository 37 k idm-console-framework noarch 1.1.7-2.el6 epel 1.1 M java-1.5.0-gcj i686 1.5.0.0-29.1.el6 CentOS6.2-Repository 138 k java-1.6.0-openjdk i686 1:1.6.0.0-1.43.1.10.6.el6_2 updates 26 M java_cup i686 1:0.10k-5.el6 CentOS6.2-Repository 178 k jline noarch 0.9.94-0.8.el6 CentOS6.2-Repository 86 k jpackage-utils noarch 1.7.5-3.12.el6 CentOS6.2-Repository 59 k jss i686 4.2.6-20.el6 CentOS6.2-Repository 745 k ldapjdk i686 4.18-6.el6 CentOS6.2-Repository 749 k libcgroup i686 0.37-3.el6 CentOS6.2-Repository 102 k libgcj i686 4.4.6-3.el6 CentOS6.2-Repository 17 M libicu i686 4.2.1-9.1.el6_2 updates 5.0 M libsemanage-python i686 2.0.43-4.1.el6 CentOS6.2-Repository 80 k lm_sensors-libs i686 3.1.1-10.el6 CentOS6.2-Repository 36 k mod_nss i686 1.0.8-13.el6 CentOS6.2-Repository 82 k net-snmp-libs i686 1:5.5-37.el6_2.1 updates 1.5 M nss-tools i686 3.13.1-7.el6_2 updates 741 k perl-CGI i686 3.51-119.el6_1.1 CentOS6.2-Repository 206 k perl-Mozilla-LDAP i686 1.5.3-4.el6 CentOS6.2-Repository 161 k policycoreutils-python i686 2.0.83-19.21.el6_2 updates 338 k rhino noarch 1.7-0.7.r2.2.el6 CentOS6.2-Repository 778 k setools-libs i686 3.3.7-4.el6 CentOS6.2-Repository 400 k setools-libs-python i686 3.3.7-4.el6 CentOS6.2-Repository 210 k sinjdoc i686 0.5-9.1.el6 CentOS6.2-Repository 646 k svrcore i686 4.0.4-5.1.el6 CentOS6.2-Repository 15 k tzdata-java noarch 2011n-2.el6 updates 153 k zip i686 3.0-1.el6 CentOS6.2-Repository 252 k Updating for dependencies: nspr i686 4.8.9-3.el6_2 updates 113 k nss i686 3.13.1-7.el6_2 updates 763 k nss-sysinit i686 3.13.1-7.el6_2 updates 30 k nss-util i686 3.13.1-3.el6_2 updates 52 k policycoreutils i686 2.0.83-19.21.el6_2 updates 640 k Transaction Summary ==================================================================================================== Install 42 Package(s) Upgrade 5 Package(s) Total download size: 63 M Downloading Packages: (1/47): 389-admin-1.1.25-1.el6.i686.rpm | 341 kB 00:03 (2/47): 389-admin-console-1.1.8-1.el6.noarch.rpm | 202 kB 00:01 (3/47): 389-admin-console-doc-1.1.8-1.el6.noarch.rpm | 43 kB 00:00 (4/47): 389-adminutil-1.1.14-2.el6.i686.rpm | 64 kB 00:00 (5/47): 389-console-1.1.7-1.el6.noarch.rpm | 72 kB 00:00 (6/47): 389-ds-1.2.2-1.el6.noarch.rpm | 9.9 kB 00:00 (7/47): 389-ds-base-1.2.9.14-1.el6_2.2.i686.rpm | 1.4 MB 00:11 (8/47): 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686.rpm | 369 kB 00:03 (9/47): 389-ds-console-1.2.6-1.el6.noarch.rpm | 1.4 MB 00:13 (10/47): 389-ds-console-doc-1.2.6-1.el6.noarch.rpm | 55 kB 00:00 (11/47): 389-dsgw-1.1.7-2.el6.i686.rpm | 460 kB 00:03 (12/47): idm-console-framework-1.1.7-2.el6.noarch.rpm | 1.1 MB 00:08 (13/47): java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686.rpm | 26 MB 03:56 (14/47): libicu-4.2.1-9.1.el6_2.i686.rpm | 5.0 MB 00:44 (15/47): net-snmp-libs-5.5-37.el6_2.1.i686.rpm | 1.5 MB 00:13 (16/47): nspr-4.8.9-3.el6_2.i686.rpm | 113 kB 00:00 (17/47): nss-3.13.1-7.el6_2.i686.rpm | 763 kB 00:06 (18/47): nss-sysinit-3.13.1-7.el6_2.i686.rpm | 30 kB 00:00 (19/47): nss-tools-3.13.1-7.el6_2.i686.rpm | 741 kB 00:06 (20/47): nss-util-3.13.1-3.el6_2.i686.rpm | 52 kB 00:00 (21/47): policycoreutils-2.0.83-19.21.el6_2.i686.rpm | 640 kB 00:05 (22/47): policycoreutils-python-2.0.83-19.21.el6_2.i686.rpm | 338 kB 00:03 (23/47): tzdata-java-2011n-2.el6.noarch.rpm | 153 kB 00:01 ---------------------------------------------------------------------------------------------------- Total 174 kB/s | 63 MB 06:11 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : jpackage-utils-1.7.5-3.12.el6.noarch 1/52 Installing : perl-CGI-3.51-119.el6_1.1.i686 2/52 Installing : jline-0.9.94-0.8.el6.noarch 3/52 Installing : rhino-1.7-0.7.r2.2.el6.noarch 4/52 Installing : tzdata-java-2011n-2.el6.noarch 5/52 Updating : nspr-4.8.9-3.el6_2.i686 6/52 Updating : nss-util-3.13.1-3.el6_2.i686 7/52 Updating : nss-sysinit-3.13.1-7.el6_2.i686 8/52 Updating : nss-3.13.1-7.el6_2.i686 9/52 Installing : libicu-4.2.1-9.1.el6_2.i686 10/52 Installing : perl-Mozilla-LDAP-1.5.3-4.el6.i686 11/52 Installing : nss-tools-3.13.1-7.el6_2.i686 12/52 Installing : 389-adminutil-1.1.14-2.el6.i686 13/52 Installing : svrcore-4.0.4-5.1.el6.i686 14/52 Updating : policycoreutils-2.0.83-19.21.el6_2.i686 15/52 Installing : 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686 16/52 Installing : mod_nss-1.0.8-13.el6.i686 17/52 Installing : openldap-clients-2.4.23-20.el6.i686 18/52 Installing : lm_sensors-libs-3.1.1-10.el6.i686 19/52 Installing : 1:net-snmp-libs-5.5-37.el6_2.1.i686 20/52 Installing : giflib-4.1.6-3.1.el6.i686 21/52 Installing : zip-3.0-1.el6.i686 22/52 Installing : libgcj-4.4.6-3.el6.i686 23/52 Installing : 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686 24/52 Installing : java-1.5.0-gcj-1.5.0.0-29.1.el6.i686 25/52 Installing : 1:java_cup-0.10k-5.el6.i686 26/52 Installing : sinjdoc-0.5-9.1.el6.i686 27/52 Installing : jss-4.2.6-20.el6.i686 28/52 Installing : ldapjdk-4.18-6.el6.i686 29/52 Installing : idm-console-framework-1.1.7-2.el6.noarch 30/52 Installing : 389-console-1.1.7-1.el6.noarch 31/52 Installing : cyrus-sasl-gssapi-2.1.23-13.el6.i686 32/52 Installing : setools-libs-3.3.7-4.el6.i686 33/52 Installing : setools-libs-python-3.3.7-4.el6.i686 34/52 Installing : cyrus-sasl-md5-2.1.23-13.el6.i686 35/52 Installing : libcgroup-0.37-3.el6.i686 36/52 Installing : audit-libs-python-2.1.3-3.el6.i686 37/52 Installing : libsemanage-python-2.0.43-4.1.el6.i686 38/52 Installing : policycoreutils-python-2.0.83-19.21.el6_2.i686 39/52 Installing : 389-ds-base-1.2.9.14-1.el6_2.2.i686 40/52 Installing : 389-admin-1.1.25-1.el6.i686 41/52 Installing : 389-admin-console-1.1.8-1.el6.noarch 42/52 Installing : 389-ds-console-1.2.6-1.el6.noarch 43/52 Installing : 389-ds-console-doc-1.2.6-1.el6.noarch 44/52 Installing : 389-admin-console-doc-1.1.8-1.el6.noarch 45/52 Installing : 389-dsgw-1.1.7-2.el6.i686 46/52 Installing : 389-ds-1.2.2-1.el6.noarch 47/52 Cleanup : nss-sysinit-3.12.10-17.el6_2.i686 48/52 Cleanup : nss-3.12.10-17.el6_2.i686 49/52 Cleanup : nss-util-3.12.10-2.el6.i686 50/52 Cleanup : nspr-4.8.8-3.el6.i686 51/52 Cleanup : policycoreutils-2.0.83-19.18.el6.i686 52/52 Installed: 389-ds.noarch 0:1.2.2-1.el6 openldap-clients.i686 0:2.4.23-20.el6 Dependency Installed: 389-admin.i686 0:1.1.25-1.el6 389-admin-console.noarch 0:1.1.8-1.el6 389-admin-console-doc.noarch 0:1.1.8-1.el6 389-adminutil.i686 0:1.1.14-2.el6 389-console.noarch 0:1.1.7-1.el6 389-ds-base.i686 0:1.2.9.14-1.el6_2.2 389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2 389-ds-console.noarch 0:1.2.6-1.el6 389-ds-console-doc.noarch 0:1.2.6-1.el6 389-dsgw.i686 0:1.1.7-2.el6 audit-libs-python.i686 0:2.1.3-3.el6 cyrus-sasl-gssapi.i686 0:2.1.23-13.el6 cyrus-sasl-md5.i686 0:2.1.23-13.el6 giflib.i686 0:4.1.6-3.1.el6 idm-console-framework.noarch 0:1.1.7-2.el6 java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6 java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2 java_cup.i686 1:0.10k-5.el6 jline.noarch 0:0.9.94-0.8.el6 jpackage-utils.noarch 0:1.7.5-3.12.el6 jss.i686 0:4.2.6-20.el6 ldapjdk.i686 0:4.18-6.el6 libcgroup.i686 0:0.37-3.el6 libgcj.i686 0:4.4.6-3.el6 libicu.i686 0:4.2.1-9.1.el6_2 libsemanage-python.i686 0:2.0.43-4.1.el6 lm_sensors-libs.i686 0:3.1.1-10.el6 mod_nss.i686 0:1.0.8-13.el6 net-snmp-libs.i686 1:5.5-37.el6_2.1 nss-tools.i686 0:3.13.1-7.el6_2 perl-CGI.i686 0:3.51-119.el6_1.1 perl-Mozilla-LDAP.i686 0:1.5.3-4.el6 policycoreutils-python.i686 0:2.0.83-19.21.el6_2 rhino.noarch 0:1.7-0.7.r2.2.el6 setools-libs.i686 0:3.3.7-4.el6 setools-libs-python.i686 0:3.3.7-4.el6 sinjdoc.i686 0:0.5-9.1.el6 svrcore.i686 0:4.0.4-5.1.el6 tzdata-java.noarch 0:2011n-2.el6 zip.i686 0:3.0-1.el6 Dependency Updated: nspr.i686 0:4.8.9-3.el6_2 nss.i686 0:3.13.1-7.el6_2 nss-sysinit.i686 0:3.13.1-7.el6_2 nss-util.i686 0:3.13.1-3.el6_2 policycoreutils.i686 0:2.0.83-19.21.el6_2 Complete!
How to Install phpPgAdmin for Managing PostgreSQL Databases on CentOS 6.2
phpPgAdmin is a web application, written in PHP and web-based administration utility for managing PostgreSQL databases. It handles all the basic functionality as well as some advanced features such as triggers, views and functions. It can create databases, create tables, alter tables and query the data. In this post, i will show how to install phpPgAdmin for PostgreSQL Databases on linux CentOS 6.2 server. Assumed that you have already configured EPEL repository.
[root@centos62 ~]# yum install phpPgAdmin -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.averse.net * epel: ftp.riken.jp * extras: mirror.averse.net * updates: mirror.issp.co.th Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package phpPgAdmin.noarch 0:5.0.3-1.el6 will be installed --> Processing Dependency: php-pgsql >= 4.2 for package: phpPgAdmin-5.0.3-1.el6.noarch --> Running transaction check ---> Package php-pgsql.i686 0:5.3.3-3.el6_2.6 will be installed --> Finished Dependency Resolution Dependencies Resolved ==================================================================================================== Package Arch Version Repository Size ==================================================================================================== Installing: phpPgAdmin noarch 5.0.3-1.el6 epel 909 k Installing for dependencies: php-pgsql i686 5.3.3-3.el6_2.6 updates 67 k Transaction Summary ==================================================================================================== Install 2 Package(s) Total download size: 976 k Installed size: 4.9 M Downloading Packages: (1/2): php-pgsql-5.3.3-3.el6_2.6.i686.rpm | 67 kB 00:00 (2/2): phpPgAdmin-5.0.3-1.el6.noarch.rpm | 909 kB 00:10 ---------------------------------------------------------------------------------------------------- Total 83 kB/s | 976 kB 00:11 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : php-pgsql-5.3.3-3.el6_2.6.i686 1/2 Installing : phpPgAdmin-5.0.3-1.el6.noarch 2/2 Non-fatal POSTIN scriptlet failure in rpm package phpPgAdmin-5.0.3-1.el6.noarch warning: %post(phpPgAdmin-5.0.3-1.el6.noarch) scriptlet failed, exit status 7 Installed: phpPgAdmin.noarch 0:5.0.3-1.el6 Dependency Installed: php-pgsql.i686 0:5.3.3-3.el6_2.6 Complete!
How to Install and Configure EPEL Repository on CentOS 6.2
In this post, i will show you on how to install and configure the Extra Packages for Enterprise Linux (EPEL) repository on CentOS 6.2. EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. To install the repository, you can follow this steps :
1. First we import the GPG keys for EPEL software packages:
[root@centos62 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-6
[root@centos62 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-6 --2012-03-07 22:08:39-- http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-6 Resolving ftp.riken.jp... 134.160.38.1 Connecting to ftp.riken.jp|134.160.38.1|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1649 (1.6K) [text/plain] Saving to: âRPM-GPG-KEY-EPEL-6â 100%[==========================================================>] 1,649 --.-K/s in 0.002s 2012-03-07 22:08:40 (929 KB/s) - âRPM-GPG-KEY-EPEL-6â
2. Then we enable the EPEL repositories using the following command :
[root@centos62 ~]# rpm --import RPM-GPG-KEY-EPEL-6
3. Download EPEL repository for 32-bit CentOS :
[root@centos62 ~]# wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm
[root@centos62 ~]# wget http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm --2012-03-07 22:06:10-- http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm Resolving dl.fedoraproject.org... 209.132.181.27, 209.132.181.23, 209.132.181.24, ... Connecting to dl.fedoraproject.org|209.132.181.27|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 14064 (14K) [application/x-rpm] Saving to: âepel-release-6-5.noarch.rpmâ 100%[==========================================================>] 14,064 36.7K/s in 0.4s 2012-03-07 22:06:14 (36.7 KB/s) - âepel-release-6-5.noarch.rpmâ
4. Install EPEL repository on 32-bit CentOS :
[root@centos62 ~]# rpm -ivh epel-release-6-5.noarch.rpm Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
5. Edit the the EPEL repository file and Set priority for the EPEL repository as below :
[root@centos62 ~]# vi /etc/yum.repos.d/epel.repo
6. Add priority=3 to the [epel] section, under enabled=1 :
[epel] name=Extra Packages for Enterprise Linux 6 - $basearch #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch failovermethod=priority enabled=1 priority=3 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 [epel-debuginfo] name=Extra Packages for Enterprise Linux 6 - $basearch - Debug #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch/debug mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-6&arch=$basearch failovermethod=priority enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 gpgcheck=1 [epel-source] name=Extra Packages for Enterprise Linux 6 - $basearch - Source #baseurl=http://download.fedoraproject.org/pub/epel/6/SRPMS mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-source-6&arch=$basearch failovermethod=priority enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 gpgcheck=1
What packages and versions are available in EPEL?
You can take a look on any of the available EPEL mirrors from our mirror list
Alternately, you can browse the package set using repoview:
How to Install and Configure EPEL Repository on CentOS 5.8
EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. In this post, i will show you on how to install and configure the Extra Packages for Enterprise Linux (EPEL) repository on CentOS 5.8. To install the repository, you can follow this steps :
1. First we import the GPG keys for EPEL software packages:
[root@centos58 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-5
Example :
[root@centos58 ~]# wget http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-5 --2012-05-12 05:01:11-- http://ftp.riken.jp/Linux/fedora/epel/RPM-GPG-KEY-EPEL-5 Resolving ftp.riken.jp... 134.160.38.1 Connecting to ftp.riken.jp|134.160.38.1|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1698 (1.7K) [text/plain] Saving to: `RPM-GPG-KEY-EPEL-5' 100%[==========================================================>] 1,698 --.-K/s in 0s 2012-05-12 05:01:12 (42.2 MB/s) - `RPM-GPG-KEY-EPEL-5' saved [1698/1698]
2. Then we enable the EPEL repositories using the following command :
[root@centos58 ~]# rpm --import RPM-GPG-KEY-EPEL-5
3. Download EPEL repository for 32-bit CentOS :
[root@centos58 ~]# wget http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
Example :
[root@centos58 ~]# wget http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm --2012-05-12 05:04:03-- http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm Resolving dl.fedoraproject.org... 209.132.181.25, 209.132.181.26, 209.132.181.27, ... Connecting to dl.fedoraproject.org|209.132.181.25|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 12232 (12K) [application/x-rpm] Saving to: `epel-release-5-4.noarch.rpm' 100%[==========================================================>] 12,232 43.7K/s in 0.3s 2012-05-12 05:04:04 (43.7 KB/s) - `epel-release-5-4.noarch.rpm' saved [12232/12232]
4. Install EPEL repository on 32-bit CentOS :
[root@centos58 ~]# rpm -ivh epel-release-5-4.noarch.rpm Preparing... ########################################### [100%] 1:epel-release ########################################### [100%]
5. You can start using EPEL repository :
# yum install package name -y
Example :
[root@centos58 ~]# yum install phpmyadmin -y
