FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having the same problem. I assume its just the yum repository is down because you can still get to the ftp directories from Fedoras site. Weird, but I imagine it will be corrected soon.
add the following lines into your /etc/sysconfig/rhn/sources file
yum fedora-core-1 http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/os/
yum updates-released http://download.fedora.redhat.com/pub/fedora/linux/core/updates/1/i386/
#yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/i386/
leave the # in front of yum updates otherwise you'll get unstable (RAWHIDE) as well AND comment out up2date default in the sources file when it occurs otherwise it will still error out
hope this helps
Originally posted by lhm0155 add the following lines into your /etc/sysconfig/rhn/sources file
I used the "iv" program inside the GUI to modify the source file. It is something similiar to notepad, but acts very strangely after pasting the below lines. I am not sure if I did this correctly? Could not figure out if it needed to be saved either? Can anyone please help...
leave the # in front of yum updates otherwise you'll get unstable (RAWHIDE) as well
AND comment out up2date default in the sources file when it occurs otherwise it will still error out hope this helps
Here is what my source file looks like:
### this describes the various package repos up2date will look into
### for packages. It currently supports apt-rpm repos, yum repos,
### and "dir" repos
### format is one repo entry per line, # starts comments, the
### first word on each line is the type of repo.
### the defalt rhn (using "default" as the url means
### use the one in the up2date config file
#up2date default
### When a channel-label is required for the non up2date repo's,
### the label is soley used as an internal identifier and is not
### based on the url or any other info from the repo.
### an apt style repo, this time arjanv's 2.6 kernel repo
### format is:
### type channel-label service:server path repo name
I start off by placing my root password in first. I keep getting an error message dealing with the /var/temp/ folder when trying to modify the source file. I get a warning about duplicate files, but it is referencing the /var/temp/folder. I deleted all of the files inside of the /var/temp/folder, then altered the file according to the instructions. After I closed the file out, I tried to copy and paste the file to /etc/sysconfig/rhn/ and it turns out that I do not have permissions to the /etc/sysconfig/rhn/sources file, so the next question is how do I give myself permissions for this? I logged in under the root password and also tried to change permissions of the folder, but it mentions that I am not the owner of these files. Any help would greatly be appreciated.
After examining other posts the solution was very easy. I used the terminal screen, logged in as root and copied the file over to the correct directory. I then had two files named sources and sources.swp. The sources.swp was the new modified one so I renamed the sources to sourcesold and the sources.swp to sources. I am now able to check for updates....
Thanks for all of the support...
From one Newbie to the next. Please visit this site for basic instructions on how to manage your way through the terminal... With some knowledge of DOS, I was able to figure this out rather quickly....
The .swp file is there because you're still editing it (may be in another application or terminal window?). Most probably it still there because you killed the terminal w/o closing the editor properly.
tthe system WILL register by typing in rhn_register, then it will tell you that its not a valid archictecture and all and by putting the above lines into your up2date sources file, it will associate the channel to your machine... so yes the nag about the registration did go away at least on my machine
Originally posted by wiraone The .swp file is there because you're still editing it (may be in another application or terminal window?). Most probably it still there because you killed the terminal w/o closing the editor properly.
Wira one,
You were correct! It turned out that I was using the emacs program incorrectly and resulting in the creation of the sources.swp file. I spent about 15 - 20 minutes in the tutorial on how to use the program, and now as a Newbie, I am more dangerous then ever before. LOL.... For newbies, open emacs, click on help, then tutorial. Really appreciate all of the help from the community...
Lessons Learned:
- Spent numerous hours trying to get the update to work
- You cannot use the ecmacs or the IV program like notepad
- Kicking the dog actually helps when solving problems (Note to self: kick dog lightly!)
- Use the CTRL/ALT/F1 key to gain access (sign in as root)
- More importantly type "exit" and then CTRL/ALT/F7 to get back to the desktop
- Achieve one milestone at a time...
- Keep smiling and thanking the Fedora community ("Thanks Everyone")
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.