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

13
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.5.3, Nov 23, 2019"
.TH XORRISOFS 1 "Version 1.5.3, Sep 11, 2020"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1216,13 +1216,14 @@ but may be set to 64 disk blocks by option \-partition_offset 16.
For the meaning of special disk_path "." see option \-G.
.TP
\fB\-isohybrid-gpt-basdat\fR
Mark the current El Torito boot image (see options \-b and \-e) in GPT as
partition of type Basic Data. This works only with \-isohybrid\-mbr and
has the same impact on the system area as \-efi\-boot\-part. It cannot be
combined with \-efi\-boot\-part or \-hfsplus.
Mark the current El Torito boot image (see options \-b and \-e) in an actually
invalid GPT as partition of type Basic Data. This works only with
\-isohybrid\-mbr and has the same impact on the system area as \-efi\-boot\-part.
It cannot be combined with \-efi\-boot\-part or \-hfsplus.
.br
The first three boot images which are marked by GPT will also show up
as partition entries of type 0xef in MBR.
as partition entries in MBR. The MBR partition of type 0xEF is what actually
is used by EFI firmware for booting from USB stick.
The MBR partition for PC\-BIOS gets type 0x00 rather than 0x17 in this case.
Often the further MBR entries are the ones which actually get used by EFI.
.TP