> -----Original Message----- > From: centos-devel-bounces at centos.org > [mailto:centos-devel-bounces at centos.org] On Behalf Of Matt Hyclak > Sent: Friday, March 02, 2007 10:29 AM > To: The CentOS developers mailing list. > Subject: Re: [CentOS-devel] Back-port md raid1/10 BIO_RW_SYNC > patch for DRBD > > On Fri, Mar 02, 2007 at 09:49:37AM -0500, Ross S. W. Walker > enlightened us: > > > -----Original Message----- > > > From: centos-devel-bounces at centos.org > > > [mailto:centos-devel-bounces at centos.org] On Behalf Of > Johnny Hughes > > > Sent: Friday, March 02, 2007 3:39 AM > > > To: CentOS-Devel > > > Subject: RE: [CentOS-devel] Back-port md raid1/10 BIO_RW_SYNC > > > patch for DRBD > > > > > > On Thu, 2007-03-01 at 14:47 -0500, Ross S. W. Walker wrote: > > > > > -----Original Message----- > > > > > From: centos-devel-bounces at centos.org > > > > > [mailto:centos-devel-bounces at centos.org] On Behalf Of Ross S. > > > > > W. Walker > > > > > Sent: Thursday, March 01, 2007 9:22 AM > > > > > To: The CentOS developers mailing list. > > > > > Subject: RE: [CentOS-devel] Back-port md raid1/10 BIO_RW_SYNC > > > > > patch for DRBD > > > > > > > > > > > -----Original Message----- > > > > > > From: centos-devel-bounces at centos.org > > > > > > [mailto:centos-devel-bounces at centos.org] On Behalf Of > > > Johnny Hughes > > > > > > Sent: Thursday, March 01, 2007 6:15 AM > > > > > > To: CentOS-Devel > > > > > > Subject: RE: [CentOS-devel] Back-port md raid1/10 > BIO_RW_SYNC > > > > > > patch for DRBD > > > > > > > > > > <snip> > > > > > > > > > > Does that make a difference, will yum recognize it as a > > > > > upgrade or dependency from the current version? > > > > > > > > > > Also I didn't install the standard kernel I did a yum update > > > > > from 2.6.9-42.0.8.plus.c4smp and it went ahead and installed > > > > > the standard? > > > > > > > > > > Maybe the mirror hadn't received all the updates yet and it > > > > > decided the standard was the best candidate? > > > > > > > > It was the mirror having not sync'd up all the updates. > > > > > > > > I did notice something, that might have been true before, but > > > > just noticed now. The kernel development headers are marked > > > > as upgrades to the previous ones so you can only have one > > > > installed at a time. > > > > > > > > That makes it hard to compile kernel drivers for previous > > > > versions you may have installed if you need to revert back > > > > to the previous version. > > > > > > That is true, and is how the version of YUM is written that > > > is included > > > in c4 ... you can fix this issue with this line in your > > > yum.config file > > > (all one line): > > > > > > installonlypkgs=kernel kernel-smp kernel-devel > > > kernel-smp-devel kernel-largesmp kernel-devel-largesmp > > > kernel-hugemem kernel-hugemem-devel > > > > Thanks, mate, that should help. > > > > So the above option will make sure that the kernel-devel* > are included in the installonly algorithm. > > > > Is there an option to select how many previous installonlys > are to be allowed? I looked in the man pages, but didn't see > the option there. I just want to bump it to 3 from 2. > > > > I believe there is an installonlyn plugin you could probably get. > > Matt Hmmm, I suppose you mean outside the CentOS repo, as I looked in there and found fastestmirror, protectbase, priorities, but no installonly :-( I want to try and avoid Frankensteining my setup, especially for such a small item. Nah, I can live with only 2 kernel versions,. -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.