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 To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Soren A Newsgroups: gmane.os.cygwin Subject: Re: Tar Problems Under Cygwin Date: Wed, 21 Aug 2002 15:26:48 +0000 (UTC) Organization: Occasionally Sporadically Lines: 26 Message-ID: References: NNTP-Posting-Host: ny-kenton2a-572.buf.adelphia.net X-Trace: main.gmane.org 1029943608 13093 24.51.94.60 (21 Aug 2002 15:26:48 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Wed, 21 Aug 2002 15:26:48 +0000 (UTC) User-Agent: Xnews/L5 X-Archive: encrypt "Anthony Massa" wrote around 21 Aug 2002 news:NBBBJIKCMKBJFEAHMGMAGECDEHAA DOT amassa AT san DOT rr DOT com about %s: > This file was then placed on a CD-ROM. When I tried to un-tar the file > using the command: > > $ tar xjvf f:/i386rdwr.tar.bz2 > > I get the following output error message: > > f: unknown host > tar (child): f\:/i386rdwr.tar.bz2: Cannot open: I/O error > tar (child): Error is not recoverable: exiting now You've received advice to mess with your mounts in order to fix a problem known to happen with the tar that's packaged with Cygwin. That's fine, but TMTOWTDI: just set the appropriate default options for tar that (IMHO) make sense on an average Win32 system: TAR_OPTIONS=--force-local Somewhere in your bash start-up files (~/.bashrc). Then pass ordinary windows-style paths to tar freely. It won't choke on them anymore. HTH, Soren A -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/