Message-Id: <200610112311.k9BNBrnW009619@tigris.pounder.sol.net>
From: cygzx AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: zero byte /bin/bash file - what creates it?
In-reply-to: <452D6B16.9070407@cygwin.com>
References: <200610112043 DOT k9BKh1Lr008690 AT tigris DOT pounder DOT sol DOT net> <452D6B16 DOT 9070407 AT cygwin DOT com>
Date: Wed, 11 Oct 2006 18:11:52 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Wed 10/11/06 18:07 EDT cygwin AT cygwin DOT com wrote:
> Are you untarring files into '/' and does that tar file have a '/bin/bash' file?

Thanks Larry. I was untarring to a subdir below root. I can check the
tar archive, but I doubt it has a bash file w/"000" perms, even if it
did I would expect that to end up below the sub-dir; this problem may
have nothing to do w/tar- I was also fixing up perms in that subdir tree
piping the already saved tar STDERR to a series of commands, and finally
to "xargs chmod u+rw". I'm content to let this thread die ( I know I'm
not supplying enough info ). If I unravel it I'll report back.

--
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/