sc94597 said:
|
I had a feeling this would come up. The acronym "Wine" stands for "Wine Is Not an Emulator". The truth is Wine is not actually an emaulator, it's a compatibility layer which intercepts native Windows calls and translates them into native Linux calls. What does this mean to the user? What pray tell, is the difference between an "emulator" and a "compatibility layer"?
The main difference is that with Wine, the software is running on the actual chip itself. It is not being run through an emulator, the actual machine code that the compiler generated is being run on the actual CPU of your machine. Then when the hardware requests a specific windows function (such as to draw a window on a screen) wine intercepts that call and passes it on to an equivelant Linux call. This allows for much quicker deverlopment than a full-blown emulator and also is what allows for Windows apps under Wine to run almost as fast as the equivelant Linux app.
Of course, the crux of the problem is that since Wine relies on the software running on the actual CPU, the CPU has to be able to handle the specific machine code the software is written in. In other words, a piece of software written for x86 will only work on x86 and will not run on anything else. To put it even more plainly, No Windows software can run on PS3 Linux and Wine, no matter how much RAM or whatever. It will simply not work. You will need a full blown Virtual Machine such as VMWare (and I'm not sure one exists that runs on Cell either).
Of course, There are plenty of native Linux apps that are open source and theoretically should workon Cell, to do almost everything. You will either have to hunt for precompiled cell versions or compile it yourself (and hope that it will actually compile). But Fishy is pretty much right, there will be very little software you can run on your PS3 Linux.
Help! I'm stuck in a forum signature!