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

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISO 1 "Version 1.4.5, Aug 12, 2016"
.TH XORRISO 1 "Version 1.4.5, Aug 14, 2016"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -3361,9 +3361,11 @@ Value "random" is default. Value "volume_date_uuid" produces a low quality
GUID from the value set by \-volume_date "uuid".
.br
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:
.br
E.g. gpt_disk_guid=2303cd2a\-73c7\-424a\-a298\-25632da7f446
equals gpt_disk_guid=2acd0323c7734a42a29825632da7f446
.br
The partition GUIDs get generated by minimally varying the disk GUID.
.br
@ -4159,7 +4161,7 @@ file with the path given after the colon. Compute the GPT compliant CRC number
and print it to the result channel. The number is shown like "0x690fd979".
The special disk_path "\-" causes reading from standard input.
.br
With mode \fBmake_guid\fR print a pseudo\-random GUID in RFC 4122 format
With mode \fBmake_guid\fR print a pseudo\-random GUID in RFC 4122 text format
to result channel.
.TP
.B Navigation in ISO image and disk filesystem: