There is an updated kernel available for CentOS-3.1
https://rhn.redhat.com/errata/RHSA-2004-188.html refers.
Updated files are :-
Common Files
i386/updates/RPMS/kernel-BOOT-2.4.21-15.EL.c0.i386.rpm i386/updates/RPMS/kernel-doc-2.4.21-15.EL.c0.i386.rpm i386/updates/RPMS/kernel-source-2.4.21-15.EL.c0.i386.rpm
athlon specific
i386/updates/RPMS/kernel-2.4.21-15.EL.c0.athlon.rpm i386/updates/RPMS/kernel-smp-2.4.21-15.EL.c0.athlon.rpm i386/updates/RPMS/kernel-unsupported-2.4.21-15.EL.c0.athlon.rpm i386/updates/RPMSkernel-smp-unsupported-2.4.21-15.EL.c0.athlon.rpm
i686 specific
i386/updates/RPMS/kernel-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-smp-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-hugemem-2.4.21-15.EL.c0.i686.rpm
i386/updates/RPMS/kernel-unsupported-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-smp-unsupported-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-hugemem-unsupported-2.4.21-15.EL.c0.i686.rpm
source rpm
i386/updates/SRPMS/kernel-2.4.21-15.EL.c0.src.rpm
These are available at http://mirror.centos.org/3.1/ and should be on all mirrors within a few hours.
To update to the latest version 'yum update kernel' should be sufficient.
Lance
Lance,
Kudos to all the hard work the CentOS team has put into this distribution. Will the other couple dozen updates be made available soon or will we have to wait for 3.2? What can the community do to help improve turn-around time on Redhat errata?
Lance Davis wrote:
There is an updated kernel available for CentOS-3.1
https://rhn.redhat.com/errata/RHSA-2004-188.html refers.
Updated files are :-
Common Files
i386/updates/RPMS/kernel-BOOT-2.4.21-15.EL.c0.i386.rpm i386/updates/RPMS/kernel-doc-2.4.21-15.EL.c0.i386.rpm i386/updates/RPMS/kernel-source-2.4.21-15.EL.c0.i386.rpm
athlon specific
i386/updates/RPMS/kernel-2.4.21-15.EL.c0.athlon.rpm i386/updates/RPMS/kernel-smp-2.4.21-15.EL.c0.athlon.rpm i386/updates/RPMS/kernel-unsupported-2.4.21-15.EL.c0.athlon.rpm i386/updates/RPMSkernel-smp-unsupported-2.4.21-15.EL.c0.athlon.rpm
i686 specific
i386/updates/RPMS/kernel-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-smp-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-hugemem-2.4.21-15.EL.c0.i686.rpm
i386/updates/RPMS/kernel-unsupported-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-smp-unsupported-2.4.21-15.EL.c0.i686.rpm i386/updates/RPMS/kernel-hugemem-unsupported-2.4.21-15.EL.c0.i686.rpm
source rpm
i386/updates/SRPMS/kernel-2.4.21-15.EL.c0.src.rpm
These are available at http://mirror.centos.org/3.1/ and should be on all mirrors within a few hours.
To update to the latest version 'yum update kernel' should be sufficient.
Lance
On Thu, 13 May 2004, Chris Sorisio wrote:
Lance,
Kudos to all the hard work the CentOS team has put into this distribution. Will the other couple dozen updates be made available soon or will we have to wait for 3.2?
They will mostly be built as updates to 3.1, but they are not security related, they are bugfix/enhancement ... 3.2 involves a new version of anaconda and respin of the isos and that may not be relevant to 3.1 ....
What can the community do to help improve turn-around time on Redhat errata?
Volunteers are always welcome :)
The reason the kernel takes so long is that it just takes that long to build and test.(likewise openoffice)
If you have some decent hardware then it should be quicker ...
As regards the other upodates it is a question of checking whether oatches apply cleanly, removing trademarks where necessary and testing.
An automatic system is required, buyt at the end of the day manual intervention will probably always be needed.
Lance
Time is something I'm prepared to offer, though my black magic skills are limited. I'll check to see if I can make CPU time available, but that brings up another questions: how do we establish trust? What process is reasonable to verify that packages I build, for example, are trustworthy? I have a handful of packages I'd be happy to send over this weekend (MySQL 4.0.18, etc) but how would the project prefer I sign them, what quality control steps do I need to verify first, etc?
I was also thinking of somthing automated, and while manual intervention still would be required, it would hopefully reduce the cycle time significantly. Ideally, CentOS would have a system that would:
1. Automatically detect when an update has been released (via parsing the announcement e-mail from Red Hat or something?) 2. Download the SRPM. 3. Build a first-pass RPM and notify the package maintainer when it is ready for review. 4. Depending on the maintainer's review, the package is either: a. released (another scripted process which automates GPG signing and transferring the RPM to the appropriate repositories and sends out an e-mail to the list about its availability after an appropriate time-lapse so that the mirrors have a chance to mirror it) or b. rejected, pending modifications and another build cycle.
This would at least take some of the load off the maintainer's shoulders and - hopefully - most updates would rebuild cleanly and not need modifications. When we know in advance that package X needs mods Y, we could make the system aware of it.
All we need is someone talented enough to craft such a system. I can admit without too much shame that it's mostly beyond my abilities. Anyone volunteers out there? ;)
Lance Davis wrote:
What can the community do to help improve turn-around time on Redhat errata?
Volunteers are always welcome :)
The reason the kernel takes so long is that it just takes that long to build and test.(likewise openoffice)
If you have some decent hardware then it should be quicker ...
As regards the other upodates it is a question of checking whether oatches apply cleanly, removing trademarks where necessary and testing.
An automatic system is required, buyt at the end of the day manual intervention will probably always be needed.
Lance
On Fri, 14 May 2004, Chris Sorisio wrote:
significantly. Ideally, CentOS would have a system that would:
<snip>
All we need is someone talented enough to craft such a system. I can admit without too much shame that it's mostly beyond my abilities. Anyone volunteers out there? ;)
already in process, along with some server side changes.
-- Russ Herrold
Is there a time delay on the mirrors, or am I doing something wrong? 'yum update kernel' still doesn't see the new packages when I run it. I haven't modified my yum.conf.
Lance Davis wrote:
These are available at http://mirror.centos.org/3.1/ and should be on all mirrors within a few hours.
To update to the latest version 'yum update kernel' should be sufficient.
Lance
On Fri, 14 May 2004, Chris Sorisio wrote:
Is there a time delay on the mirrors, or am I doing something wrong? 'yum update kernel' still doesn't see the new packages when I run it. I haven't modified my yum.conf.
It worked for me ...
which kernel are you using - you may need yum update kernel-smp etc
try just 'yum update' - you can always say no.
Lance
Lance Davis wrote:
These are available at http://mirror.centos.org/3.1/ and should be on all mirrors within a few hours.
To update to the latest version 'yum update kernel' should be sufficient.
Lance
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
Linux ssupp003 2.4.21-9.0.3.EL.c0smp #1 SMP Sat Apr 24 22:52:04 BST 2004 i686 i686 i386 GNU/Linux
[root@ssupp003 yum]# yum update Gathering header information file(s) from server(s) Server: CentOS-3.1 - Addons Server: CentOS-3.1 - Base Server: CentOS-3.1 - Extras Server: CentOS-3.1 - Updates Finding updated packages Downloading needed headers No Packages Available for Update No actions to take
Lance Davis wrote:
On Fri, 14 May 2004, Chris Sorisio wrote:
Is there a time delay on the mirrors, or am I doing something wrong? 'yum update kernel' still doesn't see the new packages when I run it. I haven't modified my yum.conf.
It worked for me ...
which kernel are you using - you may need yum update kernel-smp etc
try just 'yum update' - you can always say no.
Lance
On Fri, 14 May 2004, Chris Sorisio wrote:
Linux ssupp003 2.4.21-9.0.3.EL.c0smp #1 SMP Sat Apr 24 22:52:04 BST 2004 i686 i686 i386 GNU/Linux
[root@ssupp003 yum]# yum update Gathering header information file(s) from server(s) Server: CentOS-3.1 - Addons Server: CentOS-3.1 - Base Server: CentOS-3.1 - Extras Server: CentOS-3.1 - Updates Finding updated packages Downloading needed headers No Packages Available for Update No actions to take
Hmm - 'yum list \kernel*' ???
Also which mirror are you pointed at ???
Regards Lance
Lance Davis wrote:
On Fri, 14 May 2004, Chris Sorisio wrote:
Is there a time delay on the mirrors, or am I doing something wrong? 'yum update kernel' still doesn't see the new packages when I run it. I haven't modified my yum.conf.
It worked for me ...
which kernel are you using - you may need yum update kernel-smp etc
try just 'yum update' - you can always say no.
Lance
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
I'm going to feel pretty silly if I disabled kernel updating somehow. :)
Output of 'yum list \kernel*':
[root@ssupp003 yum]# yum list \kernel* Gathering header information file(s) from server(s) Server: CentOS-3.1 - Addons Server: CentOS-3.1 - Base Server: CentOS-3.1 - Extras Server: CentOS-3.1 - Updates Finding updated packages Downloading needed headers Looking in Available Packages: Name Arch Version Repo -------------------------------------------------------------------------------- kernel athlon 2.4.21-9.0.3.EL.c0 update kernel-BOOT i386 2.4.21-9.0.3.EL.c0 update kernel-doc i386 2.4.21-9.0.3.EL.c0 update kernel-hugemem i686 2.4.21-9.0.3.EL.c0 update kernel-hugemem-unsupported i686 2.4.21-9.0.3.EL.c0 update kernel-smp athlon 2.4.21-9.0.3.EL.c0 update kernel-smp-unsupported i686 2.4.21-9.0.3.EL.c0 update kernel-smp-unsupported athlon 2.4.21-9.0.3.EL.c0 update kernel-unsupported i686 2.4.21-9.0.3.EL.c0 update kernel-unsupported athlon 2.4.21-9.0.3.EL.c0 update
Looking in Installed Packages: Name Arch Version Repo -------------------------------------------------------------------------------- kernel i686 2.4.21-9.0.3.EL.c0 db kernel-pcmcia-cs i386 1:3.1.31-13 db kernel-smp i686 2.4.21-9.0.3.EL.c0 db kernel-source i386 2.4.21-9.0.3.EL.c0 db kernel-utils i386 1:2.4-8.37.1 db
yum.conf:
[root@ssupp003 mysql]# cat /etc/yum.conf [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=redhat-release installonlypkgs=kernel kernel-smp kernel-hugemem kernel-enterprise kernel-debug kernel-unsupported kernel-smp-unsupported kernel-hugemem-unsupported tolerant=1 exactarch=1
[base] name=CentOS-$releasever - Base baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/ gpgcheck=1
#released updates [update] name=CentOS-$releasever - Updates baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/ gpgcheck=1
#packages used/produced in the build but not released [addons] name=CentOS-$releasever - Addons baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/ gpgcheck=1
#additional packages that may be useful [extras] name=CentOS-$releasever - Extras baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/ gpgcheck=1
#packages in testing #[testing] #name=CentOS-$releasever - Testing #baseurl=http://mirror.centos.org/centos/$releasever/testing/$basearch/ #gpgcheck=1
Thanks,
Chris
Lance Davis wrote:
Hmm - 'yum list \kernel*' ???
Also which mirror are you pointed at ???
On Fri, 14 May 2004, Chris Sorisio wrote:
I'm going to feel pretty silly if I disabled kernel updating somehow. :)
Output of 'yum list \kernel*':
[root@ssupp003 yum]# yum list \kernel* Gathering header information file(s) from server(s) Server: CentOS-3.1 - Addons Server: CentOS-3.1 - Base Server: CentOS-3.1 - Extras Server: CentOS-3.1 - Updates Finding updated packages Downloading needed headers Looking in Available Packages: Name Arch Version Repo
kernel athlon 2.4.21-9.0.3.EL.c0 update kernel-BOOT i386 2.4.21-9.0.3.EL.c0 update kernel-doc i386 2.4.21-9.0.3.EL.c0 update kernel-hugemem i686 2.4.21-9.0.3.EL.c0 update kernel-hugemem-unsupported i686 2.4.21-9.0.3.EL.c0 update kernel-smp athlon 2.4.21-9.0.3.EL.c0 update kernel-smp-unsupported i686 2.4.21-9.0.3.EL.c0 update kernel-smp-unsupported athlon 2.4.21-9.0.3.EL.c0 update kernel-unsupported i686 2.4.21-9.0.3.EL.c0 update kernel-unsupported athlon 2.4.21-9.0.3.EL.c0 update
well you _must_ be going through a proxy or something that has an outdated cache ???
my yum.conf is identical and I get ...
yum list \kernel* Gathering header information file(s) from server(s) Server: CentOS-3.1 - Addons Server: CentOS-3.1 - Base Server: CentOS-3.1 - Extras Server: CentOS-3.1 - Updates Finding updated packages Downloading needed headers Looking in Available Packages: Name Arch Version Repo -------------------------------------------------------------------------------- kernel athlon 2.4.21-15.EL.c0 update kernel-BOOT i386 2.4.21-15.EL.c0 update kernel-doc i386 2.4.21-15.EL.c0 update kernel-hugemem i686 2.4.21-15.EL.c0 update kernel-hugemem-unsupported i686 2.4.21-15.EL.c0 update kernel-smp athlon 2.4.21-15.EL.c0 update kernel-smp-unsupported i686 2.4.21-15.EL.c0 update kernel-smp-unsupported athlon 2.4.21-15.EL.c0 update kernel-source i386 2.4.21-15.EL.c0 update kernel-unsupported athlon 2.4.21-15.EL.c0 update kernel-unsupported i686 2.4.21-15.EL.c0 update
Looking in Installed Packages: Name Arch Version Repo -------------------------------------------------------------------------------- kernel i686 2.4.21-15.EL.c0 db kernel-pcmcia-cs i386 1:3.1.31-13 db kernel-smp i686 2.4.21-15.EL.c0 db kernel-utils i386 1:2.4-8.37.1 db
Can you see the new kernels in http://mirror.centos.org/centos/3.1/updates/i386/RPMS/ ???
You could try using as mirror to force reread of the cache ???
Regards Lance
Interesting; yes, I do see the updated packages when I check the URL given via Firebird. I'm using the same proxy that the server is, though, so now I'm more puzzled than before. Even after viewing the URL from the server via links, yum list still shows the old packages.
Squid logs:
1084548376.858 211 TCP_MISS/200 10348 GET http://mirror.centos.org/centos/3.1/updates/i386/RPMS/ - DIRECT/69.56.240.122 text/html 1084548386.023 0 TCP_HIT/200 13136 GET http://mirror.centos.org/centos/3.1/addons/i386/headers/header.info - NONE/- text/plain 1084548386.055 8 TCP_HIT/200 74010 GET http://mirror.centos.org/centos/3.1/os/i386/headers/header.info - NONE/- text/plain 1084548386.161 0 TCP_MEM_HIT/200 485 GET http://mirror.centos.org/centos/3.1/extras/i386/headers/header.info - NONE/- text/plain 1084548386.166 0 TCP_MEM_HIT/200 3421 GET http://mirror.centos.org/centos/3.1/updates/i386/headers/header.info - NONE/- text/plain
The MISS occured when I tried to view the URL via links from the server. Notice it's showing as text/html. Yum appears to be grabbing it as text/plain, and it's a MEM_HIT. So it looks like a local Squid issue and I need to force a refresh.
Lance Davis wrote:
Can you see the new kernels in http://mirror.centos.org/centos/3.1/updates/i386/RPMS/ ??? You could try using as mirror to force reread of the cache ???
On Fri, 14 May 2004, Chris Sorisio wrote:
Interesting; yes, I do see the updated packages when I check the URL given via Firebird. I'm using the same proxy that the server is, though, so now I'm more puzzled than before. Even after viewing the URL from the server via links, yum list still shows the old packages.
Squid logs:
1084548376.858 211 TCP_MISS/200 10348 GET http://mirror.centos.org/centos/3.1/updates/i386/RPMS/ - DIRECT/69.56.240.122 text/html 1084548386.023 0 TCP_HIT/200 13136 GET http://mirror.centos.org/centos/3.1/addons/i386/headers/header.info - NONE/- text/plain 1084548386.055 8 TCP_HIT/200 74010 GET http://mirror.centos.org/centos/3.1/os/i386/headers/header.info - NONE/- text/plain 1084548386.161 0 TCP_MEM_HIT/200 485 GET http://mirror.centos.org/centos/3.1/extras/i386/headers/header.info - NONE/- text/plain 1084548386.166 0 TCP_MEM_HIT/200 3421 GET http://mirror.centos.org/centos/3.1/updates/i386/headers/header.info - NONE/- text/plain
The MISS occured when I tried to view the URL via links from the server. Notice it's showing as text/html. Yum appears to be grabbing it as text/plain, and it's a MEM_HIT. So it looks like a local Squid issue and I need to force a refresh.
Hmm - /RPMS/ is text./html whereas I suppose the .info files are text/plain
Maybe we need to nocache the .info files or something ???
Regards lance
Lance Davis wrote:
Can you see the new kernels in http://mirror.centos.org/centos/3.1/updates/i386/RPMS/ ??? You could try using as mirror to force reread of the cache ???
CentOS mailing list CentOS@caosity.org http://www.caosity.org/mailman/listinfo/centos
You may want to nocache the .info files. I've added a directive in my squid.conf to do so on my end going forward and after restarting Squid, I'm now able to see the current packages.
Lance Davis wrote:
Hmm - /RPMS/ is text./html whereas I suppose the .info files are
text/plain
Maybe we need to nocache the .info files or something ???
and .. you havent disabled kernel updating have you ... ??
Regards Lance
-
Chris Sorisio -
Lance Davis -
R P Herrold