Message-ID: <4530DC76.5040408@byu.net>
Date: Sat, 14 Oct 2006 06:47:50 -0600
From: Eric Blake <ebb9@byu.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: cygwin@cygwin.com
Subject: Re: zero byte /bin/bash file - what creates it?
References: <200610112043.k9BKh1Lr008690@tigris.pounder.sol.net> <452D6B16.9070407@cygwin.com> <200610112311.k9BNBrnW009619@tigris.pounder.sol.net> <200610140551.k9E5pfgT027163@tigris.pounder.sol.net>
In-Reply-To: <200610140551.k9E5pfgT027163@tigris.pounder.sol.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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

According to Tom Rodman on 10/13/2006 11:51 PM:
> 
> tar seems to be following the pre-existing soft link on the file system,
> and then writing to that target, instead of just replacing the soft
> link on the file system.  

Odd, I'll have to look further into it when I get time.  Could it also be
related to the fact that the symlink does not contain the .exe extension?
 And now that tar 1.15.92 is out, I'm due to release an upgrade, anyway.

> 
> This approach does not have any problems:
> 
>   tar zUxf /tmp/foo.tar.gz
> 
- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
volunteer cygwin tar maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMNx284KuGfSFAYARAtXAAJ9C5A52kFlvkEscQkdVmejdYGTvcACeIWV7
BPDZ0JM89FtyDvbe8sZqoqE=
=gv+H
-----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/