On Mon, 22 Oct 2001, ext Silviu Cojocaru wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Monday, October 22, 2001 at 6:17:33 PM ,
> Mike Burger wrote about "up2date and kernels":
>
> > 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.
>
> :) my problem was not upgrading the kernel, as I know how to do
> that, the problem is that the advisory text might deceive a
> newbie into believing that up2date will take care of it, like
> "setup.exe" :), so he forgets to modify lilo.conf. In this case,
> if he does mot have a bootdisk he's pretty much screwed (pardon
> my lang). The idea was that instead of soemthing like:
>
> <quote>
> Before applying this update, make sure all previously released errata
> relevant to your system have been applied.
>
> The procedure for upgrading the kernel is documented at:
>
> http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.h
> tml
>
> Please read the directions for your architecture carefully before
> proceeding with the kernel upgrade.
> </quote>
>
> this part is ok, but read below:
>
> <quote>
>
> Please note that this update is also available via Red Hat Network.
> Many
> people find this to be an easier way to apply updates. To use Red Hat
> Network, launch the Red Hat Update Agent with the following command:
>
> up2date
>
> This will start an interactive process that will result in the
> appropriate
> RPMs being upgraded on your system.
> </quote>
>
> Now that is the tricky part.. Maybe up2date should be made to
> recognize kernel updates and act a bit differently, like
> modifying lilo.conf and rerunning LILO after that...
It DOES work properly with kernels too nowadays! It even leaves a backup
entry into lilo.conf for your older kernel which it preserves etc. Just
updated last week a stock RHL 7.1 to the latest patches including kernel,
everything with just 'up2date -u'. No messing around with lilo.conf or
anything like that. It just ships configured so that it wont touch the
kernel unless you tell it to.
- Panu -
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
