X-Spam-Check-By:	sourceware.org
Message-ID:	<454B48C8.3010009@byu.net>
Date:	Fri, 03 Nov 2006 06:48:56 -0700
From:	Eric Blake <ebb9 AT byu DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666
MIME-Version:	1.0
To:	Mike Dieter <quincunx12252000 AT hotmail DOT com>
CC:	cygwin AT cygwin DOT com, bug-tar AT gnu DOT org
Subject:	Re: [Bug-tar] tar error
References:	<BAY111-F1A1968EBB17BB6C0A468DCAFF0 AT phx DOT gbl>
In-Reply-To:	<BAY111-F1A1968EBB17BB6C0A468DCAFF0@phx.gbl>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Mike Dieter on 11/2/2006 3:26 PM:
> tar version: 1.15.91
> 
> I am using Cygwin (see attachment for facts) on an IBM XP home edition.

Cygwin now ships with tar 1.16; consider upgrading.

> 
> $ tar -ztvf C:/download/Majordomo.tar.gz
> C: Unknown Host

There's your problem.  If you are using cygwin, it is assumed that you
want a POSIX environment.  On POSIX environments, the notation
c:/download/Majordomo.tar.gz tells tar to go find the remote machine named
"C" and tar the file "/download/Majordomo.tar.gz".  Cygwin is no exception
on this front, since it's goal is a POSIX-y environment on Windows.  If
you want DOS style paths to work with tar, then use a DOS compilation of
tar, such as the version provided by mingw.

> So I changed it to:
> tar -ztvf /cygdrive/c/download/Majordomo.tar.gz
> AND IT WORED!

Where as that is a POSIX path, so you are correct that it will work on
cygwin (although it won't work on the above-mentioned mingw version).

> 
> I would HOPE that BOTH would work under  Cygwin...

This is not an upstream bug in tar, nor is it a cygwin bug.  It is a
design decision.  And there was probably no need for you to slam the
upstream bug-tar list with so much information, since your problem usage
was localized to cygwin, and not indicative of an upstream tar bug.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFS0jI84KuGfSFAYARAve4AJ0crFtj9q1mqinXVTgCkBYydVFlvgCggNnG
l4JC1yt6ySkwwV9HBhznpJU=
=IM5W
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -