search for: 55.0.6

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Security Advisory 2007:0774 https://rhn.redhat.com/errata/RHSA-2007-0774.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: kernel-2.6.9-55.0.6.EL.i586.rpm kernel-2.6.9-55.0.6.EL.i686.rpm kernel-devel-2.6.9-55.0.6.EL.i586.rpm kernel-devel-2.6.9-55.0.6.EL.i686.rpm kernel-doc-2.6.9-55.0.6.EL.noarch.rpm

CentOS Errata and Security Advisory 2007:0774 https://rhn.redhat.com/errata/RHSA-2007-0774.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: kernel-2.6.9-55.0.6.EL.x86_64.rpm kernel-devel-2.6.9-55.0.6.EL.x86_64.rpm kernel-doc-2.6.9-55.0.6.EL.noarch.rpm kernel-largesmp-2.6.9-55.0.6.EL.x86_64.rpm kernel-largesmp-devel-2.6.9-55.0.6.EL.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I removed an ATA drive (/home) for a new SATA and my system would not boot. I'm guessing that it put the MBR on that drive instead of the drive that holds the / partition. What's the best way confirm where the MBR resides and, after I verify that's my problem, how I can move (or make a copy) onto a different drive? Thanks, Scott

CentOS Errata and Security Advisory 2007:0774 https://rhn.redhat.com/errata/RHSA-2007-0774.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/kernel-2.6.9-55.0.6.EL.ia64.rpm updates/ia64/RPMS/kernel-devel-2.6.9-55.0.6.EL.ia64.rpm updates/ia64/RPMS/kernel-largesmp-2.6.9-55.0.6.EL.ia64.rpm

CentOS Errata and Security Advisory 2007:0774 https://rhn.redhat.com/errata/RHSA-2007-0774.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/kernel-2.6.9-55.0.6.EL.s390.rpm updates/s390/RPMS/kernel-devel-2.6.9-55.0.6.EL.s390.rpm s390x: updates/s390x/RPMS/kernel-2.6.9-55.0.6.EL.s390x.rpm

# rpm -qa | grep kernel-2 | sort kernel-2.6.9-42.0.10.EL kernel-2.6.9-42.0.2.EL kernel-2.6.9-42.0.3.EL kernel-2.6.9-42.0.8.EL kernel-2.6.9-42.EL kernel-2.6.9-55.0.2.EL kernel-2.6.9-55.0.6.EL kernel-2.6.9-55.0.9.EL kernel-2.6.9-55.EL I'm running the most recent kernel available, and I've never had a problem with any past kernels, so I don't believe there's any reason to keep all of

I have used the package-cleanup utility to remove old kernel packages, but I noticed that it only removes the 'kernel' and 'kernel-devel' packages. It does not touch 'kernel-smp', 'kernel-hugemem', etc. What is the recommended method of cleaning up these other kernel packages? Should I just 'yum remove' the ones I don't need? Some of my servers have a

Hi, We currently have an CentOS 4.5 running Ultra Monkey box serving web requests to two real servers. Info as below : ipvsadm-1.24-6 heartbeat-2.1.2-3.el4.centos CentOS 4.5(kernel-smp-2.6.9-55.0.6.EL) All was working fine this morning until I upgraded our OS and patched the kernel to kernel-smp-2.6.9-55.0.9.EL via YUM(CESA-2007:0937). After that users started complaining that they were

(Sorry for starting a new thread; I could not find the original message in my mbox.) Martin Hamant wrote: > Johnny Hughes <johnny at centos.org> ?crivait: >> OK ... For the drbd-kmod*.plus kernels, they are now in the CentOSPlus >> directory / Repository. If you are using CentOSPlus kernel, you need >> to also get your module for DRBD (or XFS) from there too. >>

I'm running CentOS 5.1 with all updates, and the xen kernel. For some reason the OS is not seeing the full amount of ram. #uname -a Linux CentOS-VM-A 2.6.18-53.1.21.el5xen #1 SMP Tue May 20 10:03:27 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux # free total used free shared buffers cached Mem: 6104064 3445136 2658928 0 1412236

Sorry this is going to be a bit vague, but I''ve noticed something rather odd going on with EventMachine on Linux. I''ve written something uses EventMachine to proxy HTTP to other processes. On OS X, it works great, adding only about 20% extra latency into the connection when proxying versus connecting to the original backend process directly, so a 5ms connection might now take