tag:old.nabble.com,2006:forum-1806Nabble - Gnu - Tar2009-12-15T05:09:47ZThe tar program provides the ability to create tar archives, as well as various other kinds of manipulation. For example, you can use tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored. Gnu - Tar home is <a href="http://www.gnu.org/software/tar/tar.html" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26794521Re: SunCC & gtar 1.22 inttypes.in.h2009-12-15T05:09:47Z2009-12-15T05:09:47ZEric Blake-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>According to john heasley on 12/14/2009 5:11 PM:
<div class='shrinkable-quote'><br>> SunCC doesnt return 0 for _LP64; this change seems to fix it.
<br>>
<br>> --- lib/inttypes.in.h.orig 2008-12-28 13:44:04.000000000 +0000
<br>> +++ lib/inttypes.in.h
<br>> @@ -168,7 +168,7 @@
<br>> # endif
<br>> # endif
<br>> # ifdef INT64_MAX
<br>> -# if (@APPLE_UNIVERSAL_BUILD@ ? _LP64 : @INT64_MAX_EQ_LONG_MAX@)
<br>> +# if (@APPLE_UNIVERSAL_BUILD@ ? defined(_LP64) : @INT64_MAX_EQ_LONG_MAX@)
</div><br>This is the correct fix. However, it was already applied to gnulib a
<br>while ago (Feb 27, 2009). Which version of tar are you trying to build?
<br>tar 1.22 was released in March, but it obviously didn't use the latest and
<br>greatest gnulib snapshot at the time. That means we should probably
<br>consider a newer release of tar.
<br><br>- --
<br>Don't work too hard, make some time for fun as well!
<br><br>Eric Blake <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26794521&i=0" target="_top" rel="nofollow">ebb9@...</a>
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Cygwin)
<br>Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_top" rel="nofollow">http://enigmail.mozdev.org/</a><br><br>iEYEARECAAYFAksnipsACgkQ84KuGfSFAYBPsgCfbQAUvm+9QWrte4E/eSaywnro
<br>nxkAoIqk2Q0bioUNzC+zOURDtvsa6p5y
<br>=9O37
<br>-----END PGP SIGNATURE-----
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26789767SunCC & gtar 1.22 inttypes.in.h2009-12-14T16:11:35Z2009-12-14T16:11:35Zjohn heasleySunCC doesnt return 0 for _LP64; this change seems to fix it.
<br><br>--- lib/inttypes.in.h.orig 2008-12-28 13:44:04.000000000 +0000
<br>+++ lib/inttypes.in.h
<br>@@ -168,7 +168,7 @@
<br> # endif
<br> # endif
<br> # ifdef INT64_MAX
<br>-# if (@APPLE_UNIVERSAL_BUILD@ ? _LP64 : @INT64_MAX_EQ_LONG_MAX@)
<br>+# if (@APPLE_UNIVERSAL_BUILD@ ? defined(_LP64) : @INT64_MAX_EQ_LONG_MAX@)
<br> # define _PRI64_PREFIX "l"
<br> # elif defined _MSC_VER || defined __MINGW32__
<br> # define _PRI64_PREFIX "I64"
<br>@@ -185,7 +185,7 @@
<br> # endif
<br> # endif
<br> # ifdef UINT64_MAX
<br>-# if (@APPLE_UNIVERSAL_BUILD@ ? _LP64 : @UINT64_MAX_EQ_ULONG_MAX@)
<br>+# if (@APPLE_UNIVERSAL_BUILD@ ? defined(_LP64) : @UINT64_MAX_EQ_ULONG_MAX@)
<br> # define _PRIu64_PREFIX "l"
<br> # elif defined _MSC_VER || defined __MINGW32__
<br> # define _PRIu64_PREFIX "I64"
<br>@@ -661,7 +661,7 @@
<br> # endif
<br> # endif
<br> # ifdef INT64_MAX
<br>-# if (@APPLE_UNIVERSAL_BUILD@ ? _LP64 : @INT64_MAX_EQ_LONG_MAX@)
<br>+# if (@APPLE_UNIVERSAL_BUILD@ ? defined(_LP64) : @INT64_MAX_EQ_LONG_MAX@)
<br> # define _SCN64_PREFIX "l"
<br> # elif defined _MSC_VER || defined __MINGW32__
<br> # define _SCN64_PREFIX "I64"
<br>@@ -678,7 +678,7 @@
<br> # endif
<br> # endif
<br> # ifdef UINT64_MAX
<br>-# if (@APPLE_UNIVERSAL_BUILD@ ? _LP64 : @UINT64_MAX_EQ_ULONG_MAX@)
<br>+# if (@APPLE_UNIVERSAL_BUILD@ ? defined(_LP64) : @UINT64_MAX_EQ_ULONG_MAX@)
<br> # define _SCNu64_PREFIX "l"
<br> # elif defined _MSC_VER || defined __MINGW32__
<br> # define _SCNu64_PREFIX "I64"
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26717254Re: tar1.22 complains when backing up a read-only filesystem2009-12-09T12:35:49Z2009-12-09T12:35:49ZAndreas Dilger-4On 2009-12-09, at 06:55, Hill, Shannon wrote:
<div class='shrinkable-quote'><br>> using tar1.22 built on Centos 5.4 x86_64
<br>>
<br>> sim8/root@/tmp# /usr/local/bin/tar --version
<br>> tar (GNU tar) 1.22
<br>> ...with these options:
<br>>
<br>> time /usr/local/bin/tar \
<br>> --create \
<br>> --format=pax \
<br>> --blocking-factor 2048 \
<br>> --totals \
<br>> --multi-volume \
<br>> --ignore-failed-read \
<br>> --exclude .snapshot \
<br>> --new-volume-script /root/bin/eot \
<br>> --file ${TAPE} .
<br>>
<br>>
<br>> yields this output (for every file), when . resides on a read-only
<br>> file system:
<br>>
<br>> /usr/local/bin/tar: ./tcaputo/views/eclipse/.metadata/.plugins/
<br>> org.eclipse.core.resources/.root/.indexes/properties.index: Cannot
<br>> utime: Read-only file system
</div><br><br>Ironically, it doesn't need to do utime (to set the atime backward)
<br>when the filesystem is mounted read-only. tar should probably check a
<br>"skip_utime" boolean (default = 0) before calling utime(), and if
<br>utime() fails with EROFS that flag is set...
<br><br>On Linux at least there is also a "O_NOATIME" flag that prevents the
<br>atime from being changed in the first place, just to avoid the need to
<br>write (twice!) to the filesystem for every file touched (once to
<br>update atime, once to revert it). It appears that tar 1.22 has
<br>support for O_NOATIME, but it isn't being used for some reason.
<br><br>Cheers, Andreas
<br>--
<br>Andreas Dilger
<br>Sr. Staff Engineer, Lustre Group
<br>Sun Microsystems of Canada, Inc.
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26715048tar1.22 complains when backing up a read-only filesystem2009-12-09T05:55:49Z2009-12-09T05:55:49ZHill, Shannon<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3268" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=690125113-09122009><FONT face=Courier size=2><STRONG>using
tar1.22 built on Centos 5.4 x86_64</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2>Linux
sim8.chipwrights.com 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:03:03 EDT 2009 x86_64
x86_64 x86_64 GNU/Linux</FONT></STRONG></SPAN></DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2><A target="_top">sim8/root@/tmp</A># /usr/local/bin/tar --version<BR>tar (GNU tar)
1.22<BR>Copyright (C) 2009 Free Software Foundation, Inc.<BR>License GPLv3+: GNU
GPL version 3 or later <<A href="http://gnu.org/licenses/gpl.html" target="_top" rel="nofollow">http://gnu.org/licenses/gpl.html</A>>.<BR>This
is free software: you are free to change and redistribute it.<BR>There is NO
WARRANTY, to the extent permitted by law.</FONT></STRONG></SPAN></DIV>
<DIV><STRONG><FONT face=Courier size=2></FONT></STRONG> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2>Written by
John Gilmore and Jay Fenlason.</FONT></STRONG></SPAN></DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2>...with
these options:</FONT></STRONG></SPAN></DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2>time
/usr/local/bin/tar
\<BR>
--create
\<BR>
--format=pax
\<BR> --blocking-factor 2048
\<BR>
--totals
\<BR>
--multi-volume
\<BR>
--ignore-failed-read
\<BR> --exclude
.snapshot
\<BR> --new-volume-script
/root/bin/eot \<BR> --file
${TAPE} .</FONT></STRONG></SPAN></DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT></STRONG></SPAN> </DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2>yields
this output (for every file), when . resides on a read-only file
system:</FONT></STRONG></SPAN></DIV>
<DIV><SPAN class=690125113-09122009><STRONG><FONT face=Courier size=2></FONT><BR><FONT face=Courier><FONT size=2><SPAN class=690125113-09122009>/</SPAN>usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.root/.indexes/properties.index:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.root/.indexes/properties.version:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.root/.indexes/history.version:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.root/.indexes:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.root/1.tree:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.root:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.safetable/org.eclipse.core.resources:
Cannot utime: Read-only file system<BR>/usr/local/bin/tar:
./tcaputo/views/eclipse/.metadata/.plugins/org.eclipse.core.resources/.safetable:
Cannot utime: Read-only file system<BR>/</FONT></FONT></DIV>
<DIV><FONT face=Courier size=2></FONT> </DIV>
<DIV><FONT face=Courier size=2><SPAN class=690125113-09122009></SPAN></FONT> </DIV></STRONG></SPAN></BODY></HTML>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26634363[Fwd: Re: Re: need to build a Windows tar with no cywin1.dll dependency]2009-12-03T09:08:50Z2009-12-03T09:08:50ZMike MakiAdditional information - Windows version is XP Pro SP3,
<br>mike@GANDALF ~
<br>$ gcc --version
<br>gcc.exe (GCC) 3.4.5 (mingw-vista special r3)
<br>Copyright (C) 2004 Free Software Foundation, Inc.
<br>This is free software; see the source for copying conditions. There is NO
<br>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
<br><br>Resultant makefile contains:
<br><br>GNULIB_STDIO_H_SIGPIPE = 0
<br>GNULIB_UNISTD_H_SIGPIPE = 0
<br><br>gl_LIBOBJS = argmatch.o asnprintf.o backupfile.o basename.o
<br>canonicalize-lgpl.o chdir-long.o chown.o close.o close-stream.o
<br>closeout.o creat-safer.o dirfd.o dirname.o dup-safer.o error.o exclude.o
<br>exitfail.o fchdir.o fchmodat.o fchown-stub.o fchownat.o fclose.o
<br>fd-safer.o fileblocks.o fnmatch.o fpending.o fseeko.o getcwd.o
<br>getdelim.o getline.o getopt.o getopt1.o getpagesize.o gettime.o hash.o
<br>human.o imaxtostr.o lchown.o lseek.o malloc.o mempcpy.o memrchr.o
<br>mkdirat.o mkdtemp.o modechange.o obstack.o offtostr.o open.o
<br>open-safer.o openat.o openat-proc.o pipe-safer.o printf-args.o
<br>printf-parse.o quote.o quotearg.o rawmemchr.o readlink.o realloc.o
<br>regex.o rpmatch.o safe-read.o safe-write.o save-cwd.o savedir.o setenv.o
<br>sleep.o stpcpy.o strchrnul.o strdup.o strerror.o stripslash.o strndup.o
<br>strnlen.o tempname.o time_r.o uinttostr.o umaxtostr.o unlinkdir.o
<br>unsetenv.o utimens.o vasnprintf.o wcwidth.o xgetcwd.o xmalloc.o
<br>xstrtol.o xstrtol-error.o xstrtoul.o
<br>gl_LTLIBOBJS = argmatch.lo asnprintf.lo backupfile.lo basename.lo
<br>canonicalize-lgpl.lo chdir-long.lo chown.lo close.lo close-stream.lo
<br>closeout.lo creat-safer.lo dirfd.lo dirname.lo dup-safer.lo error.lo
<br>exclude.lo exitfail.lo fchdir.lo fchmodat.lo fchown-stub.lo fchownat.lo
<br>fclose.lo fd-safer.lo fileblocks.lo fnmatch.lo fpending.lo fseeko.lo
<br>getcwd.lo getdelim.lo getline.lo getopt.lo getopt1.lo getpagesize.lo
<br>gettime.lo hash.lo human.lo imaxtostr.lo lchown.lo lseek.lo malloc.lo
<br>mempcpy.lo memrchr.lo mkdirat.lo mkdtemp.lo modechange.lo obstack.lo
<br>offtostr.lo open.lo open-safer.lo openat.lo openat-proc.lo pipe-safer.lo
<br>printf-args.lo printf-parse.lo quote.lo quotearg.lo rawmemchr.lo
<br>readlink.lo realloc.lo regex.lo rpmatch.lo safe-read.lo safe-write.lo
<br>save-cwd.lo savedir.lo setenv.lo sleep.lo stpcpy.lo strchrnul.lo
<br>strdup.lo strerror.lo stripslash.lo strndup.lo strnlen.lo tempname.lo
<br>time_r.lo uinttostr.lo umaxtostr.lo unlinkdir.lo unsetenv.lo utimens.lo
<br>vasnprintf.lo wcwidth.lo xgetcwd.lo xmalloc.lo xstrtol.lo
<br>xstrtol-error.lo xstrtoul.lo
<br><br>Mike
<br><br>-------- Original Message --------
<br>Subject: Re: [Bug-tar] Re: need to build a Windows tar with no
<br>cywin1.dll dependency
<br>Date: Thu, 03 Dec 2009 11:49:19 -0500
<br>From: Mike Maki <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26634363&i=0" target="_top" rel="nofollow">mikemak009@...</a>>
<br>To: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26634363&i=1" target="_top" rel="nofollow">bug-tar@...</a>
<br>CC: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26634363&i=2" target="_top" rel="nofollow">mike@...</a>
<br>References: <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26634363&i=3" target="_top" rel="nofollow">4B16B4A1.4050005@...</a>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26634363&i=4" target="_top" rel="nofollow">4B16B5A4.40406@...</a>>
<br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26634363&i=5" target="_top" rel="nofollow">20091202224713.GA28349@...</a>>
<br><br><br><br>Thanks Lars and others who suggested MinGW, MSYS. I have that set up now.
<br><br>Where it builds in cygwin but won't run in DOS, the problem now is
<br>configure succeeds but make fails in MSYS/MinGW.
<br><br>The log messages at the end of make look like:
<br>depbase=`echo prepargs.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
<br> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
<br>prepargs.o -MD -M
<br>P -MF $depbase.Tpo -c -o prepargs.o prepargs.c &&\
<br> mv -f $depbase.Tpo $depbase.Po
<br>depbase=`echo rtapelib.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
<br> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
<br>rtapelib.o -MD -M
<br>P -MF $depbase.Tpo -c -o rtapelib.o rtapelib.c &&\
<br> mv -f $depbase.Tpo $depbase.Po
<br>rtapelib.c: In function `do_command':
<br>rtapelib.c:124: error: `SIGPIPE' undeclared (first use in this function)
<br>rtapelib.c:124: error: (Each undeclared identifier is reported only once
<br>rtapelib.c:124: error: for each function it appears in.)
<br>rtapelib.c: In function `rmt_open__':
<br>rtapelib.c:468: warning: implicit declaration of function `pipe'
<br>rtapelib.c:477: warning: implicit declaration of function `fork'
<br>rtapelib.c:500: warning: implicit declaration of function `setuid'
<br>rtapelib.c:500: warning: implicit declaration of function `getuid'
<br>rtapelib.c:500: warning: implicit declaration of function `setgid'
<br>rtapelib.c:500: warning: implicit declaration of function `getgid'
<br>rtapelib.c: In function `rmt_write__':
<br>rtapelib.c:602: error: `SIGPIPE' undeclared (first use in this function)
<br>make[4]: *** [rtapelib.o] Error 1
<br>make[4]: Leaving directory `/home/mike/tar-1.22/lib'
<br>make[3]: *** [all-recursive] Error 1
<br>make[3]: Leaving directory `/home/mike/tar-1.22/lib'
<br>make[2]: *** [all] Error 2
<br>make[2]: Leaving directory `/home/mike/tar-1.22/lib'
<br>make[1]: *** [all-recursive] Error 1
<br>make[1]: Leaving directory `/home/mike/tar-1.22'
<br>make: *** [all] Error 2
<br><br><br>I've googled the error and various people have seen it and sent the
<br>error to mailing lists, but I haven't found an appropriate solution.
<br><br>BTW, the MinGW tar works in MSYS, but when I try to run in in a cmd
<br>(DOS) window, I get an error saying:
<br><br>This application has failed to start because msys-1.0.dll was not found.
<br>Re-installing the application may fix this problem.
<br><br>Another dependency on environment, this time msys.
<br><br>Is there a switch for "configure" that removes that dependency or points
<br>to a different set of libraries to use? I have set LDFLAGS=-static to
<br>build a static executable, and am using --disable-nls to exclude
<br>language support.
<br><br>thanks,
<br><br>Mike
<br><br>Lars Stoltenow wrote:
<div class='shrinkable-quote'><br>> On Wed, Dec 02, 2009 at 01:44:52PM -0500, Mike Maki wrote:
<br>>
<br>>>> I've been looking at how to do this, but haven't found out how to
<br>>>> make a tar.exe that will run in a dos cmd shell. Do I need to
<br>>>> compile on a non-cygwin system using non-gnu compiler? The last
<br>>>> thing I want to do is use MS VCC. I'm required to update to a
<br>>>> recent version of tar.exe (we ship 1.12 now and would like to ship
<br>>>> 1.21 or better). Thanks,
<br>>>>
<br>>
<br>> Use MinGW+MSYS: <a href="http://mingw.org" target="_top" rel="nofollow">http://mingw.org</a><br>>
<br>>
</div><br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26634359Re: Re: need to build a Windows tar with no cywin1.dll dependency2009-12-03T08:49:19Z2009-12-03T08:49:19ZMike MakiThanks Lars and others who suggested MinGW, MSYS. I have that set up now.
<br><br>Where it builds in cygwin but won't run in DOS, the problem now is
<br>configure succeeds but make fails in MSYS/MinGW.
<br><br>The log messages at the end of make look like:
<br>depbase=`echo prepargs.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
<br> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
<br>prepargs.o -MD -M
<br>P -MF $depbase.Tpo -c -o prepargs.o prepargs.c &&\
<br> mv -f $depbase.Tpo $depbase.Po
<br>depbase=`echo rtapelib.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
<br> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT
<br>rtapelib.o -MD -M
<br>P -MF $depbase.Tpo -c -o rtapelib.o rtapelib.c &&\
<br> mv -f $depbase.Tpo $depbase.Po
<br>rtapelib.c: In function `do_command':
<br>rtapelib.c:124: error: `SIGPIPE' undeclared (first use in this function)
<br>rtapelib.c:124: error: (Each undeclared identifier is reported only once
<br>rtapelib.c:124: error: for each function it appears in.)
<br>rtapelib.c: In function `rmt_open__':
<br>rtapelib.c:468: warning: implicit declaration of function `pipe'
<br>rtapelib.c:477: warning: implicit declaration of function `fork'
<br>rtapelib.c:500: warning: implicit declaration of function `setuid'
<br>rtapelib.c:500: warning: implicit declaration of function `getuid'
<br>rtapelib.c:500: warning: implicit declaration of function `setgid'
<br>rtapelib.c:500: warning: implicit declaration of function `getgid'
<br>rtapelib.c: In function `rmt_write__':
<br>rtapelib.c:602: error: `SIGPIPE' undeclared (first use in this function)
<br>make[4]: *** [rtapelib.o] Error 1
<br>make[4]: Leaving directory `/home/mike/tar-1.22/lib'
<br>make[3]: *** [all-recursive] Error 1
<br>make[3]: Leaving directory `/home/mike/tar-1.22/lib'
<br>make[2]: *** [all] Error 2
<br>make[2]: Leaving directory `/home/mike/tar-1.22/lib'
<br>make[1]: *** [all-recursive] Error 1
<br>make[1]: Leaving directory `/home/mike/tar-1.22'
<br>make: *** [all] Error 2
<br><br><br>I've googled the error and various people have seen it and sent the
<br>error to mailing lists, but I haven't found an appropriate solution.
<br><br>BTW, the MinGW tar works in MSYS, but when I try to run in in a cmd
<br>(DOS) window, I get an error saying:
<br><br>This application has failed to start because msys-1.0.dll was not found.
<br>Re-installing the application may fix this problem.
<br><br>Another dependency on environment, this time msys.
<br><br>Is there a switch for "configure" that removes that dependency or points
<br>to a different set of libraries to use? I have set LDFLAGS=-static to
<br>build a static executable, and am using --disable-nls to exclude
<br>language support.
<br><br>thanks,
<br><br>Mike
<br><br>Lars Stoltenow wrote:
<div class='shrinkable-quote'><br>> On Wed, Dec 02, 2009 at 01:44:52PM -0500, Mike Maki wrote:
<br>>
<br>>>> I've been looking at how to do this, but haven't found out how to
<br>>>> make a tar.exe that will run in a dos cmd shell. Do I need to
<br>>>> compile on a non-cygwin system using non-gnu compiler? The last
<br>>>> thing I want to do is use MS VCC. I'm required to update to a
<br>>>> recent version of tar.exe (we ship 1.12 now and would like to ship
<br>>>> 1.21 or better). Thanks,
<br>>>>
<br>>
<br>> Use MinGW+MSYS: <a href="http://mingw.org" target="_top" rel="nofollow">http://mingw.org</a><br>>
<br>>
</div><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26619520Re: Re: need to build a Windows tar with no cywin1.dll dependency2009-12-02T14:47:13Z2009-12-02T14:47:13ZLars Stoltenow-3On Wed, Dec 02, 2009 at 01:44:52PM -0500, Mike Maki wrote:
<br>> >I've been looking at how to do this, but haven't found out how to
<br>> >make a tar.exe that will run in a dos cmd shell. Do I need to
<br>> >compile on a non-cygwin system using non-gnu compiler? The last
<br>> >thing I want to do is use MS VCC. I'm required to update to a
<br>> >recent version of tar.exe (we ship 1.12 now and would like to ship
<br>> >1.21 or better). Thanks,
<br><br>Use MinGW+MSYS: <a href="http://mingw.org" target="_top" rel="nofollow">http://mingw.org</a><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26618727Re: need to build a Windows tar with no cywin1.dll dependency2009-12-02T14:36:43Z2009-12-02T14:36:43ZMike FrysingerOn Wednesday 02 December 2009 13:40:33 Mike Maki wrote:
<br>> I've been looking at how to do this, but haven't found out how to make a
<br>> tar.exe that will run in a dos cmd shell. Do I need to compile on a
<br>> non-cygwin system using non-gnu compiler? The last thing I want to do is
<br>> use MS VCC. I'm required to update to a recent version of tar.exe (we
<br>> ship 1.12 now and would like to ship 1.21 or better). Thanks,
<br><br>use mingw ... in fact, it looks like they already host a pre-compiled gnu tar
<br>-mike
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>signature.asc</strong> (853 bytes) <a href="http://old.nabble.com/attachment/26618727/0/signature.asc" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26618699Re: need to build a Windows tar with no cywin1.dll dependency2009-12-02T14:25:08Z2009-12-02T14:25:08ZKarl Berry I've been looking at how to do this, but haven't found out how to make a
<br> tar.exe that will run in a dos cmd shell.
<br><br>I am not sure what version it is, but if a precompiled executable would
<br>suit, try
<br>mirror.ctan.org/systems/texlive/tlnet/tlpkg/installer/tar.exe. Source
<br>at <a href="http://tug.org/texlive/devsrc/Master/source/tar-w32.zip" target="_top" rel="nofollow">http://tug.org/texlive/devsrc/Master/source/tar-w32.zip</a> (among other
<br>places).
<br><br> Do I need to compile on a non-cygwin system using non-gnu compiler?
<br><br>I believe that executable was indeed made with a Windows compiler :(.
<br>If you need to compile it yourself, the only other option I can think of
<br>is mingw32. I had the impression it had the goal of providing "native"
<br>exe's without such dependencies, although I am far from sure.
<br><br>Good luck,
<br>Karl
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26617468Re: need to build a Windows tar with no cywin1.dll dependency2009-12-02T10:44:52Z2009-12-02T10:44:52ZMike MakiMike Maki wrote:
<br>> I've been looking at how to do this, but haven't found out how to make
<br>> a tar.exe that will run in a dos cmd shell. Do I need to compile on a
<br>> non-cygwin system using non-gnu compiler? The last thing I want to do
<br>> is use MS VCC. I'm required to update to a recent version of tar.exe
<br>> (we ship 1.12 now and would like to ship 1.21 or better). Thanks,
<br>>
<br>> Mike
<br>>
<br>Oh, I forgot it needs to be static and as small as possible. Mike
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26617465need to build a Windows tar with no cywin1.dll dependency2009-12-02T10:40:33Z2009-12-02T10:40:33ZMike MakiI've been looking at how to do this, but haven't found out how to make a
<br>tar.exe that will run in a dos cmd shell. Do I need to compile on a
<br>non-cygwin system using non-gnu compiler? The last thing I want to do is
<br>use MS VCC. I'm required to update to a recent version of tar.exe (we
<br>ship 1.12 now and would like to ship 1.21 or better). Thanks,
<br><br>Mike
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26539222RE: Inquiry on GNU Tar2009-11-27T00:27:12Z2009-11-27T00:27:12ZNick Lewis-4> Please let me know whether the backup utility GNU Tar supports the
<br>following requirements.
<br>>
<br>> File Backup and Restore
<br>> Backup to CD/DVD, Local hard disk, network share, Tape drive
<br>> Full Backup supported (Rewrite the old data)
<br>> File size supported
<br>> File Compression technology
<br>> Manual and Scheduled backup
<br>> Command line utility
<br><br>Yes
<br><br>> Tool usability and manageability
<br>> Detailed logs
<br>> Support on Windows Server 2008 with tape drives. (Also please let me
<br>know the Supported Operating systems)
<br><br>(I am not sure that tar is the tool for you)
<br><br>_____________________________________________________________________
<br>This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
<br>_____________________________________________________________________
<br>Disclaimer of Liability
<br>ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the information described and/or contained herein and assumes no responsibility for anyones use of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement or substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this system, even if advised of the possibility of such damage.
<br><br>Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
<br>Registered in Wales Number 4335781
<br><br>All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26538757Inquiry on GNU Tar2009-11-25T21:22:12Z2009-11-25T21:22:12ZShain, DL IN BLR SISL<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Please let me know whether the backup
utility GNU Tar supports the following requirements.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File Backup and Restore<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Backup to CD/DVD, Local
hard disk, network share, Tape drive<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Full Backup supported
(Rewrite the old data)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File size supported<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File Compression
technology<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Manual and Scheduled
backup<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Command line utility<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Tool usability and
manageability<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Detailed logs<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Support on Windows Server
2008 with tape drives. (Also please let me know the Supported Operating
systems)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Thanks,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Shain<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26538754Inquiry on GNU Tar2009-11-25T21:15:12Z2009-11-25T21:15:12ZShain, DL IN BLR SISL<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Please let me know whether the backup
utility GNU Tar supports the following requirements.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File Backup and Restore<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Backup to CD/DVD, Local
hard disk, network share, Tape drive<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Full Backup supported
(Rewrite the old data)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File size supported<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File Compression technology<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Manual and Scheduled
backup<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Command line utility<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Tool usability and
manageability<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Detailed logs<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Support on Windows Server
2008 with tape drives. (Also please let me know the Supported Operating
systems)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Thanks,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Shain<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26538756Inquiry on GNU Tar2009-11-25T21:07:56Z2009-11-25T21:07:56ZShain, DL IN BLR SISL<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Please let me know whether the backup
utility GNU Tar supports the following requirements.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File Backup and Restore<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Backup to CD/DVD, Local
hard disk, network share, Tape drive<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Full Backup supported
(Rewrite the old data)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File size supported<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>File Compression
technology<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Manual and Scheduled
backup<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Command line utility<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Tool usability and
manageability<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Detailed logs<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-indent:.5in'><font size=2 color=blue face=Arial><span style='font-size:10.0pt;font-family:Arial;color:blue'>Support on Windows Server
2008 with tape drives. (Also please let me know the Supported Operating
systems)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Thanks,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Shain<o:p></o:p></span></font></p>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26538753Inquiry on GNU Tar2009-11-25T20:44:29Z2009-11-25T20:44:29ZShain, DL IN BLR SISL<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Please let me
know whether the backup utility GNU Tar supports the following requirements.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>File Backup and
Restore<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Backup to CD/DVD,
Local hard disk, network share, Tape drive<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Full Backup
supported (Rewrite the old data)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>File size supported<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>File Compression
technology<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Manual and
Scheduled backup<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Command line
utility<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Tool usability
and manageability<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Detailed logs<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Support on
Windows Server 2008 with tape drives. (Also please let me know the Supported
Operating systems)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Thanks,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";color:blue'>Shain<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26538749Inquiry on GNU Tar2009-11-25T20:39:36Z2009-11-25T20:39:36ZShain, DL IN BLR SISL<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Please let me know whether the backup utility GNU Tar supports the following
requirements.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>File Backup and Restore<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Backup to CD/DVD, Local hard disk, network share, Tape drive<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Full Backup supported (Rewrite the old data)<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>File size supported<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>File Compression technology<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Manual and Scheduled backup<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Command line utility<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Tool usability and manageability<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Detailed logs<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Support on Windows Server 2008 with tape drives. (Also please let
me know the Supported Operating systems)<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Thanks,<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 color=blue face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New";
color:blue'>Shain<o:p></o:p></span></font></p>
</div>
</body>
</html>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26520197Re: Removing folders from a tar2009-11-25T12:36:00Z2009-11-25T12:36:00ZERSEK Laszlo-2On Mon, 23 Nov 2009, Jessie Grenfell wrote:
<br><div class='shrinkable-quote'><br>> I'm creating a tar file (with a VBA script, but that shouldn't matter). The
<br>> command used to generate the file is below. The problem is, the tar file
<br>> includes the full path of the files that were included in the file. I need
<br>> to either create it or modify it afterwards so the resulting tar file
<br>> includes just the files in the last folder (8314048612111209). I realize
<br>> this is probably simple, but my attempts to add in the strip-components
<br>> option have resulted in syntax errors. Can anyone help with the correct
<br>> command for this?
<br>>
<br>> C:\Progra~1\GnuWin32\bin\bsdtar -cf
<br>> L:\HRA-LIDS\BatchFiles\2009-11-12\8314048612111209.tar
<br>> L:\HRA-LIDS\BatchFiles\2009-11-12\8314048612111209
</div><br>chdir to L:\HRA-LIDS\BatchFiles\2009-11-12 first, then
<br><br>tar -c -f 8314048612111209.tar 8314048612111209
<br><br>With GNU tar, you may want to try the -C option as well.
<br><br>lacos
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26513710Re: [Fwd: Bug#556114: patch]2009-11-25T06:35:04Z2009-11-25T06:35:04ZEric Blake-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br><br>According to Bdale Garbee on 11/25/2009 7:22 AM:
<br>> Issues not solved by this patch:
<br>> - For filesystems with a better time resolution than 1 second, more
<br>> files may be included in incremental backups than strictly necessary,
<br>> but never more than 1 second worth. IMHO this is preferable to the
<br>> alternative of some files not being included on filesystems with a
<br>> larger time resolution. Especially since this is not limited to the
<br>> snapshot case, but can (will) also happen during regular dumps - see
<br>> above.
<br><br>The gnulib module utimecmp helps deal with this. However, gnulib has also
<br>empirically determined that you need a window of at least 20 milliseconds,
<br>even with utimensat and filesystems that support full nanosecond
<br>resolution, since many OSs quantize timestamps to something like a 10
<br>millisecond boundary even though you can access the additional resolution.
<br> But 20 milliseconds is indeed smaller than 1 second, when there is enough
<br>support.
<br><br>> - For filesystems with a worse time resolution than 1 second, files
<br>> may still be left out of an incremental backup. In that case, the
<br>> behavior is no worse than it is now.
<br><br>The only file system in this category is FAT, and its resolution is 2
<br>seconds. But FAT has other problems, such as lack of permissions.
<br><br>- --
<br>Don't work too hard, make some time for fun as well!
<br><br>Eric Blake <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26513710&i=0" target="_top" rel="nofollow">ebb9@...</a>
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.9 (Cygwin)
<br>Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_top" rel="nofollow">http://enigmail.mozdev.org/</a><br><br>iEYEARECAAYFAksNQJgACgkQ84KuGfSFAYAKugCdEhUYjOuZs53Re04qesi9N0dU
<br>WmsAoJ2MXqNSTRfJaNLDoHryIqL1eAey
<br>=XxHM
<br>-----END PGP SIGNATURE-----
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26513569[Fwd: Bug#556114: patch]2009-11-25T06:22:06Z2009-11-25T06:22:06ZBdale GarbeeSergey,
<br><br>Forwarding this note from Rogier with a proposed patch for the
<br>incremental timing issue. He apparently sent it as a reply to the
<br>Debian bug tracking system without copying you, which I suspect means
<br>you would never see it. My apologies if this is a duplicate in your
<br>inbox.
<br><br>Bdale
<br><br />Hi,
<br><br>I have created the following small patch, which, solves the problem as
<br>much as possible without a major rework.
<br><br>Basically, instead of recording the start time of the backup in the
<br>incremental file list, it computes a time based on the most recent
<br>modification time of all files that are in the archive, and that were
<br>modified *before* the backup started. The computation consists of
<br>adding one second, and then trunctating the fractional part, unless
<br>that would make the time larger than the start time of the backup, in
<br>which case it is left unchanged. Effectively, if the filesystem is not
<br>being modified, the recorded timestamp now deterministically depends on
<br>the actual state of the filesystem instead of on the arbitrary time tar
<br>happens to be invoked.
<br><br>The result is that the next level incremental backup will contain all
<br>files modified since the youngest file that was in the backup, if that
<br>file was modified at least 1 second before the dump started. Files that
<br>were modified since: very shortly before, during or after the backup,
<br>will always be included in the next incremental backup.
<br><br>This patch also takes care of another problem: If the filesystem has a
<br>1-second resolution for its times, and if a backup starts at time T.100
<br>(T seconds + 100 milliseconds), and finishes at time T.300, and if
<br>directly thereafter, at T.400, a file is modified, its modification
<br>time will be stored (with 1-second resolution) as T.000. I.e. it will
<br>have a modification time earlier than the time of the backup (which tar
<br>stores as T.100). Therefore, that file will not be included in the next
<br>incremental backup.
<br><br>Similarly, with the same 1-second resolution, if tar starts at T.100,
<br>if it stores a file at T.200, and if at T.300, i.e. after it was dumped,
<br>but before tar terminates (which may be at T+1000), that file is
<br>modified, then the filesystem will record a modification time of T.000,
<br>and again, the next level incremental backup will not include the file.
<br><br>The patch was made against tar 1.20, and it passes all tests. One of the
<br>test cases required a small fix. The patch also applies to tar 1.22,
<br>passing all tests as well.
<br><br>Issues not solved by this patch:
<br>- For filesystems with a better time resolution than 1 second, more
<br> files may be included in incremental backups than strictly necessary,
<br> but never more than 1 second worth. IMHO this is preferable to the
<br> alternative of some files not being included on filesystems with a
<br> larger time resolution. Especially since this is not limited to the
<br> snapshot case, but can (will) also happen during regular dumps - see
<br> above.
<br>- For filesystems with a worse time resolution than 1 second, files
<br> may still be left out of an incremental backup. In that case, the
<br> behavior is no worse than it is now.
<br><br>Use it as you see fit. Comments etc. are welcome.
<br><br>Regards,
<br><br>Rogier
<br><br>------------------------------------------------------------------------
<br>diff -Naur tar-1.20/src/buffer.c tar-1.20-rjg1/src/buffer.c
<br>--- tar-1.20/src/buffer.c 2008-02-04 11:36:51.000000000 +0100
<br>+++ tar-1.20-rjg1/src/buffer.c 2009-11-25 11:24:10.000000000 +0100
<br>@@ -175,6 +175,29 @@
<br> gettime (&start_time);
<br> volume_start_time = start_time;
<br> last_stat_time = start_time;
<br>+ deterministic_start_time.tv_sec = TYPE_MINIMUM (time_t);
<br>+ deterministic_start_time.tv_nsec = 0;
<br>+}
<br>+
<br>+void
<br>+update_deterministic_start_time (struct timespec t)
<br>+{
<br>+ /* The deterministic start time is a timestamp that can be
<br>+ deterministically computed from the 'input' (i.e. filesystem
<br>+ status).
<br>+ Theoretically, the dump could have been started at any time
<br>+ between the last change to the filesystem before the actual
<br>+ start, and the first change after the actual start.
<br>+ The deterministic time will be that of the last change
<br>+ before the start of the dump.
<br>+ Using this value instead of the actual start time makes
<br>+ the file list of a listed-incremental backup deterministic
<br>+ as well
<br>+ */
<br>+
<br>+ if (timespec_cmp (t,deterministic_start_time) > 0
<br>+ && timespec_cmp (t,start_time) < 0)
<br>+ deterministic_start_time = t;
<br> }
<br>
<br> void
<br>diff -Naur tar-1.20/src/common.h tar-1.20-rjg1/src/common.h
<br>--- tar-1.20/src/common.h 2008-04-14 14:03:12.000000000 +0200
<br>+++ tar-1.20-rjg1/src/common.h 2009-11-25 11:24:10.000000000 +0100
<br>@@ -304,6 +304,9 @@
<br>
<br> /* Timestamps: */
<br> GLOBAL struct timespec start_time; /* when we started execution */
<br>+GLOBAL struct timespec deterministic_start_time; /* alternative start-time,
<br>+ deterministically computed from
<br>+ contents of filesystem */
<br> GLOBAL struct timespec volume_start_time; /* when the current volume was
<br> opened*/
<br> GLOBAL struct timespec last_stat_time; /* when the statistics was last
<br>@@ -406,6 +409,7 @@
<br> void archive_read_error (void);
<br> off_t seek_archive (off_t size);
<br> void set_start_time (void);
<br>+void update_deterministic_start_time (struct timespec t);
<br>
<br> void mv_begin (struct tar_stat_info *st);
<br> void mv_end (void);
<br>diff -Naur tar-1.20/src/create.c tar-1.20-rjg1/src/create.c
<br>--- tar-1.20/src/create.c 2009-11-25 07:45:14.000000000 +0100
<br>+++ tar-1.20-rjg1/src/create.c 2009-11-25 11:24:10.000000000 +0100
<br>@@ -1553,6 +1553,13 @@
<br> if (!is_dir && dump_hard_link (st))
<br> return;
<br>
<br>+ /* File will be dumped (albeit with some exceptions) - record time */
<br>+ if (listed_incremental_option)
<br>+ {
<br>+ update_deterministic_start_time(st->mtime);
<br>+ update_deterministic_start_time(st->ctime);
<br>+ }
<br>+
<br> if (is_dir || S_ISREG (st->stat.st_mode) || S_ISCTG (st->stat.st_mode))
<br> {
<br> bool ok;
<br>diff -Naur tar-1.20/src/incremen.c tar-1.20-rjg1/src/incremen.c
<br>--- tar-1.20/src/incremen.c 2008-04-14 14:03:13.000000000 +0200
<br>+++ tar-1.20-rjg1/src/incremen.c 2009-11-25 11:24:10.000000000 +0100
<br>@@ -19,6 +19,7 @@
<br>
<br> #include <system.h>
<br> #include <hash.h>
<br>+#include <time.h>
<br> #include <quotearg.h>
<br> #include "common.h"
<br>
<br>@@ -1285,11 +1286,37 @@
<br> fprintf (fp, "%s-%s-%d\n", PACKAGE_NAME, PACKAGE_VERSION,
<br> TAR_INCREMENTAL_VERSION);
<br>
<br>+ /* A level n+1 dump will include files modified after or *at* the time
<br>+ recorded in the directory file. Therefore, record a timestamp that
<br>+ is higher than the time of the newest file in the archive, but less
<br>+ than the start time of the dump.
<br>+ In order to make the time deterministic, it should be incremented
<br>+ with as little as possible, preferably with the filesystem's time
<br>+ resolution, which might be 1 msec, 1 usec, 1 sec, or 2 sec ! Also,
<br>+ before comparison, the start time of the dump should be rounded down
<br>+ to match the filesystem's resolution.
<br>+ That would add significant complexity. It may even be (probably is)
<br>+ impossible to reliably determine the resolution.
<br>+ So, this code just assumes the resolution is 1 second, and increments
<br>+ the recorded time to the next full second, if that remains less than
<br>+ the start time in seconds.
<br>+ Note that this will break if the filesystem's resolution is larger
<br>+ than 1 second, the result being that modified files may be left out of
<br>+ a level n+1 incremental dump.
<br>+ The more reliable solution would be to record more metadata for every
<br>+ file, but that is a nontrivial change.
<br>+ */
<br>+ if (deterministic_start_time.tv_sec < start_time.tv_sec)
<br>+ {
<br>+ deterministic_start_time.tv_sec += 1;
<br>+ deterministic_start_time.tv_nsec = 0;
<br>+ }
<br>+
<br> s = (TYPE_SIGNED (time_t)
<br>- ? imaxtostr (start_time.tv_sec, buf)
<br>- : umaxtostr (start_time.tv_sec, buf));
<br>+ ? imaxtostr (deterministic_start_time.tv_sec, buf)
<br>+ : umaxtostr (deterministic_start_time.tv_sec, buf));
<br> fwrite (s, strlen (s) + 1, 1, fp);
<br>- s = umaxtostr (start_time.tv_nsec, buf);
<br>+ s = umaxtostr (deterministic_start_time.tv_nsec, buf);
<br> fwrite (s, strlen (s) + 1, 1, fp);
<br>
<br> if (! ferror (fp) && directory_table)
<br>diff -Naur tar-1.20/tests/rename01.at tar-1.20-rjg1/tests/rename01.at
<br>--- tar-1.20/tests/rename01.at 2007-06-27 15:30:32.000000000 +0200
<br>+++ tar-1.20-rjg1/tests/rename01.at 2009-11-25 11:24:34.000000000 +0100
<br>@@ -32,6 +32,7 @@
<br> genfile --file foo/file2
<br> mkdir foo/bar
<br> genfile --file foo/bar/file
<br>+sleep 1
<br>
<br> echo "Creating base archive"
<br> tar -g incr -cf arch.1 -v foo
<br>-------------------------------------------------------------------------------
<br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26484711Removing folders from a tar2009-11-23T11:53:00Z2009-11-23T11:53:00ZJessie GrenfellI'm creating a tar file (with a VBA script, but that shouldn't matter). The command used to generate the file is below. The problem is, the tar file includes the full path of the files that were included in the file. I need to either create it or modify it afterwards so the resulting tar file includes just the files in the last folder (8314048612111209). I realize this is probably simple, but my attempts to add in the strip-components option have resulted in syntax errors. Can anyone help with the correct command for this?
<br><br>C:\Progra~1\GnuWin32\bin\bsdtar -cf L:\HRA-LIDS\BatchFiles\2009-11-12\8314048612111209.tar L:\HRA-LIDS\BatchFiles\2009-11-12\8314048612111209<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Help-f1808.html" embed="fixTarget[1808]" target="_top" >Gnu - Tar - Help</a></p>tag:old.nabble.com,2006:post-26457423gpg-zip --clear doesn't work (as expected)2009-11-21T06:43:53Z2009-11-21T06:43:53ZUwe ZybellIn the manpage of gpg --clearsign is descripted as making a signed file, that
<br>is even useful when gpg is not installed. So I understand gpg-zip --clear
<br>as (should) making a tar file that is even unpackable when gpg is not
<br>installed. But that is not so.
<br>I have included in this mail such a file, that I made by hand. As testdata
<br>it contains the (gzipped) key that was used to sign it. But I had to
<br>overcome some peculiarities, that I would call bugs. First I had to use
<br>MD5 as hash, because otherwise the header was too long to fit into the
<br>fileformat of tar. To do that I had to construct a special key. Even with
<br>MD5 tar steadfastly refused to write such a file although tar can read it.
<br>Your commercial is simply too long.
<br>To extract the example from this mail, you can use the command
<br><br> sed '/#[^.]*!/,/#[^.]*!/w'/tmp/somefile
<br><br>I have used a poor-man's ascii-armor to distinguish from the gpg-armor.
<br>It can be unpacked with the command
<br> sed -f /tmp/somefile /tmp/somefile|sort|sh>signed.tar
<br>That file signed.tar is an example for what I wanted to get from
<br>gpg-zip --clear
<br><br>#!/bin/sed -f
<br>#c0000000\055\055\055\055\055\102\105\107\111\116\040\120\107\120\040\123
<br>#c0000020\111\107\116\105\104\040\115\105\123\123\101\107\105\055\055\055
<br>#c0000040\055\055\012\110\141\163\150\072\040\115\104\065\012\116\157\164
<br>#c0000060\104\141\163\150\105\163\143\141\160\145\144\072\040\131\157\165
<br>#c0000100\040\156\145\145\144\040\107\156\165\120\107\040\164\157\040\166
<br>#c0000120\145\162\151\146\171\040\164\150\151\163\040\155\145\163\163\141
<br>#c0000140\147\145\012\012\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000160\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000200\000\000\000\000\000\000\000\000\061\061\062\067\066\066\063\061
<br>#c0000220\060\067\065\000\060\062\060\066\066\065\000\040\126\000\000\000
<br>#c0000240\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000260\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000300\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000320\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000340\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000360\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000400\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000420\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000440\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000460\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000500\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000520\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000540\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000560\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000600\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000620\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000640\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000660\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000700\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000720\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000740\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0000760\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001000\164\145\163\164\153\145\171\056\147\172\000\000\000\000\000\000
<br>#c0001020\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001040\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001060\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001100\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001120\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001140\000\000\000\000\060\060\060\060\066\064\064\000\060\060\060\061
<br>#c0001160\067\065\060\000\060\060\060\061\067\065\060\000\060\060\060\060
<br>#c0001200\060\060\060\063\062\064\066\000\061\061\062\067\066\066\062\062
<br>#c0001220\062\060\066\000\060\061\061\066\063\067\000\040\060\000\000\000
<br>#c0001240\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001260\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001300\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001320\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001340\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001360\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001400\000\165\163\164\141\162\040\040\000\165\163\145\162\000\000\000
<br>#c0001420\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001440\000\000\000\000\000\000\000\000\000\165\163\145\162\000\000\000
<br>#c0001460\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001500\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001520\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001540\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001560\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001600\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001620\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001640\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001660\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001700\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001720\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001740\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0001760\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0002000\037\213\010\010\206\044\373\112\000\003\164\145\163\164\153\145
<br>#c0002020\171\000\175\226\267\016\363\112\222\106\163\076\305\037\356\202
<br>#c0002040\270\103\043\211\042\027\330\240\105\357\105\157\062\172\357\075
<br>#c0002060\237\176\164\147\242\111\246\303\056\024\120\175\360\235\106\375
<br>#c0002100\365\327\357\174\130\136\324\376\174\371\357\237\257\363\121\104
<br>#c0002120\372\217\314\006\177\076\212\116\313\177\127\377\202\334\154\136
<br>#c0002140\252\241\377\277\077\174\277\175\371\077\073\366\217\347\077\210
<br>#c0002160\077\377\303\153\016\242\124\375\166\376\057\004\165\006\137\175
<br>#c0002200\330\231\240\206\306\374\000\106\327\102\257\300\361\341\233\334
<br>#c0002220\230\075\156\113\000\043\202\061\357\021\035\217\315\153\077\366
<br>#c0002240\240\070\206\323\145\321\066\113\013\146\215\037\002\044\221\247
<br>#c0002260\216\066\001\102\165\174\310\127\050\307\110\206\247\206\242\143
<br>#c0002300\315\213\246\034\345\340\367\143\357\044\257\162\232\111\005\134
<br>#c0002320\063\102\042\256\001\076\002\250\237\127\344\247\330\001\175\151
<br>#c0002340\313\113\132\052\002\065\031\171\223\021\066\123\102\062\265\147
<br>#c0002360\346\217\276\051\117\156\041\005\374\327\217\141\264\362\262\034
<br>#c0002400\000\016\330\252\270\006\027\160\341\240\213\013\337\167\310\313
<br>#c0002420\365\147\113\351\174\252\177\032\251\376\314\021\256\205\316\113
<br>#c0002440\145\201\334\067\104\251\042\310\304\312\351\065\125\307\311\271
<br>#c0002460\131\230\156\373\145\346\325\202\210\202\334\047\310\074\155\120
<br>#c0002500\066\105\266\353\314\217\013\240\155\105\226\166\377\164\261\212
<br>#c0002520\113\146\272\143\203\372\361\115\345\330\233\371\225\307\160\230
<br>#c0002540\200\173\001\061\324\307\107\242\257\012\041\370\120\322\342\367
<br>#c0002560\010\311\274\047\174\375\376\305\050\232\074\357\142\264\032\371
<br>#c0002600\134\275\324\321\333\273\310\303\220\273\011\272\041\207\255\107
<br>#c0002620\300\066\051\361\246\064\162\025\017\203\112\345\040\264\062\232
<br>#c0002640\243\155\110\230\031\005\040\150\144\362\116\374\025\045\212\170
<br>#c0002660\156\237\122\234\062\112\274\351\221\256\343\142\365\165\105\074
<br>#c0002700\207\101\375\204\276\315\162\207\012\047\162\207\237\113\066\162
<br>#c0002720\005\107\004\220\046\333\362\035\027\263\230\024\132\351\155\241
<br>#c0002740\277\334\242\261\161\001\157\226\004\363\346\355\202\124\373\144
<br>#c0002760\367\031\142\146\012\107\306\030\123\357\167\234\024\001\347\322
<br>#c0003000\150\246\336\054\224\134\034\136\251\347\012\307\013\201\166\370
<br>#c0003020\355\023\143\335\170\345\333\163\117\122\156\344\360\255\064\324
<br>#c0003040\167\010\172\241\351\062\375\220\130\103\061\352\224\167\357\224
<br>#c0003060\137\333\314\002\044\224\372\132\233\064\237\045\306\265\062\346
<br>#c0003100\313\075\171\030\133\314\123\165\340\035\133\202\267\150\150\023
<br>#c0003120\142\140\030\066\153\210\100\064\304\030\034\142\006\014\321\057
<br>#c0003140\200\103\133\373\302\101\134\021\050\264\121\010\277\002\307\031
<br>#c0003160\054\115\003\225\345\012\221\001\006\220\151\023\040\137\201\142
<br>#c0003200\344\062\051\074\253\357\176\067\145\026\120\042\332\205\006\351
<br>#c0003220\357\145\135\355\031\264\332\321\040\211\364\061\025\164\061\001
<br>#c0003240\230\106\216\000\135\020\007\247\274\051\244\022\162\232\264\346
<br>#c0003260\205\076\370\027\050\120\326\332\147\174\056\201\010\164\336\127
<br>#c0003300\305\345\160\343\323\207\176\303\034\107\305\252\230\264\057\037
<br>#c0003320\240\235\312\320\026\364\005\157\313\372\044\215\240\244\224\160
<br>#c0003340\310\255\362\171\342\021\136\034\144\056\154\062\070\203\061\344
<br>#c0003360\134\056\156\062\247\036\041\351\224\157\230\110\004\066\013\373
<br>#c0003400\225\142\242\326\032\217\270\242\131\366\140\232\230\343\034\357
<br>#c0003420\106\275\274\115\101\265\273\134\146\304\332\017\214\220\344\325
<br>#c0003440\067\014\236\202\114\113\041\164\325\156\103\065\072\233\221\306
<br>#c0003460\166\140\373\164\051\162\166\270\145\336\277\276\035\257\034\130
<br>#c0003500\102\001\053\070\100\321\225\260\271\045\053\354\317\051\076\256
<br>#c0003520\123\147\036\054\151\325\326\011\025\072\207\353\263\135\362\253
<br>#c0003540\277\035\323\355\230\163\161\244\275\133\004\327\003\124\204\103
<br>#c0003560\014\343\352\337\227\122\241\124\070\225\330\024\231\332\263\145
<br>#c0003600\066\171\213\174\007\056\177\300\041\307\361\231\112\266\103\015
<br>#c0003620\111\064\040\262\224\143\360\314\216\211\024\252\227\276\007\177
<br>#c0003640\107\076\221\220\020\146\047\334\272\066\300\030\270\204\226\375
<br>#c0003660\273\052\267\230\316\027\166\267\336\220\143\036\165\326\163\146
<br>#c0003700\071\047\340\003\120\021\310\360\351\171\213\204\007\317\245\176
<br>#c0003720\032\243\104\133\204\345\210\115\136\225\372\072\331\134\211\265
<br>#c0003740\261\372\043\057\130\004\113\202\131\205\174\132\131\060\346\114
<br>#c0003760\104\037\033\203\231\016\036\341\326\172\022\355\050\367\323\162
<br>#c0004000\067\007\141\262\373\236\074\233\003\144\214\316\121\220\274\222
<br>#c0004020\265\326\154\067\177\060\243\147\175\361\017\024\076\177\252\053
<br>#c0004040\312\113\072\237\337\323\244\203\265\111\173\163\214\116\164\312
<br>#c0004060\325\271\155\323\226\206\257\302\063\276\171\074\264\367\231\157
<br>#c0004100\162\060\047\050\107\133\026\234\327\173\122\314\220\071\234\051
<br>#c0004120\053\310\235\274\324\145\325\051\123\100\163\060\225\122\027\125
<br>#c0004140\306\104\377\315\333\307\144\104\027\073\251\000\041\325\033\003
<br>#c0004160\275\242\233\052\142\331\237\076\233\334\306\177\043\120\166\024
<br>#c0004200\075\111\104\335\270\276\037\070\061\170\244\035\125\116\231\037
<br>#c0004220\102\133\335\332\215\264\060\227\077\132\152\326\013\371\015\363
<br>#c0004240\175\310\040\307\223\025\353\053\302\067\121\300\066\177\203\004
<br>#c0004260\113\060\221\167\327\335\264\171\152\304\366\225\134\276\040\261
<br>#c0004300\225\335\003\365\304\336\074\354\236\265\102\176\052\321\062\214
<br>#c0004320\340\157\241\150\343\157\211\176\221\056\304\230\001\100\206\376
<br>#c0004340\103\030\107\052\200\104\371\340\242\162\106\100\102\126\244\106
<br>#c0004360\074\272\232\135\366\307\232\330\317\000\320\105\153\117\073\336
<br>#c0004400\075\256\241\060\302\345\040\036\277\044\276\321\341\024\006\067
<br>#c0004420\271\236\265\141\312\360\361\005\300\060\300\023\061\210\313\172
<br>#c0004440\331\013\053\141\017\244\155\154\155\137\216\033\106\155\341\115
<br>#c0004460\326\035\025\364\207\360\142\311\223\206\360\133\351\341\130\333
<br>#c0004500\047\244\344\176\361\232\342\306\046\165\156\236\054\066\241\045
<br>#c0004520\142\172\214\210\160\054\057\144\214\155\260\115\327\033\337\054
<br>#c0004540\211\215\131\057\213\035\370\232\202\375\005\215\217\347\317\001
<br>#c0004560\046\304\350\226\365\165\026\013\205\133\144\302\221\025\257\310
<br>#c0004600\035\125\222\155\326\122\107\207\332\254\164\225\170\315\002\150
<br>#c0004620\236\326\251\232\050\340\250\227\331\133\242\000\255\207\012\130
<br>#c0004640\203\005\040\250\373\317\247\060\301\217\302\307\220\376\375\224
<br>#c0004660\162\241\201\134\110\054\103\222\071\252\116\334\365\011\173\013
<br>#c0004700\260\374\357\343\371\065\160\240\231\337\020\040\301\017\115\143
<br>#c0004720\164\230\312\023\337\315\116\265\242\367\215\057\022\371\057\156
<br>#c0004740\245\273\324\016\202\364\355\222\356\135\356\132\206\247\111\237
<br>#c0004760\235\322\067\057\103\202\317\133\170\240\135\350\162\005\102\004
<br>#c0005000\014\101\175\200\212\027\165\060\034\233\243\177\057\367\352\026
<br>#c0005020\263\371\315\242\155\257\214\170\341\275\322\023\124\316\342\047
<br>#c0005040\221\206\234\172\007\353\115\216\064\065\077\053\050\313\334\062
<br>#c0005060\015\064\121\263\005\052\171\060\353\222\352\000\145\306\365\302
<br>#c0005100\114\222\027\062\335\312\060\326\367\044\057\350\234\317\131\076
<br>#c0005120\333\374\232\366\063\015\010\164\054\121\236\062\066\210\123\072
<br>#c0005140\043\070\350\114\316\312\255\146\027\261\302\221\072\327\000\032
<br>#c0005160\353\021\051\052\121\247\345\016\030\244\301\106\210\143\036\246
<br>#c0005200\276\247\216\347\060\116\376\025\134\037\266\230\113\032\372\177
<br>#c0005220\252\161\071\350\137\353\004\253\061\377\145\327\370\047\252\357
<br>#c0005240\070\047\221\010\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005260\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005300\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005320\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005340\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005360\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005400\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005420\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005440\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005460\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005500\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005520\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005540\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005560\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005600\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005620\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005640\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005660\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005700\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005720\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005740\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0005760\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006020\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006040\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006060\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006100\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006120\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006140\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006160\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006200\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006220\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006240\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006260\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006300\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006320\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006340\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006360\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006400\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006420\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006440\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006460\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006500\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006520\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006540\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006560\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006600\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006620\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006640\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006660\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006700\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006720\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006740\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0006760\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007020\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007040\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007060\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007100\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007120\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007140\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007160\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007200\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007220\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007240\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007260\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007300\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007320\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007340\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007360\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007400\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007420\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007440\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007460\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007500\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007520\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007540\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007560\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007600\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007620\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007640\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007660\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007700\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007720\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007740\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0007760\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
<br>#c0010000\012\055\055\055\055\055\102\105\107\111\116\040\120\107\120\040
<br>#c0010020\123\111\107\116\101\124\125\122\105\055\055\055\055\055\012\126
<br>#c0010040\145\162\163\151\157\156\072\040\107\156\165\120\107\040\166\061
<br>#c0010060\056\064\056\066\040\050\107\116\125\057\114\151\156\165\170\051
<br>#c0010100\012\012\151\121\103\126\101\167\125\102\123\166\163\171\122\160
<br>#c0010120\164\124\102\165\152\067\153\063\124\131\101\121\107\163\146\147
<br>#c0010140\121\101\170\155\146\104\124\065\144\062\062\126\143\053\171\116
<br>#c0010160\153\141\124\125\147\153\171\114\113\152\160\150\127\161\153\142
<br>#c0010200\053\171\012\067\143\066\157\164\162\125\102\164\107\154\125\113
<br>#c0010220\125\126\102\066\130\160\062\065\127\101\061\103\063\131\116\064
<br>#c0010240\162\160\152\112\061\060\147\154\156\126\114\110\064\151\063\160
<br>#c0010260\062\117\157\066\067\057\160\070\161\152\171\057\164\126\107\113
<br>#c0010300\143\071\065\012\150\157\153\150\153\101\102\167\121\113\107\114
<br>#c0010320\150\141\111\171\116\111\141\165\126\123\161\122\142\160\172\071
<br>#c0010340\124\142\131\057\060\141\150\063\155\171\127\053\115\163\132\161
<br>#c0010360\126\172\172\101\171\152\123\145\101\156\103\142\112\154\163\111
<br>#c0010400\131\166\062\152\012\110\121\171\154\154\141\142\062\071\102\157
<br>#c0010420\075\012\075\120\154\064\164\012\055\055\055\055\055\105\116\104
<br>#c0010440\040\120\107\120\040\123\111\107\116\101\124\125\122\105\055\055
<br>#c0010460\055\055\055\012
<br>$,/de:/a\
<br>':' df'\
<br>';export _=:-
<br>/:[^ez]/d
<br>s=9 z=: exec sh -c 'tar -cT- "$@"'"|od -vtoC| sed -e '"'$r'"$0' -e '/0 /!d' -e 'y/ /\\\\/' -e 's+^+#c+'| sort" "$0" "$@" #=
<br>/^#[^!]/s+^+';echo cdefghiABCDEFGH|tr '0-8c-iA-H\\012': '+
<br><br><br>__________________________________________________
<br>Do You Yahoo!?
<br>Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
<br><a href="http://mail.yahoo.com" target="_top" rel="nofollow">http://mail.yahoo.com</a><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26429716Re: [GNU tar 1.22] testsuite: 67 failed2009-11-19T08:14:22Z2009-11-19T08:14:22ZGene LeDucSergey Poznyakoff wrote:
<div class='shrinkable-quote'><br>> Gene LeDuc <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26429716&i=0" target="_top" rel="nofollow">gleduc@...</a>> ha escrit:
<br>>
<br>>> Here is tests/testsuite.log (zipped). Thanks for any help you can
<br>>> give.
<br>>
<br>> It is a bug in the testsuite: tar issues a diagnostics message which the
<br>> testsuite is not prepared to deal with. You can safely ignore the
<br>> error. It has already been fixed in the repository and the next version
<br>> (1.23) will include the fix.
<br>>
<br>> Regards,
<br>> Sergey
</div><br>Thanks for your quick response (and the good news)!
<br><br>Gene
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26457354Re: Error compiling from git master: misplaced comma2009-11-19T08:02:40Z2009-11-19T08:02:40ZRob Vermaas-2Obviously I was smart enough to forget to attach the patch, here it is.
<br><br>greetings,
<br>Rob
<br><br>2009/11/19 Rob Vermaas <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457354&i=0" target="_top" rel="nofollow">rob.vermaas@...</a>>:
<div class='shrinkable-quote'><div class='shrinkable-quote'><br>> Hi,
<br>>
<br>> while trying to compile tar from the master branch of the GIT
<br>> repository, I encountered the following errror:
<br>>
<br>> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../gnu -I../ -I../gnu
<br>> -I../lib -I../lib -g -O2 -c tar.c [b
<br>> tar.c: In function 'format_default_settings':
<br>> tar.c:914: error: expected expression before ')' token
<br>> make[2]: *** [tar.o] Error 1
<br>>
<br>> Attached is a patch to fix the problem of a misplaced comma.
<br>>
<br>> greetings,
<br>>
<br>> Rob
<br>>
<br>> --
<br>> Rob Vermaas
<br>>
<br>> [email] <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457354&i=1" target="_top" rel="nofollow">rob.vermaas@...</a>
<br>>
</div></div><br><br>--
<br>Rob Vermaas
<br><br>[email] <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457354&i=2" target="_top" rel="nofollow">rob.vermaas@...</a>
<br><br /><tt>[tar-remote-shell-correction.patch]</tt><br /><hr align="left" width="300" /><tt>diff --git a/src/tar.c b/src/tar.c
<br>index a1185f6..8662bf4 100644
<br>--- a/src/tar.c
<br>+++ b/src/tar.c
<br>@@ -907,9 +907,9 @@ format_default_settings (void)
<br> archive_format_string (DEFAULT_ARCHIVE_FORMAT),
<br> DEFAULT_ARCHIVE, DEFAULT_BLOCKING,
<br> quoting_style_args[DEFAULT_QUOTING_STYLE],
<br>- DEFAULT_RMT_COMMAND,
<br>+ DEFAULT_RMT_COMMAND
<br> #ifdef REMOTE_SHELL
<br>- REMOTE_SHELL
<br>+ ,REMOTE_SHELL
<br> #endif
<br> );
<br> }
<br></tt><hr align="left" width="300" /><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26425241Re: [GNU tar 1.22] testsuite: 67 failed2009-11-19T04:08:01Z2009-11-19T04:08:01ZSergey Poznyakoff-2Gene LeDuc <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26425241&i=0" target="_top" rel="nofollow">gleduc@...</a>> ha escrit:
<br><br>> Here is tests/testsuite.log (zipped). Thanks for any help you can
<br>> give.
<br><br>It is a bug in the testsuite: tar issues a diagnostics message which the
<br>testsuite is not prepared to deal with. You can safely ignore the
<br>error. It has already been fixed in the repository and the next version
<br>(1.23) will include the fix.
<br><br>Regards,
<br>Sergey
<br><br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26457331Problem while extracting an 53 GB .tar file2009-11-19T03:07:12Z2009-11-19T03:07:12ZSelliah K<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>ISMS-Logical Access Control</title>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="3074" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>I
have got a problem while extracting a 53 GB .tar file. The tar version is: tar
(GNU tar) 1.15.1.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Command
used: tar –xf export.tar<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Error:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>tar:
export.tar: Cannot read: Input/output error<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>tar:
At beginning of tape, quitting now<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>tar:
Error is not recoverable: exiting now<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Can
you please provide the solution to extract the archive file? <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Thanks
in advance<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Selliah
K<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'><o:p> </o:p></span></font></p>
</div>
<pre>DISCLAIMER:
Information transmitted by this e-mail may be proprietary to Ramco Systems Ltd., and / or the
authors of the information and is intended for use only by the individual or entity to which it is
addressed, and may contain confidential or legally privileged information. If you are not the
intended recipient or it appears that this mail has been forwarded to you without proper authority,
you are not authorised to access, read, disclose, copy, use or otherwise deal with it and any such
actions are prohibited and may be unlawful.
Internet communications cannot be guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, arrive late or contain viruses. Ramco Systems Limited therefore does
not accept liability for any errors, omissions, viruses or computer problems experienced as a
result of this transmission.
If you have received this e-mail in error, please notify us immediately at
mail to: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26457331&i=0" target="_top" rel="nofollow">mailadmin@...</a> and delete this mail from your records. Notice is hereby
given that no representation, contract or other binding obligation shall be created by this e-mail.
</pre></body>
</html>
<p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26416888[GNU tar 1.22] testsuite: 67 failed2009-11-18T10:39:04Z2009-11-18T10:39:04ZGene LeDucGreetings,
<br><br>Here is tests/testsuite.log (zipped). Thanks for any help you can give.
<br><br>Regards,
<br>Gene
<br><br /> <div class="small"><br/><img src="http://old.nabble.com/images/icon_attachment.gif" > <strong>testsuite.zip</strong> (71K) <a href="http://old.nabble.com/attachment/26416888/0/testsuite.zip" target="_top">Download Attachment</a></div><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26404123Re: Re: [GNU tar 1.22] testsuite: 1 3 4 25 52 failed, 18 19 46 48 56 57 59 69 passed unexpectedly2009-11-18T00:20:33Z2009-11-18T00:20:33ZGirish Shilamkar-3Thanks a lot. SLES11 distro was using diff 2.8.7-cvs. Once I replaced it
<br>with 2.8.1 all the tests passed.
<br><br>Regards,
<br>Girish
<br><br>On Wed, 2009-11-18 at 00:04 +0200, Sergey Poznyakoff wrote:
<div class='shrinkable-quote'><br>> Girish Shilamkar <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26404123&i=0" target="_top" rel="nofollow">Girish.Shilamkar@...</a>> ha escrit:
<br>>
<br>> > Hello,
<br>> > I ran a "make check" and found many failures in 1.22.
<br>>
<br>> Looks like your diff does not accept dash - (dash) as argument.
<br>>
<br>> Regards,
<br>> Sergey
<br>>
<br>>
</div><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26398665Re: [GNU tar 1.22] testsuite: 1 3 4 25 52 failed, 18 19 46 48 56 57 59 69 passed unexpectedly2009-11-17T14:04:21Z2009-11-17T14:04:21ZSergey Poznyakoff-2Girish Shilamkar <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26398665&i=0" target="_top" rel="nofollow">Girish.Shilamkar@...</a>> ha escrit:
<br><br>> Hello,
<br>> I ran a "make check" and found many failures in 1.22.
<br><br>Looks like your diff does not accept dash - (dash) as argument.
<br><br>Regards,
<br>Sergey
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26360954Re: --listed-incremental ignores changed files when using filesystem snapshots2009-11-15T08:59:14Z2009-11-15T08:59:14ZJean-Louis Martineau-2I already found the documentation and found that the files mtime are in
<br>in the snapshot file, and so there is no easy fix.
<br><br>A temporary workaround could be to change the mtime in the snapshot file
<br>with the time of the creation of the filesysytem snapshot.
<br><br>Jean-Louis
<br><br>Sergey Poznyakoff wrote:
<div class='shrinkable-quote'><br>> Jean-Louis Martineau <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26360954&i=0" target="_top" rel="nofollow">martineau@...</a>> ha escrit:
<br>>
<br>>
<br>>> It is a major bug for all users that use filesystem snapshot to make backup.
<br>>>
<br>>
<br>> I did not argue whether this could be considered a bug or not. I only
<br>> described the way tar works.
<br>>
<br>>
<br>>> What is the reference timestamp stored in the snapshot file? Is it
<br>>> - the time the backup started?
<br>>> - the time when the file was put in the archive?
<br>>> - the mtime of the file when it was put in the archive?
<br>>>
<br>>
<br>> The first. It is documented in the Tar Manual, Appendix D.
<br>>
<br>> Each file's mtime is compared with the time the previous backup
<br>> was created. In the case reported by Bdale, the actual file's mtime
<br>> happens to be older than that, so it is not considered for the next
<br>> backup.
<br>>
<br>> Let T be the time of mounting mnt-snap (line 26 of the script), in
<br>> seconds. Then, in this testcase, approximate mtimes of the `somefile'
<br>> before creating level-0 backup file will be:
<br>>
<br>> Backup creation time T+4
<br>> ./mnt-snap/somefile mtime T-1
<br>> ./mnt/somefile mtime T+3
<br>>
<br>> At the time of level-1 backup, tar notices that somefile is one second
<br>> younger than the level-0 backup and therefore does not archive it.
<br>>
<br>>
<br>>> A file should be in the incremental if its mtime is newer than any of
<br>>> these.
<br>>>
<br>>
<br>> Right. This would imply a major (or even complete) rewrite of the
<br>> incremental backup support. That's why I said that I could not propose
<br>> any immediate solution. FWIW, I can get to rewriting the incremental code
<br>> only after releasing version 1.23, which is scheduled to the end of
<br>> November.
<br>>
<br>> Regards,
<br>> Sergey
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>>
</div><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26360543Re: --listed-incremental ignores changed files when using filesystem snapshots2009-11-15T08:17:00Z2009-11-15T08:17:00ZSergey Poznyakoff-2Jean-Louis Martineau <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26360543&i=0" target="_top" rel="nofollow">martineau@...</a>> ha escrit:
<br><br>> It is a major bug for all users that use filesystem snapshot to make backup.
<br><br>I did not argue whether this could be considered a bug or not. I only
<br>described the way tar works.
<br><br>> What is the reference timestamp stored in the snapshot file? Is it
<br>> - the time the backup started?
<br>> - the time when the file was put in the archive?
<br>> - the mtime of the file when it was put in the archive?
<br><br>The first. It is documented in the Tar Manual, Appendix D.
<br><br>Each file's mtime is compared with the time the previous backup
<br>was created. In the case reported by Bdale, the actual file's mtime
<br>happens to be older than that, so it is not considered for the next
<br>backup.
<br><br>Let T be the time of mounting mnt-snap (line 26 of the script), in
<br>seconds. Then, in this testcase, approximate mtimes of the `somefile'
<br>before creating level-0 backup file will be:
<br><br> Backup creation time T+4
<br> ./mnt-snap/somefile mtime T-1
<br> ./mnt/somefile mtime T+3
<br><br>At the time of level-1 backup, tar notices that somefile is one second
<br>younger than the level-0 backup and therefore does not archive it.
<br><br>> A file should be in the incremental if its mtime is newer than any of
<br>> these.
<br><br>Right. This would imply a major (or even complete) rewrite of the
<br>incremental backup support. That's why I said that I could not propose
<br>any immediate solution. FWIW, I can get to rewriting the incremental code
<br>only after releasing version 1.23, which is scheduled to the end of
<br>November.
<br><br>Regards,
<br>Sergey
<br><br><br><br><br>
<br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26359566Re: --listed-incremental ignores changed files when using filesystem snapshots2009-11-15T06:28:21Z2009-11-15T06:28:21ZJean-Louis Martineau-2Sergey Poznyakoff wrote:
<div class='shrinkable-quote'><br>> Hi Bdale,
<br>>
<br>>
<br>>> When creating incremental backups using snapshot filesystems, tar fails
<br>>> to include files in a level 1 backup (presumably any level > 0) if they
<br>>> were modified in the original filesystem between the time the snapshot
<br>>> was created and the time the level 0 backup was created of the
<br>>> snapshot.
<br>>>
<br>>
<br>> Yes, it is a known fact. There is a certain lapse of time between a
<br>> file is registered in the incremental snapshot and actually archived.
<br>> If it changes in between, these changes are not stored in the snapshot.
<br>>
</div>That's not the bug reported by Bdale.
<br>He backup a snapshot filesystem, there is no change in the filesystem
<br>during the backup, the change are made in the original filesystem.
<br>The change made between the filesystem snapshot creation and the backup
<br>time will not be included in the next higher level backup.
<br>It is a major bug for all users that use filesystem snapshot to make backup.
<br><div class='shrinkable-quote'><br>>> I have had a look at the source, and the cause seems to be that the option
<br>>> newer_mtime_option is set from the creation time of the previous incremental
<br>>> archive (in incremen.c:read_incr_db_01 and incremen.c:read_incr_db_2)
<br>>> While I can't think of any good reason to set this option at all, except as a
<br>>> (failed) attempt to avoid unnecessary work, I cannot assess the full
<br>>> impact of simply removing the code in question.
<br>>>
<br>>
<br>> The full impact of this would be rendering the incremental backup code
<br>> completely inoperational and useless: tar's incremental backups are
<br>> based on comparing file's mtimes with the reference timestamp stored in
<br>> the snapshot file.
<br>>
</div><br>What is the reference timestamp stored in the snapshot file? Is it
<br> - the time the backup started?
<br> - the time when the file was put in the archive?
<br> - the mtime of the file when it was put in the archive?
<br><br>A file should be in the incremental if its mtime is newer than any of these.
<br><br>Jean-Louis
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26357913Re: --listed-incremental ignores changed files when using filesystem snapshots2009-11-15T02:15:21Z2009-11-15T02:15:21ZSergey Poznyakoff-2Hi Bdale,
<br><br>> When creating incremental backups using snapshot filesystems, tar fails
<br>> to include files in a level 1 backup (presumably any level > 0) if they
<br>> were modified in the original filesystem between the time the snapshot
<br>> was created and the time the level 0 backup was created of the
<br>> snapshot.
<br><br>Yes, it is a known fact. There is a certain lapse of time between a
<br>file is registered in the incremental snapshot and actually archived.
<br>If it changes in between, these changes are not stored in the snapshot.
<br><br>> I have had a look at the source, and the cause seems to be that the option
<br>> newer_mtime_option is set from the creation time of the previous incremental
<br>> archive (in incremen.c:read_incr_db_01 and incremen.c:read_incr_db_2)
<br>> While I can't think of any good reason to set this option at all, except as a
<br>> (failed) attempt to avoid unnecessary work, I cannot assess the full
<br>> impact of simply removing the code in question.
<br><br>The full impact of this would be rendering the incremental backup code
<br>completely inoperational and useless: tar's incremental backups are
<br>based on comparing file's mtimes with the reference timestamp stored in
<br>the snapshot file.
<br><br>Right now I cannot propose any immediate solution to this.
<br><br>Regards,
<br>Sergey
<br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>tag:old.nabble.com,2006:post-26339999--listed-incremental ignores changed files when using filesystem snapshots2009-11-13T09:11:18Z2009-11-13T09:11:18ZBdale GarbeeA user of my Debian package of tar provided this very thorough analysis
<br>of a problem when using tar to back up systems where file system
<br>snapshots are in use.
<br><br>Thoughts?
<br><br>Bdale
<br><br><br />Package: tar
<br>Version: 1.20-1
<br>Severity: normal
<br><br>When creating incremental backups using snapshot filesystems, tar fails
<br>to include files in a level 1 backup (presumably any level > 0) if they
<br>were modified in the original filesystem between the time the snapshot
<br>was created and the time the level 0 backup was created of the
<br>snapshot.
<br>(actually, they are not included if their modification times are less
<br>than the creation time of of the higher-level incremental backup -
<br>whatever may have been the cause: the use of a snapshot, a bad system
<br>clock, etc.)
<br><br>The net result is that it may not be possible to restore the filesystem
<br>to the state at the time of last backup: files that were changed may
<br>not have their latest version in any archive. Only level 0 archives
<br>will be complete.
<br><br>I.e.:
<br>- Level 0 backup
<br> (e.g. sunday full backup)
<br> - create snapshot of filesystem
<br> - (system is busy: some files modified on original filesystem)
<br> - create level 0 archive of snapshot
<br>- Level 1 backup
<br> (e.g. monday level 1 incremental backup)
<br> - create snapshot of filesystem
<br> - create level 1 archive of snapshot
<br>- Restore backup
<br> (e.g. tuesday afternoon after crash tuesday morning)
<br> - restore level 0 backup
<br> - restore level 1 backup
<br> (files modified on sunday, between shapshot and archive creation
<br> are now again at their pre-sunday versions. Changes made on sunday
<br> are lost)
<br><br>I have had a look at the source, and the cause seems to be that the option
<br>newer_mtime_option is set from the creation time of the previous incremental
<br>archive (in incremen.c:read_incr_db_01 and incremen.c:read_incr_db_2)
<br>While I can't think of any good reason to set this option at all, except as a
<br>(failed) attempt to avoid unnecessary work, I cannot assess the full impact of
<br>simply removing the code in question.
<br><br>The code seems to be present since the file's creation (1997-04-24) and in
<br>that version, it has a 'FIXME' comment about the dubious nature of it. The
<br>comment is no longer in the next version of the file, but the code stayed.
<br>(version dated 2003-08-31, which has extensive restructuring and modification)
<br><br>The following script demonstrates the behavior:
<br>Basically, it implements the testcase outlined above
<br>Make sure to run this in an empty directory - the script does some indiscriminate
<br>cleaning up.
<br>-------------------------------------------------------------------------------
<br># Clean up stuff from previous tests (indiscriminate)
<br>umount ./mnt* 2> /dev/null
<br>rm -rf filesys* mnt* backup*
<br><br>set -v
<br><br># Create & mount test filesystem
<br>dd if=/dev/zero of=filesys bs=1k count=200 2> /dev/null
<br>mke2fs -F -q ./filesys
<br>mkdir mnt
<br>mount -o loop ./filesys ./mnt
<br><br># Create files, & let them age
<br>echo "somefile, first version" > mnt/somefile
<br>echo "otherfile, first version" > mnt/otherfile
<br>echo "yetanotherfile, first version" > mnt/yetanotherfile
<br>echo "fourthfile, first version" > mnt/fourthfile
<br>echo "fifthfile, first version" > mnt/fifthfile
<br>sleep 1
<br><br># Start making backup: create and mount snapshot
<br>mount -o remount -r ./mnt
<br>cp filesys filesys-snap
<br>mount -o remount -w ./mnt
<br>mkdir -p mnt-snap
<br>mount -r -o loop ./filesys-snap ./mnt-snap
<br><br># Processing backup scripts takes some time; in the mean
<br># time, original filesystem is in use
<br>sleep 1
<br>echo "somefile, second version" > mnt/somefile
<br>rm mnt/fourthfile
<br>sleep 1
<br><br># Backup script gets around to running tar on snapshot filesystem
<br>tar -cvf backup.0.tar -g backup.0.list --no-check-device -C mnt-snap .
<br>umount ./mnt-snap
<br># (snapshot could be removed now.)
<br><br># Usage of original filesystem continues
<br>sleep 1
<br>echo "otherfile, second version" > mnt/otherfile
<br>rm mnt/fifthfile
<br>echo "newfile, first version" > mnt/newfile
<br>sleep 1
<br><br># Time for an incremental backup.
<br># Normally, this would be done using a snapshot, but for the
<br># sake of this test, that is not necessary
<br># Note that mnt/somefile was modified, but is not archived.
<br># The problem: it was modified in the original filesystem, *before* the
<br># timestamp recorded in the level 0 backup's list file
<br>cp backup.0.list backup.1.list
<br>tar -cvf backup.1.tar -g backup.1.list --no-check-device -C mnt .
<br><br># Additional verification that the level 1 backup is indeed incomplete:
<br># Restoring everything from backup
<br>mkdir mnt2
<br>tar -xGf backup.0.tar -C mnt2
<br>tar -xGf backup.1.tar -C mnt2
<br>diff mnt mnt2
<br>-------------------------------------------------------------------------------
<br><br>Output is the following:
<br>-------------------------------------------------------------------------------
<br># Create & mount test filesystem
<br>dd if=/dev/zero of=filesys bs=1k count=200 2> /dev/null
<br>mke2fs -F -q ./filesys
<br>mkdir mnt
<br>mount -o loop ./filesys ./mnt
<br><br># Create files, & let them age
<br>echo "somefile, first version" > mnt/somefile
<br>echo "otherfile, first version" > mnt/otherfile
<br>echo "yetanotherfile, first version" > mnt/yetanotherfile
<br>echo "fourthfile, first version" > mnt/fourthfile
<br>echo "fifthfile, first version" > mnt/fifthfile
<br>sleep 1
<br><br># Start making backup: create and mount snapshot
<br>mount -o remount -r ./mnt
<br>cp filesys filesys-snap
<br>mount -o remount -w ./mnt
<br>mkdir -p mnt-snap
<br>mount -r -o loop ./filesys-snap ./mnt-snap
<br><br># Processing backup scripts takes some time;
<br># in the mean time, original filesystem is in use
<br>sleep 1
<br>echo "somefile, second version" > mnt/somefile
<br>rm mnt/fourthfile
<br>sleep 1
<br><br># Backup script gets around to running tar on snapshot filesystem
<br>tar -cvf backup.0.tar -g backup.0.list --no-check-device -C mnt-snap .
<br>tar: ./lost+found: Directory is new
<br>./
<br>./lost+found/
<br>./fifthfile
<br>./fourthfile
<br>./otherfile
<br>./somefile
<br>./yetanotherfile
<br>umount ./mnt-snap
<br># (snapshot could be removed now.)
<br><br># Usage of original filesystem continues
<br>sleep 1
<br>echo "otherfile, second version" > mnt/otherfile
<br>rm mnt/fifthfile
<br>echo "newfile, first version" > mnt/newfile
<br>sleep 1
<br><br># Time for an incremental backup.
<br># Normally, this would be done using a snapshot, but for the
<br># sake of this test, that is not necessary
<br># Note that mnt/somefile was modified, but is not archived.
<br># The problem: it was modified in the original filesystem, *before* the
<br># level 0 backup started
<br>cp backup.0.list backup.1.list
<br>tar -cvf backup.1.tar -g backup.1.list --no-check-device -C mnt .
<br>./
<br>./lost+found/
<br>./newfile
<br>./otherfile
<br><br># Additional verification that the level 1 backup is indeed incomplete:
<br># Restoring everything from backup
<br>mkdir mnt2
<br>tar -xGf backup.0.tar -C mnt2
<br>tar -xGf backup.1.tar -C mnt2
<br>diff mnt mnt2
<br>Common subdirectories: mnt/lost+found and mnt2/lost+found
<br>diff mnt/somefile mnt2/somefile
<br>1c1
<br>< somefile, second version
<br>---
<br>> somefile, first version
<br>-------------------------------------------------------------------------------
<br><br><br>Note: The same kind of behavior is seen when a file is modified shortly
<br>*after* an archive was created:
<br>Test script:
<br>-------------------------------------------------------------------------------
<br># remove leftovers from previous run
<br>rm -rf dir*
<br><br>set -v
<br><br># setup directory tree & let age
<br>mkdir dir
<br>touch dir/{a,b,c}
<br>sleep 1
<br><br># Create archive; Immediately thereafter, modify a file
<br>tar -cvf dir.0.tar -g dir.0.list dir
<br>touch dir/a
<br><br># Wait & modify more files
<br>sleep 1
<br>touch dir/b
<br><br># Create incremental archive.
<br># In general, dir/a will not be included, even though
<br># it was modified after the level 0 archive was created
<br># (i.e. I haven't seen it included, even though I assume
<br># that there is a chance it will be, depending on the
<br># timing)
<br>cp dir.0.list dir.1.list
<br>tar -cvf dir.1.tar -g dir.1.list dir
<br>-------------------------------------------------------------------------------
<br><br>Output of the script:
<br>-------------------------------------------------------------------------------
<br># setup directory tree & let age
<br>mkdir dir
<br>touch dir/{a,b,c}
<br>sleep 1
<br><br># Create archive; Immediately thereafter, modify a file
<br>tar -cvf dir.0.tar -g dir.0.list dir
<br>dir/
<br>dir/a
<br>dir/b
<br>dir/c
<br>touch dir/a
<br><br># Wait & modify more files
<br>sleep 1
<br>touch dir/b
<br><br># Create incremental archive.
<br># In general, dir/a will not be included, even though
<br># it was modified after the level 0 archive was created
<br># (i.e. I haven't seen it included, even though I assume
<br># that there is a chance it will be, depending on the
<br># timing)
<br>cp dir.0.list dir.1.list
<br>tar -cvf dir.1.tar -g dir.1.list dir
<br>dir/
<br>dir/b
<br>-------------------------------------------------------------------------------
<br><br>-- System Information:
<br>Debian Release: 5.0.3
<br> APT prefers stable
<br> APT policy: (500, 'stable')
<br>Architecture: i386 (i686)
<br><br>Kernel: Linux 2.6.26-2-486
<br>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
<br>Shell: /bin/sh linked to /bin/bash
<br><br>Versions of packages tar depends on:
<br>ii libc6 2.7-18 GNU C Library: Shared libraries
<br><br>tar recommends no packages.
<br><br>Versions of packages tar suggests:
<br>ii bzip2 1.0.5-1 high-quality block-sorting file co
<br>pn ncompress <none> (no description available)
<br><br>-- no debconf information
<br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/Gnu---Tar---Bugs-f1807.html" embed="fixTarget[1807]" target="_top" >Gnu - Tar - Bugs</a></p>