[haiku-development] Re: Defining the Haiku UUID for GPT and other uses
- From: André Braga <meianoite@xxxxxxxxx>
- To: "haiku-development@xxxxxxxxxxxxx" <haiku-development@xxxxxxxxxxxxx>
- Date: Mon, 8 Jun 2009 04:28:04 -0300
2009/6/7 André Braga <meianoite@xxxxxxxxx>:
> Em 07/06/2009, às 18:24, "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> escreveu:
>>
>> What exactly is missing, anyway? The boot loader should support GPT
>> just fine.
>
> It can't find any volumes. Naturally, as it doesn't know what volumes are
> BFS and it doesn't scan the GPT for partitions. Or at least it seemingly
> doesn't. Haven't checked the code yet.
Okay, now I understand what you meant. There is plenty of support on
our loader :)
But the code was not active, and I had to bang my head around the
build system a bit to understand what was missing.
So, for documentation purposes, and for other people who might want to
try, what was missing was:
o enabling compiling the efi_gpt partitioning system by adding
this to my UserBuildConfig: "AddFilesToHaikuImage system add-ons
kernel partitioning_systems : efi_gpt ;",
o creating a "AddSymlinkToHaikuImage system add-ons kernel boot :
/boot/system/add-ons/kernel/partitioning_systems/efi_gpt : efi_gpt ;"
jamrule on UserBuildConfig as well,
o and in my particular case modifying efi_gpt.cpp to have its
priority higher than of "intel" partitioning, else it will take over.
And now I can happily boot Haiku on a hybrid GPT/MBR disk *and* have
it recognising and listing all the partitions on
/dev/disk/ata/n/master/xyz. And now I can finally have two Haiku
partitions on the same disk *and* not mess with hiding partitions,
mucking with extended partitions, and pieces of paper with MBR dumps
and more of this kind of junk.
IOW, this is just fantastic :D
This email is being sent from via BeZilla on Haiku, booted from the
scratch BFS partition that isn't at all mentioned on my MBR. And I
can't even begin to express how happy this makes me :D
Cheers,
A.
--
One last piece of advice: "ice".
Other related posts:
