David wrote: > David wrote: > >> David wrote: >> >>> Just installed kernel-2.4.12-3mdk on the other computer and >>> everything works fine. lilo -v >>> completed and installed the new bootloader for the lilo.conf. >>> >>> Now, on the other computer everything is done and need to run 'lilo -v' >>> on it to finish. It has the same version of lilo, but complains. >>> Have two kernels on each machine, so got rid of the symlinks in /boot >>> on each. This computer is complaining about no vmlinuz. >>> What gives, just reran lilo on the other computer and still works. >>> Any one have a clue what I need to do? >>> >>> >>> >>> >>> lilo -v >>> LILO version 21.7-5, Copyright (C) 1992-1998 Werner Almesberger >>> Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof >>> Development beyond version 21 Copyright (C) 1999-2001 John Coffman >>> Released 06-May-2001 and compiled at 17:29:46 on Aug 5 2001. >>> >>> Reading boot sector from /dev/hda >>> Merging with /boot/boot.b >>> Mapping message file /boot/message >>> Boot image: /boot/vmlinuz >>> Fatal: open /boot/vmlinuz: No such file or directory >>> >> >> Okay, made a new symlink to the old kernel and that worked. Still, >> what changed where I had to do that on one computer (has more cooker >> updates on the one with the problem) and not the other computer (less >> cooker updates). >> I mean it works, but there is now a useless symlink in the /boot >> folder, doesn't hurt anything, but is there reasoning behind this? Is >> it just to make sure that there is always a link incase someone screws >> something up? >> > Stupid me!!!! Sorry. Found the problem. Still had vmlinuz in lilo.conf on the one computer. That was why it was looking for it. It's been a bad day since I woke up. And it seems to be continuing until I go to bed. Damn.
