[SOLVED] Crating a YUM repository but suck on the best solution
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Crating a YUM repository but suck on the best solution
I was asked to come up with a solution to get updates to our linux computers on a classified network.
I was told to create a local YUM repository and have the clients connect to it. -- Simple right. No at least not to me.
The last time I worked with linux was back on WS3, things have changed. So let me explain my situation.
I have various Red Hat Linux versions -- 5.1, 5.4 & 5.5 that are not connected to the internet and never will be. I need a way to grab updates for those versions and load them.
I have one linux RHEL 5.5 with paid subscription that is allowed to be connected to the internet.
I was going to use this one as my repository to download the packages I need, disconnect from the internet and have my "blessed" machines access it through an nfs share.
Possible solutions were to create a local YUM repository, set up a mirror or perhaps red hat satellite (which may or may not coast more money.)
I need an easy to step by step guide or what would be the best solution. I am getting overwhelmed with all the try this solutions. My boss is losing faith and I starting to feel like an idiot.
Anyway helpful suggestions or guides would be useful.
I thought just creating the local YUM repo and connect it via an NFS share would work but I'm lost.
Below are the steps I was given to help me accomplish setting it up.
In red are the steps that are not clear to me.
I created a folder under /var/www/html/yum/rhel5/updates. Then copied all the files in the "workstation" folder of my rhel 5.5 disk.
Copy Red Hat Enterprise Linux 5 DVD ISO RHEL5-Client-20070208.0-i386-DVD.iso from Red Hat Network and create a local repository on the local Repository server.
#mkdir -p /var/www/html/cdrom/iso
#mount -o loop /RHEL5-Client-20070208.0-i386-DVD.iso /var/www/html/cdrom/iso
#cd /var/www/html/cdrom -- this is where I would change it to the directory structure mentioned above on my server
#yum clean all
2. Create a file /etc/yum.repos.d/file.repo which should have the contents as mentioned below :
baseurl=file:///cdrom -- how would I change this ? This would be the same file path as mentioned above.
Share with httpd by making sure you have lines like these in your /etc/httpd/conf/httpd.conf file: -- completely confused with this step? I was going to setup a NFS share but maybe this better.??
(Where 10.65.6.141 is the local Repository server)
# httpd -t
# service httpd start
Client side configuration:
name= RHEL 5.1 Server Repository
baseurl=http://10.65.6.141/cdrom --- change the "cdrom" to the filepath I setup on my server (the one mentioned above)
Verify from client: this seems pretty straight foward.
# yum list
Loading "installonlyn" plugin
Setting up repositories
Reading repository metadata in from local files
5.0.0-19 RH51-Server ========
# yum update