From: NoEMail@home.org   
      
   Mike Small  wrote:   
   > One thing that's changed with 15.0 is the addition of a new script,   
   > /usr/sbin/geninitrd.  In 14.2 when upgrading a kernel I would skim the   
   > instructions under /boot on how to make a new initrd, once again finding   
   > what arguments to pass (don't know why I didn't make an alias). Now I   
   > run geninitrd followed by lilo without thinking about it much.  The head   
   > of geninitrd warns, however, that it's not for use if you have an   
   > encrypted root partition.   
   >   
   > I think there might be a difference in what goes into your generic   
   > initrd now too.  There's some indirection involved with geninitrd,   
   > but eventually it runs /usr/share/mkinitrd/mkinitrd_command_generator.sh   
   > which has this comment near the top:   
   >   
   > # Create an initrd which fits the system.   
   > # Take into account the use of LVM/LUKS/RAID.   
   > # Find out about any hardware drivers the system may need in an initrd when   
   > # booting from a generic lightweight kernel.   
   >   
   > It didn't always do that did it?   
      
   I have always used mkinitrd, and the script seems to use   
   that as well. mkinitrd worked for me after upgrade-all   
      
   The chroot thing reminded me to post about how to recover   
   when your boot sector has been wiped. I'll do that   
   now.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)