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

Made HFS creator, type, blessing persistent in AAIP isofs.hx isofs.hb

Browse Source
This commit is contained in:
Thomas Schmitt
2012-06-08 07:09:30 +00:00
parent 7847538099
commit 7f72530f68
9 changed files with 384 additions and 208 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
libisoburn/trunk/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.2.3, Jun 06, 2012"
.TH XORRISO 1 "Version 1.2.3, Jun 07, 2012"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1666,7 +1666,7 @@ 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
These are codes of 4 characters which get stored if \-hfsplus is
enabled. Use a single dash '\-' as wildcard that matches any such code.
E.g:.
.br
@ -1679,9 +1679,6 @@ 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
@ -1881,6 +1878,12 @@ E.g.: \-exec set_hfs_crtp YYDN TEXT
.br
E.g.: \-find /my/dir \-prune \-exec set_hfs_crtp \-\-delete \-
.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
\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:
@ -1897,21 +1900,12 @@ 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
@ -2282,6 +2276,20 @@ 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.
.br
The HFS+ filesystem is not suitable for add\-on sessions produced by the
multi\-session method of growing. An existing ISO image may nevertheless
be the base for a new image produced by the method of modifying.
If \-hfsplus is enabled when \-indev or \-dev gets executed, then AAIP
attributes get loaded from the input image and checked for information about
HFS creator, filetype, or blessing. If found, then they get enabled as
settings for the next image production.
Therefore it is advisable to perform \-hfsplus "on" before \-indev or \-dev.
.br
Information about HFS creator, type, and blessings gets stored by xorriso
if \-hfsplus is enabled at \-commit time. It is stored as copy outside the
HFS+ partition, but rather along with the Rock Ridge information.
xorriso does not read any information from the HFS+ meta data.
.TP
\fB\-rockridge\fR "on"|"off"
Mode "off" disables production of Rock Ridge information for the ISO 9660 file