Reporting some relaxation commands with -report_el_torito modes "cmd" and "mkisofs" if CHRP is detected. Performing them with -boot_image any "replay".
This commit is contained in:
@ -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.5, Sep 18, 2022"
|
||||
.TH XORRISO 1 "Version 1.5.5, Oct 06, 2022"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -4586,6 +4586,14 @@ Mode \fBas_mkisofs\fR tries to print the \fBxorriso \-as mkisofs\fR
|
||||
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.
|
||||
.br
|
||||
If CHRP equipment is detected, then modes \fBcmd\fR and \fBas_mkisofs\fR
|
||||
issue some of the relaxation commands or options which get detected by
|
||||
command \fB\-assess_indev_features\fR. This happens because CHRP firmware
|
||||
reads file paths from file /ppc/bootinfo.txt and tries to find them
|
||||
case\-insensitively in the ECMA\-119 tree without using Rock Ridge. If such a
|
||||
path has actually forbidden properties, like the name "powerpc\-ieee1275", then
|
||||
the relaxations are needed to bring it unmangled into the ECMA\-119 tree.
|
||||
.TP
|
||||
\fB\-report_system_area\fR mode
|
||||
With mode \fBplain\fR print a report about the information found in
|
||||
|
Reference in New Issue
Block a user