This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: tar Does Not Handle Win32 Pathnames ...
- To: Cygwin <cygwin at sourceware dot cygnus dot com>
- Subject: Re: tar Does Not Handle Win32 Pathnames ...
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Thu, 25 May 2000 12:03:05 -0400
- References: <392D3AF0.3E43D3F0@dothill.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Thu, May 25, 2000 at 10:38:40AM -0400, Jason Tishler wrote:
>Date: Thu, 25 May 2000 10:38:40 -0400
>From: Jason Tishler <Jason.Tishler@dothill.com>
>Organization: Dot Hill Systems Corporation
>To: Cygwin <cygwin@sourceware.cygnus.com>
>Subject: tar Does Not Handle Win32 Pathnames ...
>
>... but other commands like gunzip, ls, etc. do:
>
> $ ls C:/temp/make-3.79.tar.gz
> C:/temp/make-3.79.tar.gz
>
> $ tar -tvzf C:/temp/make-3.79.tar.gz
> tar (grandchild): Cannot open archive C:/temp/make-3.79.tar.gz
> ...
>
> $ gunzip C:/temp/make-3.79.tar.gz
>
> $ ls C:/temp/make-3.79.tar
> C:/temp/make-3.79.tar
>
> $ tar -tvf C:/temp/make-3.79.tar
> tar: Cannot open C:/temp/make-3.79.tar
> ...
>
>Is the above expected behavior?
Yes. Tar is a port of a unix program. A colon in a pathname indicates
that tar should access a remote host named 'c'.
Check tar's help output for ways around this. Look for the word 'colon'.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com