X-Spam-Check-By: sourceware.org Message-ID: X-Sender: tom_lee01 AT hotmail DOT com In-Reply-To: <451FD344.7070208@byu.net> From: "Tom Lee" To: cygwin AT cygwin DOT com Subject: Re: mssing packages for cygwin Date: Mon, 02 Oct 2006 00:43:31 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 >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. For postx-like behavior, I find that djgpp mv.exe allows me to run mv *.txt /my/directory/ or mv *.txt c:/my/directory/ in the c drive while cygwin have to use: mv *.txt /cygdrive/c/my/directory/ do you think ignoring /cygdrive/c would be an advantage to reduce the typing? Tom _________________________________________________________________ Try the new Live Search today! http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&FORM=WLMTAG -- 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/