RE: tar 1.15.91 doesn't support mixed mode paths

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

RE: tar 1.15.91 doesn't support mixed mode paths

ejohanson
tar 1.15.91 does not support the use of mixed-mode paths via the "f"
command-line option.  for example, if you run the command:
        tar tvf c:/temp/myfile.tar

then you get the following error message from tar:
        d: Unknown Host
        tar: c\:/temp/myfile.tar: Cannot open: Input/Output error
        ar: Error is not recoverable: exiting now

tar is one of the few commands with a problem like this.  it would be
really nice to see it fixed.  based on the error message "d: Unknown
Host", it sounds like tar is trying to interpret the colon as a
node-name seperator, similar to the way that "rcp" does.  is that a
feature of tar?  i didn't see anything like that in the documentation
for tar but i could have missed it.

-Eric Johanson
Newpoint Technologies, Inc.
 
Reply | Threaded
Open this post in threaded view
|

Re: tar 1.15.91 doesn't support mixed mode paths

Christopher Faylor-2
On Wed, Aug 16, 2006 at 03:35:22PM -0400, Eric Johanson wrote:

>tar 1.15.91 does not support the use of mixed-mode paths via the "f"
>command-line option.  for example, if you run the command:
> tar tvf c:/temp/myfile.tar
>
>then you get the following error message from tar:
> d: Unknown Host
> tar: c\:/temp/myfile.tar: Cannot open: Input/Output error
> ar: Error is not recoverable: exiting now
>
>tar is one of the few commands with a problem like this.  it would be
>really nice to see it fixed.  based on the error message "d: Unknown
>Host", it sounds like tar is trying to interpret the colon as a
>node-name seperator, similar to the way that "rcp" does.  is that a
>feature of tar?  i didn't see anything like that in the documentation
>for tar but i could have missed it.

The above is not a bug and, if it was, this is not a bug-reporting
mailing list.

I've unsubscribed you from this list.  If you want to discuss this issue,
please use the main cygwin list.

cgf