diff options
Diffstat (limited to 'archivers/libarchive/files/doc/man')
| -rw-r--r-- | archivers/libarchive/files/doc/man/cpio.5 | 10 | ||||
| -rw-r--r-- | archivers/libarchive/files/doc/man/tar.5 | 12 |
2 files changed, 11 insertions, 11 deletions
diff --git a/archivers/libarchive/files/doc/man/cpio.5 b/archivers/libarchive/files/doc/man/cpio.5 index a77d96b3b25..e389f71e119 100644 --- a/archivers/libarchive/files/doc/man/cpio.5 +++ b/archivers/libarchive/files/doc/man/cpio.5 @@ -137,7 +137,7 @@ Each of the two 16 bit values are stored in machine-native byte order. .TP \fInamesize\fP The number of bytes in the pathname that follows the header. -This count includes the trailing NULL byte. +This count includes the trailing NUL byte. .TP \fIfilesize\fP The size of the file. @@ -149,8 +149,8 @@ above for a description of the storage of four-byte integers. The pathname immediately follows the fixed header. If the \fBnamesize\fP -is odd, an additional NULL byte is added after the pathname. -The file data is then appended, padded with NULL +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. Hardlinked files are not given special treatment; the full file contents are included with each copy of the @@ -187,7 +187,7 @@ 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 -NULL byte that terminates the name field. +NUL byte that terminates the name field. .SS New ASCII Format The "new" ASCII format uses 8-byte hexadecimal fields for all numbers and separates device numbers into separate fields @@ -220,7 +220,7 @@ The string \fIcheck\fP This field is always set to zero by writers and ignored by readers. See the next section for more details. -The pathname is followed by NULL bytes so that the total size +The pathname is followed by NUL bytes so that the total size of the fixed header plus pathname is a multiple of four. Likewise, the file data is padded to a multiple of four bytes. Note that this format supports only 4 gigabyte files (unlike the diff --git a/archivers/libarchive/files/doc/man/tar.5 b/archivers/libarchive/files/doc/man/tar.5 index 3b4414fc4a0..4901e2c6c68 100644 --- a/archivers/libarchive/files/doc/man/tar.5 +++ b/archivers/libarchive/files/doc/man/tar.5 @@ -193,7 +193,7 @@ field with several new type values: .TP ``0'' Regular file. -NULL should be treated as a synonym, for compatibility purposes. +NUL should be treated as a synonym, for compatibility purposes. .TP ``1'' Hard link. @@ -238,7 +238,7 @@ by readers. \fImagic\fP Contains the magic value ``ustar'' -followed by a NULL byte to indicate that this is a POSIX standard archive. +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. .TP \fIversion\fP @@ -267,7 +267,7 @@ the prefix value and a \fI/\fP character to the regular name field to obtain the full pathname. Note that all unused bytes must be set to -.BR NULL. +.BR NUL. Field termination is specified slightly differently by POSIX than by previous implementations. The @@ -276,14 +276,14 @@ The and \fIgname\fP fields must have a trailing -.BR NULL. +.BR NUL. The \fIpathname\fP, \fIlinkname\fP, and \fIprefix\fP fields must have a trailing -.BR NULL +.BR NUL unless they fill the entire field. (In particular, it is possible to store a 256-character pathname if it happens to have a @@ -291,7 +291,7 @@ happens to have a as the 156th character.) POSIX requires numeric fields to be zero-padded in the front, and allows them to be terminated with either space or -.BR NULL +.BR NUL characters. Currently, most tar implementations comply with the ustar format, occasionally extending it by adding new fields to the |