Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Mon, 23 Apr 2001 10:38:28 +0400 From: egor duda X-Mailer: The Bat! (v1.45) Personal Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <139154426543.20010423103828@logos-m.ru> To: Corinna Vinschen Subject: Re: ash stdin mode is set to O_TEXT In-reply-To: <20010422135957.O15499@cygbert.vinschen.de> References: <11216876326 DOT 20010421202556 AT logos-m DOT ru> <20010421131957 DOT B4033 AT redhat DOT com> <20010422135957 DOT O15499 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Sunday, 22 April, 2001 Corinna Vinschen cygwin-apps AT cygwin DOT com wrote: >> But then, if ash is reading from a pipe, stdin should, IMO, be in binary >> mode. CV> That's really tricky: CV> sh < foo O_TEXT? CV> cat foo | sh O_BINARY? how about sh -c bar.sh < foo cat foo | sh -c bar.sh ? shouldn't it be O_BINARY in both cases here? Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19