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.
That still seems normal; the error appears to be related exclusively to the updates repo - which makes sense because that one was scheduled to be the last to be opened. As a little experiment, could you open the file /etc/yum.repos.d/updates-repo and set the "enabled" item to 0 rather than 1? (This has the effect of disabling it).
If my suspicions are correct, yum should run perfectly fine after that. Of course, the updates repo won't be available anymore but you can simply re-enable it as soon as it does get opened to the public (I think there aren't any updates yet anyway - Fedora has barely been released).
Or here is an alternative where you don't have to edit any files:
(the "fedora-updates" part assumes that the repo file in /etc/yum.repos.d is actually called "fedora-updates.repo" - if that's a wrong assumption, you will have to adjust the command accordingly). As soon as the updates repo comes up, the "disablerepo ..." option can be dropped.
I'm afraid those are the limitations that come with being an early adopter. Still, I think it's weird that a package from the core repo should depend on something from the updates repo; after all, the core repo offers essentially the same as the cds/dvd. Unless you are upgrading an FC6 install instead of installing to a fresh partition.
Whatever, I just checked the mirrors and apparently there still isn't any updates repo yet.
that is no fair. I had to guess were at. could someone tell me what the name of the add/remove software name is. I uninstalled it and forgot the name of it. I think its starts with a p amd ents with a t and no it would not open for me so I had to do someing. when I read on adding a repo page I see then talking about getting the repo file. that would have been nice. since the repo file is mainly the same from computer to computer. and some How I used yum to get from FC5 to FC7.