Lab 5
A Lesson in Disaster Recovery


As we learn the Linux operating system, our confidence will build.  With this confidence, we will be apt to try things just for the thrill of not knowing what will happen.  When this starts we must be ready for an inevitable disaster.  Don't fret or worry!  This lab will present a couple of possible situations that you could encounter as you experiment and tinker with your system.

No working kernel

The first simulated situation is one most likely to be encountered by those among us that will tinker with building our own kernels.  Once a kernel is built, it is placed in the /boot directory with any other kernels used by your system.  Don't destroy the working kernels because you still need them until yours is confidently debugged.  Let's  create the 'no working kernel' situation.



The problem is the Grub Boot Loader cannot find the kernel stated in the grub configuration file.  Of course, we just changed its name by appending a '.save' to it.  Well, this is an easy fix.  Follow the steps to correct this problem. All changes in Grub Boot Loader are temporary changes.  The next time the system is booted the same problem will occur unless you return to the /boot directory and return the kernel to its original name.  For further details on working with the Grub and Lilo boot loaders, refer to pages 60-69.

Bad conf files prevent a boot

Our second simulated problem will be a situation that can be encountered because any one of the several configuration and initialization files have errors.  Our choice will be the 'grub.conf' file.

Forgotten passwords

A common situation that can occur to everyone of us, is a forgotten password.  Oh Dear!  Do I reinstall the system?  No!  Stop thinking that way!  We can work through this very easily.  During the boot process you must enter the system at runlevel 1.  We used this runlevel in the previous method by entering 'linux 1' at the boot: prompt when using the emergency boot disk.  If you permit the Grub Boot Loader to be used,