-Various people have been having problems using floppies on a NeXT.
-I've gotten conflicting reports about what should be done to solve the
-problems, and we have no way to test it ourselves.
-
-
-User-visible changes since 1.09:
-
-Filename to -G is optional. -C works right.
-Names newer and --newer-mtime work right.
-
--g is now --incremental
--G is now --listed-incremental
-
-Sparse files now work correctly.
-
---volume is now called --label.
-
---exclude now takes a filename argument, and --exclude-from does what
---exclude used to do.
-
-Exit status is now correct.
-
---totals keeps track of total I/O and prints it when tar exits.
-
-When using --label with --extract, the label is now a regexp.
-
-New option --tape-length (-L) does multi-volume handling like BSD dump:
-you tell tar how big the tape is and it will prompt at that point
-instead of waiting for a write error.
+Various people have been having problems using floppies on a NeXT. In
+order to have them work right, you need to kill the automounting
+program which tries to monut floppies as soon as they are added.
+
+If you want to do incremental dumps, use the distributed backup
+scripts. They are what we use at the FSF to do all our backups. Most
+importantly, do not use --incremental (-G) or --after-date (-N) or
+--newer-mtime to do incremental dumps. The only option that works
+correctly for this purpose is --listed-incremental. (When extracting
+incremental dumps, use --incremental (-G).)
+
+There is no tar manual in this release. The old manual has too many
+problems to make it usable. A new manual will appear in version 1.12.
+
+If your system needs to link with -lPW to get alloca, but has
+rename in the C library (so HAVE_RENAME is defined), -lPW might
+give you an incorrect version of rename. On HP-UX this manifests
+itself as an undefined data symbol called "Error" when linking cp, ln,
+and mv. If this happens, use `ar x' to extract alloca.o from libPW.a
+and `ar rc' to put it in a library liballoca.a, and put that in LIBS
+instead of -lPW. This problem does not occur when using gcc, which
+has alloca built in.