Re: Closed: After an update som modules points to the old kernel

On Mon, 20 Sep 2004 09:55:19 +0200, Henrik Grevelund wrote:

> Hi There 
> 
> Michael wrote:
> > Next problem, How do i get the "vmlinuz-2.4.20-31.9" file onto the 
> > disk, when the machine doesn't have network, floppy or cdrom loadable.
> 
> I don't know yet where exactly your boot-image/bootdisk is located and
> how you use vmware to boot Fedora Core.
> 
> And Michael wrote:
> Perhaps 'man mkbootdisk' will tell you what you want.

I didn't write that. Brian T. Brunner did.
 
> I did run into a some problems that seems to be no end to. As i
> understand it, i had to have the old /lib/modules/old kernel, otherwise
> i couldn't correct the path.

?
 
> So i simply reinstalled. 
>
> Now i just have to figure which option to use when installing the
> kernel(rpm -i isn't the one).

It is for sure. But you don't seem to boot those kernels, but a
separate one on some boot disk or boot partition. If that is true,
you need to update your boot "thingy" everytime you erase a kernel
package. 'rpm -i' or better 'rpm -ivh' (verbose/hash output) installs
a new kernel and doesn't erase old kernels. Whenever you 'rpm -e' an
old kernel, update your boot media.
 
-- 
Fedora Core release 2 (Tettnang) - Linux 2.6.7-1.494.2.2
loadavg: 0.17 0.49 0.67


-- 
Shrike-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/shrike-list