Forgive me if I just missed this (although I don't see it in man 5 yum.conf), but is there a config parameter that can be set which will disable changing the default kernel to what was just installed? For systems with 3rd party kernel modules for hardware devices (ie. SCSI), this can be a fatal issue when 'chkconfig yum on'. Thanks, Greg On Mon, Aug 11, 2003 at 01:51:08PM -0400, seth vidal told me: > > > Some days ago we had some discussion, when I proposed that handling of > > "special cases", like kernel install/upgrades, should better not be > > done via Yum "built-in" functions, but via external scripts and/or > > external Python modules/functions (currently not possible). Some > > predefined scripts/functions could then be included with Yum, or > > admins can write their own handler. This would also cover your request. > > Just to be clear the following is a description of what yum does: > > kernels are kept as a special case. They are always installed, they are > never updated. This is done so that older kernels are not replaced by > the newer kernels. > > After the transaction is complete yum looks through the list of packages > and checks to see if a kernel was in the list. If so, then it passes the > lists of kernels to a second function which then sets one of the kernels > to be the default boot kernel. > > This is, currently, handled internally to yum in python. I use the same > routines that up2date uses to update kernels. I did this so the updating > behavior would be the most consistent to red hat's behavior. > > -sv > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum -- Greg M. Kurtzer, CSE: Linux cluster specialist Lawrence Berkeley National Laboratory Contact: O=510.495.2307, P=510.448.4540, M=510.928.9953 1 Cyclotron Road #90-1116, Berkeley, CA 94720 http://www.lbl.gov, http://scs.lbl.gov/, http://lug.lbl.gov/ Email: GMKurtzer_at_lbl.gov, Text: 5109289953_at_mobileatt.net
