Date: Wed, 16 Nov 2005 13:58:17 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: WINE on Cygwin
Message-ID: <20051116125817.GQ3462@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <200511140753 DOT 46784 DOT leon-cygwin-list AT cyberknights DOT com DOT au> <005701c5eaad$f8847800$8002a7c0 AT dir DOT sparsi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <005701c5eaad$f8847800$8002a7c0@dir.sparsi.com>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Nov 16 10:02, Informa??es wrote:
>    Guys,
> 
>    Sorry for not getting involved with this discussion before.
> 
>    For those interested in more details about this topic, I included 
> several good references in this message.
> 
>    I can think of many reasons why someone would want to run WINE under 
> Cygwin and my reason, put shortly, is: GDI->X11. I did quite a research to 
> identify all the issues related to this, and end up knowning that this 
> sendmsg() limitation is a major one. I was really willing to start making 
> things happen by getting more info on how to tackle this, but the 
> discussion diverged to the rather philosophical "why do this" discussion. 
> The only useful info I got from this thread was that "this is still an 
> issue", from Corinna.
> 
>    Can anyone point me to any reference covering the implementation of the 
> missing sendmsg functionality (exchanging file descriptors across 
> processes) ? Any (incomplete) piece of code ? Any help ?
> 
>    My company has manifested a clear commitment to having this done, and 
> I'm trying to do my best not to let this die again.

Red Hat would be delighted to do some contractual work for your company
to target the problem of the missing descriptor passing functionality.
See http://www.redhat.com/software/cygwin/ for contact information.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/