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

Mentioned that partition_entry=gpt_basdat and -isohybrid-gpt-basdat create invalid GPT but also a valid MBR partition table

Browse Source
This commit is contained in:
Thomas Schmitt
2020-09-11 12:23:50 +02:00
parent ffb7fe64c9
commit 56b2d88667
6 changed files with 174 additions and 164 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
xorriso/xorriso.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 XORRISO 1 "Version 1.5.3, Aug 26, 2020"
.TH XORRISO 1 "Version 1.5.3, Sep 11, 2020"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -3549,9 +3549,11 @@ may be augmented by
\fBisolinux partition_entry=gpt_basdat\fR
or \fBisolinux partition_entry=gpt_hfsplus\fR,
and by \fBisolinux partition_entry=apm_hfsplus\fR.
The boot image will then be mentioned in GPT as Basic Data
or GPT HFS+ partition, and in APM as HFS+ partition.
The first three GPT partitions will also be marked by MBR partitions.
The boot image will then be mentioned in an invalid GPT as Basic Data
or GPT HFS+ partition, and in a valid APM as HFS+ partition.
The first three GPT partitions will also be marked by MBR partitions. The
MBR partition of type 0xEF is what actually is used by EFI firmware for
booting from USB stick.
.br
In multi\-session situations the existing System Area is preserved by default.
In in this case, the special disk_path "." prevents reading of