Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: WINE on Cygwin
Date:	Thu, 3 Nov 2005 18:19:27 -0000
MIME-Version:	1.0
In-Reply-To:	<436A5357.1535F407@dessent.net>
Message-ID:	<SERRANO69YDqSkcJse100000127@SERRANO.CAM.ARTIMI.COM>

Brian Dessent wrote:
> Dave Korn wrote:
> 
>>> But WINE isn't a virtual machine, and it doesn't offer that kind of
>>> protection.  You would need Xen / VMWare / etc for that.
>> 
>>   Oh, I stand corrected.  You mean it doesn't even do
>> virtual-drive-in-a-file-on-the-real-HD then?  That's a shame.
> 
> Well, considering WINE stands for WINE Is Not an Emulator...


  It doesn't need to be an emulator.  It translates file-system accesses from
something like "C:\foo.txt" into something that makes sense to the underlying
FS, yeh?  But that could just as easily be done by translating
device-driver-level read and write block calls into reads and writes to
sectors within a file on the host FS.  The issues of virtualisation/emulation
are entirely orthogonal to that.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/

- Raw text -