Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: Subject: RE: WINE on Cygwin Date: Thu, 3 Nov 2005 16:46:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: Andy Moreton wrote: > On Thu, 03 Nov 2005 16:00:51 GMT, Alexander Gottwald wrote: > >> On Thu, 2005-11-03 at 07:41 -0800, Andrew DeFaria wrote: >> >>> I guess I don't see the point. Isn't Wine an emulator for running >>> Windows apps on Unix/Linux? If so then why would you need it under >>> Cygwin as Cygwin already runs on Windows so if your want to run a >>> Windows apps, well then just run the Windows app! >> >> Sometimes it's useful to have a separation between the program and >> windows. You could trace all registry or file access of a program. Wine >> would be useful for remote program usage since it exports the display >> via X11. > > This still sounds fairly pointless. the tools from sysinternals.com allow > you to monitor all file and registry access from an application. A VNC > client will solve your remote operation needs. > > So what is the real reason for wanting to do something so perverse ? > > AndyM Well, how about sandboxing? It's the ideal way to test out a virus or other suspect warez: run it on a virtual machine where it can't escape into your real one. 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/