diff options
Diffstat (limited to 'archivers/libarchive/files/doc/html')
43 files changed, 718 insertions, 319 deletions
diff --git a/archivers/libarchive/files/doc/html/Makefile b/archivers/libarchive/files/doc/html/Makefile index e045e7c3ffa..c3da36a9d67 100644 --- a/archivers/libarchive/files/doc/html/Makefile +++ b/archivers/libarchive/files/doc/html/Makefile @@ -104,15 +104,15 @@ archive_write_set_passphrase.3.html: ../../libarchive/archive_write_set_passphra cpio.5.html: ../../libarchive/cpio.5 groff -mdoc -T html ../../libarchive/cpio.5 > cpio.5.html +libarchive-formats.5.html: ../../libarchive/libarchive-formats.5 + groff -mdoc -T html ../../libarchive/libarchive-formats.5 > libarchive-formats.5.html + libarchive.3.html: ../../libarchive/libarchive.3 groff -mdoc -T html ../../libarchive/libarchive.3 > libarchive.3.html libarchive_changes.3.html: ../../libarchive/libarchive_changes.3 groff -mdoc -T html ../../libarchive/libarchive_changes.3 > libarchive_changes.3.html -libarchive-formats.5.html: ../../libarchive/libarchive-formats.5 - groff -mdoc -T html ../../libarchive/libarchive-formats.5 > libarchive-formats.5.html - libarchive_internals.3.html: ../../libarchive/libarchive_internals.3 groff -mdoc -T html ../../libarchive/libarchive_internals.3 > libarchive_internals.3.html @@ -127,4 +127,4 @@ bsdtar.1.html: ../../tar/bsdtar.1 bsdcpio.1.html: ../../cpio/bsdcpio.1 groff -mdoc -T html ../../cpio/bsdcpio.1 > bsdcpio.1.html -all: archive_entry.3.html archive_entry_acl.3.html archive_entry_linkify.3.html archive_entry_paths.3.html archive_entry_perms.3.html archive_entry_stat.3.html archive_entry_time.3.html archive_read.3.html archive_read_add_passphrase.3.html archive_read_data.3.html archive_read_disk.3.html archive_read_extract.3.html archive_read_filter.3.html archive_read_format.3.html archive_read_free.3.html archive_read_header.3.html archive_read_new.3.html archive_read_open.3.html archive_read_set_options.3.html archive_util.3.html archive_write.3.html archive_write_blocksize.3.html archive_write_data.3.html archive_write_disk.3.html archive_write_filter.3.html archive_write_finish_entry.3.html archive_write_format.3.html archive_write_free.3.html archive_write_header.3.html archive_write_new.3.html archive_write_open.3.html archive_write_set_options.3.html archive_write_set_passphrase.3.html cpio.5.html libarchive.3.html libarchive_changes.3.html libarchive-formats.5.html libarchive_internals.3.html mtree.5.html tar.5.html bsdtar.1.html bsdcpio.1.html +all: archive_entry.3.html archive_entry_acl.3.html archive_entry_linkify.3.html archive_entry_paths.3.html archive_entry_perms.3.html archive_entry_stat.3.html archive_entry_time.3.html archive_read.3.html archive_read_add_passphrase.3.html archive_read_data.3.html archive_read_disk.3.html archive_read_extract.3.html archive_read_filter.3.html archive_read_format.3.html archive_read_free.3.html archive_read_header.3.html archive_read_new.3.html archive_read_open.3.html archive_read_set_options.3.html archive_util.3.html archive_write.3.html archive_write_blocksize.3.html archive_write_data.3.html archive_write_disk.3.html archive_write_filter.3.html archive_write_finish_entry.3.html archive_write_format.3.html archive_write_free.3.html archive_write_header.3.html archive_write_new.3.html archive_write_open.3.html archive_write_set_options.3.html archive_write_set_passphrase.3.html cpio.5.html libarchive-formats.5.html libarchive.3.html libarchive_changes.3.html libarchive_internals.3.html mtree.5.html tar.5.html bsdtar.1.html bsdcpio.1.html diff --git a/archivers/libarchive/files/doc/html/archive_entry.3.html b/archivers/libarchive/files/doc/html/archive_entry.3.html index 2c1de4985fb..fc75a82e5c6 100644 --- a/archivers/libarchive/files/doc/html/archive_entry.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:05 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:01 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_acl.3.html b/archivers/libarchive/files/doc/html/archive_entry_acl.3.html index f4068d341bf..7e76efb9bb8 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_acl.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_acl.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:05 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:01 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -30,10 +30,13 @@ ARCHIVE_ENTRY_ACL(3)</p> <b>archive_entry_acl_add_entry_w</b>, <b>archive_entry_acl_clear</b>, <b>archive_entry_acl_count</b>, -<b>archive_entry_acl_next</b>, -<b>archive_entry_acl_next_w</b>, +<b>archive_entry_acl_from_text</b>, +<b>archive_entry_acl_from_text_w, +archive_entry_acl_next</b>, <b>archive_entry_acl_next_w</b>, <b>archive_entry_acl_reset</b>, -<b>archive_entry_acl_text_w</b> — functions for +<b>archive_entry_acl_to_text</b>, +<b>archive_entry_acl_to_text_w</b>, +<b>archive_entry_acl_types</b> — functions for manipulating Access Control Lists in archive entry descriptions</p> @@ -77,6 +80,20 @@ descriptions</p> <p style="margin-left:6%; margin-top: 1em"><i>int</i></p> +<p><b>archive_entry_acl_from_text</b>(<i>struct archive_entry *a</i>, +<i>const char *text</i>, +<i>int type</i>);</p> + +<p style="margin-left:6%; margin-top: 1em"><i>int</i></p> + + +<p><b>archive_entry_acl_from_text_w</b>(<i>struct archive_entry *a</i>, +<i>const wchar_t *text</i>, +<i>int type</i>);</p> + +<p style="margin-left:6%; margin-top: 1em"><i>int</i></p> + + <p><b>archive_entry_acl_next</b>(<i>struct archive_entry *a</i>, <i>int type</i>, <i>int *ret_type</i>, <i>int *ret_permset</i>, <i>int *ret_tag</i>, @@ -98,86 +115,287 @@ descriptions</p> <p style="margin-left:12%;"><b>archive_entry_acl_reset</b>(<i>struct archive_entry *a</i>, <i>int type</i>);</p> -<p style="margin-left:6%; margin-top: 1em"><i>const wchar_t +<p style="margin-left:6%; margin-top: 1em"><i>char +*</i></p> + + +<p><b>archive_entry_acl_to_text</b>(<i>struct archive_entry *a</i>, +<i>ssize_t *len_p</i>, <i>int flags</i>);</p> + +<p style="margin-left:6%; margin-top: 1em"><i>wchar_t *</i></p> -<p style="margin-left:12%;"><b>archive_entry_acl_text_w</b>(<i>struct archive_entry *a</i>, -<i>int flags</i>);</p> +<p><b>archive_entry_acl_to_text_w</b>(<i>struct archive_entry *a</i>, +<i>ssize_t *len_p</i>, <i>int flags</i>);</p> + +<p style="margin-left:6%; margin-top: 1em"><i>int</i></p> + + +<p style="margin-left:12%;"><b>archive_entry_acl_types</b>(<i>struct archive_entry *a</i>);</p> <p style="margin-top: 1em"><b>DESCRIPTION</b></p> -<p style="margin-left:6%;">An ’’Access Control -List’’ is a generalisation of the classic Unix -permission system. The ACL interface of <b>libarchive</b> is -derived from the POSIX.1e draft, but restricted to simplify -dealing with practical implementations in various Operating -Systems and archive formats.</p> +<p style="margin-left:6%;">The ‘‘Access Control +Lists (ACLs)’’ extend the standard Unix perssion +model. The ACL interface of <b>libarchive</b> supports both +POSIX.1e and NFSv4 style ACLs. Use of ACLs is restricted by +various levels of ACL support in operating systems, file +systems and archive formats.</p> -<p style="margin-left:6%; margin-top: 1em">An ACL consists -of a number of independent entries. Each entry specifies the -permission set as bitmask of basic permissions. Valid -permissions are:</p> +<p style="margin-left:6%; margin-top: 1em"><b>POSIX.1e +Access Control Lists</b> <br> +A POSIX.1e ACL consists of a number of independent entries. +Each entry specifies the permission set as bitmask of basic +permissions. Valid permissions in the <i>permset</i> +are:</p> -<p>ARCHIVE_ENTRY_ACL_EXECUTE <br> -ARCHIVE_ENTRY_ACL_WRITE <br> -ARCHIVE_ENTRY_ACL_READ</p> +<p>ARCHIVE_ENTRY_ACL_READ (<b>r</b>) <br> +ARCHIVE_ENTRY_ACL_WRITE (<b>w</b>) <br> +ARCHIVE_ENTRY_ACL_EXECUTE (<b>x</b>)</p> -<p style="margin-left:6%; margin-top: 1em">The permissions -correspond to the normal Unix permissions.</p> +<p style="margin-left:6%;">The permissions correspond to +the normal Unix permissions.</p> -<p style="margin-left:6%; margin-top: 1em">The tag +<p style="margin-left:6%; margin-top: 1em">The <i>tag</i> specifies the principal to which the permission applies. Valid values are:</p> <p>ARCHIVE_ENTRY_ACL_USER</p> -<p style="margin-left:51%; margin-top: 1em">The user -specified by the name field.</p> +<p style="margin-left:51%;">The user specified by the name +field.</p> <p>ARCHIVE_ENTRY_ACL_USER_OBJ</p> -<p style="margin-left:51%; margin-top: 1em">The owner of -the file.</p> +<p style="margin-left:51%;">The owner of the file.</p> <p>ARCHIVE_ENTRY_ACL_GROUP</p> -<p style="margin-left:51%; margin-top: 1em">The group -specied by the name field.</p> +<p style="margin-left:51%;">The group specied by the name +field.</p> <p>ARCHIVE_ENTRY_ACL_GROUP_OBJ</p> -<p style="margin-left:51%; margin-top: 1em">The group who -owns the file.</p> +<p style="margin-left:51%;">The group who owns the +file.</p> <p>ARCHIVE_ENTRY_ACL_MASK</p> -<p style="margin-left:51%; margin-top: 1em">The maximum -permissions to be obtained via group permissions.</p> +<p style="margin-left:51%;">The maximum permissions to be +obtained via group permissions.</p> <p>ARCHIVE_ENTRY_ACL_OTHER</p> -<p style="margin-left:51%; margin-top: 1em">Any principal -who doesn’t have a user or group entry.</p> +<p style="margin-left:51%;">Any principal who is not file +owner or a member of the owning group.</p> -<p style="margin-left:6%;">The principals +<p style="margin-left:6%; margin-top: 1em">The principals ARCHIVE_ENTRY_ACL_USER_OBJ, ARCHIVE_ENTRY_ACL_GROUP_OBJ and ARCHIVE_ENTRY_ACL_OTHER are equivalent to user, group and other in the classic Unix permission model and specify non-extended ACL entries.</p> -<p style="margin-left:6%; margin-top: 1em">All files have -an access ACL (ARCHIVE_ENTRY_ACL_TYPE_ACCESS). This +<p style="margin-left:6%; margin-top: 1em">All files with +have an access ACL (ARCHIVE_ENTRY_ACL_TYPE_ACCESS). This specifies the permissions required for access to the file itself. Directories have an additional ACL (ARCHIVE_ENTRY_ACL_TYPE_DEFAULT), which controls the initial access ACL for newly created directory entries.</p> +<p style="margin-left:6%; margin-top: 1em"><b>NFSv4 Access +Control Lists</b> <br> +A NFSv4 ACL consists of multiple individual entries called +Access Control Entries (ACEs).</p> + +<p style="margin-left:6%; margin-top: 1em">There are four +possible types of a NFSv4 ACE:</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_ALLOW</p> + +<p style="margin-left:51%;">Allow principal to perform +actions requiring given permissions.</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_DENY</p> + +<p style="margin-left:51%;">Prevent principal from +performing actions requiring given permissions.</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_AUDIT</p> + +<p style="margin-left:51%;">Log access attempts by +principal which require given permissions.</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_ALARM</p> + +<p style="margin-left:51%;">Trigger a system alarm on +access attempts by principal which require given +permissions.</p> + +<p style="margin-left:6%; margin-top: 1em">The <i>tag</i> +specifies the principal to which the permission applies. +Valid values are:</p> + +<p>ARCHIVE_ENTRY_ACL_USER</p> + +<p style="margin-left:51%;">The user specified by the name +field.</p> + +<p>ARCHIVE_ENTRY_ACL_USER_OBJ</p> + +<p style="margin-left:51%;">The owner of the file.</p> + +<p>ARCHIVE_ENTRY_ACL_GROUP</p> + +<p style="margin-left:51%;">The group specied by the name +field.</p> + +<p>ARCHIVE_ENTRY_ACL_GROUP_OBJ</p> + +<p style="margin-left:51%;">The group who owns the +file.</p> + +<p>ARCHIVE_ENTRY_ACL_EVERYONE</p> + +<p style="margin-left:51%;">Any principal who is not file +owner or a member of the owning group.</p> + +<p style="margin-left:6%; margin-top: 1em">Entries with the +ARCHIVE_ENTRY_ACL_USER or ARCHIVE_ENTRY_ACL_GROUP tag store +the user and group name in the <i>name</i> string and +optionally the user or group ID in the <i>qualifier</i> +integer.</p> + +<p style="margin-left:6%; margin-top: 1em">NFSv4 ACE +permissions and flags are stored in the same <i>permset</i> +bitfield. Some permissions share the same constant and +permission character but have different effect on +directories than on files. The following ACE permissions are +supported:</p> + +<p>ARCHIVE_ENTRY_ACL_READ_DATA (<b>r</b>)</p> + +<p style="margin-left:24%;">Read data (file).</p> + +<p>ARCHIVE_ENTRY_ACL_LIST_DIRECTORY (<b>r</b>)</p> + +<p style="margin-left:24%;">List entries (directory).</p> + +<p>ARCHIVE_ENTRY_ACL_WRITE_DATA (<b>w</b>)</p> + +<p style="margin-left:24%;">Write data (file).</p> + +<p>ARCHIVE_ENTRY_ACL_ADD_FILE (<b>w</b>)</p> + +<p style="margin-left:24%;">Create files (directory).</p> + +<p>ARCHIVE_ENTRY_ACL_EXECUTE (<b>x</b>)</p> + +<p style="margin-left:24%;">Execute file or change into a +directory.</p> + +<p>ARCHIVE_ENTRY_ACL_APPEND_DATA (<b>p</b>)</p> + +<p style="margin-left:24%;">Append data (file).</p> + +<p>ARCHIVE_ENTRY_ACL_ADD_SUBDIRECTORY (<b>p</b>)</p> + +<p style="margin-left:24%;">Create subdirectories +(directory).</p> + +<p>ARCHIVE_ENTRY_ACL_DELETE_CHILD (<b>D</b>)</p> + +<p style="margin-left:24%;">Remove files and subdirectories +inside a directory.</p> + +<p>ARCHIVE_ENTRY_ACL_DELETE (<b>d</b>)</p> + +<p style="margin-left:24%;">Remove file or directory.</p> -<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_add_entry</b>() -and <b>archive_entry_acl_add_entry_w</b>() add a single ACL +<p>ARCHIVE_ENTRY_ACL_READ_ATTRIBUTES (<b>a</b>)</p> + +<p style="margin-left:24%;">Read file or directory +attributes.</p> + +<p>ARCHIVE_ENTRY_ACL_WRITE_ATTRIBUTES (<b>A</b>)</p> + +<p style="margin-left:24%;">Write file or directory +attributes.</p> + +<p>ARCHIVE_ENTRY_ACL_READ_NAMED_ATTRS (<b>R</b>)</p> + +<p style="margin-left:24%;">Read named file or directory +attributes.</p> + +<p>ARCHIVE_ENTRY_ACL_WRITE_NAMED_ATTRS (<b>W</b>)</p> + +<p style="margin-left:24%;">Write named file or directory +attributes.</p> + +<p>ARCHIVE_ENTRY_ACL_READ_ACL (<b>c</b>)</p> + +<p style="margin-left:24%;">Read file or directory ACL.</p> + +<p>ARCHIVE_ENTRY_ACL_WRITE_ACL (<b>C</b>)</p> + +<p style="margin-left:24%;">Write file or directory +ACL.</p> + +<p>ARCHIVE_ENTRY_ACL_WRITE_OWNER (<b>o</b>)</p> + +<p style="margin-left:24%;">Change owner of a file or +directory.</p> + +<p>ARCHIVE_ENTRY_ACL_SYNCHRONIZE (<b>s</b>)</p> + +<p style="margin-left:24%;">Use synchronous I/O.</p> + +<p style="margin-left:6%; margin-top: 1em">The following +NFSv4 ACL inheritance flags are supported:</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_FILE_INHERIT (<b>f</b>)</p> + +<p style="margin-left:24%;">Inherit parent directory ACE to +files.</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_DIRECTORY_INHERIT (<b>d</b>)</p> + +<p style="margin-left:24%;">Inherit parent directory ACE to +subdirectories.</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_INHERIT_ONLY (<b>i</b>)</p> + +<p style="margin-left:24%;">Only inherit, do not apply the +permission on the directory itself.</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_NO_PROPAGATE_INHERIT +(<b>n</b>)</p> + +<p style="margin-left:24%;">Do not propagate inherit flags. +Only first-level entries inherit ACLs.</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_SUCCESSFUL_ACCESS (<b>S</b>)</p> + +<p style="margin-left:24%;">Trigger alarm or audit on +succesful access.</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_FAILED_ACCESS (<b>F</b>)</p> + +<p style="margin-left:24%;">Trigger alarm or audit on +failed access.</p> + +<p>ARCHIVE_ENTRY_ACL_ENTRY_INHERITED (<b>I</b>)</p> + +<p style="margin-left:24%;">Mark that ACE was +inherited.</p> + +<p style="margin-left:6%; margin-top: 1em"><b>Functions +<br> +archive_entry_acl_add_entry</b>() and +<b>archive_entry_acl_add_entry_w</b>() add a single ACL entry. For the access ACL and non-extended principals, the -classic Unix permissions are updated.</p> +classic Unix permissions are updated. An archive enry cannot +contain both POSIX.1e and NFSv4 ACL entries.</p> <p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_clear</b>() @@ -187,12 +405,45 @@ pointer.</p> <p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_count</b>() counts the ACL entries that have the given type mask. -<i>type</i> can be the bitwise-or of -ARCHIVE_ENTRY_ACL_TYPE_ACCESS and -ARCHIVE_ENTRY_ACL_TYPE_DEFAULT. If -ARCHIVE_ENTRY_ACL_TYPE_ACCESS is included and at least one -extended ACL entry is found, the three non-extened ACLs are -added.</p> +<i>type</i> can be the bitwise-or of</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_ACCESS <br> +ARCHIVE_ENTRY_ACL_TYPE_DEFAULT</p> + +<p style="margin-left:6%; margin-top: 1em">for POSIX.1e +ACLs and</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_ALLOW <br> +ARCHIVE_ENTRY_ACL_TYPE_DENY <br> +ARCHIVE_ENTRY_ACL_TYPE_AUDIT <br> +ARCHIVE_ENTRY_ACL_TYPE_ALARM</p> + +<p style="margin-left:6%; margin-top: 1em">for NFSv4 ACLs. +For POSIX.1e ACLs if ARCHIVE_ENTRY_ACL_TYPE_ACCESS is +included and at least one extended ACL entry is found, the +three non-extened ACLs are added.</p> + + +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_from_text</b>() +and <b>archive_entry_acl_from_text_w</b>() add new (or merge +with existing) ACL entries from (wide) text. The argument +<i>type</i> may take one of the following values:</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_ACCESS <br> +ARCHIVE_ENTRY_ACL_TYPE_DEFAULT <br> +ARCHIVE_ENTRY_ACL_TYPE_NFS4</p> + +<p style="margin-left:6%; margin-top: 1em">Supports all +formats that can be created with +<b>archive_entry_acl_to_text</b>() or respective +<b>archive_entry_acl_to_text_w</b>(). Existing ACL entries +are preserved. To get a clean new ACL from text +<b>archive_entry_acl_clear</b>() must be called first. +Entries prefixed with ‘‘default:’’ +are treated as ARCHIVE_ENTRY_ACL_TYPE_DEFAULT unless +<i>type</i> is ARCHIVE_ENTRY_ACL_TYPE_NFS4. Invalid entries, +non-parseable ACL entries and entries beginning with the +‘#’ character (comments) are skipped.</p> <p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_next</b>() @@ -213,27 +464,89 @@ function returns the same value as <b>archive_entry_acl_count</b>().</p> -<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_text_w</b>() -converts the ACL entries for the given type mask into a wide -string. In addition to the normal type flags, -ARCHIVE_ENTRY_ACL_STYLE_EXTRA_ID and -ARCHIVE_ENTRY_ACL_STYLE_MARK_DEFAULT can be specified to -further customize the result. The returned long string is -valid until the next call to -<b>archive_entry_acl_clear</b>(), -<b>archive_entry_acl_add_entry</b>(), -<b>archive_entry_acl_add_entry_w</b>() or -<b>archive_entry_acl_text_w</b>().</p> +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_to_text</b>() +and <b>archive_entry_acl_to_text_w</b>() convert the ACL +entries for the given type into a (wide) string of ACL +entries separated by newline. If the the pointer +<i>len_p</i> is not NULL, then the function shall return the +length of the string (not including the NULL terminator) in +the location pointed to by <i>len_p</i>. The <i>flag</i> +argument is a bitwise-or.</p> + +<p style="margin-left:6%; margin-top: 1em">The following +flags are effective only on POSIX.1e ACL:</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_ACCESS</p> + +<p style="margin-left:24%;">Output access ACLs.</p> + +<p>ARCHIVE_ENTRY_ACL_TYPE_DEFAULT</p> + +<p style="margin-left:24%;">Output POSIX.1e default +ACLs.</p> + +<p>ARCHIVE_ENTRY_ACL_STYLE_MARK_DEFAULT</p> + +<p style="margin-left:24%;">Prefix each default ACL entry +with the word ‘‘default:’’.</p> + +<p>ARCHIVE_ENTRY_ACL_STYLE_SOLARIS</p> + +<p style="margin-left:24%;">The mask and other ACLs don not +contain a double colon.</p> + +<p style="margin-left:6%; margin-top: 1em">The following +flags are effecive only on NFSv4 ACL:</p> + +<p>ARCHIVE_ENTRY_ACL_STYLE_COMPACT</p> + +<p style="margin-left:24%;">Do not output minus characters +for unset permissions and flags in NFSv4 ACL permission and +flag fields.</p> + +<p style="margin-left:6%; margin-top: 1em">The following +flags are effective on both POSIX.1e and NFSv4 ACL:</p> + +<p>ARCHIVE_ENTRY_ACL_STYLE_EXTRA_ID</p> + +<p style="margin-left:24%;">Add an additional +colon-separated field containing the user or group id.</p> + +<p>ARCHIVE_ENTRY_ACL_STYLE_SEPARATOR_COMMA</p> + +<p style="margin-left:24%;">Separate ACL entries with comma +instead of newline.</p> + +<p style="margin-left:6%; margin-top: 1em">If the archive +entry contains NFSv4 ACLs, all types of NFSv4 ACLs are +returned. It the entry contains POSIX.1e ACLs and none of +the flags ARCHIVE_ENTRY_ACL_TYPE_ACCESS or +ARCHIVE_ENTRY_ACL_TYPE_DEFAULT are specified, both access +and default entries are returned and default entries are +prefixed with ‘‘default:’’.</p> + + +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_types</b>() +get ACL entry types contained in an archive entry’s +ACL. As POSIX.1e and NFSv4 ACL entries cannot be mixed, this +function is a very efficient way to detect if an ACL already +contains POSIX.1e or NFSv4 ACL entries.</p> <p style="margin-top: 1em"><b>RETURN VALUES</b></p> <p style="margin-left:6%;"><b>archive_entry_acl_count</b>() and <b>archive_entry_acl_reset</b>() returns the number of -ACL entries that match the given type mask. If the type mask -includes ARCHIVE_ENTRY_ACL_TYPE_ACCESS and at least one -extended ACL entry exists, the three classic Unix -permissions are counted.</p> +ACL entries that match the given type mask. For POSIX.1e +ACLS if the type mask includes ARCHIVE_ENTRY_ACL_TYPE_ACCESS +and at least one extended ACL entry exists, the three +classic Unix permissions are counted.</p> + + +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_from_text</b>() +and <b>archive_entry_acl_from_text_w</b>() return ARCHIVE_OK +if all entries were successfully parsed and ARCHIVE_WARN if +one or more entries were invalid or non-parseable.</p> <p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_next</b>() @@ -243,29 +556,27 @@ ARCHIVE_WARN if <b>archive_entry_acl_reset</b>() has not been called first.</p> -<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_text_w</b>() -returns a wide string representation of the ACL entrise -matching the given type mask. The returned long string is -valid until the next call to -<b>archive_entry_acl_clear</b>(), -<b>archive_entry_acl_add_entry</b>(), -<b>archive_entry_acl_add_entry_w</b>() or -<b>archive_entry_acl_text_w</b>().</p> +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_to_text</b>() +returns a string representing the ACL entries matching the +given type and flags on success or NULL on error.</p> -<p style="margin-top: 1em"><b>SEE ALSO</b></p> -<p style="margin-left:6%;">archive_entry(3) -libarchive(3),</p> +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_to_text_w</b>() +returns a wide string representing the ACL entries matching +the given type and flags on success or NULL on error.</p> -<p style="margin-top: 1em"><b>BUGS</b></p> +<p style="margin-left:6%; margin-top: 1em"><b>archive_entry_acl_types</b>() +returns a bitmask of ACL entry types or 0 if archive entry +has no ACL entries.</p> + +<p style="margin-top: 1em"><b>SEE ALSO</b></p> -<p style="margin-left:6%;">ARCHIVE_ENTRY_ACL_STYLE_EXTRA_ID -and ARCHIVE_ENTRY_ACL_STYLE_MARK_DEFAULT are not -documented.</p> +<p style="margin-left:6%;">archive_entry(3), +libarchive(3)</p> <p style="margin-left:6%; margin-top: 1em">BSD -February 2, 2012 BSD</p> +February 15, 2017 BSD</p> <hr> </body> </html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html b/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html index 2e7af8b1db7..d0a995565c4 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_linkify.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:01 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_paths.3.html b/archivers/libarchive/files/doc/html/archive_entry_paths.3.html index 4e7d559512d..a431c708074 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_paths.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_paths.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_perms.3.html b/archivers/libarchive/files/doc/html/archive_entry_perms.3.html index a20c6c8235d..ba8ed77282a 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_perms.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_perms.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_stat.3.html b/archivers/libarchive/files/doc/html/archive_entry_stat.3.html index be32b922965..9716c124f18 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_stat.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_stat.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_entry_time.3.html b/archivers/libarchive/files/doc/html/archive_entry_time.3.html index a385f50d796..bac2cb886d8 100644 --- a/archivers/libarchive/files/doc/html/archive_entry_time.3.html +++ b/archivers/libarchive/files/doc/html/archive_entry_time.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read.3.html b/archivers/libarchive/files/doc/html/archive_read.3.html index 2f1a80e985b..a9b3759131d 100644 --- a/archivers/libarchive/files/doc/html/archive_read.3.html +++ b/archivers/libarchive/files/doc/html/archive_read.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -224,7 +224,7 @@ example, many implementations of tar(1) allow you to append entries to an empty file. Of course, it is impossible to determine the format of an empty file by inspecting the contents, so this library treats empty files as having a -special ’’empty’’ format.</p> +special ‘‘empty’’ format.</p> <p style="margin-left:6%; margin-top: 1em">BSD February 2, 2012 BSD</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html b/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html index 7d32eea3eee..34d7e000b25 100644 --- a/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_add_passphrase.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_data.3.html b/archivers/libarchive/files/doc/html/archive_read_data.3.html index 4ca22addcb2..e6b52850bf8 100644 --- a/archivers/libarchive/files/doc/html/archive_read_data.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_data.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:02 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_disk.3.html b/archivers/libarchive/files/doc/html/archive_read_disk.3.html index c2a782a5ae9..db78662d4d6 100644 --- a/archivers/libarchive/files/doc/html/archive_read_disk.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_disk.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -70,13 +70,15 @@ archive *</i></p> <p style="margin-left:12%;"><b>archive_read_disk_set_symlink_hybrid</b>(<i>struct archive *</i>);</p> -<p style="margin-left:6%; margin-top: 1em"><i>int</i></p> +<p style="margin-left:6%; margin-top: 1em"><i>const char +*</i></p> <p style="margin-left:12%;"><b>archive_read_disk_gname</b>(<i>struct archive *</i>, <i>gid_t</i>);</p> -<p style="margin-left:6%; margin-top: 1em"><i>int</i></p> +<p style="margin-left:6%; margin-top: 1em"><i>const char +*</i></p> <p style="margin-left:12%;"><b>archive_read_disk_uname</b>(<i>struct archive *</i>, @@ -146,11 +148,11 @@ information from disk.</p> <p style="margin-left:17%;">This sets the mode used for handling symbolic links. The -’’logical’’ mode follows all -symbolic links. The ’’physical’’ +‘‘logical’’ mode follows all +symbolic links. The ‘‘physical’’ mode does not follow any symbolic links. The -’’hybrid’’ mode currently behaves -identically to the ’’logical’’ +‘‘hybrid’’ mode currently behaves +identically to the ‘‘logical’’ mode.</p> @@ -323,7 +325,7 @@ was written by Tim Kientzle <p style="margin-top: 1em"><b>BUGS</b></p> <p style="margin-left:6%;">The -’’standard’’ user name and group +‘‘standard’’ user name and group name lookup functions are not the defaults because getgrgid(3) and getpwuid(3) are sometimes too large for particular applications. The current design allows the @@ -346,11 +348,11 @@ such information.</p> provide a set of methods for walking a directory tree. That would make it a direct parallel of the archive_read(3) API. When such methods are implemented, the -’’hybrid’’ symbolic link mode will +‘‘hybrid’’ symbolic link mode will make sense.</p> <p style="margin-left:6%; margin-top: 1em">BSD -February 2, 2012 BSD</p> +December 30, 2016 BSD</p> <hr> </body> </html> diff --git a/archivers/libarchive/files/doc/html/archive_read_extract.3.html b/archivers/libarchive/files/doc/html/archive_read_extract.3.html index 5928645bbd6..5c618986917 100644 --- a/archivers/libarchive/files/doc/html/archive_read_extract.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_extract.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:06 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_filter.3.html b/archivers/libarchive/files/doc/html/archive_read_filter.3.html index 2e143476d1c..837b2083190 100644 --- a/archivers/libarchive/files/doc/html/archive_read_filter.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_filter.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -149,7 +149,7 @@ functions may fall back on external programs if an appropriate library was not available at build time. Decompression using an external program is usually slower than decompression through built-in libraries. Note that -’’none’’ is always enabled by +‘‘none’’ is always enabled by default.</p> <p><b>archive_read_support_filter_all</b>()</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_format.3.html b/archivers/libarchive/files/doc/html/archive_read_format.3.html index 548eed903cd..31ac3e29b3a 100644 --- a/archivers/libarchive/files/doc/html/archive_read_format.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_format.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -153,7 +153,7 @@ variants.</p> <p><b>archive_read_support_format_all</b>()</p> <p style="margin-left:17%;">Enables support for all -available formats except the ’’raw’’ +available formats except the ‘‘raw’’ format (see below).</p> <p><b>archive_read_support_format_by_code</b>()</p> @@ -180,10 +180,10 @@ distinct format.</p> <p><b>archive_read_support_format_raw</b>()</p> <p style="margin-left:17%;">The -’’raw’’ format handler allows +‘‘raw’’ format handler allows libarchive to be used to read arbitrary data. It treats any data stream as an archive with a single entry. The pathname -of this entry is ’’data’’; all other +of this entry is ‘‘data’’; all other entry fields are unset. This is not enabled by <b>archive_read_support_format_all</b>() in order to avoid erroneous handling of damaged archives.</p> @@ -213,10 +213,10 @@ example, many implementations of tar(1) allow you to append entries to an empty file. Of course, it is impossible to determine the format of an empty file by inspecting the contents, so this library treats empty files as having a -special ’’empty’’ format.</p> +special ‘‘empty’’ format.</p> <p style="margin-left:6%; margin-top: 1em">Using the -’’raw’’ handler together with any +‘‘raw’’ handler together with any other handler will often work but can produce surprising results.</p> diff --git a/archivers/libarchive/files/doc/html/archive_read_free.3.html b/archivers/libarchive/files/doc/html/archive_read_free.3.html index 49a21eff3e8..a7336df41b3 100644 --- a/archivers/libarchive/files/doc/html/archive_read_free.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_free.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_header.3.html b/archivers/libarchive/files/doc/html/archive_read_header.3.html index 7c16ef92023..01aae30c87e 100644 --- a/archivers/libarchive/files/doc/html/archive_read_header.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_header.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_new.3.html b/archivers/libarchive/files/doc/html/archive_read_new.3.html index d415322100b..5c35255a44f 100644 --- a/archivers/libarchive/files/doc/html/archive_read_new.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_new.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:03 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_open.3.html b/archivers/libarchive/files/doc/html/archive_read_open.3.html index 41097e86043..4e1c7b84f78 100644 --- a/archivers/libarchive/files/doc/html/archive_read_open.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_open.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:04 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_read_set_options.3.html b/archivers/libarchive/files/doc/html/archive_read_set_options.3.html index 8e7f182f715..99049a113d0 100644 --- a/archivers/libarchive/files/doc/html/archive_read_set_options.3.html +++ b/archivers/libarchive/files/doc/html/archive_read_set_options.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:04 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -142,7 +142,7 @@ option with this name will ignore it.</p> <p style="margin-left:27%; margin-top: 1em">The option will be provided to every module with a value of -’’1’’.</p> +‘‘1’’.</p> <p><i>!option</i></p> diff --git a/archivers/libarchive/files/doc/html/archive_util.3.html b/archivers/libarchive/files/doc/html/archive_util.3.html index ab0c3f0b24d..30c0919cbe5 100644 --- a/archivers/libarchive/files/doc/html/archive_util.3.html +++ b/archivers/libarchive/files/doc/html/archive_util.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:04 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -253,21 +253,21 @@ This function should be used within I/O callbacks to set system-specific error codes and error descriptions. This function accepts a printf-like format string and arguments. However, you should be careful to use only the following -printf format specifiers: ’’%c’’, -’’%d’’, -’’%jd’’, -’’%jo’’, -’’%ju’’, -’’%jx’’, -’’%ld’’, -’’%lo’’, -’’%lu’’, -’’%lx’’, -’’%o’’, -’’%u’’, -’’%s’’, -’’%x’’, -’’%%’’. Field-width specifiers and +printf format specifiers: ‘‘%c’’, +‘‘%d’’, +‘‘%jd’’, +‘‘%jo’’, +‘‘%ju’’, +‘‘%jx’’, +‘‘%ld’’, +‘‘%lo’’, +‘‘%lu’’, +‘‘%lx’’, +‘‘%o’’, +‘‘%u’’, +‘‘%s’’, +‘‘%x’’, +‘‘%%’’. Field-width specifiers and other printf features are not uniformly supported and should not be used.</p> diff --git a/archivers/libarchive/files/doc/html/archive_write.3.html b/archivers/libarchive/files/doc/html/archive_write.3.html index 44c8e429427..7c89e153713 100644 --- a/archivers/libarchive/files/doc/html/archive_write.3.html +++ b/archivers/libarchive/files/doc/html/archive_write.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:04 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -273,8 +273,8 @@ limitations and provides a generic key/value attribute facility for vendor-defined extensions. One oversight in POSIX is the failure to provide a standard attribute for large device numbers. This library uses -’’SCHILY.devminor’’ and -’’SCHILY.devmajor’’ for device +‘‘SCHILY.devminor’’ and +‘‘SCHILY.devmajor’’ for device numbers that exceed the range supported by the backwards-compatible ustar header. These keys are compatible with Joerg Schilling’s <b>star</b> archiver. Other diff --git a/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html b/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html index 2ddd3a572ca..7358c49d83e 100644 --- a/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_blocksize.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:04 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -97,7 +97,7 @@ compression. The uncompressed data is always unpadded. The default is to pad the last block to the full block size (note that <b>archive_write_open_filename</b>() will set this based on the file type). Unlike the other -’’set’’ functions, this function can +‘‘set’’ functions, this function can be called after the archive is opened.</p> diff --git a/archivers/libarchive/files/doc/html/archive_write_data.3.html b/archivers/libarchive/files/doc/html/archive_write_data.3.html index a4542eb588d..deceae08bfe 100644 --- a/archivers/libarchive/files/doc/html/archive_write_data.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_data.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:07 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:04 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_disk.3.html b/archivers/libarchive/files/doc/html/archive_write_disk.3.html index 0e976b467c5..2b909b008c2 100644 --- a/archivers/libarchive/files/doc/html/archive_write_disk.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_disk.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -450,7 +450,7 @@ of the final object happen to match those specified in the entry.</p> <p style="margin-left:6%; margin-top: 1em">The -’’standard’’ user-id and group-id +‘‘standard’’ user-id and group-id lookup functions are not the defaults because getgrnam(3) and getpwnam(3) are sometimes too large for particular applications. The current design allows the application diff --git a/archivers/libarchive/files/doc/html/archive_write_filter.3.html b/archivers/libarchive/files/doc/html/archive_write_filter.3.html index c66133a664d..107fb367552 100644 --- a/archivers/libarchive/files/doc/html/archive_write_filter.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_filter.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html b/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html index bf63015f1e1..5980913ff57 100644 --- a/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_finish_entry.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_format.3.html b/archivers/libarchive/files/doc/html/archive_write_format.3.html index 09d6147e371..901a4e461b7 100644 --- a/archivers/libarchive/files/doc/html/archive_write_format.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_format.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_free.3.html b/archivers/libarchive/files/doc/html/archive_write_free.3.html index b65a085daf0..eabdd7c8b3a 100644 --- a/archivers/libarchive/files/doc/html/archive_write_free.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_free.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_header.3.html b/archivers/libarchive/files/doc/html/archive_write_header.3.html index 404075a9ef5..12b39631f17 100644 --- a/archivers/libarchive/files/doc/html/archive_write_header.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_header.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_new.3.html b/archivers/libarchive/files/doc/html/archive_write_new.3.html index 1cd3e06caec..8c459fa5aac 100644 --- a/archivers/libarchive/files/doc/html/archive_write_new.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_new.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:05 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/archive_write_open.3.html b/archivers/libarchive/files/doc/html/archive_write_open.3.html index 5c692848a94..3bd43f143d9 100644 --- a/archivers/libarchive/files/doc/html/archive_write_open.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_open.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:06 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -83,7 +83,8 @@ archive_write_open</b>()</p> archive, and prepare for writing entries. This is the most generic form of this function, which accepts pointers to three callback functions which will be invoked by the -compression layer to write the constructed archive.</p> +compression layer to write the constructed archive. This +does not alter the default archive padding.</p> <p style="margin-top: 1em"><b>archive_write_open_fd</b>()</p> @@ -115,7 +116,7 @@ require correct blocking.</p> <b>archive_write_open</b>() that accepts a filename. A NULL argument indicates that the output should be written to standard output; an argument of -’’-’’ will open a file with that +‘‘-’’ will open a file with that name. If you have not invoked <b>archive_write_set_bytes_in_last_block</b>(), then <b>archive_write_open_filename</b>() will adjust the @@ -138,12 +139,19 @@ block of memory that will receive the archive. The final updated after each write to reflect how much of the buffer is currently in use. You should be careful to ensure that this variable remains allocated until after the archive is -closed.</p> +closed. This function will disable padding unless you have +specifically set the block size.</p> <p style="margin-left:6%;">More information about the <i>struct archive</i> object and the overall design of the library can be found in the libarchive(3) overview.</p> +<p style="margin-left:6%; margin-top: 1em">Note that the +convenience forms above vary in how they block the output. +See archive_write_blocksize(3) if you need to control the +block size used for writes or the end-of-file padding +behavior.</p> + <p style="margin-top: 1em"><b>CLIENT CALLBACKS</b></p> <p style="margin-left:6%;">To use this library, you will @@ -220,9 +228,10 @@ and <b>archive_error_string</b>() functions.</p> <p style="margin-top: 1em"><b>SEE ALSO</b></p> <p style="margin-left:6%;">tar(1), libarchive(3), -archive_write(3), archive_write_filter(3), -archive_write_format(3), archive_write_new(3), -archive_write_set_options(3), cpio(5), mtree(5), tar(5)</p> +archive_write(3), archive_write_blocksize(3), +archive_write_filter(3), archive_write_format(3), +archive_write_new(3), archive_write_set_options(3), cpio(5), +mtree(5), tar(5)</p> <p style="margin-left:6%; margin-top: 1em">BSD February 2, 2012 BSD</p> diff --git a/archivers/libarchive/files/doc/html/archive_write_set_options.3.html b/archivers/libarchive/files/doc/html/archive_write_set_options.3.html index 50e1731c9d4..8ea118926ab 100644 --- a/archivers/libarchive/files/doc/html/archive_write_set_options.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_set_options.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:06 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -138,7 +138,7 @@ option with this name will ignore it.</p> <p style="margin-left:27%; margin-top: 1em">The option will be provided to every module with a value of -’’1’’.</p> +‘‘1’’.</p> <p><i>!option</i></p> @@ -175,7 +175,7 @@ cksum</b>, <b>device</b>, <b>flags</b>, <b>gid</b>, <p style="margin-left:27%;">Enable a particular keyword in the mtree output. Prefix with an exclamation mark to disable the corresponding keyword. The default is equivalent to -’’device, flags, gid, gname, link, mode, nlink, +‘‘device, flags, gid, gname, link, mode, nlink, size, time, type, uid, uname’’.</p> <p><b>all</b></p> @@ -483,8 +483,8 @@ compression on many files.</p> compression</b></p> <p style="margin-left:27%;">The value is either -’’store’’ or -’’deflate’’ to indicate how the +‘‘store’’ or +‘‘deflate’’ to indicate how the following entries should be compressed. Note that this setting is ignored for directories, symbolic links, and other special entries.</p> diff --git a/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html b/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html index 94e90b3ff52..9d490d58a8d 100644 --- a/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html +++ b/archivers/libarchive/files/doc/html/archive_write_set_passphrase.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:06 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/bsdcpio.1.html b/archivers/libarchive/files/doc/html/bsdcpio.1.html index 31c9378c55b..8c30ec9d2c3 100644 --- a/archivers/libarchive/files/doc/html/bsdcpio.1.html +++ b/archivers/libarchive/files/doc/html/bsdcpio.1.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:10 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:08 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -191,7 +191,7 @@ description.</p> <p style="margin-left:17%;">(i and p mode only) Disable security checks during extraction or copying. This allows extraction via symbolic links, absolute paths, and path -names containing ’..’ in the name.</p> +names containing ‘..’ in the name.</p> <p style="margin-top: 1em"><b>−J</b>, <b>−−xz</b></p> @@ -439,7 +439,7 @@ pattern:</p> <p style="margin-left:6%; margin-top: 1em">This example copies files from <i>src</i> to <i>dest</i> that are more than 2 days old and which contain the word -’’</p> +‘‘</p> <p>foobar ’’:</p> @@ -477,13 +477,13 @@ libarchive-formats(5), tar(5)</p> <p style="margin-left:6%;">There is no current POSIX standard for the cpio command; it appeared in ISO/IEC -9945-1:1996 (’’POSIX.1’’) but was +9945-1:1996 (‘‘POSIX.1’’) but was dropped from IEEE Std 1003.1-2001 -(’’POSIX.1’’).</p> +(‘‘POSIX.1’’).</p> <p style="margin-left:6%; margin-top: 1em">The cpio, ustar, and pax interchange file formats are defined by IEEE Std -1003.1-2001 (’’POSIX.1’’) for the +1003.1-2001 (‘‘POSIX.1’’) for the pax command.</p> <p style="margin-top: 1em"><b>HISTORY</b></p> @@ -492,7 +492,7 @@ pax command.</p> <b>find</b> utilities were written by Dick Haight while working in AT&T’s Unix Support Group. They first appeared in 1977 in PWB/UNIX 1.0, the -’’Programmer’s Work Bench’’ +‘‘Programmer’s Work Bench’’ system developed for use within AT&T. They were first released outside of AT&T as part of System III Unix in 1981. As a result, <b>cpio</b> actually predates <b>tar</b>, @@ -512,7 +512,7 @@ to transfer files between systems with dissimilar user and group numbering. Older cpio formats limit the user and group numbers to 16 or 18 bits, which is insufficient for modern systems. The cpio archive formats cannot support files over -4 gigabytes, except for the ’’odc’’ +4 gigabytes, except for the ‘‘odc’’ variant, which can support files up to 8 gigabytes.</p> <p style="margin-left:6%; margin-top: 1em">BSD diff --git a/archivers/libarchive/files/doc/html/bsdtar.1.html b/archivers/libarchive/files/doc/html/bsdtar.1.html index 92e798af951..8e9edc809a6 100644 --- a/archivers/libarchive/files/doc/html/bsdtar.1.html +++ b/archivers/libarchive/files/doc/html/bsdtar.1.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:10 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:08 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -54,7 +54,7 @@ and ISO 9660 cdrom images and can create tar, pax, cpio, ar, zip, 7-zip, and shar archives.</p> <p style="margin-left:6%; margin-top: 1em">The first -synopsis form shows a ’’bundled’’ +synopsis form shows a ‘‘bundled’’ option word. This usage is provided for compatibility with historical implementations. See COMPATIBILITY below for details.</p> @@ -123,7 +123,7 @@ modes.</p> <p style="margin-top: 1em"><b>@</b><i>archive</i></p> -<p style="margin-left:17%;">(c and r mode only) The +<p style="margin-left:17%;">(c and r modes only) The specified archive is opened and the entries in it will be appended to the current archive. As a simple example,</p> @@ -179,7 +179,7 @@ format,</p> <i>archive.tgz source.c source.h</i></p> <p style="margin-left:17%;">ignores the -’’-j’’ option, and creates a new +‘‘-j’’ option, and creates a new archive with restricted pax format and gzip compression,</p> <p style="margin-left:24%;"><b>tar −a −jcf</b> @@ -189,6 +189,17 @@ archive with restricted pax format and gzip compression,</p> suffix, creates a new archive with restricted pax format and bzip2 compression.</p> +<p style="margin-top: 1em"><b>−−acls</b></p> + +<p style="margin-left:17%; margin-top: 1em">(c, r, u, x +modes only) Archive or extract POSIX.1e or NFSv4 ACLs. This +is the reverse of <b>−−no-acls</b> and the +default behavior in c, r, and u modes (except Mac OS X) or +if <b>tar</b> is run in x mode as root. On Mac OS X this +option translates extended ACLs to NFSv4 ACLs. To store +extended ACLs the <b>−−mac-metadata</b> option +is preferred.</p> + <p style="margin-top: 1em"><b>−B</b>, <b>−−read-full-blocks</b></p> @@ -227,12 +238,6 @@ to the current directory after processing any file system objects to replace them, clear platform-specific file flags that might prevent removal.</p> - -<p style="margin-top: 1em"><b>−−disable-copyfile</b></p> - -<p style="margin-left:17%;">Mac OS X specific. Disable the -use of copyfile(3).</p> - <p style="margin-top: 1em"><b>−−exclude</b> <i>pattern</i></p> @@ -241,15 +246,23 @@ directories that match the specified pattern. Note that exclusions take precedence over patterns or filenames specified on the command line.</p> +<p style="margin-top: 1em"><b>−−fflags</b></p> + +<p style="margin-left:17%;">(c, r, u, x modes only) Archive +or extract file flags. This is the reverse of +<b>−−no-fflags</b> and the default behavior in +c, r, and u modes or if <b>tar</b> is run in x mode as +root.</p> + <p style="margin-top: 1em"><b>−−format</b> <i>format</i></p> <p style="margin-left:17%;">(c, r, u mode only) Use the specified format for the created archive. Supported formats -include ’’cpio’’, -’’pax’’, -’’shar’’, and -’’ustar’’. Other formats may also be +include ‘‘cpio’’, +‘‘pax’’, +‘‘shar’’, and +‘‘ustar’’. Other formats may also be supported; see libarchive-formats(5) for more information about currently-supported formats. In r and u modes, when extending an existing archive, the format specified here @@ -290,14 +303,14 @@ group database.</p> <p style="margin-top: 1em"><b>−H</b></p> -<p style="margin-left:17%; margin-top: 1em">(c and r mode +<p style="margin-left:17%; margin-top: 1em">(c and r modes only) Symbolic links named on the command line will be followed; the target of the link will be archived, not the link itself.</p> <p style="margin-top: 1em"><b>−h</b></p> -<p style="margin-left:17%; margin-top: 1em">(c and r mode +<p style="margin-left:17%; margin-top: 1em">(c and r modes only) Synonym for <b>−L</b>.</p> <p style="margin-top: 1em"><b>−I</b></p> @@ -312,9 +325,9 @@ only) Synonym for <b>−L</b>.</p> <p style="margin-top: 1em"><b>−−hfsCompression</b></p> -<p style="margin-left:17%;">(x mode only) Mac OS X -specific(v10.6 or later). Compress extracted regular files -with HFS+ compression.</p> +<p style="margin-left:17%;">(x mode only) Mac OS X specific +(v10.6 or later). Compress extracted regular files with HFS+ +compression.</p> <p style="margin-top: 1em"><b>−−ignore-zeros</b></p> @@ -340,7 +353,7 @@ when filtering archives. For example, the command</p> <p style="margin-left:17%;">creates a new archive <i>new.tar</i> containing only the entries from -<i>old.tgz</i> containing the string ’foo’.</p> +<i>old.tgz</i> containing the string ‘foo’.</p> <p style="margin-top: 1em"><b>−J</b>, <b>−−xz</b></p> @@ -379,7 +392,7 @@ the archive being extracted.</p> <p style="margin-top: 1em"><b>−L</b>, <b>−−dereference</b></p> -<p style="margin-left:17%;">(c and r mode only) All +<p style="margin-left:17%;">(c and r modes only) All symbolic links will be followed. Normally, symbolic links are archived as such. With this option, the target of the link will be archived instead.</p> @@ -427,6 +440,16 @@ list modes, this option is ignored.</p> modification time. By default, the modification time is set to the time stored in the archive.</p> + +<p style="margin-top: 1em"><b>−−mac-metadata</b></p> + +<p style="margin-left:17%;">(c, r, u and x mode only) Mac +OS X specific. Archive or extract extended ACLs and extended +attributes using copyfile(3) in AppleDouble format. This is +the reverse of <b>−−no-mac-metadata</b>. and the +default behavior in c, r, and u modes or if <b>tar</b> is +run in x mode as root.</p> + <p style="margin-top: 1em"><b>−n</b>, <b>−−norecurse</b>, <b>−−no-recursion</b></p> @@ -487,6 +510,37 @@ often used to read filenames output by the <b>−print0</b> option to find(1).</p> +<p style="margin-top: 1em"><b>−−no-acls</b></p> + +<p style="margin-left:17%;">(c, r, u, x modes only) Do not +archive or extract POSIX.1e or NFSv4 ACLs. This is the +reverse of <b>−−acls</b> and the default +behavior if <b>tar</b> is run as non-root in x mode (on Mac +OS X also in c, r and u modes).</p> + + +<p style="margin-top: 1em"><b>−−no-fflags</b></p> + +<p style="margin-left:17%;">(c, r, u, x modes only) Do not +archive or extract file flags. This is the reverse of +<b>−−fflags</b> and the default behavior if +<b>tar</b> is run as non-root in x mode.</p> + + +<p style="margin-top: 1em"><b>−−no-mac-metadata</b></p> + +<p style="margin-left:17%;">(x mode only) Mac OS X +specific. Do not archive or extract ACLs and extended +attributes using copyfile(3) in AppleDouble format. This is +the reverse of <b>−−mac-metadata</b>. and the +default behavior if <b>tar</b> is run as non-root in x +mode.</p> + +<p style="margin-top: 1em"><b>−n</b>, +<b>−−norecurse</b>, +<b>−−no-recursion</b></p> + + <p style="margin-top: 1em"><b>−−no-same-owner</b></p> <p style="margin-left:17%;">(x mode only) Do not extract @@ -501,7 +555,19 @@ owner and group IDs. This is the reverse of full permissions (SGID, SUID, sticky bit, ACLs, extended attributes or extended file flags). This is the reverse of <b>−p</b> and the default behavior if <b>tar</b> is -run as non-root.</p> +run as non-root and can be overridden by also specifying +<b>−−acls</b>, <b>−−fflags</b>, +<b>−−mac-metadata, −−same-owner</b>, +<b>−−same-permissions</b> and +<b>−−xattrs</b>.</p> + + +<p style="margin-top: 1em"><b>−−no-xattrs</b></p> + +<p style="margin-left:17%;">(c, r, u, x modes only) Do not +archive or extract extended attributes. This is the reverse +of <b>−−xattrs</b> and the default behavior if +<b>tar</b> is run as non-root in x mode.</p> <p style="margin-top: 1em"><b>−−numeric-owner</b></p> @@ -692,7 +758,7 @@ output. Supported keywords include: <b>cksum</b>, <b>nlink</b>, <b>rmd160</b>, <b>sha1</b>, <b>sha256</b>, <b>sha384</b>, <b>sha512</b>, <b>size</b>, <b>time</b>, <b>uid</b>, <b>uname</b>. The default is equivalent to: -’’device, flags, gid, gname, link, mode, nlink, +‘‘device, flags, gid, gname, link, mode, nlink, size, time, type, uid, uname’’.</p> <p><b>mtree:all</b></p> @@ -759,12 +825,16 @@ option suppresses these behaviors.</p> <p style="margin-left:17%;">(x mode only) Preserve file permissions. Attempt to restore the full permissions, -including owner, file modes, file flags and ACLs, if -available, for each item extracted from the archive. This is -the default, if <b>tar</b> is being run by root and can be -overridden by also specifying -<b>−−no-same-owner</b> and -<b>−−no-same-permissions</b>.</p> +including owner, file modes, ACLs, extended atributes and +extended file flags, if available, for each item extracted +from the archive. This is the default, if <b>tar</b> is +being run by root and can be overridden by also specifying +<b>−−no-acls</b>, +<b>−−no-fflags</b>, +<b>−−no-mac-metadata, +−−no-same-owner</b>, +<b>−−no-same-permissions</b> and +<b>−−no-xattrs</b>.</p> <p style="margin-top: 1em"><b>−−passphrase</b> <i>passphrase</i></p> @@ -852,18 +922,18 @@ checks.</p> read the list of names to be extracted from <i>filename</i>. In c mode, <b>tar</b> will read names to be archived from <i>filename</i>. The special name -’’-C’’ on a line by itself will +‘‘-C’’ on a line by itself will cause the current directory to be changed to the directory specified on the following line. Names are terminated by newlines unless <b>−−null</b> is specified. Note that <b>−−null</b> also disables the special -handling of lines containing ’’-C’’. +handling of lines containing ‘‘-C’’. Note: If you are generating lists of files using find(1), you probably want to use <b>−n</b> as well.</p> <p style="margin-top: 1em"><b>−−totals</b></p> -<p style="margin-left:17%;">(c, r, u mode only) After +<p style="margin-left:17%;">(c, r, u modes only) After archiving all files, print a summary to stderr.</p> <p style="margin-top: 1em"><b>−U</b>, @@ -937,6 +1007,14 @@ patterns from the specified file. See <b>−−exclude</b> for more information about the handling of exclusions.</p> +<p style="margin-top: 1em"><b>−−xattrs</b></p> + +<p style="margin-left:17%;">(c, r, u, x modes only) Archive +or extract extended attributes. This is the reverse of +<b>−−no-xattrs</b> and the default behavior in +c, r, and u modes or if <b>tar</b> is run in x mode as +root.</p> + <p style="margin-top: 1em"><b>−y</b></p> <p style="margin-left:17%; margin-top: 1em">(c mode only) @@ -1080,10 +1158,10 @@ $ tar -cvf output.tar @input.mtree</p> <b>−−newer</b> and <b>−−newer-mtime</b> switches accept a variety of common date and time specifications, including -’’12 Mar 2005 7:14:29pm’’, -’’2005-03-12 19:14’’, -’’5 minutes ago’’, and -’’19:14 PST May 1’’.</p> +‘‘12 Mar 2005 7:14:29pm’’, +‘‘2005-03-12 19:14’’, +‘‘5 minutes ago’’, and +‘‘19:14 PST May 1’’.</p> <p style="margin-left:6%; margin-top: 1em">The <b>−−options</b> argument can be used to control @@ -1213,9 +1291,9 @@ libarchive-formats(5), tar(5)</p> <p style="margin-left:6%;">There is no current POSIX standard for the tar command; it appeared in ISO/IEC -9945-1:1996 (’’POSIX.1’’) but was +9945-1:1996 (‘‘POSIX.1’’) but was dropped from IEEE Std 1003.1-2001 -(’’POSIX.1’’). The options supported +(‘‘POSIX.1’’). The options supported by this implementation were developed by surveying a number of existing tar implementations as well as the old POSIX specification for tar and the current POSIX specification @@ -1223,7 +1301,7 @@ for pax.</p> <p style="margin-left:6%; margin-top: 1em">The ustar and pax interchange file formats are defined by IEEE Std -1003.1-2001 (’’POSIX.1’’) for the +1003.1-2001 (‘‘POSIX.1’’) for the pax command.</p> <p style="margin-top: 1em"><b>HISTORY</b></p> @@ -1245,7 +1323,7 @@ library. It was first released with FreeBSD 5.4 in May, <p style="margin-top: 1em"><b>BUGS</b></p> <p style="margin-left:6%;">This program follows ISO/IEC -9945-1:1996 (’’POSIX.1’’) for the +9945-1:1996 (‘‘POSIX.1’’) for the definition of the <b>−l</b> option. Note that GNU tar prior to version 1.15 treated <b>−l</b> as a synonym for the <b>−−one-file-system</b> option.</p> @@ -1314,7 +1392,7 @@ incompatible ways that different archive formats store hardlink information.)</p> <p style="margin-left:6%; margin-top: 1em">BSD -September 16, 2014 BSD</p> +February 24, 2017 BSD</p> <hr> </body> </html> diff --git a/archivers/libarchive/files/doc/html/cpio.5.html b/archivers/libarchive/files/doc/html/cpio.5.html index a5321169270..af75de4974e 100644 --- a/archivers/libarchive/files/doc/html/cpio.5.html +++ b/archivers/libarchive/files/doc/html/cpio.5.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:08 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:06 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -46,7 +46,7 @@ those integers (binary, octal, or hexadecimal). The header is followed by the pathname of the entry (the length of the pathname is stored in the header) and any file data. The end of the archive is indicated by a special record with the -pathname ’’TRAILER!!!’’.</p> +pathname ‘‘TRAILER!!!’’.</p> <p style="margin-left:6%; margin-top: 1em"><b>PWB format</b> <br> @@ -239,11 +239,11 @@ included with each copy of the file.</p> <p style="margin-left:6%; margin-top: 1em"><b>Portable ASCII Format</b> <br> Version 2 of the Single UNIX Specification -(’’SUSv2’’) standardized an ASCII +(‘‘SUSv2’’) standardized an ASCII variant that is portable across all platforms. It is -commonly known as the ’’old +commonly known as the ‘‘old character’’ format or as the -’’odc’’ format. It stores the same +‘‘odc’’ format. It stores the same numeric fields as the old binary format, but represents them as 6-character or 11-character octal values.</p> @@ -302,7 +302,7 @@ the old binary format above.</p> <p style="margin-top: 1em"><i>magic</i></p> <p style="margin-left:17%; margin-top: 1em">The string -’’070701’’.</p> +‘‘070701’’.</p> <p style="margin-top: 1em"><i>check</i></p> @@ -326,7 +326,7 @@ archive.</p> Format</b> <br> The CRC format is identical to the new ASCII format described in the previous section except that the magic -field is set to ’’070702’’ and the +field is set to ‘‘070702’’ and the <i>check</i> field is set to the sum of all bytes in the file data. This sum is computed treating all bytes as unsigned values and using unsigned arithmetic. Only the @@ -355,7 +355,7 @@ XXX</p> <p style="margin-left:6%;">The <b>cpio</b> utility is no longer a part of POSIX or the Single Unix Standard. It last appeared in Version 2 of the Single UNIX Specification -(’’SUSv2’’). It has been supplanted +(‘‘SUSv2’’). It has been supplanted in subsequent standards by pax(1). The portable ASCII format is currently part of the specification for the pax(1) utility.</p> @@ -365,14 +365,14 @@ utility.</p> <p style="margin-left:6%;">The original cpio utility was written by Dick Haight while working in AT&T’s Unix Support Group. It appeared in 1977 as part of PWB/UNIX -1.0, the ’’Programmer’s Work +1.0, the ‘‘Programmer’s Work Bench’’ derived from Version 6 AT&T UNIX that was used internally at AT&T. Both the old binary and old character formats were in use by 1980, according to the System III source released by SCO under -their ’’Ancient Unix’’ license. The +their ‘‘Ancient Unix’’ license. The character format was adopted as part of IEEE Std 1003.1-1988 -(’’POSIX.1’’). XXX when did +(‘‘POSIX.1’’). XXX when did "newc" appear? Who invented it? When did HP come out with their variant? When did Sun introduce ACLs and extended attributes? XXX</p> @@ -380,7 +380,7 @@ extended attributes? XXX</p> <p style="margin-top: 1em"><b>BUGS</b></p> <p style="margin-left:6%;">The -’’CRC’’ format is mis-named, as it +‘‘CRC’’ format is mis-named, as it uses a simple checksum and not a cyclic redundancy check.</p> diff --git a/archivers/libarchive/files/doc/html/libarchive-formats.5.html b/archivers/libarchive/files/doc/html/libarchive-formats.5.html index 2298d6b446d..3c6df7fc96f 100644 --- a/archivers/libarchive/files/doc/html/libarchive-formats.5.html +++ b/archivers/libarchive/files/doc/html/libarchive-formats.5.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:09 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:06 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -34,7 +34,7 @@ library</p> <p style="margin-left:6%;">The libarchive(3) library reads and writes a variety of streaming archive formats. Generally speaking, all of these archive formats consist of a series -of ’’entries’’. Each entry stores a +of ‘‘entries’’. Each entry stores a single file system object, such as a file, directory, or symbolic link.</p> @@ -52,8 +52,8 @@ all supported formats.</p> <p style="margin-left:6%; margin-top: 1em"><b>Tar Formats</b> <br> The libarchive(3) library can read most tar archives. It can -write POSIX-standard ’’ustar’’ and -’’pax interchange’’ formats as well +write POSIX-standard ‘‘ustar’’ and +‘‘pax interchange’’ formats as well as v7 tar format and a subset of the legacy GNU tar format.</p> @@ -99,7 +99,7 @@ standard are in all lowercase; vendors are allowed to define custom keys by preceding them with the vendor name in all uppercase. When writing pax archives, libarchive uses many of the SCHILY keys defined by Joerg Schilling’s -’’star’’ archiver and a few +‘‘star’’ archiver and a few LIBARCHIVE keys. The libarchive library can read most of the SCHILY keys and most of the GNU keys introduced by GNU tar. It silently ignores any keywords that it does not @@ -236,23 +236,21 @@ numbers.</p> <p style="margin-top: 1em">Solaris extensions</p> <p style="margin-left:17%;">Libarchive recognizes ACL and -extended attribute records written by Solaris tar. -Currently, libarchive only has support for old-style ACLs; -the newer NFSv4 ACLs are recognized but discarded.</p> +extended attribute records written by Solaris tar.</p> <p style="margin-left:6%; margin-top: 1em">The first tar program appeared in Seventh Edition Unix in 1979. The first official standard for the tar file format was the -’’ustar’’ (Unix Standard Tar) format +‘‘ustar’’ (Unix Standard Tar) format defined by POSIX in 1988. POSIX.1-2001 extended the ustar -format to create the ’’pax +format to create the ‘‘pax interchange’’ format.</p> <p style="margin-left:6%; margin-top: 1em"><b>Cpio Formats</b> <br> The libarchive library can read a number of common cpio -variants and can write ’’odc’’ and -’’newc’’ format archives. A cpio +variants and can write ‘‘odc’’ and +‘‘newc’’ format archives. A cpio archive stores each entry as a fixed-size header followed by a variable-length filename and variable-length data. Unlike the tar format, the cpio format does only minimal padding of @@ -274,11 +272,11 @@ mtime, and 16-bit binary values for the other fields.</p> <p style="margin-left:17%; margin-top: 1em">The libarchive library can both read and write this POSIX-standard format, -which is officially known as the ’’cpio +which is officially known as the ‘‘cpio interchange format’’ or the -’’octet-oriented cpio archive +‘‘octet-oriented cpio archive format’’ and sometimes unofficially referred to -as the ’’old character format’’. +as the ‘‘old character format’’. This format stores the header contents as octal values in ASCII. It is standard, portable, and immune from byte-order confusion. File sizes and mtime are limited to 33 bits (8GB @@ -314,7 +312,7 @@ systems with dissimilar user numbering.</p> <p style="margin-left:6%; margin-top: 1em"><b>Shar Formats</b> <br> -A ’’shell archive’’ is a shell +A ‘‘shell archive’’ is a shell script that, when executed on a POSIX-compliant system, will recreate a collection of file system objects. The libarchive library can write two different kinds of shar archives:</p> @@ -381,7 +379,7 @@ variables.</p> format</b> <br> Libarchive can read and write zip format archives that have uncompressed entries and entries compressed with the -’’deflate’’ algorithm. Other zip +‘‘deflate’’ algorithm. Other zip compression algorithms are not supported. It can extract jar archives, archives that use Zip64 extensions and self-extracting zip archives. Libarchive can use either of @@ -471,7 +469,7 @@ Need more information</p> <p style="margin-left:6%; margin-top: 1em"><b>CAB</b> <br> Libarchive can read Microsoft Cabinet ( -’’CAB’’) format archives. TODO: Need +‘‘CAB’’) format archives. TODO: Need more information.</p> <p style="margin-left:6%; margin-top: 1em"><b>LHA</b> <br> @@ -486,7 +484,7 @@ the RARv3 format. Libarchive can also read self-extracting RAR archives.</p> <p style="margin-left:6%; margin-top: 1em"><b>Warc</b> <br> -Libarchive can read and write ’’web +Libarchive can read and write ‘‘web archives’’. TODO: Need more information</p> <p style="margin-left:6%; margin-top: 1em"><b>XAR</b> <br> @@ -500,7 +498,7 @@ shar(1), tar(1), zip(1), zlib(3), cpio(5), mtree(5), tar(5)</p> <p style="margin-left:6%; margin-top: 1em">BSD -March 18, 2012 BSD</p> +December 27, 2016 BSD</p> <hr> </body> </html> diff --git a/archivers/libarchive/files/doc/html/libarchive.3.html b/archivers/libarchive/files/doc/html/libarchive.3.html index a1286257b3a..bddaee823aa 100644 --- a/archivers/libarchive/files/doc/html/libarchive.3.html +++ b/archivers/libarchive/files/doc/html/libarchive.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:09 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:07 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -53,11 +53,11 @@ for:</p> <p><b>•</b></p> <p style="margin-left:12%;">most variants of the POSIX -’’ustar’’ format,</p> +‘‘ustar’’ format,</p> <p><b>•</b></p> -<p style="margin-left:12%;">the POSIX ’’pax +<p style="margin-left:12%;">the POSIX ‘‘pax interchange’’ format,</p> <p><b>•</b></p> @@ -117,11 +117,11 @@ format to use. The library can write</p> <p><b>•</b></p> <p style="margin-left:12%;">POSIX-standard -’’ustar’’ archives,</p> +‘‘ustar’’ archives,</p> <p><b>•</b></p> -<p style="margin-left:12%;">POSIX ’’pax +<p style="margin-left:12%;">POSIX ‘‘pax interchange format’’ archives,</p> <p><b>•</b></p> diff --git a/archivers/libarchive/files/doc/html/libarchive_changes.3.html b/archivers/libarchive/files/doc/html/libarchive_changes.3.html index 76b62329bec..7bf820d2c85 100644 --- a/archivers/libarchive/files/doc/html/libarchive_changes.3.html +++ b/archivers/libarchive/files/doc/html/libarchive_changes.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:09 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:07 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -57,7 +57,7 @@ can be easily converted to UTF-8.</p> <p style="margin-left:6%; margin-top: 1em">Libarchive3 uses the standard iconv library to convert between character sets -and is introducing the notion of a ’’default +and is introducing the notion of a ‘‘default character set for the archive’’. To support this, archive_entry objects can now be bound to a particular archive when they are created. The automatic character set diff --git a/archivers/libarchive/files/doc/html/libarchive_internals.3.html b/archivers/libarchive/files/doc/html/libarchive_internals.3.html index 4b9aa520053..8be18c9a099 100644 --- a/archivers/libarchive/files/doc/html/libarchive_internals.3.html +++ b/archivers/libarchive/files/doc/html/libarchive_internals.3.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:09 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:07 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> diff --git a/archivers/libarchive/files/doc/html/mtree.5.html b/archivers/libarchive/files/doc/html/mtree.5.html index 5f37ee9c789..f7d3fba68d6 100644 --- a/archivers/libarchive/files/doc/html/mtree.5.html +++ b/archivers/libarchive/files/doc/html/mtree.5.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:09 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:07 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -175,7 +175,7 @@ pathname of a file that holds the contents of this file.</p> <p style="margin-left:22%; margin-top: 1em">The file flags as a symbolic name. See chflags(1) for information on these names. If no flags are to be set the string -’’none’’ may be used to override the +‘‘none’’ may be used to override the current default.</p> <p style="margin-top: 1em"><b>gid</b></p> @@ -239,7 +239,7 @@ file hierarchy.</p> <p style="margin-top: 1em"><b>resdevice</b></p> <p style="margin-left:22%; margin-top: 1em">The -’’resident’’ device number of the +‘‘resident’’ device number of the file, e.g. the ID of the device that contains the file. Its format is the same as the one for <b>device</b>.</p> @@ -261,7 +261,7 @@ the file.</p> <p style="margin-top: 1em"><b>sha1</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 160-1 -(’’SHA-1’’) message digest of the +(‘‘SHA-1’’) message digest of the file.</p> <p style="margin-top: 1em"><b>sha1digest</b></p> @@ -272,7 +272,7 @@ file.</p> <p style="margin-top: 1em"><b>sha256</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 180-2 -(’’SHA-256’’) message digest of the +(‘‘SHA-256’’) message digest of the file.</p> <p style="margin-top: 1em"><b>sha256digest</b></p> @@ -283,7 +283,7 @@ file.</p> <p style="margin-top: 1em"><b>sha384</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 180-2 -(’’SHA-384’’) message digest of the +(‘‘SHA-384’’) message digest of the file.</p> <p style="margin-top: 1em"><b>sha384digest</b></p> @@ -294,7 +294,7 @@ file.</p> <p style="margin-top: 1em"><b>sha512</b></p> <p style="margin-left:22%; margin-top: 1em">The FIPS 180-2 -(’’SHA-512’’) message digest of the +(‘‘SHA-512’’) message digest of the file.</p> <p style="margin-top: 1em"><b>sha512digest</b></p> @@ -374,7 +374,7 @@ RIPEMD160 digests were added in FreeBSD 4.0, as new attacks have demonstrated weaknesses in MD5. The SHA-256 digest was added in FreeBSD 6.0. Support for file flags was added in FreeBSD 4.0, and mostly comes from NetBSD. -The ’’full’’ entry format was added +The ‘‘full’’ entry format was added by NetBSD.</p> <p style="margin-left:6%; margin-top: 1em">BSD diff --git a/archivers/libarchive/files/doc/html/tar.5.html b/archivers/libarchive/files/doc/html/tar.5.html index c30306db593..692a7993167 100644 --- a/archivers/libarchive/files/doc/html/tar.5.html +++ b/archivers/libarchive/files/doc/html/tar.5.html @@ -1,5 +1,5 @@ <!-- Creator : groff version 1.22.3 --> -<!-- CreationDate: Sun Jun 19 19:54:09 2016 --> +<!-- CreationDate: Sat Feb 25 11:22:08 2017 --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> @@ -50,14 +50,14 @@ entirely of zero bytes.</p> compatibility with tape drives that use fixed block sizes, programs that read or write tar files always read or write a fixed number of records with each I/O operation. These -’’blocks’’ are always a multiple of +‘‘blocks’’ are always a multiple of the record size. The maximum block size supported by early implementations was 10240 bytes or 20 records. This is still the default for most implementations although block sizes of 1MiB (2048 records) or larger are commonly used with modern high-speed tape drives. (Note: the terms -’’block’’ and -’’record’’ here are not entirely +‘‘block’’ and +‘‘record’’ here are not entirely standard; this document follows the convention established by John Gilmore in documenting <b>pdtar</b>.)</p> @@ -224,7 +224,7 @@ matches.</p> and conserve tape, a file with multiple links is only written to the archive the first time it is encountered. The next time it is encountered, the <i>linkflag</i> is set to -an ASCII ’1’ and the <i>linkname</i> field holds +an ASCII ‘1’ and the <i>linkname</i> field holds the first name under which this file appears. (Note that regular files have a null value in the <i>linkflag</i> field.)</p> @@ -239,14 +239,14 @@ size and mtime fields must end in a space; the checksum is terminated by a null and a space. Early implementations filled the numeric fields with leading spaces. This seems to have been common practice until the IEEE Std 1003.1-1988 -(’’POSIX.1’’) standard was released. +(‘‘POSIX.1’’) standard was released. For best portability, modern implementations should fill the numeric fields with leading zeros.</p> <p style="margin-left:6%; margin-top: 1em"><b>Pre-POSIX Archives</b> <br> An early draft of IEEE Std 1003.1-1988 -(’’POSIX.1’’) served as the basis +(‘‘POSIX.1’’) served as the basis for John Gilmore’s <b>pdtar</b> program and many system implementations from the late 1980s and early 1990s. These archives generally follow the POSIX ustar format @@ -255,7 +255,7 @@ described below with the following variations:</p> <p><b>•</b></p> <p style="margin-left:17%;">The magic value consists of the -five characters ’’ustar’’ followed +five characters ‘‘ustar’’ followed by a space. The version field contains a space character followed by a null.</p> @@ -273,12 +273,12 @@ archives.</p> <p style="margin-left:6%; margin-top: 1em"><b>POSIX ustar Archives</b> <br> -IEEE Std 1003.1-1988 (’’POSIX.1’’) +IEEE Std 1003.1-1988 (‘‘POSIX.1’’) defined a standard tar file format to be read and written by compliant implementations of tar(1). This format is often -called the ’’ustar’’ format, after +called the ‘‘ustar’’ format, after the magic value used in the header. (The name is an acronym -for ’’Unix Standard TAR’’.) It +for ‘‘Unix Standard TAR’’.) It extends the historic format with new fields:</p> <p style="margin-left:14%; margin-top: 1em">struct @@ -432,40 +432,40 @@ header_posix_ustar {</p> the earlier <i>linkflag</i> field with several new type values:</p> -<p>’’0’’</p> +<p>‘‘0’’</p> <p style="margin-left:27%; margin-top: 1em">Regular file. NUL should be treated as a synonym, for compatibility purposes.</p> -<p>’’1’’</p> +<p>‘‘1’’</p> <p style="margin-left:27%; margin-top: 1em">Hard link.</p> -<p>’’2’’</p> +<p>‘‘2’’</p> <p style="margin-left:27%; margin-top: 1em">Symbolic link.</p> -<p>’’3’’</p> +<p>‘‘3’’</p> <p style="margin-left:27%; margin-top: 1em">Character device node.</p> -<p>’’4’’</p> +<p>‘‘4’’</p> <p style="margin-left:27%; margin-top: 1em">Block device node.</p> -<p>’’5’’</p> +<p>‘‘5’’</p> <p style="margin-left:27%; margin-top: 1em">Directory.</p> -<p>’’6’’</p> +<p>‘‘6’’</p> <p style="margin-left:27%; margin-top: 1em">FIFO node.</p> -<p>’’7’’</p> +<p>‘‘7’’</p> <p style="margin-left:27%; margin-top: 1em">Reserved.</p> @@ -493,7 +493,7 @@ should be set to zero by writers and ignored by readers.</p> <p style="margin-top: 1em"><i>magic</i></p> <p style="margin-left:17%; margin-top: 1em">Contains the -magic value ’’ustar’’ followed by a +magic value ‘‘ustar’’ followed by a NUL byte to indicate that this is a POSIX standard archive. Full compliance requires the uname and gname fields be properly set.</p> @@ -501,7 +501,7 @@ properly set.</p> <p style="margin-top: 1em"><i>version</i></p> <p style="margin-left:17%;">Version. This should be -’’00’’ (two copies of the ASCII +‘‘00’’ (two copies of the ASCII digit zero) for POSIX standard archives.</p> <p style="margin-top: 1em"><i>uname</i>, <i>gname</i></p> @@ -589,14 +589,14 @@ implementation.</p> Interchange Format</b> <br> There are many attributes that cannot be portably stored in a POSIX ustar archive. IEEE Std 1003.1-2001 -(’’POSIX.1’’) defined a -’’pax interchange format’’ that uses +(‘‘POSIX.1’’) defined a +‘‘pax interchange format’’ that uses two new types of entries to hold text-formatted metadata that applies to following entries. Note that a pax interchange format archive is a ustar archive in every respect. The new data is stored in ustar-compatible archive -entries that use the ’’x’’ or -’’g’’ typeflag. In particular, older +entries that use the ‘‘x’’ or +‘‘g’’ typeflag. In particular, older implementations that do not fully support these extensions will extract the metadata into regular files, where the metadata can be examined as necessary.</p> @@ -641,11 +641,11 @@ including pathnames, user names, and group names. In some cases, it is not possible to translate local conventions into UTF-8. If this key is present and the value is the six-character ASCII string -’’BINARY’’, then all textual values +‘‘BINARY’’, then all textual values are assumed to be in a platform-dependent multi-byte encoding. Note that there are only two valid values for this -key: ’’BINARY’’ or -’’ISO-IR 10646 2000 UTF-8’’. +key: ‘‘BINARY’’ or +‘‘ISO-IR 10646 2000 UTF-8’’. No other values are permitted by the standard, and the latter value should generally not be used as it is the default when this key is not specified. In particular, this @@ -692,16 +692,17 @@ the historic 8GB limit.</p> by Joerg Schilling’s <b>star</b> implementation.</p> <p style="margin-top: 1em"><b>SCHILY.acl.access</b>, -<b>SCHILY.acl.default</b></p> - -<p style="margin-left:17%;">Stores the access and default -ACLs as textual strings in a format that is an extension of -the format specified by POSIX.1e draft 17. In particular, -each user or group access specification can include a fourth -colon-separated field with the numeric UID or GID. This -allows ACLs to be restored on systems that may not have -complete user or group information available (such as when -NIS/YP or LDAP services are temporarily unavailable).</p> +<b>SCHILY.acl.default, SCHILY.acl.ace</b></p> + +<p style="margin-left:17%;">Stores the access, default and +NFSv4 ACLs as textual strings in a format that is an +extension of the format specified by POSIX.1e draft 17. In +particular, each user or group access specification can +include an additional colon-separated field with the numeric +UID or GID. This allows ACLs to be restored on systems that +may not have complete user or group information available +(such as when NIS/YP or LDAP services are temporarily +unavailable).</p> <p style="margin-top: 1em"><b>SCHILY.devminor</b>, <b>SCHILY.devmajor</b></p> @@ -738,7 +739,7 @@ it.</p> <p style="margin-left:17%;">The time when the file was created. (This should not be confused with the POSIX -’’ctime’’ attribute, which refers to +‘‘ctime’’ attribute, which refers to the time when the file metadata was last changed.)</p> @@ -748,9 +749,9 @@ the time when the file metadata was last changed.)</p> POSIX.1e-style extended attributes using keys of this form. The <i>key</i> value is URL-encoded: All non-ASCII characters and the two special characters -’’=’’ and -’’%’’ are encoded as -’’%’’ followed by two uppercase +‘‘=’’ and +‘‘%’’ are encoded as +‘‘%’’ followed by two uppercase hexadecimal digits. The value of this key is the extended attribute value encoded in base 64. XXX Detail the base-64 format here XXX</p> @@ -1136,8 +1137,8 @@ equal to realsize.</p> They contained a list of files to be renamed or symlinked after extraction; this was originally used to support long names. The contents of this record are a text description of -the operations to be done, in the form ’’Rename -%s to %s\n’’ or ’’Symlink %s to +the operations to be done, in the form ‘‘Rename +%s to %s\n’’ or ‘‘Symlink %s to %s\n’’; in either case, both filenames are escaped using K&R C syntax. Due to security concerns, "N" records are now generally ignored when reading @@ -1146,13 +1147,13 @@ archives.</p> <p style="margin-top: 1em">S</p> <p style="margin-left:27%; margin-top: 1em">This is a -’’sparse’’ regular file. Sparse +‘‘sparse’’ regular file. Sparse files are stored as a series of fragments. The header contains a list of fragment offset/length pairs. If more than four such entries are required, the header is extended -as necessary with ’’extra’’ header +as necessary with ‘‘extra’’ header extensions (an older format that is no longer used), or -’’sparse’’ extensions.</p> +‘‘sparse’’ extensions.</p> <p style="margin-top: 1em">V</p> @@ -1163,7 +1164,7 @@ This entry should generally be ignored on extraction.</p> <p style="margin-top: 1em"><i>magic</i></p> <p style="margin-left:17%; margin-top: 1em">The magic field -holds the five characters ’’ustar’’ +holds the five characters ‘‘ustar’’ followed by a space. Note that POSIX ustar archives have a trailing null.</p> @@ -1172,7 +1173,7 @@ trailing null.</p> <p style="margin-left:17%;">The version field holds a space character followed by a null. Note that POSIX ustar archives use two copies of the ASCII digit -’’0’’.</p> +‘‘0’’.</p> <p style="margin-top: 1em"><i>atime</i>, <i>ctime</i></p> @@ -1199,7 +1200,7 @@ written to the file at appropriate offsets.</p> <p style="margin-top: 1em"><i>isextended</i></p> <p style="margin-left:17%;">If this is set to non-zero, the -header will be followed by additional ’’sparse +header will be followed by additional ‘‘sparse header’’ records. Each such record contains information about as many as 21 additional sparse blocks as shown here:</p> @@ -1288,16 +1289,16 @@ interchange format closely, using some <b>SCHILY</b> tags and introducing new keywords to store sparse file information. There have been three iterations of the sparse file support, referred to as -’’0.0’’, -’’0.1’’, and -’’1.0’’.</p> +‘‘0.0’’, +‘‘0.1’’, and +‘‘1.0’’.</p> <p style="margin-top: 1em"><b>GNU.sparse.numblocks</b>, <b>GNU.sparse.offset</b>, <b>GNU.sparse.numbytes</b>, <b>GNU.sparse.size</b></p> <p style="margin-left:17%;">The -’’0.0’’ format used an initial +‘‘0.0’’ format used an initial <b>GNU.sparse.numblocks</b> attribute to indicate the number of blocks in the file, a pair of <b>GNU.sparse.offset</b> and <b>GNU.sparse.numbytes</b> to indicate the offset and @@ -1312,7 +1313,7 @@ which is not officially permitted by the standards.</p> <p style="margin-top: 1em"><b>GNU.sparse.map</b></p> <p style="margin-left:17%;">The -’’0.1’’ format used a single +‘‘0.1’’ format used a single attribute that stored a comma-separated list of decimal numbers. Each pair of numbers indicated the offset and size, respectively, of a block of data. This does not work well if @@ -1325,7 +1326,7 @@ simply discard unrecognized attributes.</p> <b>GNU.sparse.realsize</b></p> <p style="margin-left:17%;">The -’’1.0’’ format stores the sparse +‘‘1.0’’ format stores the sparse block map in one or more 512-byte blocks prepended to the file data in the entry body. The pax attributes indicate the existence of this map (via the <b>GNU.sparse.major</b> and @@ -1341,7 +1342,7 @@ XXX More Details Needed XXX</p> <p style="margin-left:6%; margin-top: 1em">Solaris tar (beginning with SunOS XXX 5.7 ?? XXX) supports an -’’extended’’ format that is +‘‘extended’’ format that is fundamentally similar to pax interchange format, with the following differences:</p> @@ -1380,7 +1381,7 @@ Tar</b> <br> The tar distributed with Apple’s Mac OS X stores most regular files as two separate files in the tar archive. The two files have the same name except that the first one has -’’._’’ prepended to the last path +‘‘._’’ prepended to the last path element. This special file stores an AppleDouble-encoded binary blob with additional metadata about the second file, including ACL, extended attributes, and resources. To @@ -1388,7 +1389,7 @@ recreate the original file on disk, each separate file can be extracted and the Mac OS X <b>copyfile</b>() function can be used to unpack the separate metadata file and apply it to th regular file. Conversely, the same function provides a -’’pack’’ option to encode the +‘‘pack’’ option to encode the extended metadata from a file into a separate file whose contents can then be put into a tar archive.</p> @@ -1526,11 +1527,11 @@ interchange format per-file extensions.</p> <p style="margin-left:6%;">The <b>tar</b> utility is no longer a part of POSIX or the Single Unix Standard. It last appeared in Version 2 of the Single UNIX Specification -(’’SUSv2’’). It has been supplanted +(‘‘SUSv2’’). It has been supplanted in subsequent standards by pax(1). The ustar format is currently part of the specification for the pax(1) utility. The pax interchange file format is new with IEEE Std -1003.1-2001 (’’POSIX.1’’).</p> +1003.1-2001 (‘‘POSIX.1’’).</p> <p style="margin-top: 1em"><b>HISTORY</b></p> @@ -1552,7 +1553,7 @@ and <b>bsdtar</b> project by Tim Kientzle <kientzle@FreeBSD.org>.</p> <p style="margin-left:6%; margin-top: 1em">BSD -December 23, 2011 BSD</p> +December 27, 2016 BSD</p> <hr> </body> </html> |