summaryrefslogtreecommitdiff
path: root/archivers/libarchive/files/doc/text/cpio.5.txt
diff options
context:
space:
mode:
Diffstat (limited to 'archivers/libarchive/files/doc/text/cpio.5.txt')
-rw-r--r--archivers/libarchive/files/doc/text/cpio.5.txt66
1 files changed, 33 insertions, 33 deletions
diff --git a/archivers/libarchive/files/doc/text/cpio.5.txt b/archivers/libarchive/files/doc/text/cpio.5.txt
index 5ece811eda3..f4802cf2584 100644
--- a/archivers/libarchive/files/doc/text/cpio.5.txt
+++ b/archivers/libarchive/files/doc/text/cpio.5.txt
@@ -1,4 +1,4 @@
-CPIO(5) FreeBSD File Formats Manual CPIO(5)
+CPIO(5) NetBSD File Formats Manual CPIO(5)
NAME
cpio -- format of cpio archive files
@@ -11,7 +11,7 @@ DESCRIPTION
General Format
Each file system object in a cpio archive comprises a header record with
basic numeric metadata followed by the full pathname of the entry and the
- file data. The header record stores a series of integer values that gen-
+ file data. The header record stores a series of integer values that gen-
erally follow the fields in struct stat. (See stat(2) for details.) The
variants differ primarily in how they store those integers (binary,
octal, or hexadecimal). The header is followed by the pathname of the
@@ -98,7 +98,7 @@ DESCRIPTION
to four gigabyte file sizes. See mtime above for a description
of the storage of four-byte integers.
- The pathname immediately follows the fixed header. If the namesize is
+ The pathname immediately follows the fixed header. If the namesize is
odd, an additional NUL byte is added after the pathname. The file data
is then appended, padded with NUL bytes to an even length.
@@ -113,21 +113,21 @@ DESCRIPTION
them as 6-character or 11-character octal values.
struct cpio_odc_header {
- char c_magic[6];
- char c_dev[6];
- char c_ino[6];
- char c_mode[6];
- char c_uid[6];
- char c_gid[6];
- char c_nlink[6];
- char c_rdev[6];
- char c_mtime[11];
- char c_namesize[6];
- char c_filesize[11];
+ char c_magic[6];
+ char c_dev[6];
+ char c_ino[6];
+ char c_mode[6];
+ char c_uid[6];
+ char c_gid[6];
+ char c_nlink[6];
+ char c_rdev[6];
+ char c_mtime[11];
+ char c_namesize[6];
+ char c_filesize[11];
};
The fields are identical to those in the old binary format. The name and
- file body follow the fixed header. Unlike the old binary format, there
+ file body follow the fixed header. Unlike the old binary format, there
is no additional padding after the pathname or file contents. If the
files being archived are themselves entirely ASCII, then the resulting
archive will be entirely ASCII, except for the NUL byte that terminates
@@ -139,20 +139,20 @@ DESCRIPTION
bers.
struct cpio_newc_header {
- char c_magic[6];
- char c_ino[8];
- char c_mode[8];
- char c_uid[8];
- char c_gid[8];
- char c_nlink[8];
- char c_mtime[8];
- char c_filesize[8];
- char c_devmajor[8];
- char c_devminor[8];
- char c_rdevmajor[8];
- char c_rdevminor[8];
- char c_namesize[8];
- char c_check[8];
+ char c_magic[6];
+ char c_ino[8];
+ char c_mode[8];
+ char c_uid[8];
+ char c_gid[8];
+ char c_nlink[8];
+ char c_mtime[8];
+ char c_filesize[8];
+ char c_devmajor[8];
+ char c_devminor[8];
+ char c_rdevmajor[8];
+ char c_rdevminor[8];
+ char c_namesize[8];
+ char c_check[8];
};
Except as specified below, the fields here match those specified for the
@@ -195,10 +195,10 @@ BUGS
cyclic redundancy check.
The old binary format is limited to 16 bits for user id, group id,
- device, and inode numbers. It is limited to 4 gigabyte file sizes.
+ device, and inode numbers. It is limited to 4 gigabyte file sizes.
The old ASCII format is limited to 18 bits for the user id, group id,
- device, and inode numbers. It is limited to 8 gigabyte file sizes.
+ device, and inode numbers. It is limited to 8 gigabyte file sizes.
The new ASCII format is limited to 4 gigabyte file sizes.
@@ -223,7 +223,7 @@ STANDARDS
HISTORY
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,
+ AT&T's Unix Support Group. It appeared in 1977 as part of PWB/UNIX 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
@@ -232,4 +232,4 @@ HISTORY
appear? Who invented it? When did HP come out with their variant? When
did Sun introduce ACLs and extended attributes? XXX
-FreeBSD 8.0 October 5, 2007 FreeBSD 8.0
+NetBSD 5.0 October 5, 2007 NetBSD 5.0