New -find test -name_limit_blocker. Made -file_name_limit ready for loaded ISOs
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.4.1, Sep 25, 2015"
|
||||
.TH XORRISO 1 "Version 1.4.1, Sep 28, 2015"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -993,14 +993,17 @@ oversized name. Potential incomplete UTF\-8 characters will get their
|
||||
leading bytes replaced by '_'.
|
||||
.br
|
||||
iso_rr_paths with the long components will still be able to access the
|
||||
file paths with truncated components. To avoid confusion by having both
|
||||
truncated and untruncated names in the same directory, it is highly deprecated
|
||||
to change this setting after a drive was acquired. All file names must get
|
||||
truncated by the same length.
|
||||
file paths with truncated components.
|
||||
.br
|
||||
Normally this command will produce a SORRY event if it is executed while a
|
||||
drive is aquired. One may override this ban by prepending the character "+"
|
||||
to the argument of \-file_name_limit.
|
||||
If \-file_name_limit is executed while an ISO tree is present, the file names
|
||||
in the ISO tree get checked for existing truncated file names of the current
|
||||
limit and for name collisions between newly truncated files and existing files.
|
||||
In both cases, the setting will be refused with a SORRY event.
|
||||
.br
|
||||
One may lift this ban by prepending the character "+" to the argument
|
||||
of \-file_name_limit. Truncated filenames may then get truncated again,
|
||||
invalidating their MD5 part. Colliding truncated names are made unique,
|
||||
consuming at least 9 more bytes of the remaining name part.
|
||||
.br
|
||||
If writing of xattr is enabled, then the length will be stored in "isofs.nt"
|
||||
of the root directory.
|
||||
@ -1886,6 +1889,10 @@ to name length, permissible characters, and mandatory name components.
|
||||
"rockridge" uses the character set defined by \-out_charset,
|
||||
"joliet" uses UCS\-2BE, "ecma119" uses ASCII, "hfsplus" uses UTF\-16BE.
|
||||
.br
|
||||
\fB\-name_limit_blocker\fR length :
|
||||
Matches file names which would prevent command \-file_name_limit with the
|
||||
given length. The command itself reports only the first problem file.
|
||||
.br
|
||||
\fB\-prune\fR :
|
||||
If this test is reached and the tested file is a directory then \-find will not
|
||||
dive into that directory. This test itself does always match.
|
||||
@ -2156,6 +2163,7 @@ E.g.: \-exec sort_weight 3 \-\-
|
||||
.br
|
||||
\fBshow_stream\fR
|
||||
shows the content stream chain of a data file.
|
||||
.br
|
||||
\fBshow_stream_id\fR
|
||||
is like show_stream, but also prints between stream type and first ":"
|
||||
in square brackets libisofs id numbers: [fs_id,dev_id,ino_id].
|
||||
|
Reference in New Issue
Block a user