Lilo
 

This question should be easy.

When I install RH7.3, I wanted the LILO boot menu to show "RedHatLinux7.3" not "linux"...so thats what I did. Then I got online and updated via up2date, and rebooted.....now it shows:

Windows98SE
RedHatLinux7.3
linux

???huh??? How would this happed, and how do I remove this third entry?

:newbie:

During the up2date proccess the kernel was updated also, for a couple of different reasons the old one is not removed (like you can specify that in /etc/rhn/sysconfig/up2date). If you want to remove that entry you need to modify /etc/lilo.conf and then run lilo to activate the changes!

Well done! Unfortunatally, we have uncovered another problem.

What I have found out is that when the update is applied, it does not check to see if you have put anything in beside the default label. At any rate when I select "RedHatLinux7.3" I am booting the old kernel. Ergo, "linux" is the new kernel. Here's the new problem, when I load up the new kernel, it freezes after enabling the swap space, what supposed to happen right after that is the init 5 level. So, here is my copy of lilo.conf if it helps:

prompt
timeout=50
default=Windows98SE
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.18-3
label=RedHatLinux7.3
initrd=/boot/initrd-2.4.18-3.img
read-only
root=/dev/hda2
append="hdc=ide-scsi"

other=/dev/hda1
optional
label=Windows98SE

image=/boot/vmlinuz-2.4.18-10
label=linux
root=/dev/hda2
append="hdc=ide-scsi"
read-only
initrd=/boot/initrd-2.4.18-10.img



now what??

:cry:

what's the last message you can see before it freezes? enabling swap space or something alike?

The very last thing is:

Enabling SWAP space [ OK ]
*blinking cursor here*


That's it....

had a problem like that sometime but can't remember how i got rid of it :eek:

Just an idea...

What's the massive difference between 2.4.18-3 and -10? Is it something you actually need, or are you just staying on the bleeding edge.

This would be a good time to repeat the old adage:
If it ain't broke, don't fix it. And it would appear that in your case you tried to fix this thing that "ain't broke" and broke it.

I would just hold off on "updates" until needed. If it's because of a hardware issue, and -10 is the only thing that will support it, then I guess it's worth looking into.

One thing that comes to mind is the initrd. Is the initrd actually pointing to the correct initrd? Change directory to /boot and see if your initrd's are just symlinks. If so, make sure it's symlinked to the correct file.

Cool

Kernel updates are EXCLUDED on default aren't they? well you can exclude them by updating /etc/sysconfig/rhn/up2date

set

pkgSkipList=kernel;

Ok, so I can live without the kernel update.....should I change my label to linux instead of RedHatLinux7.3 for future use? Also, in my up2date package is annoying me by giving me a warning telling me to run the new kernel....you know what.....screw it....I'll format....it won't take long to get it to this point again.....see ya on the other side folks...