Thanks Randy, that worked perfectly! BTW, any idea as to what caused the problem to begin with? I got the 2.2.12 kernel when I "dist-upgrade" to potato, then the 2.2.15-idepci kernel by way of "apt-get install kernel-image-2.2.15-idepci" and when I ran "apt-get upgrade" last night the package mgmt didn't like the way I acquired 2.2.15-idepci :(
> > apt-get upgrade tried to upgrade my kernel image. I moved 2.2.15-idepci > > to .old and apt installed a new image but now when lilo tries to boot > > off the hard drive it complains that /vmlinuz is missing. > > Yes, you've got exactly the idea -- recreate the vmlinuz symbolic link. > > As you've probably deduced, /vmlinuz is just a symbolic link pointing to > the "real" kernel file which is located in /boot. > > As root, do the following: > > "cd /" (make sure we're in the root directory. > > "rm vmlinuz" (delete the old symbolic link because it's probably broken; > we're going to recreate the symbolic link below anyway) > > "ln -s boot/2.2.15-idepci vmlinuz" (recreate the symbolic link; this of > course will differ depending on what your kernel in /boot is named) > > "liloconfig" (run liloconfig so that lilo knows about the new kernel and can > boot it) > > -- > Regards, | "The ultimate result is that some innovations that would > . | truly benefit consumers never occur for the sole reason > Randy | that they do not coincide with Microsoft's self-interest." > | -- Judge Thomas Penfield Jackson, U.S. District Judge -- Debian GNU/Linux 2.2 100% M$ free