in case this helps anyone

[Jude DaShiell]

Now I think I can help out but it's only as a result of researching this 
disk -99 problem.  By the way, that disk -99 problem has its own dedicated 
blog some linux installer in India got so annoyed he now has a running 
blog. Here's something that should help with files not being able to be 
found.  The file /etc/yum.conf controls much of yum's behavior on fedora 
core systems and whenever yum is installed on other systems too.  There 
are lines inside of /etc/yum.conf that have repo on them because those are 
repository addresses.  These are where yum gets those files for you.  You 
will notice all of those repo lines are commented out by default.  A 
commented out line has no effect in Linux either in an executable or 
configuration file that is to say linux will read the line and do nothing 
but read the next line.  Comment lines start with # and many in these 
configuration files have informational text on them.  To remove a comment, 
edit the line and remove the # symbol and what was a comment earlier will 
then be executable provided the line has the proper syntax. If you use ex 
as an editor ex /etc/yum.conf gets you an editing session. A command like 
/freshrpms <cr> should get you to the freshrpms line or close to it. 
Since the # character is usually the first character on the line, a 
command like .,.s/#// <cr> should remove it.  Check your work with .p <cr> 
and =p <cr> if it's good do :w <cr> :q <cr> and you should be out at the 
fedora prompt again.