LinuxQuestions.org - lilo.conf doesn't have an effect on my boot-partition...

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - lilo.conf doesn't have an effect on my boot-partition... (https://www.linuxquestions.org/questions/linux-software-2/lilo-conf-doesnt-have-an-effect-on-my-boot-partition-106042/)

lilo.conf doesn't have an effect on my boot-partition...

Hello

I've got my /dev/hda partitioned like this:

hda1->win2kloader
2->bootloader for linux
3->root-partition for redhat9 on hda 3
5->swap for both linux
6->root-partition for redhat9 on hda6

and since i've installed my redhat9 on hda3 (i told my installation about using /dev/hda2 as boot-partition), i can't boot my redhat9 on hda6 anymore and the most important thing is:

when i booted up my redhat9 on hda3.... I'm verifiyng my lilo.conf to this, because of my new kernel....:

Code:

prompt

timeout=30

default=1

boot=/dev/hda2

map=/boot/map

install=/boot/boot.b

message=/boot/message

lba32



image=/boot/kernel-openmosix-2.4.20

        label=RH9_1

        initrd=/boot/initrd-2.4.20-8.img

        read-only

        append="root=LABEL=/"





image=/boot/kernel-openmosix-2.4.20

        root=/dev/hda6

        label=RH9_2

#        initrd=/boot/initrd-2.4.20-8.img

        read-only



other=/dev/hda1

        optional

        label=WindowsLoader

my redhat 9 shows me this, when i'm aplying these changes:

Code:

[root@master1 pablo]# lilo

Added RH9_1

Added RH9_2

Added WindowsLoader

Fatal: No images have been defined.

......welll, changes have been made... but when i boot up... the os are called "1", "2", yet....

1. why does my lilo not change my boot-sector (entry in mtab: /dev/hda2 is /boot)
2. what does "No images....." mean???? I really entered these images, they ae in the lilo.conf
please help me....thanks

you need to run lilo for the changes in lilo.conf to take effect. As root, do
/sbin/lilo -v

well, of course, I've also already done that....here:

[root@master1 pablo]# lilo -v
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman

Reading boot sector from /dev/hda2
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/kernel-openmosix-2.4.20
Mapping RAM disk /boot/initrd-2.4.20-8.img
Added RH9_1
Boot image: /boot/kernel-openmosix-2.4.20
Added RH9_2
Boot other: /dev/hda1, on /dev/hda, loader /boot/chain.b
Added WindowsLoader
Fatal: No images have been defined.

no changes, when I'm booting up again.... the os-names are: "1", "2"......yet....
it's important ....please help***

oops, sorry. You did run lilo.

What is in your MBR? That's the first thing that gets loaded and you do not have lilo installed there since you have boot=/dev/hda2. Also, default=1 isn't right. You have to specify the label (e.g. defauly=RH9_1) If you change boot/dev/hda2 to boot=/dev/hda (w/0 any numbers) lilo will be installed in the MBR and you should see the entries the way you want.

image=/boot/kernel-openmosix-2.4.20
label=RH9_1
initrd=/boot/initrd-2.4.20-8.img
read-only
append="root=LABEL=/"

This doesn't look right either. I think you can get rid of the append line. Instead, have
root=/dev/hda3

Quote:

Originally posted by quatsch
oops, sorry. You did run lilo.

What is in your MBR? That's the first thing that gets loaded and you do not have lilo installed there since you have boot=/dev/hda2. Also, default=1 isn't right. You have to specify the label (e.g. defauly=RH9_1) If you change boot/dev/hda2 to boot=/dev/hda (w/0 any numbers) lilo will be installed in the MBR and you should see the entries the way you want.

thanks a lot......so... I'm trying this...i'll be back i a few seconds....my lilo-verification didn't message an error, here:

Code:

[root@master1 pablo]# lilo

Added RH9_1 *

Added RH9_2

Added WindowsLoader

[root@master1 pablo]#

ok, ....I'm doing some other trying's.... but I think, .... the problem is solved
thanks a lot...