Linux OS.: Technical questions Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Linux OS.: Technical questions

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Mitch Blevins who wrote (259)	9/19/1999 1:10:00 PM
From: E. Charters	of 484

In general MB is right. It caught my eye too that I admonished you to remove the kernel as it would make the system unbootable from the hard disk if you did normally. But I left out the correction since your system is unbootable anyway. Also I told you first to rename the kernel as vmlinuz.old and rerun lilo to name this as one boot image. This would allow you to reboot with your old kernel even if the original kernel was gone or did not work. I should have said copy the kernel to vmlinuz.old, not rename. In fact when you recompile normally it would be a good idea to not remove vmlinuz at all until the recompile is successful. But if the compile is done where the removal and replacement of the old vmlinuz in root is automatic, which you can do, and that version does not work, what then? At least one should cp the old working kernel in the root directory to vmlinuz.old, then rereun lilo naming vmlinuz.old as one possible boot image then run the automatic compile_and_replace _system, that replaces vmlinuz. vmlinux in my system is, in fact, in usr/src/linux. The actual image, in my case called bzImage, is in /usr/src/linux/arch/i386/boot. I guess it varies with distributions. EC<:-}

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next