diff options
Diffstat (limited to 'archivers/libarchive/files/doc/text/libarchive-formats.5.txt')
| -rw-r--r-- | archivers/libarchive/files/doc/text/libarchive-formats.5.txt | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/archivers/libarchive/files/doc/text/libarchive-formats.5.txt b/archivers/libarchive/files/doc/text/libarchive-formats.5.txt index 62df74916e9..dabfe5687b2 100644 --- a/archivers/libarchive/files/doc/text/libarchive-formats.5.txt +++ b/archivers/libarchive/files/doc/text/libarchive-formats.5.txt @@ -1,4 +1,4 @@ -libarchive-formats(5) NetBSD File Formats Manual libarchive-formats(5) +libarchive-formats(5) FreeBSD File Formats Manual libarchive-formats(5) NAME libarchive-formats -- archive formats supported by the libarchive library @@ -41,15 +41,15 @@ DESCRIPTION interchange format archives. Pax interchange format archives are an extension of the older ustar format that adds a separate entry with additional attributes stored as key/value pairs immediately - before each regular entry. The presence of these additional + before each regular entry. The presence of these additional entries is the only difference between pax interchange format and the older ustar format. The extended attributes are of unlimited length and are stored as UTF-8 Unicode strings. Keywords defined in the 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 + uppercase. When writing pax archives, libarchive uses many of the SCHILY keys defined by Joerg Schilling's ``star'' archiver - and a few LIBARCHIVE keys. The libarchive library can read most + 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 under- stand. @@ -70,16 +70,16 @@ DESCRIPTION ustar The libarchive library can both read and write this format. This format has the following limitations: - Device major and minor numbers are limited to 21 bits. Nodes + o Device major and minor numbers are limited to 21 bits. Nodes with larger numbers will not be added to the archive. - Path names in the archive are limited to 255 bytes. (Shorter + o Path names in the archive are limited to 255 bytes. (Shorter if there is no / character in exactly the right place.) - Symbolic links and hard links are stored in the archive with + o Symbolic links and hard links are stored in the archive with the name of the referenced file. This name is limited to 100 bytes. - Extended attributes, file flags, and other extended security + o Extended attributes, file flags, and other extended security information cannot be stored. - Archive entries are limited to 8 gigabytes in size. + o Archive entries are limited to 8 gigabytes in size. Note that the pax interchange format has none of these restric- tions. @@ -93,7 +93,7 @@ DESCRIPTION Libarchive allows these fields to be written without terminator characters. This extends the allowable range; in particular, ustar archives with this extension can support entries up to 64 - gigabytes in size. Libarchive also recognizes base-256 values in + gigabytes in size. Libarchive also recognizes base-256 values in most numeric fields. This essentially removes all limitations on file size, modification time, and device numbers. @@ -118,7 +118,7 @@ DESCRIPTION binary values of varying byte order and length. binary The libarchive library transparently reads both big-endian and - little-endian variants of the original binary cpio format. This + little-endian variants of the original binary cpio format. This format used 32-bit binary values for file size and mtime, and 16-bit binary values for the other fields. @@ -143,7 +143,7 @@ DESCRIPTION of AT&T in 1981. This makes cpio older than tar, although cpio was not included in Version 7 AT&T Unix. As a result, the tar command became much better known in universities and research groups that used Version - 7. The combination of the find and cpio utilities provided very precise + 7. The combination of the find and cpio utilities provided very precise control over file selection. Unfortunately, the format has many limita- tions that make it unsuitable for widespread use. Only the POSIX format permits files over 4GB, and its 18-bit limit for most other fields makes @@ -167,7 +167,7 @@ DESCRIPTION shardump This format is similar to shar but encodes files using uuencode(1) so that the result will be a plain text file regard- - less of the file contents. It also includes additional shell + less of the file contents. It also includes additional shell commands that attempt to reproduce as many file attributes as possible, including owner, mode, and flags. The additional com- mands used to restore file attributes make shardump archives less @@ -204,7 +204,7 @@ DESCRIPTION primarily in their handling of filenames longer than 15 characters: the GNU/SVR4 variant writes a filename table at the beginning of the archive; the BSD format stores each long filename in an extension area adjacent to - the entry. Libarchive can read both extensions, including archives that + the entry. Libarchive can read both extensions, including archives that may include both types of long filenames. Programs using libarchive can write GNU/SVR4 format if they provide a filename table to be written into the archive before any of the entries. Any entries whose names are not @@ -216,12 +216,12 @@ DESCRIPTION Libarchive can read and write files in mtree(5) format. This format is not a true archive format, but rather a textual description of a file hierarchy in which each line specifies the name of a file and provides - specific metadata about that file. Libarchive can read all of the key- + specific metadata about that file. Libarchive can read all of the key- words supported by both the NetBSD and FreeBSD versions of mtree(1), although many of the keywords cannot currently be stored in an archive_entry object. When writing, libarchive supports use of the archive_write_set_options(3) interface to specify which keywords should - be included in the output. If libarchive was compiled with access to + be included in the output. If libarchive was compiled with access to suitable cryptographic libraries (such as the OpenSSL libraries), it can compute hash entries such as sha512 or md5 from file data being written to the mtree writer. @@ -238,4 +238,4 @@ SEE ALSO ar(1), cpio(1), mkisofs(1), shar(1), tar(1), zip(1), zlib(3), cpio(5), mtree(5), tar(5) -NetBSD 5.0 December 27, 2009 NetBSD 5.0 +FreeBSD 9.0 December 27, 2009 FreeBSD 9.0 |