Actually on your computer you may have a copy of the same kernel whic
got corrupted. In a directory named:
/usr/src/linux-2.2.16/arch/i386/boot and the file will be called
bZImage.
That could then be copied to /boot/vmlinuz and /sbin/lilo would have to
be re-run. This is all assuming that you can boot with an emergency
floppy and see your hard disk and its file-systems.
In short, I think you can proceed as if you are installing a new kernel,
and whenever I've done that I have never (to my knowledge) had to mess
with a map file.
Shaheen.
Loyd Goodbar wrote:
>
> I've got a RedHat 6.2 system that corrupted its vmlinuz image during a power
> failure. When I boot the system, I get:
>
> lilo: <cr>
> Loading linux...
> Uncompressing linux................
>
> and the machine resets, and this happens over and over. Sometimes, it hangs
> with "Uncompressing linux" and the screen goes black.
>
> I guess I can boot with a boot floppy or emergency disk, and copy the vmlinuz
> file from another machine (also running 6.2). These are stock kernels, no
> recompiles.
>
> I should be able to copy vmlinuz to its location on the failing computer. I
> suspect I need to recreate the .map file. How would I do this? The .map file
> is the list of inodes or sectors on which vmlinuz resides, correct?
>
> And after that is accomplished, I should be able to run lilo to flush the
> changes to LILO.
>
> So how would I recreate the map file in the /boot directory?
>
> Thanks!
> Loyd
> --
> Loyd Goodbar
> [EMAIL PROTECTED] ICQ#504581
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
--
QotD:
Human beings are perhaps never more frightening than when they are
convinced
beyond doubt that they are right. -Laurens van der Post
--
email: [EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
