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 Message-ID: <3D5E0EA708C5DD44B7575859D366728C2DC300@svr-orw-exc-02.wv.mentorg.com> From: "Biederman, Steve" To: "'cygwin AT cygwin DOT com'" Subject: RE: tar and remote machines (was RE: What is the minimum needed t o run gtar?) Date: Wed, 20 Aug 2003 14:18:21 -0700 MIME-Version: 1.0 Content-Type: text/plain The one user in particular who is testing this for me claims that with the --force-local, tar is running to completion but the tar file it's creating is zero length. Sounds doubtful to me, but I haven't gotten any more information from him yet to figure out what's going on ... Thanks again for your time. -----Original Message----- From: David Rothenberger [mailto:daveroth AT acm DOT org] Sent: Wednesday, August 20, 2003 2:06 PM To: Biederman, Steve Cc: 'cygwin AT cygwin DOT com' Subject: tar and remote machines (was RE: What is the minimum needed to run gtar?) Biederman, Steve writes: > > (Resuming an earlier discussion ...) > > In my Cygwin environment, I can invoke tar with Windows-style pathnames, > i.e, "tar -cf C:/temp/foo.tar ." My non-Cygwin users can't; for them, the > "C:" is interpreted as a remote machine name and they get "cannot execute > remote shell". In my Cygwin environment, "tar -cf C:/temp/foo.tar ." does not work; I get an error about C being a hostname. Looking at the tar code, this is what I'd expect. The comment in the code is /* A filename is remote if it contains a colon not preceded by a slash, to take care of `/:/' which is a shorthand for `/...//fs' on machines running OSF's Distributing Computing Environment (DCE) and Distributed File System (DFS). However, when --force-local, a filename is never remote. */ I don't think the problem your non-Cygwin users are having has anything to do with Cygwin, and I'm mystified as to why it works correctly for you. Are you using the same version of tar and the cygwin DLL as your "non-Cygwin" users? > What is the correct solution to this problem? As you guessed, provide the --force-local switch. Alternatively, download the tar source, patch rmt.h to ignore remote paths, and recompile. Dave -- 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/