do yum rpm and hand compiles conflict?
 

i have rh9 legacy yum installed running the "nightly update". i scratched an itch and compiled 2.6.9, and have that as default in grub.conf, running with no bugs or probs.

if the yum nightly update gets a new kernel legacy rpm, willl that pose problems with my 2.6 kernel default, if any?

i would like the nightly auto yum updates to remain in effect, and have the kernels as well; should i put yum/kernel into exclude, or will that prevent it from downloading the kernel update altogether?
i'd just like to have it "handy". best scenario would be to rpm any new legacy kernel into the system, shoehorn it into grub, but not override my 2.6 config as default boot selection. i have no idea if this is do-able, in a cron or auto manner.
is manual <yum update> my only option, here? i can make this happen manually, i'd just like to know if i have to clean house on my auto stuff here. and i have NO idean how to get yum back out of it (if i really wanted to)!
any ideas?

tnx. -O

Not sure what mechanism you are using to do the nightly updates.

I manually update, if I want to exclude the kernels; I use: "yum --exclude kernel* update"

It really shouldn't pose a problem to include or exclude the kernel updates.

If by default your current kernel in grub.conf is not 0 then grub will probably not be modified.
Even if it is, it shouldn't be an issue. Before you manually reboot your machine, check that the
default kernel (the one that you want to boot) is still being pointed to by grub before rebooting.

Besides as far as I know RH9 is no longer supported. So, I doubt you'll be downloading any
new packages via yum (or anything else for that matter).

/Les

Interesting question and I don't claim to have a complete answer but this is the way I understand it. The updating of your kernel and grub.conf entry would depend on the way the rpm was built. yum only automates the process of downloading and installing updates. The rpm performs all the real work on the files. I believe grub.conf is updated with a %post script in the specfile that was used to build the rpm. I've seen entries append sometimes and become the default other times.

I have not heard of a way to use yum for downloading an rpm, but not have it install. That would make a nice post for the yum mailing list at Duke. For now, I would continue with your automated process and exclude kernel packages using yum.conf. You could get on the Fedora-Legacy-Announce mailing list to be notified when a new kernel has arrived. That way you can go through the process of manually updating the kernel on your schedule and keep track of the results.

Les: You might want to take a look at http://www.fedoralegacy.org. RH 7.3, 9.0, and FC1 are being supported by the community.

Bill

To clarify; what I've seen is that if the default kernel is not "0" by default, then it increments the
current default entry by 1.

So, if it is "0", then it leaves the default at "0" and bumps each entry down by 1, and the new entry
becomes "0", or the first entry in the list. When you reboot the new kernel becomes the default.

If it is not "0", say the current kernel boot entry is "1", then the update puts the new entry at the top
of the list and updates the "1" to a "2" to match the current default kernel entry. When you reboot,
the previous kernel is still the default.

Hope this makes sense...

Bill: Thanks for the tip on fedoralegacy.org

/Les

thanks! the thing that got my attention on this was the grub change from 0 to 1 on default. i guess what it boiled down to is just grabbing the grub.conf if my default kernel "highlighting" on boot ever changes, and putting the default back to 0.
see how easily i took something simple and made it as complicated as i could?
i shoulda been a politician.
happy holidays, folks.