From: listerr AT mail DOT mclaren DOT co DOT uk (Robert Lister) Subject: B19: * expansion problem in bash? 9 May 1998 19:01:03 -0700 Message-ID: <3554C048.3D1F.cygnus.gnu-win32@mail.mclaren.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MimeMultipartBoundary" To: gnu-win32 AT cygnus DOT com --MimeMultipartBoundary Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Having just upgraded tp B19 (it rocks, the job control is much better!) I am trying to use tar to, well, tar a directory containing some 6,066 files. - From bash: tar -cf March-1998.tar * Tar happily starts doing tar-like things, but eventaully stops with something like this: tar: Cannot add file ./Mar-1998/34E152: No such file or directory tar: Error exit delayed from previous errors It's obvious that "./Mar-1998/34E152" is a partial filename. (they all end in .TCP or .CCM) Could it be that bash is truncating the command passed to tar, expanding tar -cf March-1998.tar * to mean: tar -cf March-1998.tar - Running the same tar command from NT's CMD.exe shell works okay (from the same directory, since it doesn't understand "\" So it isn't a problem with tar itself, but just with the line is it being called with. Any ideas, or is it something I'm missing? --MimeMultipartBoundary-- - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".