On Tuesday 09 December 2003 12:33 pm, John Richard Smith wrote:
> I Hadn't thought of that, a bit obvious really.
> So I decided, what have I got to loose.
> but instead, I decided to try installing the original
> kernel-2.4.21-0.13mdk off the discs. sure enough it installed
> something.
> ls - /boot
>
> vmlinuz-2.4.21-0.13mdk
>
> there it is, back again, but will it work , I don't know,
> I mean originally on first install it had to do a complicated
> device scan and choose options to build into the kernel so
> that what you are left with is a synthesis of the original
> kernel built to your hardware needs, so how does it know
> how to do this again, without going through all the same old
> device scan proceedure ?
> Or perhaps it does,unseen behind the install script ?
>
> At the moment I'm of the mind set that I only get the one
> chance to reboot, the old kernel is in memory now, but if
> things are not right no chance to replace.
> Any one know if it will work ?
I think you've got it fixed, tho I would'a used
'rpm -ivh --force kernel-2.4.21-0.13mdk..rpm' The addition of
force would insure that all the needed files and dirs for the
kernel are replaced. You can still do it, and I suggest you do.
This is about the only proper use of --force, ie, to replace
files and packages for existing packages, in this case the
kernel. (see 'man rpm').
If you're worried that this kernel won't boot, as already
suggested, just install the updated kernel along side the old.
Then you'll have two to boot to. You really should be usin the
updated kernel anyhow.
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
