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

Mentioned --interval:appended_partition_NNN in man pages

Browse Source
This commit is contained in:
Thomas Schmitt
2016-09-12 14:38:22 +00:00
parent e3933ca63c
commit 32e08e5c8e
6 changed files with 258 additions and 181 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
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.4.5, Aug 20, 2016"
.TH XORRISO 1 "Version 1.4.5, Sep 12, 2016"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -3121,6 +3121,15 @@ when a follow\-up session gets written. But one should not rely on the
capability to influence the bootability of the existing sessions, unless one
can assume overwriteable media.
.br
Normally the boot images are data files inside the ISO filesystem. By
special path "\-\-interval:appended_partition_NNN:all::" it is possible to
refer to an appended partition. The number NNN gives the partition number
as used with the corresponding option \-append_partition.
E.g.:
.br
\-append_partition 2 0xef /tmp/efi.img
\-e \-\-interval:appended_partition_2:all::
.br
There are booting mechanisms which do not use an El Torito record but rather
start at the first bytes of the image: PC\-BIOS MBR or EFI GPT for
hard\-disk\-like devices,
@ -3151,6 +3160,11 @@ The component Flags modifies the further interpretation:
"imported_iso" demands to read from the \-indev. This works only if \-outdev
is not the same as \-indev. The Source component is ignored.
.br
"appended_partition_NNN" with a decimal number NNN works only for \-boot_image
bootspecs which announce El Torito boot image paths: bin_path=, efi_path=.
The number gives the partition number as used with the corresponding
option \-append_partition.
.br
The component Interval consists of two byte address numbers separated by a "\-" character. E.g. "0\-429" means to read bytes 0 to 429.
.br
The component Zeroizers consists of zero or more comma separated strings.