![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to README CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / g / usr / bin / pax / doc|
Return to README CVS log | Up to [MW Coherent from dump] / coherent / g / usr / bin / pax / doc |
1.1 root 1: PAX - Portable Archive Interchange
2:
3: Copyright (C) 1989 Mark H. Colburn
4: All Rights Reserved.
5:
6:
7: Introduction
8:
9: This is version 1.1 of Pax, a public domain archiving utility.
10:
11: Pax is an archiving utility that reads and writes tar and cpio formats,
12: both the traditional ones and the extended formats specified in IEEE
13: 1003.1. It handles multi-volume archives and automatically determines
14: the format of an archive while reading it. Three user interfaces are
15: supported: tar, cpio, and pax. The pax interface was designed by IEEE
16: 1003.2 as a compromise in the chronic controversy over which of tar or
17: cpio is best.
18:
19: The USENIX Association provided some support for this implementation
20: project. As a result, the Pax utility is being distributed free of
21: charge and may be redistributed by others in either source or binary
22: form. (See the liscensing section for restrictions)
23:
24: The source for Pax is being posted to comp.sources.unix on USENET and
25: will also be available by anonymous FTP on the Internet from uunet.uu.net,
26: moon.honeywell.com and from one of the Berkeley machines. The source
27: to Pax will be available via anonymous UUCP from jhereg.mn.org, the
28: author's home machine and possibly other sites.
29:
30: The source for Pax will continue to change as long as the definition of
31: the utility is modified by the 1003.2 working group. (For example,
32: there are a number of changes in Draft 8 which will be incorporated as
33: soon as Draft 8 is available). Additional modifications will be made
34: based on user input, such as request for support of additional archive
35: formats, etc. Patches and new releases will be made as new functionality
36: is added or problems are diagnosed and fixed.
37:
38:
39: Installation
40:
41: In order to install Pax, you must first edit the Makefile and the
42: config.h file according to the directions in each of the files.
43: These two files provide the configuration information for most
44: commonly available machines. Please be sure to read through all
45: the directions in each of these files before attempting to compile
46: Pax.
47:
48:
49: Portability
50:
51: Pax is intended to run on as many systems as possible. If you have
52: problems getting Pax to compile or run on your system, please let me
53: know so that the source or the installation procedure can be modified.
54:
55: Pax has been tested and appears to run correctly on the following
56: machines:
57:
58: Machine Operating System/Release
59: -------------------------------------------------------
60: Altos 586 System III (2.3)
61: AT&T UNIX PC System V.2 (Release 3.51)
62: Cray 2 UNICOS
63: HP 9000 HP/UX 6.0.1
64: Mac II A/UX 1.0
65: NCR Tower System V.2
66: Pyramid AT&T and Berkeley universe
67: Sequent Symetry Dynix 3.0
68: SGI Iris 4D/60G UNIX 3.0
69: SGI Iris 4D/70G UNIX 3.0
70: Sun 2 SunOS 3.4
71: Sun 2 SunOS 3.5
72: Sun 3 SunOS 3.4
73: Sun 3 SunOS 3.5
74: Sun 3 SunOS 4.0
75: Sun 4 SunOS 4.0
76: VAX 8750 BSD 4.3 (Mt. Xinu)
77: VAX 8650 BSD 4.3 (Mt. Xinu)
78: VAX 780 BSD 4.3 (Berkeley)
79: -------------------------------------------------------
80:
81: In future releases, the source will be moving toward ANSI C and POSIX
82: compatibility. This should allow for portability over any system
83: supporting both ANSI and POSIX. In addition, POSIX/ANSI portability
84: library routines will be developed which will allow the code to run on
85: the standard machines available now.
86:
87:
88: Credit Where Credit is Due
89:
90: Parts of the code which makes up Pax were gleaned from a number of
91: different sources: the directory access routines in paxdir.h are
92: modified copies of Doug Gwyn's dirent library; the regular expression
93: matching routines in regexp.c are from Henry Spencer, some of the tar
94: archive routines were initially written by John Gilmore for his PDTAR;
95: and finally afio, written by Mark Brukhartz at Lachman Associates, was
96: the basis for the buffering schemes used in pax.
97:
98:
99: Licensing
100:
101: Copyright (c) 1989 Mark H. Colburn.
102: All rights reserved.
103:
104: Redistribution and use in source and binary forms are permitted
105: provided that the above copyright notice is duplicated in all such
106: forms and that any documentation, advertising materials, and other
107: materials related to such distribution and use acknowledge that the
108: software was developed by Mark H. Colburn and sponsored by The
109: USENIX Association.
110:
111: THE SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
112: IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
113: WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
114:
115: Please report any bug or problems to:
116:
117: Mark Colburn
118: NAPS International
119: 117 Mackubin St., Suite 1
120: St. Paul MN 55102
121: (612) 224-9108
122: [email protected]
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.