I need to edit my lilo.conf file so I can finally reload a newly compiled kernel. It is supposed to be in the /etc directory, but it is not there. I am using SuSE 9.0.

So...where is it?

Can someone explain to a linux newb how/why things so often are not where all the references I read through say they are? How does anything ever get done in Linux when things aren't where howtos, forums, references, mans say they are? Jeez....

Thanks in advance....

If you don't have a lilo.conf file, it is likely Suse loaded grub instead as the boot loader. Look for a grub.conf file.

I found a grub.conf file but doesn't look like it is able to be edited. I'm following some instructions that say I need to edit the lilo.conf file so it will load my new kernel. I don't see anything in the grub.conf file that I can edit to have it load the new kernel. Here's what's in the grub.conf:

root (hd0,0)
install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd0,0)/grub/menu.1st
quit

Any ideas?

Thanks

Yeah, SuSE 9 uses grub. Grub is installed in /boot/grub, the file to edit is /boot/grub/menu.lst. This can also be changed via yast. In fact, the menu.lst file is full of warnings not to screw up the comment lines, as they are used by yast to identify the menu items. This is the place to remove the 'desktop' parameter if you are having performance issues with the original 9.0 kernel.

Anyone know how to add suse entry to slackware's lilo?

I tried mounting suse to my /mnt/suse but only a lilo+found directory appeared.

Any idea why?

could u post ur lilo.conf here and the name of suse partiton
which filesystem are u using in suse,does slackware support that filesystem

regards

# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Slackware bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda7
label = Slackware
read-only
# Slackware bootable partition config ends
# Fedora Core 2
image = /mnt/fc2/boot/vmlinuz-2.6.5-1.358
initrd = /mnt/fc2/boot/initrd-2.6.5-1.358.img
root = /dev/hda6
label = Fedora
read-only
# Fedora Core 2

What I did to the FC2 is I boot to Slackware, mount FC2 to /mnt then specify the path to the kernel image and initrd.

I try using the same method as above to add suse but after I mount suse, theres only a lost+found directory there. So I not sure how do I specify the path to the image file.

All my linux filesystem are using ext3

u r trying to mount suse partiton manually?? through mount /dev/.....

lost+found directory implies that ur mounting an emplty linux extfs partiton
check if u r mounting the correct device(/dev/hdax) for suse

regards

Yes, I'm very sure that the device is correct. Don't tell me it somehow got messed up in the process

can u start fedora and mount ur suse partion there
try out all posiblities

try out mounting with knoppix because i do not think that if we are using the correct device etc etc then we should be facing any problems

also try using lilo from fedora

regards

I tried mounting with knoppix and fedora, both with same results. (lost+found directory only).

Strange problem, guess I gonna try re-install suse again.

Anyway, its strange that suse can only install to the last partition huh? I partition till hda8, tried using the front few partition as /, but it insist on the last partition

one more try u can give is by trying out
explore2fs from windows to access ur suse partition it will also show the contents of ur suse drive

u can get explore2fs from here
http://uranus.it.swin.edu.au/~jn/linux/

regards