in case this helps anyone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jude, at what point is the yum.conf file created?  If it's created before the missing package message kicks in, I wonder how the commented-out lines might cause it not to find on the CD images but have no trouble with the DVD image?  Or do I misunderstand what you're telling me?

What's that disk -99 error blog?  Sounds like something I should read with a beer or two in hand.

Could the commented-out lines be the reason for my update failures?  Still being largely a novice, I'm real careful about changing defaults, including lines in files like yum.conf.  

Thanks!

Al
----- Original Message ----- 
From: "Jude DaShiell" <jdashiel@xxxxxxxxxxxxxx>
To: <speakup at braille.uwo.ca>
Sent: Tuesday, January 30, 2007 11:06 PM
Subject: re: in case this helps anyone


> 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.
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.410 / Virus Database: 268.17.15/659 - Release Date: 1/30/2007
> 
> 




[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux