I had two kernels in my redhat7.2 PC.

One normal and the other one customized.
The customized one i set as default and had /usr/src/2.4.7-10custom as the dir for kernel modules,etc.

Now I have changed my lilo to make my default linux [Normal] and run /sbin/lilo

I have removed the custom kernel option from lilo.conf.
But still the same old screen comes up showing two kernel images and boots into the customised one by default.


Any help would be great


Cheers
Z

Note:
Also I have removed that custom directory link /usr/src/linux-2.4.10custom.

When you run lilo you should get no errors and it should say
Added linux
Added Windows
And any other images should also be listed.
Could you post your lilo.conf file.

No when i run /sbin/lilo it shows

Added Linux*

It displays no error

Lilo file
----------
prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.7-10
label=linux
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/hda1

Cheers
Z

I would suspect that the /boot/vmlinuz-2.4.7-10 has actually been overwritten by the 2.4.7-custom except for the multiple options in the lilo menu.

Do you have a separate /boot partition?
Do you have more than one hard drive?

Yes i have another hard disk as HDB.

ANd my boot partition is a separate one.

But surprise is that this vmlinux i replaced with the previous orginal kernel I had in backup , ran lilo and still its showing the same two images at lilo prompt.

The default boot up still gets into the custom kernel image which is not there !!!

Just surprised rather than frustrated

What am i to do?

Cheers
Z

Make sure that the bios is booting the right drive. You may be booting off the other drive with an old lilo in the mbr.

Check with fdisk and make sure the "bootable" flag is set on your /boot partition.

Try unmounting your /boot partition and see if you have a /boot directory on /hda1.

umount /boot
ls /boot
If you have files in /boot after unmounting /boot then possibly those are the files that are booting your linux.

You may want to consider using that /boot partition for some other purpose, e.g. /var. The original reason for having a /boot partition was the "bios 1024 cylinder limit" thingy which is not a problem with modern bios.

Output of fsck

Device Boot Start End Blocks Id System
/dev/hda1 * 1 510 4096543+ 83 Linux
/dev/hda2 511 1785 10241437+ 83 Linux
/dev/hda3 1786 2422 5116702+ 83 Linux
/dev/hda4 2423 4865 19623397+ f Win95 Ext'd (LBA)
/dev/hda5 2423 3059 5116671 83 Linux
/dev/hda6 3060 3441 3068383+ 83 Linux
/dev/hda7 3442 3568 1020096 82 Linux swap

Disk /dev/hdb: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 382 3068383+ 83 Linux
/dev/hdb2 383 1657 10241437+ 83 Linux
/dev/hdb3 1658 2804 9213277+ 83 Linux
/dev/hdb4 2805 4865 16554982+ f Win95 Ext'd (LBA)
/dev/hdb5 2805 3569 6144831 83 Linux
/dev/hdb6 3570 4334 6144831 83 Linux
/dev/hdb7 4335 4716 3068383+ 83 Linux
/dev/hdb8 4717 4792 610438+ 82 Linux swap


Sorry for my earlier mail , /boot is not a separate partition.

And i think i`ll try grub and then go back to lilo. [It looks crazy but i had a even more crazy idea of clearing the mbr with a windows boot disk 'fdisk /mbr' and then running lilo using a linux rescue cd]




Lilo file
----------
prompt
timeout=50
default=linux
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

#serial=1,9600n8
image=/boot/vmlinuz-2.4.7-10
label=linux
initrd=/boot/initrd-2.4.7-10.img
read-only
#append="console=ttyS1,9600n8 console=tty0"
root=/dev/hda1

Cheers
Z

What does /etc/fstab look like?