Tsvetkov, Vladimir (external) <[EMAIL PROTECTED]> wrote:
> Hello,
> We are using the gtar (version 1.13) for creating and updating the
> backup.
Please upgrade your version. The latest tar release is 1.16
Regards,
Sergey
Ch4p1n Loko <[EMAIL PROTECTED]> wrote:
> lo utilice asi
> tar xvfz archivo.tar.gz y sako en el siguiente mensaje.
>
>
> Esta* versiĆ³n de tar tiene por defecto:
> --format=gnu -f- -b20 --rmt-command=/usr/sbin/rmt --rsh-command=/usr/bin/rsh
Por favor, verifique el valor del variable de entorno TA
<[EMAIL PROTECTED]> wrote:
> But I found that stdout was corrupted after calling tarMain in my code
> .because printf is not printing any thing in console.
Before returning main() closes both stdout and stderr.
Regards,
Sergey
Karl Berry <[EMAIL PROTECTED]> wrote:
> I typed (by mistake):
> tar czfT x.tgz `cat /tmp/b`
>
> and got:
> Segmentation fault
Thank you. I have installed the following fix:
2006-11-01 Sergey Poznyakoff <[EMAIL PROTECTED]>
* src/tar.c: Handle zero-length entries in a files-from file
Thank you.
Regards,
Sergey
Eelco Dolstra <[EMAIL PROTECTED]> wrote:
> It seems that GNU tar 1.16 has a problem unpacking archives that have symlinks
> in read-only directories. Example:
Thank you. Here is the fix:
Index: src/extract.c
===
RCS file: /cvsroot/
Hi,
It seems that GNU tar 1.16 has a problem unpacking archives that have symlinks
in read-only directories. Example:
$ tar --version
tar (GNU tar) 1.16
...
$ mkdir archive
$ ln -s /foo archive/symlink
$ chmod -w archive
$ tar cvf archive.tar archive/
archive/
archive/symlink
$ mkdir unpack