www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2003/01/22/11:23:59

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3E2EC595.8040004@yahoo.com>
Date: Wed, 22 Jan 2003 11:23:49 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: cygwin-developers AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: setregid() and setreuid() implementation proposal
References: <20030117120131 DOT GF1142 AT cygbert DOT vinschen DOT de> <20030116190119 DOT GD820 AT tishler DOT net> <20030117120131 DOT GF1142 AT cygbert DOT vinschen DOT de> <3 DOT 0 DOT 5 DOT 32 DOT 20030121202701 DOT 007db4f0 AT mail DOT attbi DOT com> <20030122014007 DOT GA23365 AT redhat DOT com> <20030122102919 DOT GA29236 AT cygbert DOT vinschen DOT de> <20030122154704 DOT GE4903 AT redhat DOT com> <20030122155757 DOT GA16081 AT cygbert DOT vinschen DOT de> <20030122161000 DOT GF4903 AT redhat DOT com>

Christopher Faylor wrote:
>>
>>May I dream?  Let's break binary compatibility with 1.3 and switch
>>over to 64 bit off_t/fpos_t etc and 32bit uid_t/gid_t once and for all.
>>No big chnanges to newlib needed then.  We could get rid of all
>>func32/func64 function pairs... sounds like holiday on Hawaii.
> 
> 
> That would imply a cygwin2.dll.  Do we really want to go there?  I could
> get rid of my signal-compatibility hacks, too.  And the termios hacks,
> and...
> 

FWIW, and that shouldn't be much, yes, I've thought it was time last 
year for a cygwin2.dll.  As long as cygwin1.dll and cygwin2.dll can live 
together it shouldn't be that big of a hardship.

Earnie.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019