Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Sat, 22 Jan 2000 11:35:36 -0500
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: binmode idea
Message-ID: <20000122113536.A18995@cygnus.com>
Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i

Is there anywhere in an executable header where we could commandeer a 32
bit word for cygwin's use?  I was thinking that we could write a utility
that could set bits in this word which would indicate whether the
default mode was "binmode" for file opens and maybe even other "CYGWIN"
defaults.

This is not a replacement for DJ's capability idea but it would allow us
to create executables that could be copied from system to system with
no extra setup.

Mumit, do you know if there is something in an executable that could be
used like this?

Alternatively, we could add a linker section for this, but that would
require relinking an exeutable to gain the benefit.

-- 
cgf AT redhat DOT com
http://www.redhat.com/