> 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. Okay, I understand this. But this doesn't cover, at least from what I understand, the second part of my request which is to (1) tag the previous kernel with some configurable tag like "-old" (e.g. "Red Hat Linux (2.4.20-18.9)-old") and (2) remove all old kernels (i.e. kernels other than the new one and the "-old" one). That's where the additional scripting (external or internal) that Jos mentions would come in. Is this right or am I missing something? -- Jeremy Dreese Engineering Computing Systems Integrator College of Engineering Bucknell University voice: (570) 577-3714 fax: (570) 577-3579 email: jdreese@xxxxxxxxxxxx
