From: "Earnie Boyd" <earnie_boyd@hotmail.com>
To: kkont@estia.iit.nrcps.ariadne-t.gr
Cc: gnu-win32@cygnus.com
Subject: Re: Consistent mode of file-opens
Date: Thu, 09 Oct 1997 15:57:00 -0000 [thread overview]
Message-ID: <19971009133008.272.qmail@hotmail.com> (raw)
>From: kkont@estia.iit.nrcps.ariadne-t.gr (Kimon Kontovassilis)
>Subject: Consistent mode of file-opens
>To: gnu-win32@cygnus.com
>Date: Wed, 8 Oct 1997 18:31:19 +0200 (EET)
>Cc: kkont@estia.iit.nrcps.ariadne-t.gr (Kimon Kontovassilis)
>
>Hello, fellows!
>
---snip---
>
>Consider now a system setup where all mount points have been flagged as
>binary. (As previous discussions on this list have fully explained,
such a
>setting is virtually necessary, if binary-file-oriented applications
are to
>behave properly without being individually modified.)
>The problem is that stdin, stdout and stderr are still opened in text
mode.
>This breaks redirection and pipe operations dealing with binary data.
>Things like
>
> gunzip -c file.tar.gz | tar xvf -
You must be executing from the MSDosshell. I've done this sort of
operation many times both on WNT3.51 and W95 within BASH without any
problems.
- \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-10-09 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-09 15:57 Earnie Boyd [this message]
1997-10-09 16:37 ` Kimon Kontovasilis
-- strict thread matches above, loose matches on Subject: below --
1997-10-10 15:04 Larry Hall
1997-10-09 16:37 dahms
1997-10-10 6:25 ` Kimon Kontovasilis
1997-10-09 12:13 Earnie Boyd
1997-10-10 15:04 ` Kimon Kontovasilis
1997-10-08 14:47 Kimon Kontovassilis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19971009133008.272.qmail@hotmail.com \
--to=earnie_boyd@hotmail.com \
--cc=gnu-win32@cygnus.com \
--cc=kkont@estia.iit.nrcps.ariadne-t.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).