Am 18. Aug, 2003 schw=E4tzte Bill Jonas so:

> From what you're telling us, it sounds like all you need to do is run
> 'dpkg --purge kernel-image-2.4.bad', followed by 'apt-get install
> kernel-image-2.4.new'.  My understanding of your situation is that the

And check that lilo is configged properly.

> current default kernel is not working and you manually select the
> alternate kernel each time you boot.  In this case, purging the kernel
> image will remove the /vmlinuz symlink and leave the /vmlinuz.old as it
> is.  Then installing the new kernel will cause the /vmlinuz symlink to
> be created and the /vmlinuz.old will still not be touched.  (If you were
> just removing the newer one, you could 'mv /vmlinuz.old /vmlinuz' and
> then re-run lilo.)

Don't forget initrd.img and initrd.img.old.

> If you still have the Debian installation media, they can be used to
> boot into your system if anything goes wrong.  I believe at the boot
> prompt it would be 'rescue root=3D/dev/hdXY'.  Since you're using
> 2.4.18-bf2.4 on your machine, it would be the same kernel as what you're
> using.

rescbf24 to use the bf24 kernel.

> Out of curiosity, what's the new (non-working) kernel?  Does it require
> that you specify an initrd?  (Just wondering why it panics rather than
> booting.)

For debian using a prepackaged 2.4 kernel other than the installation kerne=
l
an initrd is required.

ciao,

der.hans
--=20
#  https://www.LuftHans.com/    http://www.AZOTO.org/
#  Stell dir vor, es ist Krieg und keiner geht hin...