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

Updated man xorriso about -report_system_area cmd

Browse Source
This commit is contained in:
Thomas Schmitt
2015-05-16 10:36:06 +00:00
parent 0a8b9c3af4
commit 70d5101d12
3 changed files with 96 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
libisoburn/trunk/xorriso/xorriso.texi
View File

@ -50,7 +50,7 @@
@c man .\" First parameter, NAME, should be all caps
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
@c man .\" other parameters are allowed: see man(7), man(1)
@c man .TH XORRISO 1 "Version 1.3.9, Apr 20, 2015"
@c man .TH XORRISO 1 "Version 1.3.9, Mai 16, 2015"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -4495,46 +4495,50 @@ The timestamps get not automatically propagated from loaded image to newly
written image. The ones for new images may be set by command -volume_date.
See there for the meaning of the particular timestamps.
@c man .TP
@item -report_el_torito "plain"|"help"
@item -report_el_torito mode
@kindex -report_el_torito shows Boot Catalog
@cindex Image, show Boot Catalog
@*
With parameter @strong{plain} print a report about the information found
With mode @strong{plain} print a report about the information found
in the El Torito boot catalog of the loaded ISO image.
@*
With parameter @strong{help} print a text which explains the meaning of the
With mode @strong{help} print a text which explains the meaning of the
lines put out by "plain".
@*
Parameter @strong{cmd} tries to print the @strong{xorriso} commands which are
necessary to produce the found El Torito equipment and System Area.
Mode @strong{cmd} tries to print the @strong{xorriso} commands which are
necessary to produce the found boot equipment: disk identifiers,
El Torito boot images, and System Area. Disk identifiers are strings
which the booting operating system might use to find the ISO filesystem
from where it comes. Currently known is the use of volume id and
modification date.
@*
The intended use case is modification of the filesystem by having -indev
and -outdev pointing to different images or drives.
The result might be insufficient, if the found equipment cannot be
produced by xorriso.
produced by xorriso. Various SORRY events may arise in this case, but
it is not guaranteed that xorriso recognizes all its insufficiencies.
@*
Parameter @strong{as_mkisofs} tries to print the @strong{xorriso -as mkisofs}
Mode @strong{as_mkisofs} tries to print the @strong{xorriso -as mkisofs}
options, which are necessary to produce the found equipment.
The intended use case is to use the mounted filesystem as input tree
together with the printed options. In some cases (e.g. -isohybrid-mbr) it
might be necessary to extract data from ISO to hard disk in order to
use the hard disk files as arguments of -as mkisofs options.
together with the printed options.
@c man .TP
@item -report_system_area "plain"|"help"|"gpt_crc_of:"disk_path
@item -report_system_area mode
@kindex -report_system_area shows MBR, GPT, and alike
@cindex Image, show MBR, GPT, and alike, -pvd_info
With parameter @strong{plain} print a report about the information found in
With mode @strong{plain} print a report about the information found in
the System Area of the loaded ISO image. The report consists of zero to
many lines with a header text, a colon, and information text.
@*
With parameter @strong{help} print a text which explains the meaning of the
With mode @strong{help} print a text which explains the meaning of the
lines put out by "plain". You probably will have to look
for more documentation which explains the technical details of the
mentioned boot facilities.
@*
Parameters @strong{cmd} and @strong{as_mkisofs} work like with
Modes @strong{cmd} and @strong{as_mkisofs} work like with
command -report_el_torito. See above.
@*
With parameter @strong{gpt_crc_of:}disk_path read up to 32 KiB from the disk
With mode @strong{gpt_crc_of:}disk_path read up to 32 KiB from the disk
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.