NetBSD/gnu/usr.bin/tar
lukem ed401558f2 Implement MKDYNAMICROOT, which currently defaults to "no", but will
be changed in the future to "yes".

If MKDYNAMICROOT == "no", there is no change from existing behaviour
of a static /bin and /sbin (and a few programs in elsewhere).

If MKDYNAMICROOT == "yes", the following changes occur:
    in <bsd.own.mk>:
	SHLIBDIR?=     /lib
	SHLINKDIR?=	/lib
    in various Makefiles, the following entry is DISABLED.
	LDSTATIC?=-static
This results in all programs (except those "standalone" programs built
in sys/arch/*/stand) are linked dynamically, the shared linker is moved
from /usr/libexec to /lib (with a compat symlink), and the shared
libraries used by /bin and /sbin programs are moved from /usr/lib to
/lib (with compat symlinks).
2002-08-27 14:46:11 +00:00
..
COPYING
ChangeLog
Makefile Implement MKDYNAMICROOT, which currently defaults to "no", but will 2002-08-27 14:46:11 +00:00
Makefile.gnu
README
VERSION
buffer.c
create.c
diffarch.c
extract.c
fnmatch.c
fnmatch.h
getdate.y
getoldopt.c
getopt.c
getopt.h
getopt1.c
gnu.c
list.c
mangle.c
msd_dir.h
names.c
open3.h
pathmax.h
port.c
port.h
regex.c
regex.h
rmt.h
rtapelib.c
tar.1 Remove superfluous Ns. 2002-08-20 15:28:11 +00:00
tar.c
tar.h
update.c
version.c

README

Hey!  Emacs!  Yo!  This is -*- Text -*- !!!

This GNU tar 1.11.2.  Please send bug reports, etc., to
bug-gnu-utils@prep.ai.mit.edu.  This is a beta-test release.  Please
try it out.  There is no manual; the release of version 1.12 will
contain a manual.

GNU tar is based heavily on John Gilmore's public domain tar, but with
added features.  The manual is currently being written.  

This distribution also includes rmt, the remote tape server (which
normally must reside in /etc).  The mt tape drive control program is
in the GNU cpio distribution.

See the file INSTALL for compilation and installation instructions for Unix.
See the file NEWS for information on all that is new in this version
of tar.

makefile.pc is a makefile for Turbo C 2.0 on MS-DOS.

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).)

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.