bzt wrote:
I've moved this from the other topic, because this has absolutely nothing to do with BOOTBOOT.
rename this BS and remove my nickname from it. you may behave as much as crackpot as you want, just don't f&cking use my nickname in your clowning as you did here.
Quote:
zaval wrote:
that modifying ESP in some circumstances is harder than an ordinary FAT volume.
Harder how and when? You are talking to someone who has implemented an ESP creator, so unlike you, I know what ESP is and isn't. This has nothing to do with BOOTBOOT.
a utility may reject to delete it because it's ESP. for example. and no, you have zero clue judging by your BS.
Quote:
zaval wrote:
GPT may be unavailable for some (virtual) disk sizes.
Interesting, show me such a case! This has nothing to do with BOOTBOOT either.
for small size it can be true. if one makes a small virtual HD, some utilities reject creating GPT with it.
Quote:
zaval wrote:
SD cards cannot be formatted with it, without breaking their standard.
Pure lie, no partitioning tool nor formater refuses to do so, you can format SD cards with GPT no probs. I for one use GPT partitioned SD cards on my Pi machines all the time, all works fine. Nobody ever reported non-functioning SD card with GPT. NEVER. Also, this has nothing to do with BOOTBOOT.
official SD Formatter lets you do this? GPT with non-FAT volume(s)? pure lie is your BS. I am tired to point you to the 2nd part of SD specification, where it's specified.
Quote:
zaval wrote:
wrong! it's such a BS, that I even don't know what to say against.
You should say nothing. You even have quoted the part of the spec that contradicts you.
Quote:
The following is the order in which a block device must be scanned to determine if it contains partitions. When a check for a valid partitioning scheme succeeds, the search terminates.
1. Check for GUID Partition Table Headers.
2. Follow ISO-9660 specification to search for ISO-9660 volume structures on the magic LBA.
3. Check for an “El Torito” volume extension and follow the “El Torito” CD-ROM specification.
4. If none of the above, check LBA 0 for a legacy MBR partition table.
5. No partition found on device.
Meaning if your storage has GPT (point 1), then EFI shouldn't and won't parse the legacy tables (point 4). Nobody cares if you have another disk which is not the boot disk.
Furthermore, BOOTBOOT uses GPT, so you can't use MBR tables (this is
third time I've written down this), therefore MBR tables have nothing to do with BOOTBOOT.
Seriously? You would better pretend to be an idiot instead of admitting you got the text wrong? Okay. "nobody" cares, let's leave this to that "nobody".
There is no such a term as "boot" disk in UEFI. all disks MUST be inspected because any of them may contain a valid Load Option target or be accessed by the FW/OSLs during boot time. the partition discovery algorithm mandates a compliant FW, to first check every disk for GPT scheme and stop discovery FOR THIS DISK if the scheme is found, then proceed WITH THE SAME DISK if not found with checking for other schemes. this procedure is being applied FOR EVERY DISK. if you found "Nobody cares if you have another disk which is not the boot disk." in the spec. then either show this line or you are hallucinating or making things up on the fly to still look a smart aleck. just try to read the quote you are waving - it literally sais:
Quote:
The following is the order in which A BLOCK DEVICE must be scanned to determine if it contains partitions.
just one of any. no "boot disks", no "special ones". for every. attach to qemu several vhds with GPT and MBR and then look at "mounted" devices listed, genius.
PeterX wrote:
I personally think that Zaval is wrong about his kind of crusade against the GPT.
you just have a strong need to talk in every thread, do you? I started in that thread just by pointing out, that bzt as always sais wrong about what's allowed and what's not. and suggested the user to try an ordinary (non ESP) FAT volume with MBR (with his own UEFI OSL, which is always way better, than the lamery from some loonies) to overcome issues he had. and also made a note about the fallacy of abusing the resort path of \efi\boot\bootXXX.efi especially on non-removable storages.
my first post there:
Quote:
just for the note, despite bzt scares you, that you are required to mark a FAT partition as ESP and use only GPT, it's not true. you can create MBR with an ordinary FAT partition and be sure - it will be recognized by UEFI. since you are only at the start, I'd go this way (it's easier and maybe you'd have less troubles)
it's as a "crusade" against GPT as bzt's bootboot worth trying, honestly.