Skip to main content

Managing & Configuring YUM [Centos 6.0]

Yum Configuration


Hi Friends, we all have faced problems while configuring yum in RedHat, Fedora and Centos. Please find the below mention steps to use all the RPM packages come along with your distribution. Yum configuration will allow you to use them with proper dependency resolution.

To configure yum you must have two packages,
1. yum
2. createrepo

To obtain the same do the below mention just after you have mounted you disk.

There could be two conditions

a.) You have the distribution disk i.e. DVD. Please follow the below mention instructions to manage the same.
Your system mush have the greater or equal space of DVD.
# df -ah
User the partition which has the space and create a directory. In my case /mnt has the space.# mount /dev/dvdwriter /mnt
# cd /mnt/Packages/
# rpm -ivh yum-* --nodeps –force
# rpm -ivh vsftps* -y
# rpm -ivh createrepo* --nodeps --force
# cp -rpvf /mnt/* /var/ftp/pub

It will create the dump on /var/ftp/pub now we need to unmount the disk.
# umount /mnt
b.) You have an iso of you distribution. In that condition you need to mount it with loop so,
cd to iso location
It will mount the ISO to /mnt#mount -o loop rhel.iso /mnt
# cd /mnt/Packages/
# rpm -ivh yum-* --nodeps –force
# rpm -ivh vsftps* -y
# rpm -ivh createrepo* --nodeps --force

Copy packages folder to /var/ftp/pub
# cp -rpvh /mnt/Packages/* /var/ftp/pub


Now you have the dump of your distribution and you are ready to configure yum. To configure the same you must be aware of your hostname. Run the following command to know your hostname,

# hostname
CentOs

Now you have your host name create directories at /var/ftp/pub i.e. Server and VT by following command,

#mkdir -p Server; mkdir -p VT


You are ready to configure your Server and VT repos. Run the following command in order to generate the repos,

# createrepo -v Server ; createrepo -v VT

It will create the directory structure like /var/ftp/pub/Server/repodata & /var/ftp/pub/VT/repodata and a file repomd.xml under each. Configuration of yum is just a step ahead. Search a file like *debuginfo.repo* under /etc/yum/yum.repos.d/. Keep a copy of it for disaster and rename the same with a different command name,

# cp -rf *debuginfo.repo* `hostname`.repo

Edit the hostname.repo using your editor. I will you vim and will comment all the lines that are UN-commented and write new lines on it.# vim `hostname`.repo

#[debug]
#name=CentOS-6 - Debuginfo
#baseurl=http://debuginfo.centos.org/6/$basearch/
#gpgcheck=1
#gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-Debug-6
#enabled=0
#

[Server]
name=CentOs
baseurl=file:///var/ftp/pub/Server/
gpgcheck=0


[VT]
name=CentOs
baseurl=file:///var/ftp/pub/VT/
gpgcheck=0




Run yum clean all and you are done.

Thanks

Comments

Popular posts

Istio multicluster, gotchas ....

istio.md Istio lets you connect, secure, control, and observe services. At a high level, Istio helps reduce the complexity of these deployments, and eases the strain on your development teams. It is a completely open source service mesh that layers transparently onto existing distributed applications. It is also a platform, including APIs that let it integrate into any logging platform, or telemetry or policy system. Istio’s diverse feature set lets you successfully, and efficiently, run a distributed microservice architecture, and provides a uniform way to secure, connect, and monitor microservices. In context of Vuclip istio allows us to reduce the code and environment configurations while keeping the similar or more feature sets at our disposal. Since istio is designed to bridge the gap for both development teams and SRE, it is essential to see and visualize that in practice. Istio will affect us in our ability to connect , secure(HTTPs TLS, mtls [Phase-2]), control(external comm

Nodejs SSA learnings

nodejs-akamai-page.MD Overview In almost every blog when people talk about deploying something on K8S they use node mostly because setting up http server is not that easy. I wish that it could be this easy for our case, (which it wasn’t). Manly because the way we wanted the application to work, plans for SEO and multiple data pipelines for business including Amplitude for client and Pubsub for application and business metrics. Making all these calls from nodejs was easy for developers just 1 more promise. Everything went smoothly as long as functional testing was required. We were ready to launch and somebody from SRE/Devops team asked: “Have you done load testing?” . Everything was superb up to this point where load testing results are required to make service live. Load Testing We started to put load to our services using apache benchmark. Very soon we realised our application is not scaling as much as we expected. To our surprise application was able to handle only 3 requ

Enter your email address: