hi thanx for U'r interest in this problem.
here is the complete /etc/lilo.conf file
corresponding to the output in previous mail.
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
image=/boot/vmlinuz-2.2.13
label=linux-2.2.13
root=/dev/hda2
read-only
image=/boot/vmlinuz-2.2.22
label=linux-2.2.22
root=/dev/hda2
read-only
image=/boot/vmlinuz-2.2.5-15
label=linux-2.2.5
root=/dev/hda2
read-only
here both linux-2.2.5 and 2.2.13 are getting added and
iam able to see them at boot time. linux-2.2.22 is the
new image. iam sure that it is an image.
Madhu P
On Mon, 4 Sep 2000, Ray Curtis wrote:
> >>>>> "m" == madhu <[EMAIL PROTECTED]> writes:
>
> m> hi,
>
> m> you can see the output of lilo -v -v down here.
>
> m> it does gave somewhat clear info of what is going on.
>
>
> m> $lilo
>
> m> LILO version 21, Copyright 1992-1998 Werner Almesberger
>
> m> Reading boot sector from /dev/hda
> m> Merging with /boot/boot.b
> m> Secondary loader: 8 sectors.
> m> Boot image: /boot/vmlinuz-2.2.13
> m> Setup length is 7 sectors.
> m> Mapped 938 sectors.
> m> Added linux-2.2.13
> m> Boot image: /boot/vmlinuz-2.2.22 ---------\
> m> Setup length is 7 sectors. ----------\ These correspond to
> m> Mapped 1021 sectors. ----------/ the new image i added.
> m> Added linux-2.2.22 ---------/
> m> Boot image: /boot/vmlinuz-2.2.5-15
> m> Setup length is 7 sectors.
> m> Mapped 1208 sectors.
> m> Added linux-2.2.5
> m> No images have been defined. --------\ error messages that are
> m> Removed temporary file /boot/map~ --------/ disallowing the newimage
>
>
> m> the file /boot/map~ was not there before and after runnunig lilo.
>
> m> so it might be creating it during the process i think.
>
> m> but the problem sitll remains unsolved.
>
> m> any help is appreciated.
>
>
> Show me the complete lilo.conf file itself please, you must have something
> really strange there or the one you called newimage is not a image at
> all.
>
> Its not the name of the image like suggested, I have a couple that are named
> something other than 'linux-xxxx' and mine work perfectly.
>
>
>
>
> >>
> 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.
> >>
>
> --
> Ray Curtis Unix Programmer/Consultant Curtis Consulting
> mailto:[EMAIL PROTECTED] http://www.clark.net/pub/ray
> ============================================================================
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
