<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
-------- Original Message --------<br>
Subject: Re: [CentOS] Update from 5.2 to 5.3 kernel not on mirror<br>
From: Blake Hudson <a class="moz-txt-link-rfc2396E" href="mailto:blake@ispn.net"><blake@ispn.net></a><br>
To: CentOS mailing list <a class="moz-txt-link-rfc2396E" href="mailto:centos@centos.org"><centos@centos.org></a><br>
Date: Tuesday, April 07, 2009 10:00:53 PM<br>
<blockquote cite="mid:49DC1365.3020807@ispn.net" type="cite">
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
<br>
<br>
-------- Original Message --------<br>
Subject: Re: [CentOS] Update from 5.2 to 5.3 kernel not on mirror<br>
From: John R Pierce <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:pierce@hogranch.com"><pierce@hogranch.com></a><br>
To: CentOS mailing list <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:centos@centos.org"><centos@centos.org></a><br>
Date: Tuesday, April 07, 2009 4:46:21 PM<br>
<blockquote cite="mid:49DBC9AD.804@hogranch.com" type="cite">
<blockquote type="cite">
<pre wrap="">Interesting.....I thought that i686 used instructions only available
on later processors, i.e. i486 and pentium III do not have the later
instruction set to accept compiled code for i686.....
I'm no expert, but that is why there are i386, i686 and x86_64 type
packages to cater for various processor types.
</pre>
</blockquote>
<pre wrap=""><!---->
pentium-III is a i686, as is pretty much everything since Pentium Pro
i386 - 386
i486 - 486
i586 - pentium, pentium w/ mmx
i686 - pentium pro, p-II, p-III, p4, core/core2/etc.
</pre>
</blockquote>
I simply mentioned the CPU type because it had been done previously by
the op. I'm confident the issue has nothing to do with the CPU or
kernel type. The issue appears to be with some (or all) of the mirrors
under certain configurations. I was hoping someone with more
yum/mirror/repo experience would be able to spot the problem if I
squeaked - I'm sure it's something I can work around, but I wouldn't
want it to impact others.<br>
<br>
--Blake<br>
</blockquote>
<br>
Google indicates "Requested Range Not Satisfiable" is actually an HTTP
error (not specific to yum). The description of the error indicates
that my browser (yum) requested a segment of the file that does not
exist... e.g, bytes 10-1000 of a 100 byte file. I'm thinking that this
file is possibly corrupt or the mirrors think the file is larger than
it actually is? just a guess...<br>
<br>
<br>
</body>
</html>