hi,
you can see the output of lilo -v -v down here.
it does gave somewhat clear info of what is going on.
$lilo
LILO version 21, Copyright 1992-1998 Werner Almesberger
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 8 sectors.
Boot image: /boot/vmlinuz-2.2.13
Setup length is 7 sectors.
Mapped 938 sectors.
Added linux-2.2.13
Boot image: /boot/vmlinuz-2.2.22 ---------\
Setup length is 7 sectors. ----------\ These correspond to
Mapped 1021 sectors. ----------/ the new image i added.
Added linux-2.2.22 ---------/
Boot image: /boot/vmlinuz-2.2.5-15
Setup length is 7 sectors.
Mapped 1208 sectors.
Added linux-2.2.5
No images have been defined. --------\ error messages that are
Removed temporary file /boot/map~ --------/ disallowing the newimage
the file /boot/map~ was not there before and after runnunig lilo.
so it might be creating it during the process i think.
but the problem sitll remains unsolved.
any help is appreciated.
Madhu
>
> m> Reading boot sector from /dev/hda
> m> Merging with /boot/boot.b
> m> Boot image: /boot/vmlinuz-2.2.13
> m> Added linux-2.2.13
> m> Boot image: /boot/vmlinuz-mynew -----> Image i added
> m> Added mynew ----->
> m> No images have been defined.
>
> Well this looks like you have no entry for the image to mynew in
> your lilo.conf file.
>
> What did you enter in lilo.conf, also you may find lilo -v -v
> more helpful when debugging, however in this case it looks
> evident that you just left the new image name out.
>
> image = /boot/'whatevermynewimageiscalled'
> label = mynew
> root = /dev/hda3
> alias = mn
> read-only
>
>
>
> m> and when i reboot, iam not able to see the mynew image that
>
> m> i added.
>
> m> any suggestions are welcome.
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
