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

New command -file_name_limit, -as mkisofs -file_name_limit

Browse Source
This commit is contained in:
Thomas Schmitt
2015-09-17 12:12:41 +00:00
parent 14c55329ea
commit 00eca7055e
23 changed files with 582 additions and 202 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
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.4.1, Sep 05, 2015"
.TH XORRISO 1 "Version 1.4.1, Sep 16, 2015"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -972,6 +972,31 @@ The speed advantage appears only if the loaded session was produced with
Note that \-disk_dev_ino "off" is totally in effect only if \-hardlinks is "off",
too.
.TP
\fB\-file_name_limit\fR number
Set the maximum permissible length for file names in the range of 64 to 255.
Path components which are longer than the given number will get truncated
and have their last 33 bytes overwritten by a colon ':' and the
hex representation of the MD5 of the first 4095 bytes of the whole
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 untrancated names in the same directory, it is not possible
to change this setting after a drive was aquired. All file names get
truncated by the same length.
.br
File name patterns will only work if they match the truncated name.
This might change in future.
.br
Linux kernels up to at least 4.1 misrepresent names of length 254 and 255.
If you expect such names in or under disk_paths and plan to mount the ISO
by such Linux kernels, consider to set \-file_name_limit 253.
Else just avoid names longer than 253 characters.
.br
Files with truncated names get deleted and re\-added unconditionally
during \-update and \-update_r. This might change in future.
.TP
\fB\-rom_toc_scan\fR "on"|"force"|"off"[:"emul_off"][:"emul_wide"]
Read\-only drives do not tell the actual media type but show any media as
ROM (e.g. as DVD\-ROM). The session history of MMC multi\-session media might
@ -1742,11 +1767,15 @@ if all its tests match.
Available tests are:
.br
\fB\-name\fR pattern :
Matches if pattern matches the file leaf name.
Matches if pattern matches the file leaf name. If the pattern does not contain
any of the characters "*?[", then it will be truncated according
to \-file_name_limit and thus match the truncated name in the ISO filesystem.
.br
\fB\-wholename\fR pattern :
Matches if pattern matches the file path as it would be printed by action
"echo". Character '/' is not special but can be matched by wildcards.
"echo". Character '/' can be matched by wildcards. If pattern pieces
between '/' do not contain any of the characters "*?[", they will
be truncated according to \-file_name_limit.
.br
\fB\-disk_name\fR pattern :
Like \-name but testing the leaf name of the file source on disk.
@ -3096,6 +3125,10 @@ for existing El Torito boot equipment but also for the recognizable
boot provisions in the System Area. It discards any existing \-boot_image
setting and executes the commands proposed by command \-report_el_torito "cmd".
.br
This action will only succeed if the file objects mentioned in the
output of command \-report_el_torito "cmd" are still available. Do not
remove or rename boot image files after \-indev.
.br
Drop unknown El Torito: \-boot_image "any" "discard"
.br
Maintain recognizable stuff: \-boot_image "any" "replay"