[haiku-development] Re: Defining the Haiku UUID for GPT and other uses

2009/6/9 Philippe Houdoin <philippe.houdoin@xxxxxxxxx>:
> 18 August 2001 is considered the official OpenBeOS birth date.

Wow. Where did you manage to dig this info from? :)

> Which should change a little bit the UUID, but without breaking the
> easter-egg-ish level.
> I don't have uuid tool here, so feel free to post the new,
> birthdate-fixed Haiku UUID.

Here, two options:
uuid -d f7794000-316b-10f1-802a-4861696b7521
encode: STR:     f7794000-316b-10f1-802a-4861696b7521
        SIV:     328948880968265769013908661505790539041
decode: variant: DCE 1.1, ISO/IEC 11578:1996
        version: 1 (time and node based)
        content: time:  2001-08-18 00:00:00.000000.0 UTC
                 clock: 42 (usually random)
                 node:  48:61:69:6b:75:21 (global unicast)

uuid -d f7794000-b0eb-1601-802a-4861696b7521
encode: STR:     f7794000-b0eb-1601-802a-4861696b7521
        SIV:     328948881007725131673110477295779018017
decode: variant: DCE 1.1, ISO/IEC 11578:1996
        version: 1 (time and node based)
        content: time:  2001-08-18 00:00:00.000000.0 UTC
                 clock: 42 (usually random)
                 node:  48:61:69:6b:75:21 (global unicast)

But both kind of look rather uninteresting (compared to the latter
UUID I generated) on a hex dump...

f779 4000 b0eb 1601 802a 4861 696b 7521  .y@......*Haiku!
f779 4000 316b 10f1 80 2a 4861 696b 7521  .y@.1k...*Haiku!

The first one is nicer in a silly way, in that b0eb kind of resembles
BeOS, and 0xeb is BFS' signature on Intel partitions. The second one
is IMHO unacceptable, since it produces TWO valid ASCII alphanumeric
characters right after the lower time field, which we kind of agreed
on overriding with BMessage-style 4 byte codes depending on the
object. And I don't like it that by default there's two other valid
ASCII :alnum: characters on the first 4 bytes. Baaaad.

I'd say we should trade historical accuracy for aesthetics in this case. Again,

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)

dumps to

1ed8 0000 3ba3 10f1 802a 4861 696b 7521  ....;....*Haiku!

which looks just great :)

Not trying to make much ado about nothing as I don't really expect
people to look at hexdumps all day (erm.), should we vote on those or
something?


Cheers,
A.


-- 
One last piece of advice: "ice".

Other related posts: