On Thu, 19 Feb 2004 18:34:25 +0100, mess-mate wrote:
> On Thu, 19 Feb 2004 17:20:26 +0100
> "Monique Y. Herman" <[EMAIL PROTECTED]> wrote:
>
> |On 2004-02-19, mess-mate penned:
> |
> |> Sorry, not clear enough for me.
> |> I'd a kernel-image -2.4.24-1-686 installed and did an upgrade to the 2.4.24-2
> |> Since Can't boot anymore; the boot sequence stops after loading the initrd.
> |> Didn't reinstall lilo; the vmlinuz-name seems the same .
> |> Anyone had this pb ?
> |> Regards
> |> mess-mate
> |>
> |>
> |
> |You need to re-run lilo after changing the kernel. The fact that the
> |name doesn't change is irrelevant. (However, I'm not sure if the
> |package installer prompts you to run lilo when you install a kernel
> |image?)
> |
> |--
> |monique
> |
> Yes hi did and I didn't run lilo !. I'll rerun lilo immediatly.
> Thanks for the tip.
> mess-mate
Just try to keep in mind that, on installation (i.e. when you run "lilo"),
lilo builds a map of physical locations (i.e. disk sectors) of what it
needs at boot time. That's why it's so small and why it doesn't need to
grok filesystems at boot time. The downside is that you need to remember
to rerun it when you do anything which changes where stuff it needs
physically resides.
For instance, renaming a kernel image, copying a new kernel image into
/boot with the same name as the prior kernel image, and then removing the
old kernel image will put the new kernel image in a different physical
location, even though everything "looks" exactly the same. In fact, lilo
might even still be able to boot the old deleted image if none of its
sectors get overwritten. That's speculation on my part - what is *not*
speculation is that it will not be able to boot the new image because it
knows nothing about it.
The answer is always: "You can never run lilo too many times", or: "When
in doubt, run lilo" :)
I speak from experience: I have forgotten to run lilo more times than
Madonna's dropped her underwear.
--
....................paul
It is important to realize that any lock can be picked with a big
enough hammer.
-- Sun System & Network Admin manual
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
