README 4.8 KB

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