Corrected interpretation of RFC 4122 UUID strings for GPT. Thanks Andrei Borzenkov.

This commit is contained in:
2016-08-15 10:24:21 +00:00
parent d832426c49
commit 237852c4e1
8 changed files with 142 additions and 122 deletions

View File

@ -50,7 +50,7 @@
@c man .\" First parameter, NAME, should be all caps
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
@c man .\" other parameters are allowed: see man(7), man(1)
@c man .TH XORRISOFS 1 "Version 1.4.5, Aug 12, 2016"
@c man .TH XORRISOFS 1 "Version 1.4.5, Aug 14, 2016"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -1725,9 +1725,11 @@ Value "random" is default. Value "modification-date" produces a low quality
GUID from the value set by option @minus{}@minus{}modification-date=.
@*
A string of 32 hex digits, or a RFC 4122 compliant GUID string may be used to
set the disk GUID directly.
set the disk GUID directly. UEFI prescribes the first three components of
a RFC 4122 GUID string to be byte-swapped in the binary representation:
@*
E.g. @minus{}@minus{}gpt_disk_guid 2303cd2a-73c7-424a-a298-25632da7f446
E.g. @minus{}@minus{}gpt_disk_guid 2303cd2a-73c7-424a-a298-25632da7f446
equals @minus{}@minus{}gpt_disk_guid 2acd0323c7734a42a29825632da7f446
@*
The partition GUIDs get generated by minimally varying the disk GUID.
@c man .TP