Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[adrian15 <adrian15sgd@gmail.com>]

El 21/01/16 a las 10:13, Thomas Schmitt escribió:

> > Now primary means: "First lure" and secondary means "Second lure" by your
> > definition.
>
> There are normally two lures per firmware-hardware combination.
> Depending on the medium, the lures are recognized in El Torito,
> or in MBR, or in partition tables.
>
> In general we have theses dimensions
>    {Medium: CDROM, HDD} x
>    {Firmware: BIOS, EFI, ... exotic others ...} x
>    {Hardware: i386, amd64, ... exotic others ...}
>
> Not all tuples chosen from these sets are valid and not all
> valid tuples can be combined in one ISO filesystem.
> But the 8 main combinations for PC hardware are valid and
> combinable.
>
> I would avoid ranking terms like "first" or "primary".
> Job descriptions for bootloaders could rather look like
>    (CDROM + HDD, BIOS, i386 + amd64)
>    (HDD, EFI, i386)
>    (HDD, EFI, amd64)
>
> Some of them can hardly be separated from each other.
> E.g. (HDD, BIOS, i386) and (HDD, BIOS, amd64) have identical
> technical properties.

I was thinking on this. So... what if there is a fourth dimension for 
choosing if the job description goes first or second in the mkisofs command?

E.g.:
xorriso bunch-of-options-1 -eltorito-alt-boot bunch-of-options-2
versus
xorriso bunch-of-options-2 -eltorito-alt-boot bunch-of-options-1

So you don't like the primary or secondary terms.

How does xorriso name them?

Given that man xorrisofs talks about:

-eltorito-alt-boot

maybe we can just name them as:

"Main bootloader"
and
"Alternate bootloader".

Or maybe even better:

"Main eltorito entry"
and
"Alternate eltorito entry"
?

So that we can force a given bootloader to be used only as a "Main 
eltorito entry" ?


What do you think about this idea?


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/