ng that my backups will not be destroyed
by one errant bit :-)
--
John Goerzen [EMAIL PROTECTED] www.complete.org
Sr. Software Developer, Progeny Linux Systems, Inc.www.progenylinux.com
#include std_disclaimer.h [EMAIL PROTECTED]
Alexandre Oliva [EMAIL PROTECTED] writes:
On Nov 16, 2000, John Goerzen [EMAIL PROTECTED] wrote:
The compressed representation of each block is delimited by a
48-bit pattern, which makes it possible to find the block
boundaries with reasonable certainty. Each block
, and prevent
easy untarring of tar.gz files and stuff too. Not quite an acceptable
solution.
Johannes Nieß
--
John Goerzen [EMAIL PROTECTED] www.complete.org
Sr. Software Developer, Progeny Linux Systems, Inc.www.progenylinux.com
#include std_disclaimer.h
to specify an arbitrary program in the
config file, but hey, that'll do though.
(Maybe I want different compression programs with different configs or
for different filesystems.)
--
John Goerzen [EMAIL PROTECTED] www.complete.org
Sr. Software Developer, Progeny Linux Sy
for me on two glibc platforms.
-- John
- Forwarded message from Paul Eggert [EMAIL PROTECTED] -
X-Addr-Extension: saved
Delivered-To: [EMAIL PROTECTED]
Resent-To: [EMAIL PROTECTED]
Resent-From: John Goerzen [EMAIL PROTECTED]
Resent-Date: 04 Nov 2000 11:10:44 -0500
X-Addr-Extension:
Delivered
Alexandre Oliva [EMAIL PROTECTED] writes:
On Nov 4, 2000, John Goerzen [EMAIL PROTECTED] wrote:
Apparently, there is a bug in glibc that is triggered by the pattern
patching code in tar. They gave me a tar patch that works around it,
and this solved my problem!
You may want to post
is broken. Patterns without
wildcards, eg:
./lib
correctly exclude the directory.
I have GNU tar 1.13.17, Amanda 2.4.1p1, running on a set of Debian
GNU/Linux systems.
Thanks!
-- John
--
John Goerzen [EMAIL PROTECTED] www.complete.org
Sr. Software Developer, Progeny
