From:	err AT raelity DOT com (Ernie Rael)
Subject:	Re: Observations and suggestions
1 Jan 1997 17:39:18 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<32cee826.40731468.cygnus.gnu-win32@mail.scruznet.com>
References:	<199701010551 DOT XAA03725 AT edge DOT edge DOT net>
Mime-Version:	1.0
Original-To:	Blake McBride <blake AT edge DOT net>
Original-Cc:	gnu-win32 AT cygnus DOT com
In-Reply-To:	<199701010551.XAA03725@edge.edge.net>
X-Mailer:	Forte Agent .99g/32.339
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

On Tue, 31 Dec 1996 23:52:22 -0600, Blake McBride wrote:

> ...
>ago.  I am excited about the prospects of having that environment =
available
>for NT but feel that it unnecessarily falls short in a few critical

I'm pretty jazzed myself, i've recently picked it up and am
just now getting around to really trying to use it.

>ASCII MODE PIPES
>----------------
>
>As has been reported, this kills all attempts at pipes which perform
>binary communications for example:  gzip -dc file.tar.gz |tar xvf -

Oh, so thats why gzip|tar wasn't working. After reading your note,
i came across the '-b' option to mount, and i tried mounting root
and tmp using this option. I then started a new login shell and
bash got errors reading it's profile. I have a very small profile
i'm working with now, during login i got
	: command not found
	: command not found
	bash.exe: c:/users/err/.bash_profile: line 12: syntax error:
					 unexpected end of file
	bash$
There's some funny stuff going on. Any ideas what?

>My suggestion, which may solve the problem for everyone, is to
>default to binary pipes and then allow this mode to be modified
>via something akin to an environment variable or 'set' option.

I absolutely agree that binary pipes *must* be the default. I don't
fully understand the issues or what translations are actually
going on. I did read somewhere that there the cygwin dll was
doing some character mapping in may cases. If anything, turning
a \r\n into a \n might one mode of operation, but this could be
done by insterting a 'tr' in the pipeline. Seems real dangerous,
and entirely contrary to unix, to be modifying the byte stream.

Is there a description of what the detailed intent and usage and
meaning of "ascii pipes", and how this is supposed to help with
the \r\n dos thing? I picked up the source so i can look there
for doc; some pointers would be appreciated. I'm scanning through
the archive now.

-ernie
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -