Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: localhost.localdomain: ronald set sender to blytkerchan AT users DOT sourceforge DOT net using -f Date: Tue, 12 Aug 2003 17:43:30 +0200 From: Ronald Landheer-Cieslak To: cygwin AT cygwin DOT com Subject: Re: Managed mode problem Message-ID: <20030812154330.GB13155@linux_rln.harvest> Reply-To: cygwin AT cygwin DOT com References: <20030812123923 DOT GA13155 AT linux_rln DOT harvest> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Disclaimer: I had nothing to do with it - I swear! X-loop: linux_rln.harvest On Tue, Aug 12, 2003 at 10:09:32AM -0400, Igor Pechtchanski wrote: > On Tue, 12 Aug 2003, Ronald Landheer-Cieslak wrote: > > > Hello all, > > > > I was trying to build nn under Cygwin, and found it contains a file called > > aux.sh, a file called aux.c and a file called aux.h; none of which Windows > > would like, of course. > > > > Having Cygwin 1.5.2 installed, I thought I'd try out that spiffy new managed > > mode, as running `tar xzvf nn-6.6.5.tar.Z' failed miserably (hung until I > > killed Bash, tar and gz) so I put my tarball in /foo, which is mounted in > > managed mode (see cygcheck.out for details on my system). > > > > That didn't change the behaviour of tar/gzip much, though, as the process > > still seems to hang while untarring the tarball on the managed mount. > > > > Below are the cygcheck output, the tarball itself and the last stackdump from > > gzip. If you need anything else, I'll be happy to provide. > > > > HTH > > rlc > > Ronald, > > Upon re-reading your message, I realized something: to make use of managed > mode, you have to extract *to* a directory mounted in managed mode. which is what I'm doing - unless the managed-ness of the mount doesn't propagate to the subdirs of the mount (i.e. the ones I'm creating) > IIUC, the directory where the tar file itself resides is irrelevant. $ wtf IIUC (nothingness is staring at me..) > Make sure the command you give to untar the file doesn't contain the "-C" > flag (which will actually change the output directory). Of course it doesn't.. > > mode, as running `tar xzvf nn-6.6.5.tar.Z' failed miserably (hung until I ^^^^^^^^^^^^^^^^^^^^^^^^^ rlc -- Reality is for people who lack imagination. -- 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/