2 .\" Copyright (c) 1992 Keith Muller.
3 .\" Copyright (c) 1992, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" This code is derived from software contributed to Berkeley by
7 .\" Keith Muller of the University of California, San Diego.
9 .\" Redistribution and use in source and binary forms, with or without
10 .\" modification, are permitted provided that the following conditions
12 .\" 1. Redistributions of source code must retain the above copyright
13 .\" notice, this list of conditions and the following disclaimer.
14 .\" 2. Redistributions in binary form must reproduce the above copyright
15 .\" notice, this list of conditions and the following disclaimer in the
16 .\" documentation and/or other materials provided with the distribution.
17 .\" 3. Neither the name of the University nor the names of its contributors
18 .\" may be used to endorse or promote products derived from this software
19 .\" without specific prior written permission.
21 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
22 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
25 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
26 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
27 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
28 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
30 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
38 .Nd read and write file archives and copy directory hierarchies
106 .Op Fl b Ar blocksize
147 .Op Fl diklntuvDHLOPXYZ
178 utility will read, write, and list the members of an archive file,
179 and will copy directory hierarchies.
180 These operations are independent of the specific archive format,
181 and support a wide variety of different archive formats.
182 A list of supported archive formats can be found under the description of the
190 options specifies which of the following functional modes
193 .Em list , read , write ,
201 a table of contents of the members of the archive file read from
203 whose pathnames match the specified
205 The table of contents contains one filename per line
206 and is written using single line buffering.
209 Extract the members of the archive file read from the
211 with pathnames matching the specified
213 The archive format and blocking is automatically determined on input.
214 When an extracted file is a directory, the entire file hierarchy
215 rooted at that directory is extracted.
216 All extracted files are created relative to the current file hierarchy.
217 The setting of ownership, access and modification times, and file mode of
218 the extracted files are discussed in more detail under the
223 Write an archive containing the
227 using the specified archive format.
230 operands are specified, a list of files to copy with one per line is read from
234 operand is also a directory, the entire file hierarchy rooted
235 at that directory will be included.
240 operands to the destination
244 operands are specified, a list of files to copy with one per line is read from
249 operand is also a directory the entire file
250 hierarchy rooted at that directory will be included.
253 is as if the copied files were written to an archive file and then
254 subsequently extracted, except that there may be hard links between
255 the original and the copied files (see the
262 must not be one of the
264 operands or a member of a file hierarchy rooted at one of the
269 under these conditions is unpredictable.
272 While processing a damaged archive during a
278 will attempt to recover from media defects and will search through the archive
279 to locate and process the largest number of archive members possible (see the
281 option for more details on error handling).
285 operand specifies a destination directory pathname.
288 operand does not exist, or it is not writable by the user,
289 or it is not of type directory,
291 will exit with a non-zero exit status.
295 operand is used to select one or more pathnames of archive members.
296 Archive members are selected using the pattern matching notation described
301 operand is not supplied, all members of the archive will be selected.
304 matches a directory, the entire file hierarchy rooted at that directory will
308 operand does not select at least one archive member,
312 operands in a diagnostic message to
314 and then exit with a non-zero exit status.
318 operand specifies the pathname of a file to be copied or archived.
321 operand does not select at least one archive member,
325 operand pathnames in a diagnostic message to
327 and then exit with a non-zero exit status.
329 The following options are supported:
332 Read an archive file from
334 and extract the specified
336 If any intermediate directories are needed in order to extract an archive
337 member, these directories will be created as if
339 was called with the bitwise inclusive
342 .Dv S_IRWXU , S_IRWXG ,
345 as the mode argument.
346 When the selected archive format supports the specification of linked
347 files and these files cannot be linked while the archive is being extracted,
349 will write a diagnostic message to
351 and exit with a non-zero exit status at the completion of operation.
355 in the specified archive format.
358 operands are specified,
360 is read for a list of pathnames with one per line without any leading or
366 to the end of an archive that was previously written.
367 If an archive format is not specified with a
369 option, the format currently being used in the archive will be selected.
370 Any attempt to append to an archive in a format different from the
371 format already used in the archive will cause
374 with a non-zero exit status.
375 The blocking size used in the archive volume where writing starts
376 will continue to be used for the remainder of that archive volume.
379 Many storage devices are not able to support the operations necessary
380 to perform an append operation.
381 Any attempt to append to an archive stored on such a device may damage the
382 archive or have other unpredictable results.
383 Tape drives in particular are more likely to not support an append operation.
384 An archive stored in a regular file system file or on a disk device will
385 usually support an append operation.
386 .It Fl b Ar blocksize
390 block the output at a positive decimal integer number of
391 bytes per write to the archive file.
394 must be a multiple of 512 bytes with a maximum of 64512 bytes.
397 larger than 32256 bytes violates the
399 standard and will not be portable to all systems.
406 to specify multiplication by 1024 (1K) or 512, respectively.
411 to indicate a product.
412 A specific archive device may impose additional restrictions on the size
413 of blocking it will support.
414 When blocking is not specified, the default
416 is dependent on the specific archive format being used (see the
420 Match all file or archive members
422 those specified by the
428 Cause files of type directory being copied or archived, or archive members of
429 type directory being extracted, to match only the directory file or archive
430 member and not the file hierarchy rooted at the directory.
434 as the pathname of the input or output archive, overriding the default
444 A single archive may span multiple files and different archive devices.
447 will prompt for the pathname of the file or device of the next volume in the
450 Interactively rename files or archive members.
451 For each archive member matching a
453 operand or each file matching a
459 giving the name of the file, its file mode and its modification time.
462 utility will then read a line from
464 If this line is blank, the file or archive member is skipped.
465 If this line consists of a single period, the
466 file or archive member is processed with no modification to its name.
467 Otherwise, its name is replaced with the contents of the line.
470 utility will immediately exit with a non-zero exit status if
472 is encountered when reading a response or if
474 cannot be opened for reading and writing.
476 Do not overwrite existing files.
484 hard links are made between the source and destination file hierarchies
487 Select the first archive member that matches each
490 No more than one archive member is matched for each
492 When members of type directory are matched, the file hierarchy rooted at that
493 directory is also matched (unless
497 Information to modify the algorithm for extracting or writing archive files
498 which is specific to the archive format specified by
505 Specify one or more file characteristic options (privileges).
508 option-argument is a string specifying file characteristics to be retained or
509 discarded on extraction.
510 The string consists of the specification characters
514 Multiple characteristics can be concatenated within the same string
517 options can be specified.
518 The meaning of the specification characters are as follows:
521 Do not preserve file access times.
522 By default, file access times are preserved whenever possible.
524 .Sq Preserve everything ,
525 the user ID, group ID, file mode bits,
526 file access time, and file modification time.
527 This is intended to be used by
529 someone with all the appropriate privileges, in order to preserve all
530 aspects of the files as they are recorded in the archive.
533 flag is the sum of the
539 Do not preserve file modification times.
540 By default, file modification times are preserved whenever possible.
542 Preserve the user ID and group ID.
546 This intended to be used by a
548 with regular privileges who wants to preserve all aspects of the file other
550 The file times are preserved by default, but two other flags are offered to
551 disable this and use the time of extraction instead.
554 In the preceding list,
556 indicates that an attribute stored in the archive is given to the
557 extracted file, subject to the permissions of the invoking
559 Otherwise the attribute of the extracted file is determined as
560 part of the normal file creation action.
565 specification character is specified, or the user ID and group ID are not
566 preserved for any reason,
574 bits of the file mode.
575 If the preservation of any of these items fails for any reason,
577 will write a diagnostic message to
579 Failure to preserve these items will affect the final exit status,
580 but will not cause the extracted file to be deleted.
581 If the file characteristic letters in any of the string option-arguments are
582 duplicated or conflict with each other, the one(s) given last will take
586 is specified, file modification times are still preserved.
590 are not understood by
598 Modify the file or archive member names specified by the
602 operands according to the substitution expression
604 using the syntax of the
606 utility regular expressions.
607 The format of these regular expressions are:
612 is a basic regular expression and
614 can contain an ampersand (&), \\n (where n is a digit) back-references,
615 or subexpression matching.
618 string may also contain
621 Any non-null character can be used as a delimiter (/ is shown here).
624 expressions can be specified.
625 The expressions are applied in the order they are specified on the
626 command line, terminating with the first successful substitution.
627 The optional trailing
629 continues to apply the substitution expression to the pathname substring
630 which starts with the first character following the end of the last successful
632 The first unsuccessful substitution stops the operation of the
635 The optional trailing
637 will cause the final result of a successful substitution to be written to
639 in the following format:
640 .Dl <original pathname> >> <new pathname>
641 File or archive member names that substitute to the empty string
642 are not selected and will be skipped.
644 Reset the access times of any file or directory read or accessed by
646 to be the same as they were before being read or accessed by
649 Ignore files that are older (having a less recent file modification time)
650 than a pre-existing file or archive member with the same name.
653 an archive member with the same name as a file in the file system will be
654 extracted if the archive member is newer than the file.
657 a file system member with the same name as an archive member will be
658 written to the archive if it is newer than the archive member.
661 the file in the destination hierarchy is replaced by the file in the source
662 hierarchy or by a link to the file in the source hierarchy if the file in
663 the source hierarchy is newer.
667 operation, produce a verbose table of contents using the format of the
672 For pathnames representing a hard link to a previous member of the archive,
673 the output has the format:
674 .Dl <ls -l listing> == <link name>
675 For pathnames representing a symbolic link, the output has the format:
676 .Dl <ls -l listing> => <link name>
677 Where <ls -l listing> is the output format specified by the
679 utility when used with the
682 Otherwise for all the other operational modes
686 pathnames are written and flushed to
690 as soon as processing begins on that file or
694 is not buffered, and is written only after the file has been read or written.
696 Specify the output archive format, with the default format being
700 utility currently supports the following formats:
701 .Bl -tag -width "sv4cpio"
703 The extended cpio interchange format specified in the
706 The default blocksize for this format is 5120 bytes.
707 Inode and device information about a file (used for detecting file hard links
708 by this format) which may be truncated by this format is detected by
712 The old binary cpio format.
713 The default blocksize for this format is 5120 bytes.
714 This format is not very portable and should not be used when other formats
716 Inode and device information about a file (used for detecting file hard links
717 by this format) which may be truncated by this format is detected by
721 The System V release 4 cpio.
722 The default blocksize for this format is 5120 bytes.
723 Inode and device information about a file (used for detecting file hard links
724 by this format) which may be truncated by this format is detected by
728 The System V release 4 cpio with file crc checksums.
729 The default blocksize for this format is 5120 bytes.
730 Inode and device information about a file (used for detecting file hard links
731 by this format) which may be truncated by this format is detected by
737 tar format as found in
739 The default blocksize for this format is 10240 bytes.
740 Pathnames stored by this format must be 100 characters or less in length.
744 .Em hard links , soft links ,
747 will be archived (other file system types are not supported).
748 For backwards compatibility with even older tar formats, a
750 option can be used when writing an archive to omit the storage of directories.
751 This option takes the form:
752 .Dl Fl o Cm write_opt=nodir
754 The extended tar interchange format specified in the
757 The default blocksize for this format is 10240 bytes.
758 Pathnames stored by this format must be 255 characters or less in length.
759 The directory part may be at most 155 characters and each path component
760 must be less than 100 characters.
765 utility will detect and report any file that it is unable to store or extract
766 as the result of any specific archive format restrictions.
767 The individual archive formats may impose additional restrictions on use.
768 Typical archive format restrictions include (but are not limited to):
769 file pathname length, file size, link pathname length and the type of the file.
773 to compress (decompress) the archive while writing (reading).
777 Limit the number of bytes written to a single archive volume to
786 to specify multiplication by 1048576 (1M), 1024 (1K) or 512, respectively.
789 limits can be separated by
791 to indicate a product.
793 Note that the specified size is for the uncompressed pax image itself.
796 option is also used, the resulting file may contain fewer
798 according to the compressibility of the archive contents.
800 .Xr zip 1 Pq Pa ports/archivers/zip
801 if compressed volumes of predictable size are required.
804 Only use this option when writing an archive to a device which supports
805 an end of file read condition based on last (or largest) write offset
806 (such as a regular file or a tape drive).
807 The use of this option with a floppy or hard disk is not recommended.
809 This option is the same as the
811 option, except that the file inode change time is checked instead of the
812 file modification time.
813 The file inode change time can be used to select files whose inode information
814 (e.g., uid, gid, etc.) is newer than a copy of the file in the destination
817 Limit the number of consecutive read faults while trying to read a flawed
823 will attempt to recover from an archive read error and will
824 continue processing starting with the next file stored in the archive.
829 to stop operation after the first read error is detected on an archive volume.
836 to attempt to recover from read errors forever.
839 is a small positive number of retries.
842 Using this option with
844 should be used with extreme caution as
846 may get stuck in an infinite loop on a very badly flawed archive.
848 Select a file based on its
850 name, or when starting with a
853 A '\\' can be used to escape the
857 options may be supplied and checking stops with the first match.
859 Follow only command line symbolic links while performing a physical file
862 Follow all symbolic links to perform a logical file system traversal.
864 Force the archive to be one volume.
865 If a volume ends prematurely,
867 will not prompt for a new volume.
868 This option can be useful for
869 automated tasks where error recovery cannot be performed by a human.
871 Do not follow symbolic links, perform a physical file system traversal.
872 This is the default mode.
873 .It Fl T Ar [from_date][,to_date][/[c][m]]
874 Allow files to be selected based on a file modification or inode change
875 time falling within a specified time range of
879 (the dates are inclusive).
882 is supplied, all files with a modification or inode change time
883 equal to or younger are selected.
886 is supplied, all files with a modification or inode change time
887 equal to or older will be selected.
892 only files with a modification or inode change time of exactly that
893 time will be selected.
901 mode, the optional trailing field
903 can be used to determine which file time (inode change, file modification or
904 both) are used in the comparison.
905 If neither is specified, the default is to use file modification time only.
908 specifies the comparison of file modification time (the time when
909 the file was last written).
912 specifies the comparison of inode change time (the time when the file
913 inode was last changed; e.g., a change of owner, group, mode, etc).
918 are both specified, then the modification and inode change times are
920 The inode change time comparison is useful in selecting files whose
921 attributes were recently changed or selecting files which were recently
922 created and had their modification time reset to an older time (as what
923 happens when a file is extracted from an archive and the modification time
925 Time comparisons using both file times is useful when
927 is used to create a time based incremental archive (only files that were
928 changed during a specified time range will be archived).
930 A time range is made up of six different fields and each field must contain two
934 .Dl [[[[[cc]yy]mm]dd]HH]MM[.SS]
938 is the first two digits of the year (the century),
940 is the last two digits of the year,
943 is the month (from 01 to 12),
945 is the day of the month (from 01 to 31),
947 is the hour of the day (from 00 to 23),
949 is the minute (from 00 to 59),
952 is the seconds (from 00 to 59).
955 is required, while the other fields are optional and must be added in the
957 .Ar HH , dd , mm , yy , cc .
960 field may be added independently of the other fields.
961 Time ranges are relative to the current time, so
963 would select all files with a modification or inode change time
964 of 12:34 PM today or later.
967 time range can be supplied and checking stops with the first match.
969 Select a file based on its
971 name, or when starting with a
974 A '\\' can be used to escape the
978 options may be supplied and checking stops with the first match.
980 When traversing the file hierarchy specified by a pathname,
981 do not descend into directories that have a different device ID.
984 field as described in
986 for more information about device ID's.
988 This option is the same as the
990 option, except that the inode change time is checked using the
991 pathname created after all the file name modifications have completed.
993 This option is the same as the
995 option, except that the modification time is checked using the
996 pathname created after all the file name modifications have completed.
999 The options that operate on the names of files or archive members
1013 interact as follows.
1015 When extracting files during a
1017 operation, archive members are
1019 based only on the user specified pattern operands as modified by the
1032 options will modify in that order, the names of these selected files.
1037 options will be applied based on the final pathname.
1040 option will write the names resulting from these modifications.
1042 When archiving files during a
1044 operation, or copying files during a
1046 operation, archive members are
1048 based only on the user specified pathnames as modified by the
1058 option only applies during a copy operation).
1063 options will modify in that order, the names of these selected files.
1070 options will be applied based on the final pathname.
1073 option will write the names resulting from these modifications.
1075 When one or both of the
1079 options are specified along with the
1081 option, a file is not considered selected unless it is newer
1082 than the file to which it is compared.
1086 utility will exit with one of the following values:
1089 All files were processed successfully.
1095 .Dl "pax -w -f /dev/sa0 ."
1096 copies the contents of the current directory to the device
1100 .Dl pax -v -f filename
1101 gives the verbose table of contents for an archive stored in
1104 The following commands:
1107 .Dl pax -rw .\ /tmp/to
1108 will copy the entire
1110 directory hierarchy to
1114 .Dl pax -r -s ',^//*usr//*,,' -f a.pax
1117 with all files rooted in ``/usr'' into the archive extracted relative to the
1121 .Dl pax -rw -i .\ dest_dir
1122 can be used to interactively select the files to copy from the current
1127 .Dl pax -r -pe -U root -G bin -f a.pax
1128 will extract all files from the archive
1134 and will preserve all file permissions.
1137 .Dl pax -r -w -v -Y -Z home /backup
1138 will update (and list) only those files in the destination directory
1140 which are older (less recent inode change or file modification times) than
1141 files with the same name found in the source file tree
1146 cannot create a file or a link when reading an archive or cannot
1147 find a file when writing an archive, or cannot preserve the user ID,
1148 group ID, or file mode when the
1150 option is specified, a diagnostic message is written to
1152 and a non-zero exit status will be returned, but processing will continue.
1153 In the case where pax cannot create a link to a file,
1155 will not create a second copy of the file.
1157 If the extraction of a file from an archive is prematurely terminated by
1160 may have only partially extracted a file the user wanted.
1161 Additionally, the file modes of extracted files and directories
1162 may have incorrect file bits, and the modification and access times may be
1165 If the creation of an archive is prematurely terminated by a signal or error,
1167 may have only partially created the archive which may violate the specific
1168 archive format specification.
1173 detects a file is about to overwrite itself, the file is not copied,
1174 a diagnostic message is written to
1178 completes it will exit with a non-zero exit status.
1185 utility is a superset of the
1207 and the flawed archive handling during
1211 operations are extensions to the
1221 at the University of California, San Diego
1225 utility does not recognize multibyte characters.
1229 are not preserved by
1233 has a list of utilities that are unaware of flags.