On Thu, Apr 07, 2005 at 02:56:49PM -0500, Pettit, Paul wrote: > > David Bear wrote: > > > > it looks that up2date has kernel selected to ignore. I am wondering > > why. I think the simple answer is that you don't want to surprise anybody with a new kernel that could require the user to have to reboot. You could potentially have issues with 3rd party modules that need a specific version of the kernel. It's also recommended that you reboot after you install a new kernel. You can simply configure up2date to not skip the kernel and install the updates as long as you remember to reboot after you apply them. > Because the 'stock' kernels that up2date would download may not be right > for your (or many other) setup. Also up2date does updates to currently > installed packages, when "updating" a kernel you should *install* (rpm > -i) new kernel packages not upgrade. This is to ensure that if the new > kernel is not going to work on your box you can just boot to the > previously working one. up2date does do this correctly. It always installs new kernels and does not delete the older ones. > In general it's recommended that you manually "upgrade" to new kernels > thus to make sure nothing bad happens. That's old news. up2date works fine these days. > > what are the conditions underwhich I would not want to keep my kernel > > up2date as well? Only run an old kernel if you have to or if you need to have your own customized kernel. I have one system currently configured with an old kernel because I can't afford to reboot it right now and there are significant driver changes (SAN drivers). It's just safer to run the old kernel until I'm ready to reboot, then I'll apply the update. -- Ed Wilts, RHCE Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
