X-Spam-Check-By: sourceware.org Message-ID: <45202139.2010302@cygwin.com> Date: Sun, 01 Oct 2006 16:12:41 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060916 Fedora/1.5.0.7-1.fc4.remi Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: mssing packages for cygwin References: <451FD344 DOT 7070208 AT byu DOT net> In-Reply-To: <451FD344.7070208@byu.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Tom Lee on 9/30/2006 11:24 PM: >> I don't undersand why "ls c:/test" works but not for >> "tar cvf test.tar c:/test" > > Because ls does not parse its arguments, but upstream tar treats c:/test > as meaning open the file /test on the remote machine named c; and because > I'm not in the mood to patch either ls or tar from what the upstream > packages provide. For cygwin programs in general, POSIX paths will work, > but you are lucky if DOS paths happen to work, since the point of cygwin > is to provide a Linux emulation (aka POSIX-like behavior), and DOS paths > are not supported in Linux. And indeed there is no need to patch 'tar' since it supports the '--force-local' flag. Tom, I suggest you take a read through the 'tar' man page if you need further details. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- 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/