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

Took into respect possible truncate mode change by AAIP variable isofs.nt

Browse Source
This commit is contained in:
Thomas Schmitt
2015-09-25 17:15:41 +00:00
parent 60adbd88c3
commit 7bd6c0fe77
7 changed files with 125 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
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 22, 2015"
.TH XORRISO 1 "Version 1.4.1, Sep 25, 2015"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -984,7 +984,7 @@ 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
\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
@ -994,20 +994,30 @@ 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 acquired. All file names get
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.
.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.
.br
If writing of xattr is enabled, then the length will be stored in "isofs.nt"
of the root directory.
If reading of xattr is enabled and "isofs.nt" is found, then the found length
will get into effect if it is smaller than the current setting
of \-file_name_limit.
.br
File name patterns will only work if they match the truncated name.
This might change in future.
.br
Files with truncated names get deleted and re\-added unconditionally
during \-update and \-update_r. 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