Message-ID: <40C2E045.8090708@codeweavers.com>
Date: Sun, 06 Jun 2004 18:13:41 +0900
From: Mike McCormack <mike@codeweavers.com>
Organization: Codeweavers
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514
MIME-Version: 1.0
To: Christoph Hellwig <hch@infradead.org>
CC: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: WINE + NX (No eXecute) support for x86, 2.6.7-rc2-bk2
References: <40C2B51C.9030203@codeweavers.com> <20040606073241.GA6214@infradead.org>
In-Reply-To: <20040606073241.GA6214@infradead.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1006
Lines: 25


Christoph Hellwig wrote:

> if you have a need for a special virtual memory layout please use your
> own binary loader as I already suggested earlier in the thread, i.e.
> binfmt_pecoff.

We are using our own user space loader now, but a kernel space loader is 
  neither portable or practical.

The Wine project is used by many people and companies for both comercial 
and non-comercial purposes.  In the spirit of cooperation, it would be 
nice if somebody let us know when they're going to make a change that is 
going to break Wine, and provide a way for us to workaround that change, 
or even better maintain real binary compatability...

It seems Linus's kernel does that quite well, but some vendors seem not 
to care too much about breaking Wine.

Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/