X-Spam-Check-By: sourceware.org Message-ID: <15a6d6ee0702140557q1d59db40oa0d8b2471550affb@mail.gmail.com> Date: Wed, 14 Feb 2007 08:57:39 -0500 From: "Ken Shaffer" To: cygwin AT cygwin DOT com Subject: Re: tar --exclude not working MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 > tar tf test.tar --anchored --exclude="D:/" temp$ tar tf tartest.tar -P c:/temp/file1 file2 temp$ tar tf tartest.tar -P --anchored --exclude='/temp' file2 So, if you really want to exclude your D:/Bkp files, you could enter: tar tf test.tar --anchored --exclude='/Bkp' The -P option used on my test tar file forced absolute paths and I didn't get the message "tar: Removing leading `c:/' from member names". In fact, this message clued me to how I might exclude the desired file. Even though it says it removed "c:/", it appears it only removed "c:" since I had to provide the leading / to exclude the file. mount points may also have something to do with the behaviour: c:\temp on /tmp type system (binmode) c: on /c type system (binmode) But, in any event, I'd also agree there's something up with --exclude. Ken -- 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/