This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: cpio problem
- To: "'Ian Collins'" <Ian at kiwiplan dot co dot nz>
- Subject: RE: cpio problem
- From: Bob McGowan <Bob_McGowan at xstor dot com>
- Date: Tue, 14 Apr 1998 11:41:04 -0700
- Cc: "'gnu-win32 at cygnus dot com'" <gnu-win32 at cygnus dot com>
There has been lots of talk recently about binary vs. text mode with
pipes in bash (it seems bash defaults the pipe to text mode). This may
also apply to I/O redirection. I also saw one post that seemed to
indicate that ash.exe, in the B19 distribution, does not set text mode.
You could try running ash.exe, then the cpio < file and see if that
works. If so, then this would be another good example of why text mode
I/O operations are "not good".
Please accept my apologies for sending you this directly as well as to
the list. The list is so flakey and slow currently that I felt this
would be the more reliable and speedy way to get an answer to you.
Bob McGowan
i'm: bob dot mcgowan at artecon dot com
-----Original Message-----
From: Ian Collins [mailto:Ian@kiwiplan.co.nz]
Sent: Monday, April 13, 1998 10:12 PM
To: 'Gnu Mailing list'
Subject: cpio problem
I have just compiled and made cpio on gnu win32 b19.
I tested it with a 400Mb binary cpio file.
If I use,
cpio -icv < file.cpio
then it gets a premature end of file error.
However, if I use,
cpio -icv -I file.cpio
then it works OK.
What is stdin doing?
Ian Collins.
KIWIPLAN NZ.
-
For help on using this list (especially unsubscribing), send a message
to
"gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".