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: Sat, 21 Apr 2001 13:19:57 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: ash stdin mode is set to O_TEXT Message-ID: <20010421131957.B4033@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <11216876326 DOT 20010421202556 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <11216876326.20010421202556@logos-m.ru>; from deo@logos-m.ru on Sat, Apr 21, 2001 at 08:25:56PM +0400 On Sat, Apr 21, 2001 at 08:25:56PM +0400, egor duda wrote: >ash stdin mode is set to O_TEXT, so it's impossible to checkin/chechout >binary files from cvs when CVS_RSH is sh script. > >maybe O_TEXT should be set only in interactive mode? or shouldn't be >set at all? Corinna and I have discussed this in the past. The problem is that the 'read' command should always be text mode whether it is interactive or not. Also, if sh is reading a shell script via: sh < foo the input should be in O_TEXT mode. But then, if ash is reading from a pipe, stdin should, IMO, be in binary mode. I'm not sure how to accomodate all of those issues. cgf