From: NoEMail@home.org   
      
   Over the years I could not count the number of times that one of   
   my machines which uses lilo has lost its boot sector. I use grub now   
   in my main machine, but I have a number of machines for which I   
   am responsible which still run lilo. Yesterday a friend's machine   
   lost its boot sector and I want to tell how I solved the problem   
   and ask if there was a better way.   
      
   The machine with the lost boot sector had been running 14.2   
   for several years. The owner who lives over 100 miles from   
   me brought the machine to me. I booted the machine with   
   a liveslak drive. The operational partition on the drive was   
   sda2. I followed these steps:   
      
   mkdir /sda2   
      
   cp /sda2/boot/vmlinuz /boot   
      
   mount /dev/sda2 /sda2   
   mount --bind /dev /sda2/dev   
   /dev/sda2/sbin/lilo -r /sda2   
   sync   
   umount /sda2   
      
      
   and the affected machine was able to boot.   
      
   This process could be simplified if liveslak   
   or an install usb could track slackpkg updates.   
   If, over time, slackpkg updates the kernel the   
   original install disk cannot be used to get   
   into the system. Similarly, the liveslak kernel   
   would not match the kernel on the affected system.   
      
   What would you have done apart from switching to grub?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)