Re: Kernel panic: NO INIT FOUND, but seems to be there.
On Wed, Apr 24, 2002 at 01:59:00AM -0500, Gary Turner wrote:
...
| In re using links, would you also use full file name for the kernel
| image rather than an alias? And, is a magical transformation very
| likely? If so, what would do it?
Yes, I use the full file name for both kernel and initrd images. The
magic transformation works like this :
o you have a working kernel, say 2.2.18pre21
you also have the bootloader working for it, but it is using
/vmlinuz as the kernel image
o you install a new kernel via apt-get
knowing you just installed a new kernel, you update your
bootloader to include a line for that and for the old one
o now you reboot and realize you messed up something (the new
kernel doesn't work right)
o ok, no problem, just select the old entry in the bootloader
and correct the mistake once you've booted
o DOH! the "old" kernel is really the new one because /vmlinuz
now points at the new image
(and fortunately I was using grub so I could specify the right kernel
image and actually boot the system. this is a true story, btw)
This is why I always use the full file name, and always add a new
entry to grub's config when I install a new kernel. (I know there's
the /vmlinuz and /vmlinuz.old layer, but that only allows 2 kernels
and I often have more)
-D
--
Come to me, all you who are weary and burdened, and I will give you
rest. Take my yoke upon you and learn from me, for I am gentle and
humble in heart, and you will find rest for your souls. For my yoke
is easy and my burden is light.
Matthew 11:28-30
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: