On Mon, 22 Oct 2001, Matilainen Panu (NBI/Helsinki) wrote:
> On Mon, 22 Oct 2001, ext Silviu Cojocaru wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > According to many people using RHL, the up2date utility cannot > > be used to upgrade kernels. Ok, so then, why the heck do > > advisories regarding kernel updates include info that tells > > the users that he can grab the kernel rpms using up2date. The > > average newbie will certainly use up2date to grab and > > *install* the kernel, thus resulting in a possibly hosed > > system. > > > > My suggestion would be to describe the steps to make up2date > > only grab *not* install the kernel rpms and tell the user > > where to find info about kernel upgrading. > > > > Comments ? Flames ? :) > > Old up2date cannot upgrade the kernel but since RHL 7.1 it's been > possible (and has worked for me) I tried it, once, on my laptop with 7.1. I forgot to update my lilo.conf and rerun lilo. It might be possible, but it's not advisable...up2date will "rpm -U" the kernel, upgrading it instead of installing it as an additional kernel option. The problem is that the up2date/rpm -U procedure does not update your lilo.conf, nor does it rerun lilo for you. The best bet is to download the appropriate kernel RPMs, run "rpm -i" on them, add them to your lilo.conf, run lilo, and then reboot to try them. The point of that exercise is to ensure that you don't lose the capability of booting your system with the old kernel, in case the new one doesn't work for you. _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
