wine overstepping the mark?
speeddymon at gmail.com
Thu Oct 27 15:53:19 CDT 2005
I think I mis-worded what I was trying to say.. I believe that the
mimetypes have to be updated specifically for the .exe binaries. If you
have ever tried to click on an executable when wine is not installed,
your GUI shows you the action that it is running the file, but it
doesn't do anything (because wine isnt installed, and the gui can't run
PE binaries, only aout and elf ones).. So wine has to update the
mimetype for exe's, so that when you double click on one, it does the
same as opening a console and typing "wine filename.exe"..
Hope that clears up what I was trying to say previously.
wino at piments.com wrote:
> On Thu, 27 Oct 2005 21:23:48 +0200, Dustin Navea <speeddymon at gmail.com>
>> I dont see how that is a problem? AFAIK wine has to mod them so that
>> when you double click on an exe in your GUI, the GUI knows what
>> program to load the exe's with... but then again I could be wrong.
>> anyone else?
> Well that's why the sandbox is there.
> I install Wine for one specific user account that has suitably
> restricted access rights. I do not want wine or wine installer to go
> outside that brief.
> I want wine on this system so that I can use on or two bits of windows
> software , I DO NOT want it to start thinking it really IS windows and
> start taking over my computer for me.
> That is the fundamental reason why I use Linux and not M$.
More information about the wine-devel