B19: * expansion problem in bash?
Robert Lister
listerr@mail.mclaren.co.uk
Sat May 9 13:46:00 GMT 1998
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 <every single filename......>
- 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?
More information about the Cygwin
mailing list