libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

Browse Source
This commit is contained in:
Thomas Schmitt
2016-08-15 10:24:21 +00:00
parent d832426c49
commit 237852c4e1
8 changed files with 142 additions and 122 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
xorriso/xorrisofs.1
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 XORRISOFS 1 "Version 1.4.5, Aug 12, 2016"
.TH XORRISOFS 1 "Version 1.4.5, Aug 14, 2016"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1307,9 +1307,11 @@ Value "random" is default. Value "modification\-date" produces a low quality
GUID from the value set by option \-\-modification\-date=.
.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
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.
.TP