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

New -xattr mode "any" to process all xattr namespaces of local filesystem

Browse Source
This commit is contained in:
Thomas Schmitt
2017-10-23 12:08:16 +02:00
parent 25e24911d9
commit cbc5dbf496
14 changed files with 264 additions and 114 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
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.9, Sep 16, 2017"
.TH XORRISO 1 "Version 1.4.9, Oct 10, 2017"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -464,9 +464,15 @@ only on GNU/Linux and FreeBSD.
.PP
\fBxattr\fR (aka EA, or extattr)
are pairs of name and value which can be attached to file objects. AAIP is
able to represent them and \fBxorriso\fR can record and restore pairs which
have names out of the user namespace. I.e. those which begin with "user.",
like "user.x" or "user.whatever". Name has to be a 0 terminated string.
able to represent them and \fBxorriso\fR can record and restore them.
.br
But be aware that pairs with names of non\-user namespaces are not necessarily
portable between operating systems and not even between filesystems.
I.e. only those which begin with "user.", like "user.x" or "user.whatever",
can unconditionally be expected to be appropriate on other machines and disks.
Processing of other xattr may need administrator privileges.
.br
Name has to be a 0 terminated string.
Value may be any array of bytes which does not exceed the size of 4095 bytes.
xattr processing happens only if it is enabled by command
\fB\-xattr\fR.
@ -930,10 +936,18 @@ load AAIP data from ISO images, test ACL during file comparison,
and restore ACLs to disk files when extracting them from ISO images.
See also commands \-getfacl, \-setfacl.
.TP
\fB\-xattr\fR "on"|"off"
Enable or disable processing of xattr attributes in user namespace.
\fB\-xattr\fR "on"|"user"|"any"|"off"
Enable or disable processing of xattr attributes.
If enabled, then \fBxorriso\fR will handle xattr similar to ACL.
See also commands \-getfattr, \-setfattr and above paragraph about xattr.
.br
Modes "on" and "user" read and write only attributes from namespace "user".
.br
Mode "any" processes attributes of all namespaces. This might need adminstrator
privileges, even if the owner of the disk file tries to read or write the
attributes.
.br
Note that xattr from namespace "isofs." are never restored to disk.
.TP
\fB\-md5\fR "on"|"all"|"off"|"load_check_off"
Enable or disable processing of MD5 checksums for the overall session and for
@ -970,8 +984,19 @@ actions get_md5, check_md5, and via \-check_media.
.TP
\fB\-for_backup\fR
Enable all extra features which help to produce or to restore backups with
highest fidelity of file properties.
Currently this is a shortcut for: \-hardlinks on \-acl on \-xattr on \-md5 on.
highest fidelity of file properties. Currently this is a shortcut for:
.br
\-hardlinks on \-acl on \-xattr any \-md5 on
.br
If you restore a backup with xattr from non\-user namespaces, then make sure
that the target operating system and filesystem know what these attributes
mean. Possibly you will need administrator privileges to record or restore
such attributes. At recording time, xorriso will try to tolerate missing
privileges and just record what is readable.
But at restore time, missing privileges will cause failure events.
.br
Command \-xattr "user" after command \-for_backup excludes non\-user attributes
from being recorded or restored.
.TP
\fB\-ecma119_map\fR "stripped"|"unmapped"|"lowercase"|"uppercase"
Choose the conversion of file names from the loaded session if neither