From: BitTwister@mouse-potato.com   
      
   On Mon, 24 Apr 2017 07:44:49 -0400, bad sector wrote:   
      
    < snip >   
   > wrong. I'll look into your suggestions tonight. One thing for sure is   
   > that I want any boot-loader to boot ALL installations on a disk and not   
   > just one, so that os-probing is realy unavoidable.  I'm perfectly   
   > capable of writing my own menu files but then grub2 shoud provide for   
   > that as grub1 did.   
      
   You can manage grub2 just like you did with grub1 if you want to   
   manually dink around with the menu/boot file. Instead of messing with   
   menu.lst, you mess with grub.cfg.   
      
   That is not the recommended methodology.   
      
   Personally I found it much easier to drop in my own menu stanza   
   generation scripts into /etc/grub.d/ to create my own menu selections   
   where I want them, with the menu selection titles much easier to read.   
      
   I leave the original scripts alone and let os-prober do its thing in   
   the event I might need its selections.   
      
   I have no use for UUIDs, and want to be able copy copy grub.cfg to any   
   install and boot from there if desired,   
      
   To do that, I use media labels so I link in my script   
   /etc/grub.d/10a_label_xx__grub -> /local/bin/10a_label_xx__grub   
      
   To boot a system rescue cd iso I have   
   20b_rescue_cd_xx__grub -> /local/bin/20b_rescue_cd_xx__grub   
      
   xx__ was chosen so I can easily find my customization files and I   
   added grub so I can find those when working in /local/bin.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)