From: user@example.net   
      
   Wim Cossement wrote:   
   > J.O. Aho wrote:   
   >> Wim Cossement wrote:   
      
   >>> I built in everything I could, including ramdisk/initrd stuff (but I   
   >>> don't need to use that I guess or not?),   
   >>   
   >> Only if you built what you need to do the inital kernel boot as   
   >> modules, otherwise no.   
   >   
   > Modules? So built in stuff is not okay then?   
      
   initrd is only needed if you build things as modules, say you would make your   
   SATA and ext2 as modules, then you need to make an initrd image, which you   
   need to load during boot up.   
      
   >>> device   
   >>> mapper and RAID support, some SATA drivers but I can't seem to get my   
   >>> root file system mounted.   
   >>>   
   >>> Configuring GRUB was a bit akward but it seems to work.   
   >>>   
   >>> This is what I did:   
   >>>   
   >>> grub --device-map=/dev/null   
   >>   
   >> This isn't so good, as you can't load it from /dev/null, store it in   
   >> the same directory as everything else regarding grub.   
   >   
   > I thought this was needed so Grub is not confused when you use a funky   
   > setup.   
   > You start without any configuration and then specify your 1st device,   
   > hd0 by hand as I did.   
   > What do I need to do then? Please elaborate...   
      
   You need to specify that the device.map file will be located on disk, not   
   /dev/null, as grub will try to read from it.   
      
      
      
      
   --   
      
      //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)