Dogcows Code - chaz/tar/blob - README

   1 Hey!  Emacs!  Yo!  This is -*- Text -*- !!!
   2
   3 This GNU tar 1.11.1.  Please send bug reports, etc., to
   4 bug-gnu-utils@prep.ai.mit.edu.  This is a beta-test release.  Please
   5 try it out.  After bug reports are processed for this release, version
   6 1.12 will be released.  This release includes only bugfixes past
   7 version 1.11, most of which are fairly important.
   8
   9 GNU tar is based heavily on John Gilmore's public domain tar, but with
  10 added features.  The manual is currently being written.  An old
  11 manual, surely riddled with errors, is in tar.texinfo.  Please don't
  12 send in bug reports about that manual.  In particular, the mechanism
  13 for doing incremental dumps has been significantly changed.
  14
  15 This distribution also includes rmt, the remote tape server (which
  16 normally must reside in /etc).  The mt tape drive control program is
  17 in the GNU cpio distribution.
  18
  19 See the file INSTALL for compilation and installation instructions for Unix.
  20 See the file NEWS for information on all that is new in this version
  21 of tar.
  22
  23 makefile.pc is a makefile for Turbo C 2.0 on MS-DOS.
  24
  25 Various people have been having problems using floppies on a NeXT.  In
  26 order to have them work right, you need to kill the automounting
  27 program which tries to monut floppies as soon as they are added.
  28
  29 If you want to do incremental dumps, use the distributed backup
  30 scripts.  They are what we use at the FSF to do all our backups.  Most
  31 importantly, do not use --incremental (-G) or --after-date (-N) or
  32 --newer-mtime to do incremental dumps.  The only option that works
  33 correctly for this purpose is --listed-incremental.  (When extracting
  34 incremental dumps, use --incremental (-G).)
  35
  36 There is no tar manual in this release.  The old manual has too many
  37 problems to make it usable.  A new manual will appear in version 1.12.
  38
  39 If your system needs to link with -lPW to get alloca, but has
  40 rename in the C library (so HAVE_RENAME is defined), -lPW might
  41 give you an incorrect version of rename.  On HP-UX this manifests
  42 itself as an undefined data symbol called "Error" when linking cp, ln,
  43 and mv.  If this happens, use `ar x' to extract alloca.o from libPW.a
  44 and `ar rc' to put it in a library liballoca.a, and put that in LIBS
  45 instead of -lPW.  This problem does not occur when using gcc, which
  46 has alloca built in.
  47