Guys,

Like my nick suggests, I'm absolutely new to Linux. I had to take this class as one of my directed electives. Now I have this challenge to configure 'YUM' distribution and repository in Fedora 13 as my final project.

What I have done:

1) Installed "YUM" to the server computer. (This is a project involving two computers - a server and a client)

2) Created a YUM database on server computer.

3) Defined the IP address of server on the client computer so it could access the database.

Now, when i try to access the YUM repository from the client computer, it gives me the following error:[

[root@station21 yum.repos.d]# yum install yp-tools
loaded plugins: presto, refresh-packagekit
192.168.0.17/rpm/repodata/repomd.xml: [Errno 14] HTTP Error 404:
Trying other mirror
Error: Cannot retrieve repository metadata {repomd.xml) for repository: Please verify path and try again.

I double checked the path with my instructor who said the path seems to be okay, and asked me to solve it. "Solve it" is what my final project really is.

I'll be very thankful to anyone who can provide insight to complete this project. It doesn't really sound too complicated, but please bear in mind that I'm having to do this project while my Linux-standing is really a very beginning (a,b,c,d)

Sincerely,
Rupert

Install yumex on both machines. (why not?). You can easily add the server as an additional repository. Generally, yum is used to pull updates from repositories directly from their mirrors on the web. Having a local repository is unusual.

Hi,
in server
=========
1. First the server should have the complete repository in a ftp or http server (you could copy all those rpms from the RPMS folder to /var/ftp/pub. Then only it could be accessed by ur client machine right. ( make sure u install vsftp to get those folders !)


2. install createrepo rpm. Then run the command #createrepo /var/ftp/pub. This will just put some extra folders and files
in ur repositories. ( check the error you get-those are the files ur client is unable to get)



in client
==========
3. create a repo file in /etc/yum.repos.d/
open a similar *.repo file and make a copy in same folder . eg. any_name.repo ammend the file sothat it points to ur
ftp server. ( open the file and have alook u will understand.

all the best.

...and be aware Fedora 13 is obsolete. F16 is current and F17 is around the corner.

with the VERY dead and unsupported fedora 13
you will have one and ONLY ONE update
Updating to the time of it's END OF LIFE

after that you might as well UNINSTALL everything dealing with yum

yum will be useless
and will NEVER have any updates to install

there ARE NONE for fedora 13


please stay current and install fedora 16 and then in a month fedora 17 when it comes out

Still, you should get all the updates that you can get for Fedora 13. If there is nothing there or only one thing, at least you know. It may be best to go to the net directly.

Fedora does have a handy utility known as pre-upgrade and upgrade. There is a lot of information about this on the website. If you run this for both your fedora server and/or client, you'll be in good shape to get updated and stay that way. You will (of course) need an internet connection.

This should get you off to a good start.

http://fedoraproject.org/wiki/How_to_use_PreUpgrade

The other school of thought is that if it ain't broke, don't fix it. Still for a student, this probably won't fly.

"Update" can be understood to mean getting the latest greatest distribution of Fedora, not just getting the last of the last update(s) for Fedora 13. There is no reason why what starts as Fedora 13 needs to end up being Fedora 13.

Run pre-upgrade. You don't even need to burn a DVD !! Just make sure that your machine is hooked up to a good battery backup and a fast stable Internet connection.

In many cases out there in the real world, people will be far more behind in their updates then the current one. Heck, you might end up running this for Fedora 10 or even Fedora 8 !!

Many users get cold feet when it comes to updates because of bad experiences with Microsoft or that they don't know how to backup and reinstall their data and settings.

Getting fully upgraded and updated is valuable experience and will occur often in the "real world". This is a common situation.

In this case that is not a valid argument. Fedora users should run the current release or don't run it at all.

99% of the time, it is best to run the current versions of Linux. Still, if your PC is working perfectly & any interruption would be catastrophic, leave it alone. For Fedora, I've had the best luck with preupgrade.

You know perfectly well what I mean. Admins who really need to support deprecated releases should anticipate the risks such exotic exceptions bring about. For the rest, not reading the documentation, a general lack of doing things the Linux way and lack of user and admin knowledge means we still have to educate users about standard procedures, not exceptions. Besides given the time it takes to set up a Fedora 16 machine you shouldn't want to advertise preupgrading F13 to F14 to F15 to F16 anyway.

I don't think that using preupgrade is all that excessive. Preupgrade doesn't have to be run 3 times to get from 13 to 16, only once. I have done this myself, going from either 10 or 11 to 14 in fedora. I have no idea about whether or not it's best practice or not. I only know that you can get away with it. If you use the dvd, it will also find the previous version and ask you if you want to update the pc or smoke it with a clean install. Only M$ requires you to upgrade one operating system at a time.

Indeed it doesn't have to these days:

Thank you guys for your responses. I really appreciate that. I cannot upgrade Fedora 13, because that's what we have in our school lab.

At least you now know what your options are. Still, I doubt that your lab's software would have trouble with the upgrade. So long as an application is compatible, preupgrade will leave it alone. Of course, there is nothing whatsoever wrong with 13, obsolete or not !!