Lilo and 2.4.9 problems

[Brian Kelsay]

I didn't at the time exactly know what I wanted to say after spending so
many hours looking at Windows drech, studying for the A+ exam.   I did
however mean to direct him to find his own solution by looking at the
lilo file right in front of him and pointing out areas that I saw that
disagree.   Those items jumped out at me saying "What is the new kernel
file called?!?"  Hence, only your compiler knows the truth.   James,
Lilo, like batch files in Windows or scripts in any operating system
calls a file (the kernel image) from its current location (the /boot
partition) which in the Windows world might be
c:bootvmlinuz-2.4.9-xxxx.   The key is the names must match to call
the right file and boot the computer without error and with the kernel
you intended.

At 1am none of this matters as long as the computer runs, correct?   You
can call the kernel image file whatever you want (call it Linux249 if it
makes you feel better), but call it by the same name in each place for
sanity's sake.   That's why Linux kernels go by a naming convention, so
you are not confused when looking for the latest and greatest.  As I
mentioned before it's 1am here and if I continue I'll rattle on and fall
asleep at the keyboard, so hope you fixed it.

And for those inquiring minds, I passed the bloody A+.   So now I'm
certifiable, but wasn't I always.

Brian Kelsay
If at first you don't succeed, skydiving is not for you.

----- Original Message -----
From: "Monty Harder" <lists at kc.rr.com>

> 8/26/01 9:14:01 AM, "Brian Kelsay" <bkelsay at home.com> wrote:
>
> >I remember now.  I don't change my kernel as often as some people.
>
> But this:
>
> >> The label doesn't have to match the module name, but the default
> >> parameter and one of the labels has to match.  The label is what
gets
> >> displayed on the LILO boot screen.
>
> doesn't disagree with what you said:
>
> >> > Look at the value for "default =linux249-1", now look at the line
> >> > "label=vmlinuz249".  Shouldn't that be "label=linux249-1"?   I th
ink
> >the
> >> > two must match.  Try changing one or the other and rerun lilo and
> >> > restart and se what happens.   Also, I think you want "image =
> >> > /boot/linux249082501"  to match the actual path to the new
kernel.
>
>
> which is absolutely right.  The image has to match the filename of the
kernel, and the default has to match one of the labels.
> His lilo.conf is wrong on both counts, unless the kernel filename is
really spelled that way.