Chris,
Yes, this is *exactly* what I'm wanting to do!! I'm crafting a std RHEL7 build for my company now. I've got the agnostic disk layout working -- under BIOS.
It's a GPT-partitioned system disk. Under GPT, there's not sufficient space at the beginning of the disk to drop the entire BIOS boot loader. So it drops the initial boot loader. Then you have a 1 MB partition, where the stage 1.5 BIOS bootloader goes. Looks like this:
[root@austl10geqldb04 ~]# gdisk -l /dev/sda
...
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 <-- 1 MB partition for stage 1.5 bootloader
2 4096 618495 300.0 MiB 0700 <----- /boot
...
5 1170382848 1170995199 299.0 MiB EF00 EFI System <--- /boot/efi
I'm ok if the bootloader build, location and helper scripts do the right thing for only the boot mode I've done. As long as in my %post section, I can drive them to lay down the bootloader + support files for the other method.
Of course, I'd have to know the exact syntax for this. I'm guessing it'd be something like this:
Or it'd be tolerable if I write up instructions to the sysadmins, how to trivially lay down the loader + support files for the other boot method. Then flip to that method. (It'd be trivial because the disks are already laid out in this agnostic disk scheme).
Eventually, I think UEFI will be the default boot method and BIOS will be just a distant memory. But for now manufacturers are still shipping new server model w/ BIOS as their default boot method. So we're not there yet.
Spike
PS Excellent link. Thanks!
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
