[haiku-development] Re: Defining the Haiku UUID for GPT and other uses
- From: André Braga <meianoite@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 18 May 2009 19:22:09 -0300
On Thu, May 14, 2009 at 22:09, Disreali <mdisreali@xxxxxxxxx> wrote:
> I'm still reading up on the issue, but your third option seem very Be-ish
> to me, and therefore appropriate.
And now I went overdrive and managed to derive this:
$ uuid -d 1ed80000-3ba3-10f1-802a-4861696b7521
encode: STR: 1ed80000-3ba3-10f1-802a-4861696b7521
SIV: 40998376013447749455697663873180726561
decode: variant: DCE 1.1, ISO/IEC 11578:1996
version: 1 (time and node based)
content: time: 2001-08-31 00:00:00.000000.0 UTC
clock: 42 (usually random)
node: 48:61:69:6b:75:21 (global unicast)
1ed8 0000 3ba3 10f1 802a 4861 696b 7521 ....;....*Haiku!
So now the first 4 bytes are separated from the rest by a semicolon. :D
(Beats a hash sign in a seemingly random place...)
Very visually pleasing, IMO:
4246 5331 3ba3 10f1 802a 4861 696b 7521 BFS1;....*Haiku!
Unfortunately I couldn't mangle the other bytes into ASCII, l33tspeak
or something just as nerdy, so we're left with a magic number of
0xa310f180(*). The 4 header bytes are application-defined, then
there's a semicolon, then magic#, then asterisk, then Haiku!
* - Then again, I found its bit pattern to be kinda nice! :D
(Satisfied now, Rob? ;))
Since it's been five days and there were no objections, I'm going to
use 42465331-3ba3-10f1-802a-4861696b7521 (BFS1;....*Haiku!) as the
UUID for BFS Version 1 partitions on GPT-formatted disks, and make
haiku_loader aware of it. Then I'll see if I can reach some of the
people that make GPT-aware tools (parted, OpenSolaris, *BSD) and ask
them to include this signature.
I hope this is alright by you all. If not, just shout!
Cheers,
A.
Other related posts:
