xref: /freebsd/bin/pax/pax.1 (revision 68e7a217f8019b955f87547f218e95ab237597af)
1.\" Copyright (c) 1992 Keith Muller.
2.\" Copyright (c) 1992, 1993
3.\"	The Regents of the University of California.  All rights reserved.
4.\"
5.\" This code is derived from software contributed to Berkeley by
6.\" Keith Muller of the University of California, San Diego.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions
10.\" are met:
11.\" 1. Redistributions of source code must retain the above copyright
12.\"    notice, this list of conditions and the following disclaimer.
13.\" 2. Redistributions in binary form must reproduce the above copyright
14.\"    notice, this list of conditions and the following disclaimer in the
15.\"    documentation and/or other materials provided with the distribution.
16.\" 3. All advertising materials mentioning features or use of this software
17.\"    must display the following acknowledgement:
18.\"	This product includes software developed by the University of
19.\"	California, Berkeley and its contributors.
20.\" 4. Neither the name of the University nor the names of its contributors
21.\"    may be used to endorse or promote products derived from this software
22.\"    without specific prior written permission.
23.\"
24.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
26.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
27.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
28.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
30.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34.\" SUCH DAMAGE.
35.\"
36.\"	@(#)pax.1	8.4 (Berkeley) 4/18/94
37.\" $FreeBSD$
38.\"
39.Dd April 18, 1994
40.Dt PAX 1
41.Os
42.Sh NAME
43.Nm pax
44.Nd read and write file archives and copy directory hierarchies
45.Sh SYNOPSIS
46.Nm
47.Op Fl cdnvz
48.Bk -words
49.Op Fl f Ar archive
50.Ek
51.Bk -words
52.Op Fl s Ar replstr
53.Ar ...\&
54.Ek
55.Bk -words
56.Op Fl U Ar user
57.Ar ...\&
58.Ek
59.Bk -words
60.Op Fl G Ar group
61.Ar ...\&
62.Ek
63.Bk -words
64.Oo
65.Fl T
66.Op Ar from_date
67.Op Ar ,to_date
68.Oc
69.Ar ...\&
70.Ek
71.Op Ar pattern ...\&
72.Nm
73.Fl r
74.Op Fl cdiknuvzDYZ
75.Bk -words
76.Op Fl f Ar archive
77.Ek
78.Bk -words
79.Op Fl o Ar options
80.Ar ...\&
81.Ek
82.Bk -words
83.Op Fl p Ar string
84.Ar ...\&
85.Ek
86.Bk -words
87.Op Fl s Ar replstr
88.Ar ...\&
89.Ek
90.Op Fl E Ar limit
91.Bk -words
92.Op Fl U Ar user
93.Ar ...\&
94.Ek
95.Bk -words
96.Op Fl G Ar group
97.Ar ...\&
98.Ek
99.Bk -words
100.Oo
101.Fl T
102.Op Ar from_date
103.Op Ar ,to_date
104.Oc
105.Ar ...\&
106.Ek
107.Op Ar pattern ...\&
108.Nm
109.Fl w
110.Op Fl dituvzHLPX
111.Bk -words
112.Op Fl b Ar blocksize
113.Ek
114.Oo
115.Op Fl a
116.Op Fl f Ar archive
117.Oc
118.Bk -words
119.Op Fl x Ar format
120.Ek
121.Bk -words
122.Op Fl s Ar replstr
123.Ar ...\&
124.Ek
125.Bk -words
126.Op Fl o Ar options
127.Ar ...\&
128.Ek
129.Bk -words
130.Op Fl U Ar user
131.Ar ...\&
132.Ek
133.Bk -words
134.Op Fl G Ar group
135.Ar ...\&
136.Ek
137.Bk -words
138.Op Fl B Ar bytes
139.Ek
140.Bk -words
141.Oo
142.Fl T
143.Op Ar from_date
144.Op Ar ,to_date
145.Op Ar /[c][m]
146.Oc
147.Ar ...\&
148.Ek
149.Op Ar
150.Nm
151.Fl r
152.Fl w
153.Op Fl diklntuvDHLPXYZ
154.Bk -words
155.Op Fl p Ar string
156.Ar ...\&
157.Ek
158.Bk -words
159.Op Fl s Ar replstr
160.Ar ...\&
161.Ek
162.Bk -words
163.Op Fl U Ar user
164.Ar ...\&
165.Ek
166.Bk -words
167.Op Fl G Ar group
168.Ar ...\&
169.Ek
170.Bk -words
171.Oo
172.Fl T
173.Op Ar from_date
174.Op Ar ,to_date
175.Op Ar /[c][m]
176.Oc
177.Ar ...\&
178.Ek
179.Op Ar
180.Ar directory
181.Sh DESCRIPTION
182The
183.Nm
184utility will read, write, and list the members of an archive file,
185and will copy directory hierarchies.
186These operations are independent of the specific archive format,
187and support a wide variety of different archive formats.
188A list of supported archive formats can be found under the description of the
189.Fl x
190option.
191.Pp
192The presence of the
193.Fl r
194and the
195.Fl w
196options specifies which of the following functional modes
197.Nm
198will operate under:
199.Em list , read , write ,
200and
201.Em copy .
202.Bl -tag -width 6n
203.It <none>
204.Em List .
205Write to
206.Dv standard output
207a table of contents of the members of the archive file read from
208.Dv standard input ,
209whose pathnames match the specified
210.Ar patterns .
211The table of contents contains one filename per line
212and is written using single line buffering.
213.It Fl r
214.Em Read .
215Extract the members of the archive file read from the
216.Dv standard input ,
217with pathnames matching the specified
218.Ar patterns .
219The archive format and blocking is automatically determined on input.
220When an extracted file is a directory, the entire file hierarchy
221rooted at that directory is extracted.
222All extracted files are created relative to the current file hierarchy.
223The setting of ownership, access and modification times, and file mode of
224the extracted files are discussed in more detail under the
225.Fl p
226option.
227.It Fl w
228.Em Write .
229Write an archive containing the
230.Ar file
231operands to
232.Dv standard output
233using the specified archive format.
234When no
235.Ar file
236operands are specified, a list of files to copy with one per line is read from
237.Dv standard input .
238When a
239.Ar file
240operand is also a directory, the entire file hierarchy rooted
241at that directory will be included.
242.It Fl r Fl w
243.Em Copy .
244Copy the
245.Ar file
246operands to the destination
247.Ar directory .
248When no
249.Ar file
250operands are specified, a list of files to copy with one per line is read from
251the
252.Dv standard input .
253When a
254.Ar file
255operand is also a directory the entire file
256hierarchy rooted at that directory will be included.
257The effect of the
258.Em copy
259is as if the copied files were written to an archive file and then
260subsequently extracted, except that there may be hard links between
261the original and the copied files (see the
262.Fl l
263option below).
264.Pp
265.Em Warning :
266The destination
267.Ar directory
268must not be one of the
269.Ar file
270operands or a member of a file hierarchy rooted at one of the
271.Ar file
272operands.
273The result of a
274.Em copy
275under these conditions is unpredictable.
276.El
277.Pp
278While processing a damaged archive during a
279.Em read
280or
281.Em list
282operation,
283.Nm
284will attempt to recover from media defects and will search through the archive
285to locate and process the largest number of archive members possible (see the
286.Fl E
287option for more details on error handling).
288.Sh OPERANDS
289The
290.Ar directory
291operand specifies a destination directory pathname.
292If the
293.Ar directory
294operand does not exist, or it is not writable by the user,
295or it is not of type directory,
296.Nm
297will exit with a non-zero exit status.
298.Pp
299The
300.Ar pattern
301operand is used to select one or more pathnames of archive members.
302Archive members are selected using the pattern matching notation described
303by
304.Xr fnmatch 3 .
305When the
306.Ar pattern
307operand is not supplied, all members of the archive will be selected.
308When a
309.Ar pattern
310matches a directory, the entire file hierarchy rooted at that directory will
311be selected.
312When a
313.Ar pattern
314operand does not select at least one archive member,
315.Nm
316will write these
317.Ar pattern
318operands in a diagnostic message to
319.Dv standard error
320and then exit with a non-zero exit status.
321.Pp
322The
323.Ar file
324operand specifies the pathname of a file to be copied or archived.
325When a
326.Ar file
327operand does not select at least one archive member,
328.Nm
329will write these
330.Ar file
331operand pathnames in a diagnostic message to
332.Dv standard error
333and then exit with a non-zero exit status.
334.Sh OPTIONS
335The following options are supported:
336.Bl -tag -width 4n
337.It Fl r
338Read an archive file from
339.Dv standard input
340and extract the specified
341.Ar files .
342If any intermediate directories are needed in order to extract an archive
343member, these directories will be created as if
344.Xr mkdir 2
345was called with the bitwise inclusive
346.Dv OR
347of
348.Dv S_IRWXU , S_IRWXG ,
349and
350.Dv S_IRWXO
351as the mode argument.
352When the selected archive format supports the specification of linked
353files and these files cannot be linked while the archive is being extracted,
354.Nm
355will write a diagnostic message to
356.Dv standard error
357and exit with a non-zero exit status at the completion of operation.
358.It Fl w
359Write files to the
360.Dv standard output
361in the specified archive format.
362When no
363.Ar file
364operands are specified,
365.Dv standard input
366is read for a list of pathnames with one per line without any leading or
367trailing
368.Aq blanks .
369.It Fl a
370Append
371.Ar files
372to the end of an archive that was previously written.
373If an archive format is not specified with a
374.Fl x
375option, the format currently being used in the archive will be selected.
376Any attempt to append to an archive in a format different from the
377format already used in the archive will cause
378.Nm
379to exit immediately
380with a non-zero exit status.
381The blocking size used in the archive volume where writing starts
382will continue to be used for the remainder of that archive volume.
383.Pp
384.Em Warning :
385Many storage devices are not able to support the operations necessary
386to perform an append operation.
387Any attempt to append to an archive stored on such a device may damage the
388archive or have other unpredictable results.
389Tape drives in particular are more likely to not support an append operation.
390An archive stored in a regular filesystem file or on a disk device will
391usually support an append operation.
392.It Fl b Ar blocksize
393When
394.Em writing
395an archive,
396block the output at a positive decimal integer number of
397bytes per write to the archive file.
398The
399.Ar blocksize
400must be a multiple of 512 bytes with a maximum of 64512 bytes.
401Archives larger than 32256 bytes violate the
402.Tn POSIX
403standard and will not be portable to all systems.
404A
405.Ar blocksize
406can end with
407.Li k
408or
409.Li b
410to specify multiplication by 1024 (1K) or 512, respectively.
411A pair of
412.Ar blocksizes
413can be separated by
414.Li x
415to indicate a product.
416A specific archive device may impose additional restrictions on the size
417of blocking it will support.
418When blocking is not specified, the default
419.Ar blocksize
420is dependent on the specific archive format being used (see the
421.Fl x
422option).
423.It Fl c
424Match all file or archive members
425.Em except
426those specified by the
427.Ar pattern
428and
429.Ar file
430operands.
431.It Fl d
432Cause files of type directory being copied or archived, or archive members of
433type directory being extracted, to match only the directory file or archive
434member and not the file hierarchy rooted at the directory.
435.It Fl f Ar archive
436Specify
437.Ar archive
438as the pathname of the input or output archive, overriding the default
439.Dv standard input
440(for
441.Em list
442and
443.Em read )
444or
445.Dv standard output
446(for
447.Em write ) .
448A single archive may span multiple files and different archive devices.
449When required,
450.Nm
451will prompt for the pathname of the file or device of the next volume in the
452archive.
453.It Fl i
454Interactively rename files or archive members.
455For each archive member matching a
456.Ar pattern
457operand or each file matching a
458.Ar file
459operand,
460.Nm
461will prompt to
462.Pa /dev/tty
463giving the name of the file, its file mode and its modification time.
464The
465.Nm
466utility will then read a line from
467.Pa /dev/tty .
468If this line is blank, the file or archive member is skipped.
469If this line consists of a single period, the
470file or archive member is processed with no modification to its name.
471Otherwise, its name is replaced with the contents of the line.
472The
473.Nm
474utility will immediately exit with a non-zero exit status if
475.Dv <EOF>
476is encountered when reading a response or if
477.Pa /dev/tty
478cannot be opened for reading and writing.
479.It Fl k
480Do not overwrite existing files.
481.It Fl l
482Link files.
483(The letter ell).
484In the
485.Em copy
486mode
487.Pq Fl r w ,
488hard links are made between the source and destination file hierarchies
489whenever possible.
490.It Fl n
491Select the first archive member that matches each
492.Ar pattern
493operand.
494No more than one archive member is matched for each
495.Ar pattern .
496When members of type directory are matched, the file hierarchy rooted at that
497directory is also matched (unless
498.Fl d
499is also specified).
500.It Fl o Ar options
501Information to modify the algorithm for extracting or writing archive files
502which is specific to the archive format specified by
503.Fl x .
504In general,
505.Ar options
506take the form:
507.Cm name=value
508.It Fl p Ar string
509Specify one or more file characteristic options (privileges).
510The
511.Ar string
512option-argument is a string specifying file characteristics to be retained or
513discarded on extraction.
514The string consists of the specification characters
515.Cm a , e , m , o ,
516and
517.Cm p .
518Multiple characteristics can be concatenated within the same string
519and multiple
520.Fl p
521options can be specified.
522The meaning of the specification characters are as follows:
523.Bl -tag -width 2n
524.It Cm a
525Do not preserve file access times.
526By default, file access times are preserved whenever possible.
527.It Cm e
528.Sq Preserve everything ,
529the user ID, group ID, file mode bits,
530file access time, and file modification time.
531This is intended to be used by
532.Em root ,
533someone with all the appropriate privileges, in order to preserve all
534aspects of the files as they are recorded in the archive.
535The
536.Cm e
537flag is the sum of the
538.Cm o
539and
540.Cm p
541flags.
542.It Cm m
543Do not preserve file modification times.
544By default, file modification times are preserved whenever possible.
545.It Cm o
546Preserve the user ID and group ID.
547.It Cm p
548.Sq Preserve
549the file mode bits.
550This intended to be used by a
551.Em user
552with regular privileges who wants to preserve all aspects of the file other
553than the ownership.
554The file times are preserved by default, but two other flags are offered to
555disable this and use the time of extraction instead.
556.El
557.Pp
558In the preceding list,
559.Sq preserve
560indicates that an attribute stored in the archive is given to the
561extracted file, subject to the permissions of the invoking
562process.
563Otherwise the attribute of the extracted file is determined as
564part of the normal file creation action.
565If neither the
566.Cm e
567nor the
568.Cm o
569specification character is specified, or the user ID and group ID are not
570preserved for any reason,
571.Nm
572will not set the
573.Dv S_ISUID
574.Em ( setuid )
575and
576.Dv S_ISGID
577.Em ( setgid )
578bits of the file mode.
579If the preservation of any of these items fails for any reason,
580.Nm
581will write a diagnostic message to
582.Dv standard error .
583Failure to preserve these items will affect the final exit status,
584but will not cause the extracted file to be deleted.
585If the file characteristic letters in any of the string option-arguments are
586duplicated or conflict with each other, the one(s) given last will take
587precedence.
588For example, if
589.Dl Fl p Ar eme
590is specified, file modification times are still preserved.
591.It Fl s Ar replstr
592Modify the file or archive member names specified by the
593.Ar pattern
594or
595.Ar file
596operands according to the substitution expression
597.Ar replstr ,
598using the syntax of the
599.Xr ed 1
600utility regular expressions.
601The format of these regular expressions are:
602.Dl /old/new/[gp]
603As in
604.Xr ed 1 ,
605.Cm old
606is a basic regular expression and
607.Cm new
608can contain an ampersand (&), \\n (where n is a digit) back-references,
609or subexpression matching.
610The
611.Cm old
612string may also contain
613.Dv <newline>
614characters.
615Any non-null character can be used as a delimiter (/ is shown here).
616Multiple
617.Fl s
618expressions can be specified.
619The expressions are applied in the order they are specified on the
620command line, terminating with the first successful substitution.
621The optional trailing
622.Cm g
623continues to apply the substitution expression to the pathname substring
624which starts with the first character following the end of the last successful
625substitution.
626The first unsuccessful substitution stops the operation of the
627.Cm g
628option.
629The optional trailing
630.Cm p
631will cause the final result of a successful substitution to be written to
632.Dv standard error
633in the following format:
634.Dl <original pathname> >> <new pathname>
635File or archive member names that substitute to the empty string
636are not selected and will be skipped.
637.It Fl t
638Reset the access times of any file or directory read or accessed by
639.Nm
640to be the same as they were before being read or accessed by
641.Nm .
642.It Fl u
643Ignore files that are older (having a less recent file modification time)
644than a pre-existing file or archive member with the same name.
645During
646.Em read ,
647an archive member with the same name as a file in the filesystem will be
648extracted if the archive member is newer than the file.
649During
650.Em write ,
651a filesystem member with the same name as an archive member will be
652written to the archive if it is newer than the archive member.
653During
654.Em copy ,
655the file in the destination hierarchy is replaced by the file in the source
656hierarchy or by a link to the file in the source hierarchy if the file in
657the source hierarchy is newer.
658.It Fl v
659During a
660.Em list
661operation, produce a verbose table of contents using the format of the
662.Xr ls 1
663utility with the
664.Fl l
665option.
666For pathnames representing a hard link to a previous member of the archive,
667the output has the format:
668.Dl <ls -l listing> == <link name>
669For pathnames representing a symbolic link, the output has the format:
670.Dl <ls -l listing> => <link name>
671Where <ls -l listing> is the output format specified by the
672.Xr ls 1
673utility when used with the
674.Fl l
675option.
676Otherwise for all the other operational modes
677.Em ( read , write ,
678and
679.Em copy ) ,
680pathnames are written and flushed to
681.Dv standard error
682without a trailing
683.Dv <newline>
684as soon as processing begins on that file or
685archive member.
686The trailing
687.Dv <newline> ,
688is not buffered, and is written only after the file has been read or written.
689.It Fl x Ar format
690Specify the output archive format, with the default format being
691.Ar ustar .
692The
693.Nm
694utility currently supports the following formats:
695.Bl -tag -width "sv4cpio"
696.It Ar cpio
697The extended cpio interchange format specified in the
698.St -p1003.2
699standard.
700The default blocksize for this format is 5120 bytes.
701Inode and device information about a file (used for detecting file hard links
702by this format) which may be truncated by this format is detected by
703.Nm
704and is repaired.
705.It Ar bcpio
706The old binary cpio format.
707The default blocksize for this format is 5120 bytes.
708This format is not very portable and should not be used when other formats
709are available.
710Inode and device information about a file (used for detecting file hard links
711by this format) which may be truncated by this format is detected by
712.Nm
713and is repaired.
714.It Ar sv4cpio
715The System V release 4 cpio.
716The default blocksize for this format is 5120 bytes.
717Inode and device information about a file (used for detecting file hard links
718by this format) which may be truncated by this format is detected by
719.Nm
720and is repaired.
721.It Ar sv4crc
722The System V release 4 cpio with file crc checksums.
723The default blocksize for this format is 5120 bytes.
724Inode and device information about a file (used for detecting file hard links
725by this format) which may be truncated by this format is detected by
726.Nm
727and is repaired.
728.It Ar tar
729The old
730.Bx
731tar format as found in
732.Bx 4.3 .
733The default blocksize for this format is 10240 bytes.
734Pathnames stored by this format must be 100 characters or less in length.
735Only
736.Em regular
737files,
738.Em  hard links , soft links ,
739and
740.Em  directories
741will be archived (other filesystem types are not supported).
742For backwards compatibility with even older tar formats, a
743.Fl o
744option can be used when writing an archive to omit the storage of directories.
745This option takes the form:
746.Dl Fl o Cm write_opt=nodir
747.It Ar ustar
748The extended tar interchange format specified in the
749.St -p1003.2
750standard.
751The default blocksize for this format is 10240 bytes.
752Pathnames stored by this format must be 250 characters or less in length.
753.El
754.Pp
755The
756.Nm
757utility will detect and report any file that it is unable to store or extract
758as the result of any specific archive format restrictions.
759The individual archive formats may impose additional restrictions on use.
760Typical archive format restrictions include (but are not limited to):
761file pathname length, file size, link pathname length and the type of the file.
762.It Fl z
763Use
764.Xr gzip 1
765to compress (decompress) the archive while writing (reading).
766Incompatible with
767.Fl a .
768.It Fl B Ar bytes
769Limit the number of bytes written to a single archive volume to
770.Ar bytes .
771The
772.Ar bytes
773limit can end with
774.Li m ,
775.Li k ,
776or
777.Li b
778to specify multiplication by 1048576 (1M), 1024 (1K) or 512, respectively.
779A pair of
780.Ar bytes
781limits can be separated by
782.Li x
783to indicate a product.
784.Pp
785.Em Warning :
786Only use this option when writing an archive to a device which supports
787an end of file read condition based on last (or largest) write offset
788(such as a regular file or a tape drive).
789The use of this option with a floppy or hard disk is not recommended.
790.It Fl D
791This option is the same as the
792.Fl u
793option, except that the file inode change time is checked instead of the
794file modification time.
795The file inode change time can be used to select files whose inode information
796(e.g. uid, gid, etc.) is newer than a copy of the file in the destination
797.Ar directory .
798.It Fl E Ar limit
799Limit the number of consecutive read faults while trying to read a flawed
800archives to
801.Ar limit .
802With a positive
803.Ar limit ,
804.Nm
805will attempt to recover from an archive read error and will
806continue processing starting with the next file stored in the archive.
807A
808.Ar limit
809of 0 will cause
810.Nm
811to stop operation after the first read error is detected on an archive volume.
812A
813.Ar limit
814of
815.Li NONE
816will cause
817.Nm
818to attempt to recover from read errors forever.
819The default
820.Ar limit
821is a small positive number of retries.
822.Pp
823.Em Warning :
824Using this option with
825.Li NONE
826should be used with extreme caution as
827.Nm
828may get stuck in an infinite loop on a very badly flawed archive.
829.It Fl G Ar group
830Select a file based on its
831.Ar group
832name, or when starting with a
833.Cm # ,
834a numeric gid.
835A '\\' can be used to escape the
836.Cm # .
837Multiple
838.Fl G
839options may be supplied and checking stops with the first match.
840.It Fl H
841Follow only command line symbolic links while performing a physical file
842system traversal.
843.It Fl L
844Follow all symbolic links to perform a logical filesystem traversal.
845.It Fl P
846Do not follow symbolic links, perform a physical filesystem traversal.
847This is the default mode.
848.It Fl T Ar [from_date][,to_date][/[c][m]]
849Allow files to be selected based on a file modification or inode change
850time falling within a specified time range of
851.Ar from_date
852to
853.Ar to_date
854(the dates are inclusive).
855If only a
856.Ar from_date
857is supplied, all files with a modification or inode change time
858equal to or younger are selected.
859If only a
860.Ar to_date
861is supplied, all files with a modification or inode change time
862equal to or older will be selected.
863When the
864.Ar from_date
865is equal to the
866.Ar to_date ,
867only files with a modification or inode change time of exactly that
868time will be selected.
869.Pp
870When
871.Nm
872is in the
873.Em write
874or
875.Em copy
876mode, the optional trailing field
877.Ar [c][m]
878can be used to determine which file time (inode change, file modification or
879both) are used in the comparison.
880If neither is specified, the default is to use file modification time only.
881The
882.Ar m
883specifies the comparison of file modification time (the time when
884the file was last written).
885The
886.Ar c
887specifies the comparison of inode change time (the time when the file
888inode was last changed; e.g. a change of owner, group, mode, etc).
889When
890.Ar c
891and
892.Ar m
893are both specified, then the modification and inode change times are
894both compared.
895The inode change time comparison is useful in selecting files whose
896attributes were recently changed or selecting files which were recently
897created and had their modification time reset to an older time (as what
898happens when a file is extracted from an archive and the modification time
899is preserved).
900Time comparisons using both file times is useful when
901.Nm
902is used to create a time based incremental archive (only files that were
903changed during a specified time range will be archived).
904.Pp
905A time range is made up of six different fields and each field must contain two
906digits.
907The format is:
908.Dl [yy[mm[dd[hh]]]]mm[.ss]
909Where
910.Cm yy
911is the last two digits of the year,
912the first
913.Cm mm
914is the month (from 01 to 12),
915.Cm dd
916is the day of the month (from 01 to 31),
917.Cm hh
918is the hour of the day (from 00 to 23),
919the second
920.Cm mm
921is the minute (from 00 to 59),
922and
923.Cm ss
924is the seconds (from 00 to 59).
925The minute field
926.Cm mm
927is required, while the other fields are optional and must be added in the
928following order:
929.Dl Cm hh , dd , mm , yy .
930The
931.Cm ss
932field may be added independently of the other fields.
933Time ranges are relative to the current time, so
934.Dl Fl T Ar 1234/cm
935would select all files with a modification or inode change time
936of 12:34 PM today or later.
937Multiple
938.Fl T
939time range can be supplied and checking stops with the first match.
940.It Fl U Ar user
941Select a file based on its
942.Ar user
943name, or when starting with a
944.Cm # ,
945a numeric uid.
946A '\\' can be used to escape the
947.Cm # .
948Multiple
949.Fl U
950options may be supplied and checking stops with the first match.
951.It Fl X
952When traversing the file hierarchy specified by a pathname,
953do not descend into directories that have a different device ID.
954See the
955.Li st_dev
956field as described in
957.Xr stat 2
958for more information about device ID's.
959.It Fl Y
960This option is the same as the
961.Fl D
962option, except that the inode change time is checked using the
963pathname created after all the file name modifications have completed.
964.It Fl Z
965This option is the same as the
966.Fl u
967option, except that the modification time is checked using the
968pathname created after all the file name modifications have completed.
969.El
970.Pp
971The options that operate on the names of files or archive members
972.Fl ( c ,
973.Fl i ,
974.Fl n ,
975.Fl s ,
976.Fl u ,
977.Fl v ,
978.Fl D ,
979.Fl G ,
980.Fl T ,
981.Fl U ,
982.Fl Y ,
983and
984.Fl Z )
985interact as follows.
986.Pp
987When extracting files during a
988.Em read
989operation, archive members are
990.Sq selected ,
991based only on the user specified pattern operands as modified by the
992.Fl c ,
993.Fl n ,
994.Fl u ,
995.Fl D ,
996.Fl G ,
997.Fl T ,
998.Fl U
999options.
1000Then any
1001.Fl s
1002and
1003.Fl i
1004options will modify in that order, the names of these selected files.
1005Then the
1006.Fl Y
1007and
1008.Fl Z
1009options will be applied based on the final pathname.
1010Finally the
1011.Fl v
1012option will write the names resulting from these modifications.
1013.Pp
1014When archiving files during a
1015.Em write
1016operation, or copying files during a
1017.Em copy
1018operation, archive members are
1019.Sq selected ,
1020based only on the user specified pathnames as modified by the
1021.Fl n ,
1022.Fl u ,
1023.Fl D ,
1024.Fl G ,
1025.Fl T ,
1026and
1027.Fl U
1028options (the
1029.Fl D
1030option only applies during a copy operation).
1031Then any
1032.Fl s
1033and
1034.Fl i
1035options will modify in that order, the names of these selected files.
1036Then during a
1037.Em copy
1038operation the
1039.Fl Y
1040and the
1041.Fl Z
1042options will be applied based on the final pathname.
1043Finally the
1044.Fl v
1045option will write the names resulting from these modifications.
1046.Pp
1047When one or both of the
1048.Fl u
1049or
1050.Fl D
1051options are specified along with the
1052.Fl n
1053option, a file is not considered selected unless it is newer
1054than the file to which it is compared.
1055.Sh EXAMPLES
1056The command:
1057.Dl "pax -w -f /dev/rst0 ."
1058copies the contents of the current directory to the device
1059.Pa /dev/rst0 .
1060.Pp
1061The command:
1062.Dl pax -v -f filename
1063gives the verbose table of contents for an archive stored in
1064.Pa filename .
1065.Pp
1066The following commands:
1067.Dl mkdir /tmp/foo
1068.Dl cd /tmp/bar
1069.Dl pax -rw .\ /tmp/foo
1070will copy the entire
1071.Pa /tmp/bar
1072directory hierarchy to
1073.Pa /tmp/foo .
1074.Pp
1075The command:
1076.Dl pax -r -s ',^//*usr//*,,' -f a.pax
1077reads the archive
1078.Pa a.pax ,
1079with all files rooted in ``/usr'' into the archive extracted relative to the
1080current directory.
1081.Pp
1082The command:
1083.Dl pax -rw -i .\ dest_dir
1084can be used to interactively select the files to copy from the current
1085directory to
1086.Pa dest_dir .
1087.Pp
1088The command:
1089.Dl pax -r -pe -U root -G bin -f a.pax
1090will extract all files from the archive
1091.Pa a.pax
1092which are owned by
1093.Em root
1094with group
1095.Em bin
1096and will preserve all file permissions.
1097.Pp
1098The command:
1099.Dl pax -r -w -v -Y -Z home /backup
1100will update (and list) only those files in the destination directory
1101.Pa /backup
1102which are older (less recent inode change or file modification times) than
1103files with the same name found in the source file tree
1104.Pa home .
1105.Sh STANDARDS
1106The
1107.Nm
1108utility is a superset of the
1109.St -p1003.2
1110standard.
1111The options
1112.Fl z ,
1113.Fl B ,
1114.Fl D ,
1115.Fl E ,
1116.Fl G ,
1117.Fl H ,
1118.Fl L ,
1119.Fl P ,
1120.Fl T ,
1121.Fl U ,
1122.Fl Y ,
1123.Fl Z ,
1124the archive formats
1125.Ar bcpio ,
1126.Ar sv4cpio ,
1127.Ar sv4crc ,
1128.Ar tar ,
1129and the flawed archive handling during
1130.Ar list
1131and
1132.Ar read
1133operations are extensions to the
1134.Tn POSIX
1135standard.
1136.Sh SEE ALSO
1137.Xr cpio 1 ,
1138.Xr tar 1
1139.Sh HISTORY
1140The
1141.Nm
1142utility appeared in
1143.Bx 4.4 .
1144.Sh AUTHORS
1145.An Keith Muller
1146at the University of California, San Diego
1147.Sh DIAGNOSTICS
1148The
1149.Nm
1150utility will exit with one of the following values:
1151.Bl -tag -width 2n
1152.It 0
1153All files were processed successfully.
1154.It 1
1155An error occurred.
1156.El
1157.Pp
1158Whenever
1159.Nm
1160cannot create a file or a link when reading an archive or cannot
1161find a file when writing an archive, or cannot preserve the user ID,
1162group ID, or file mode when the
1163.Fl p
1164option is specified, a diagnostic message is written to
1165.Dv standard error
1166and a non-zero exit status will be returned, but processing will continue.
1167In the case where pax cannot create a link to a file,
1168.Nm
1169will not create a second copy of the file.
1170.Pp
1171If the extraction of a file from an archive is prematurely terminated by
1172a signal or error,
1173.Nm
1174may have only partially extracted a file the user wanted.
1175Additionally, the file modes of extracted files and directories
1176may have incorrect file bits, and the modification and access times may be
1177wrong.
1178.Pp
1179If the creation of an archive is prematurely terminated by a signal or error,
1180.Nm
1181may have only partially created the archive which may violate the specific
1182archive format specification.
1183.Pp
1184If while doing a
1185.Em copy ,
1186.Nm
1187detects a file is about to overwrite itself, the file is not copied,
1188a diagnostic message is written to
1189.Dv standard error
1190and when
1191.Nm
1192completes it will exit with a non-zero exit status.
1193