Updated documentation of xorriso and xorrisofs about HFS+
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.2.3, Mai 22, 2012"
|
||||
.TH XORRISO 1 "Version 1.2.3, Jun 06, 2012"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -1580,7 +1580,7 @@ Like \-alter_date but affecting all files below eventual directories.
|
||||
.TP
|
||||
\fB\-hide\fR hide_state iso_rr_path [***]
|
||||
Prevent the names of the given files from showing up in the directory trees
|
||||
of ISO 9660 and/or Joliet when the image gets written.
|
||||
of ISO 9660 and/or Joliet and/or HFS+ when the image gets written.
|
||||
The data content of such hidden files will be included in the
|
||||
resulting image, even if they do not show up in any directory.
|
||||
But you will need own means to find nameless data in the image.
|
||||
@ -1589,8 +1589,11 @@ Warning: Data which are hidden from the ISO 9660 tree will not be copied
|
||||
by the write method of modifying.
|
||||
.br
|
||||
Possible values of hide_state are: "iso_rr" for hiding from ISO 9660 tree,
|
||||
"joliet" for Joliet tree, "on" for both trees. "off" means visibility in
|
||||
both directory trees.
|
||||
"joliet" for Joliet tree, "hfsplus" for HFS+, "on" for them all.
|
||||
"off" means visibility in all directory trees.
|
||||
.br
|
||||
These values may be combined.
|
||||
E.g.: joliet:hfsplus
|
||||
.br
|
||||
This command does not apply to the boot catalog.
|
||||
Rather use: \-boot_image "any" "cat_hidden=on"
|
||||
@ -1661,12 +1664,31 @@ Matches files which have any xattr other than ACL.
|
||||
\fB\-has_md5\fR :
|
||||
Matches data files which have MD5 checksums.
|
||||
.br
|
||||
\fB\-has_hfs_crtp\fR creator type :
|
||||
Matches files which have the given HFS+ creator and type attached.
|
||||
These are codes of 4 characters which may get stored if \-hfsplus is
|
||||
enabled. Use a single dash '\-' as wildcard that matches any such code.
|
||||
E.g:.
|
||||
.br
|
||||
\-has_hfs_crtp YYDN TEXT
|
||||
.br
|
||||
\-has_hfs_crtp \- \-
|
||||
.br
|
||||
\fB\-has_hfs_bless\fR blessing :
|
||||
Matches files which bear the given HFS+ blessing. It may be one of :
|
||||
"ppc_bootdir", "intel_bootfile", "show_folder", "os9_folder", "osx_folder",
|
||||
"any". See also action set_hfs_bless.
|
||||
.br
|
||||
Note that HFS+ information is not read with loaded images. So above two tests
|
||||
are useful only for listing effective settings before a new image gets written.
|
||||
.br
|
||||
\fB\-has_filter\fR :
|
||||
Matches files which are filtered by \-set_filter.
|
||||
.br
|
||||
\fB\-hidden\fR hide_state :
|
||||
Matches files which are hidden in "iso_rr" tree, in "joliet" tree,
|
||||
in both trees ("on"), or not hidden in any tree ("off").
|
||||
in "hfsplus" tree, in all trees ("on"), or not hidden in any tree ("off").
|
||||
.br
|
||||
Those which are hidden in some tree match \-not \-hidden "off".
|
||||
.br
|
||||
\fB\-prune\fR :
|
||||
@ -1852,6 +1874,44 @@ sets or deletes xattr name value pairs.
|
||||
.br
|
||||
E.g.: \-find / \-has_xattr \-exec setfattr \-\-remove\-all '' \-\-
|
||||
.br
|
||||
\fBset_hfs_crtp\fR
|
||||
adds, changes, or removes HFS+ creator and type attributes.
|
||||
.br
|
||||
E.g.: \-exec set_hfs_crtp YYDN TEXT
|
||||
.br
|
||||
E.g.: \-find /my/dir \-prune \-exec set_hfs_crtp \-\-delete \-
|
||||
.br
|
||||
\fBset_hfs_bless\fR
|
||||
applies or removes HFS+ blessings. They are roles which can be attributed to
|
||||
up to four directories and a data file:
|
||||
.br
|
||||
"ppc_bootdir", "intel_bootfile", "show_folder", "os9_folder", "osx_folder".
|
||||
.br
|
||||
They may be abbreviated as "p", "i", "s", "9", and "x".
|
||||
.br
|
||||
Each such role can be attributed to at most one file object. "intel_bootfile"
|
||||
is the one that would apply to a data file. All others apply to directories.
|
||||
The \-find run will end as soon as the first blessing is issued. The previous
|
||||
bearer of the blessing will lose it then.
|
||||
No file object can bear more than one blessing.
|
||||
.br
|
||||
E.g.: \-find /my/blessed/directory \-exec set_hfs_bless p
|
||||
.br
|
||||
\fBget_hfs_crtp\fR
|
||||
prints the HFS+ creator and type attributes together with the iso_rr_path,
|
||||
if the file has such attributes at all.
|
||||
.br
|
||||
E.g.: \-exec get_hfs_crtp
|
||||
.br
|
||||
\fBget_hfs_bless\fR
|
||||
prints the HFS+ blessing role and the iso_rr_path, if the file is blessed
|
||||
at all.
|
||||
.br
|
||||
E.g.: \-exec get_hfs_bless
|
||||
.br
|
||||
Note that HFS+ information is not read with loaded images. So above two actions
|
||||
are useful only for listing effective settings before a new image gets written.
|
||||
.br
|
||||
\fBset_filter\fR
|
||||
applies or removes filters.
|
||||
.br
|
||||
@ -1879,7 +1939,8 @@ E.g.: \-exec sort_weight 3 \-\-
|
||||
shows the content stream chain of a data file.
|
||||
.br
|
||||
\fBhide\fR
|
||||
brings the file into one of the hide states "on", "iso_rr", "joliet", "off".
|
||||
brings the file into one of the hide states "on", "iso_rr", "joliet",
|
||||
"hfsplus", "off". They may be combined. E.g.: joliet:hfsplus
|
||||
.br
|
||||
E.g.:
|
||||
.br
|
||||
@ -2203,6 +2264,25 @@ ACLs will be written according to the setting of command \-acl.
|
||||
If enabled by "on", generate Joliet tree additional to ISO 9660 + Rock Ridge
|
||||
tree.
|
||||
.TP
|
||||
\fB\-hfsplus\fR "on"|"off"
|
||||
If enabled by "on", generate a HFS+ filesystem inside the ISO 9660 image
|
||||
and mark it by Apple Partition Map (APM) entries in the System Area,
|
||||
the first 32 KiB of the image.
|
||||
.br
|
||||
This may collide with data submitted by \-boot_image system_area=.
|
||||
The first 8 bytes of the System Area get overwritten by
|
||||
{ 0x45, 0x52, 0x08 0x00, 0xeb, 0x02, 0xff, 0xff }
|
||||
which can be executed as x86 machine code without negative effects.
|
||||
So if an MBR gets combined with this feature, then its first 8 bytes
|
||||
should contain no essential commands.
|
||||
.br
|
||||
The next blocks of 2 KiB in the System Area will be occupied by APM entries.
|
||||
The first one covers the part of the ISO image before the HFS+ filesystem
|
||||
metadata. The second one marks the range from HFS+ metadata to the end
|
||||
of file content data. If more ISO image data follow, then a third partition
|
||||
entry gets produced. Other features of xorriso might cause the need for
|
||||
more APM entries.
|
||||
.TP
|
||||
\fB\-rockridge\fR "on"|"off"
|
||||
Mode "off" disables production of Rock Ridge information for the ISO 9660 file
|
||||
objects. The multi\-session capabilities of xorriso depend much on the naming
|
||||
@ -2620,7 +2700,7 @@ For ISOLINUX : \-boot_image "isolinux" "patch"
|
||||
and their designated fate.
|
||||
.br
|
||||
|
||||
A \fBbootspec\fR is a word of the form name=valuei. It is used to describe
|
||||
A \fBbootspec\fR is a word of the form name=value. It is used to describe
|
||||
the parameters of a boot image by an El Torito record or a MBR.
|
||||
The names "dir", "bin_path", "efi_path" lead to El Torito bootable images.
|
||||
Name "system_area" activates a given file as MBR.
|
||||
@ -2654,7 +2734,7 @@ a file with the same name.
|
||||
The catalog lists the boot images and is read by the boot facility to choose
|
||||
one of the boot images. But it is not necessary that it appears in the
|
||||
directory tree at all. One may hide it in all trees by \fBcat_hidden=on\fR.
|
||||
Other possible values are "iso_rr", "joliet", and the default "off".
|
||||
Other possible values are "iso_rr", "joliet", "hfsplus", and the default "off".
|
||||
.br
|
||||
\fBbin_path=\fR depicts a boot image file, a binary program which is to be
|
||||
started by the hardware boot facility (e.g. the BIOS) at boot time.
|
||||
@ -2788,6 +2868,9 @@ declarations made by mips_path= or mipsel_path=. They also disable production
|
||||
of SUN Disk Label.
|
||||
This removes the ban on production of other boot blocks.
|
||||
.br
|
||||
\fBhfsplus_serial=\fRhexstring sets a string of 16 digits "0" to "9"
|
||||
and letters "a" to "f", which will be used as unique serial number of
|
||||
an emerging HFS+ filesystem.
|
||||
.br
|
||||
.TP
|
||||
\fB\-append_partition\fR partition_number type_code disk_path
|
||||
@ -3340,8 +3423,9 @@ The output format resembles shell command ls \-ln.
|
||||
File type 'e' indicates the El Torito boot catalog.
|
||||
.br
|
||||
If the file has non\-trivial ACL, then a '+' is appended to the permission info.
|
||||
If the file is hidden, then 'I' for "iso_rr", 'J' for "joliet", resp. 'H' for
|
||||
"on" gets appended. Together with ACL it is 'i', 'j', resp. 'h'.
|
||||
If the file is hidden, then 'I' for "iso_rr", 'J' for "joliet", 'A'
|
||||
for "hfsplus", resp. 'H' for multiple hiding gets appended.
|
||||
Together with ACL it is 'i', 'j', 'a', resp. 'h'.
|
||||
.TP
|
||||
\fB\-lsdl\fR iso_rr_pattern [***]
|
||||
Like \-lsd but also list some of the file attributes.
|
||||
@ -4896,6 +4980,7 @@ same license.
|
||||
.SH CREDITS
|
||||
\fBxorriso\fR is in part based on work by Vreixo Formoso who provides
|
||||
libisofs together with Mario Danic who also leads the libburnia team.
|
||||
Vladimir Serbinenko contributed the HFS+ filesystem code and related knowledge.
|
||||
Thanks to Andy Polyakov who invented emulated growing,
|
||||
to Derek Foreman and Ben Jansens who once founded libburn.
|
||||
.br
|
||||
|
Reference in New Issue
Block a user