From: bliss-sf4ever@dslextreme.com   
      
   On 11/18/2013 12:58 PM, Bit Twister wrote:   
   > On Mon, 18 Nov 2013 12:27:14 -0800 (PST), Karl Dalen wrote:   
   >> On Sunday, November 17, 2013 12:34:03 PM UTC-8, Bit Twister wrote:   
   >>> On Sun, 17 Nov 2013 14:55:17 -0500, David W. Hodgins wrote:   
   >>   
   >> I would be happy to try "cauldron alpha" or other releases on my   
   >> new system after I get a stable boot environment up with all my apps   
   >> running. I suppose I should run alpha versions from a separate   
   >> disk to be on the safe side.   
   >   
   > Does not have to be separate disk. Just a separate partition and   
   > always pick Custom during the Partition phase of install.   
   >   
   >> I didn't get longer than to just install on hd from DVD Yesterday.   
   >> It loaded up nicely from the DVD and after I've completed the install   
   >> I could not boot from the hd. No matter how I changed the setting   
   >> in the BIOS boot menu (ASUS P8B75-M motherboard) it did not detect the   
   >> hd as a bootable device (although it was detected as a normal disk,   
   >> just could not boot from it)   
   >> I believe this is related to "Secure Boot" in the bios that need to be   
   >> disabled as well as the need to enable CSM to allow legacy OS to boot   
   >> from MBR.   
   >   
   > Yup. I found out I had to make two passes through my Asus bios to   
   > finally get my system to boot legacy OS.   
   >   
   >   
   >   
   >> Anyone knows what "UEFI" boot mode refers to? Is that some "Windows"   
   >> stuff ?   
   >   
   > Yep. Yet another attempt to corner the market.   
      
   	Actually not an attempt to corner the market but to extend the previous   
   BIOS.  The attempt to corner the market is the Secure Boot   
   business which is setup by Microsoft licensees to keep the MS franchise.   
      
   	UEFI and EFI had some basic improvements over the BIOS code which is   
   quite old now.   
   	The GPT which allows a lot of the SB nonesense is even an improvement   
   but the SB itself is pure Microsoft BS, trying to prevent 3rd party OSes   
   from being installed.   
      
   >   
   >> It's too bad that a mother board requires tweaking the bios setting   
   >> just to boot from standard MBR.   
   >   
   > Yes, vendors are still working out the bugs of their new code.   
   >   
   >   
   >> I did install on empty 2T sata disk. My plan for tonight is to:   
   >>   
   >> (1) Boot up live knoppix and prepartion from fdisk the disk into   
   >>      Linux (1.8TB), Linux swap (10GB),  Solaris (50GB) and fat32 20G   
   >   
   > I suggest Linux (1.8TB) is a waste. ~25g should be enough. I would use   
   > the other space for common stuff shared between distribution releases.   
   > Examples from my setup:   
   > $ ls /local   
   > bin  cron  doc  icons  lost+found  opt  ppp   sounds   tmp   
   >   
   > $ ls /misc   
   > faq  humor  jpg  mpeg  php  png  sql  txt   
   >   
   >   
   >   
   >   
   >> (2) Disable everything with respect to "secure boot/Fast boot"   
   >>      and enable legacy boot only in BIOS and reinstall Mageia 3.0   
   >>      on partition (1). I'm only going to use one partition for /.   
   >>      Earlier I used to have separated extended partitions for /var /home   
   >>      but I don't think I need that with such a big disk.   
   >> (3) If needed later I can install solaris 11 on part3.   
   >   
   > I still recommend using gpt disk partition. Then create your default   
   > partition setup. That way you would be limited to 128 partitions   
   > instead of the msdos 16 partition limit, able to always boot from   
   > anywhere on the drive. I see no good reason to allocate the whole   
   > drive at this point.   
   >   
   >>   
   >> Does Mageia use grub or grup2 ?   
   >   
   > Current default is grub legacy.   
   >   
   >> Is there a way to get the boot loader stored in the root partition   
   >> of the Linux fdisk partition rather than in MBR?   
   >   
   > It is somewhere under Advanced I think. Never used it myself.   
   >   
   >   
   >   
   >> I didn't see that option   
   >> when I installed but maybe I didn't look hard enough in the   
   >> various "advanced setting menus" that appear during the install process.   
   >> If so I could chain load Mageia from another boot loader on MBR.   
   >   
   > I always install/run grub in the MBR. Mageia will automagically add   
   > other installs to the grub menu. With that method I will get the grub   
   > menu again from the selected install.   
   >   
   >   
   >> To update packages I will definitely try your "script" method with   
   >> pulling the updates from file since I don't have 100% reliable internet.   
   >   
   > That is not a user "script" or using "from file".   
   >   
   > script is a command line application. Do a   "man script"   
   >   
      
   	bliss   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)