Yum update rest by peer?

[Olaf Olson]

Don

This is a simple one. Too many people are using the default and the pipe 
from the default yellowdog site is unable to give you all you are asking 
for, in a timely manner. Your computer grows tired of waiting and hangs 
up. If you browse to the YDL FAQ site:

http://www.sharplabs.com:8668/space/Updating+YDL/yum

Of course, this just tells you that you need to list some other 
repositories, besides the default (a repository is a place where 
application and utility packages reside and yum can grab the stuff it 
needs to get them installed and/or updated onto your machine.

If you're in the US, on the west coast, these are some good 
possibilities for repositories. Simply edit your /etc/yum.conf file and 
add these lines:

[update2]
name=Yellow Dog Linux 3.0 updates
baseurl=http://ydl.osuosl.org/yum/3.0.1/update/

[update3]
name=FreshRPMS
baseurl=http://ayo.freshrpms.net/yellowdog/3.0/ppc/freshrpms/

These will add repositories from Oregon State and the ever popular 
FreshRPMs site, which has lots of stuff that is newer than that provided 
by the YellowDog folks.

Free is still free, but it also means that you may not have the absolute 
latest and greatest stuff. You'll want to learn to compile, use source 
rpms, and all kinds of other things. Meanwhile, this will get you much 
further along the way.

Holler if you need help running a text editor!

Olaf

Dakidd wrote:

>>Hi, I don't know if I would to update my package using yum but through
>>the process, my connection was close and I receive this message:
>>
>>[Errno 104] Connection reset by peer
>>
>>Does this mean that I need to pay for a copy of yellowdog before I can
>>use the yum update software?
>>    
>>
>
>Possible, if the Yellowdog folks have configured yum to refuse to work
>unless it's bought, but I'd say that's pretty unlikely.
>
>"Connection reset by peer" is a standard internet message that's telling
>you the other end shut down the connection for some reason. It's basically
>the same as a ring-no-answer on the regular telephone - The exact reason is
>undefined, and could be anything from the person (server) on the other end
>going "CallerID says it's a phone salesman/bill collector/your
>mother-in-law/your obnoxious brother Bill - I ain't answering it!" to the
>"All circuits are busy now. Please try your call again later." recording
>you might be familiar with from trying to call a radio station when they've
>got one of those "Be the 437th caller on the studio line and win tickets to
>next week's Joe Schmoe and the Noisemakers concert!" thing going on.
>
>I've never heard an official "this condition will cause it every time"
>style explanation, but it seems to happen most often with really busy
>servers. Usually a retry (perhaps with a bit of waiting for traffic to
>clear) will work just fine, although if you're trying to get to a server
>that's super popular for some reason (Yellowdog primary download location,
>for instance), or perhaps under a DoS attack, the situation may persist for
>hours, or even days, at a time.
>
>Don Bruder -  dakidd at sonic.net      <--- Preferred Email - unmunged
>I will choose a path that's clear: I will choose Free Will! - N. Peart
>
>
>_______________________________________________
>yellowdog-newbie mailing list
>yellowdog-newbie at lists.terrasoftsolutions.com
>http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie
>
>  
>