Domain: beauchesne.info
Stories and comments across the archive that link to beauchesne.info.
Comments · 30
-
Re:The problem is not threads vs processes...
NSPluginWrapper does just this. The main use, I think, is for using 32-bit plugins with a 64-bit browser, but you can also use it to isolate plugins in separate processes (which, given how unstable flash is on linux, is damn useful).
-
nspluginwrapper got much better lately
Gwenole Beauchesne has committed a lot of fixes in the past few weeks; the latest version is quite stable. In fact, it never crashes the browser for me, at worst the plugin instances die but a simple page reload fixes it.
Separating the plugins in another process allows Fedora 9+ to isolate them in their own, limited SELinux context. Even if there's a performance price for it, it might well be worth it. -
Re:64-bit and 32-bit binaries
http://gwenole.beauchesne.info//en/projects/nspluginwrapper
it's better than nothing
-
Re:Flash content
At present, it's the only way of getting flash on FreeBSD for amd64. I believe that flash still hasn't been ported to Linux on amd64 either.
I've used nspluginwrapper successfuly on 64-bit Mandriva for Flash (comes setup and installed by default with the Flash plugin so no messy fiddling around) and it's website says it's compatable with FreeBSD (although haven't used FreeBSD so can't confirm it).
-
Stop browser crashes with nspluginwrapper
One in every three or four YouTube videos crashes the browser.
Of course the ideal solution would be for Adobe to fix Flash, but in the meantime you can use nspluginwrapper to prevent Firefox from crashing whenever Flash goes down. nspluginwrapper runs Flash in a separate child process from the web browser, and uses IPC to display the plugin's contents in your browser; it was originally created to allow people to use 32-bit plugins in 64-bit browsers, but this mechanism is also great for isolating the web browser from plugin crashes.
Another solution is to use Opera, which on Linux runs its plugins in an nspluginwrapper-like child process by default.
-
Re:3, 2, 1....
Run SheepShaver.
-
Re:Flash 64-bit Linux options
Hi, I see you feel strongly about this. But I'm not sure whether you're aware of running 32-bit browser plugins in 64-bit browsers via nspluginwrapper, and contributing to the Tamarin Project to move the just-in-time compilation and garbage collection to a 64-bit memory space. http://gwenole.beauchesne.info/projects/nspluginwrapper/ http://blogs.adobe.com/penguin.swf/2006/10/whats_so_difficult_64bit_editi.html http://www.mozilla.org/projects/tamarin/ You can get what you want now, and contribute to getting what you want in the future. Useful...? jd/adobe
-
Re:Anyone knows a Flash player on OpenBSD?
Contrary to adobe propaganda, Flash is no cross-plateform framework at all. You can always try the nspluginwrapper project which allows to use netscape plugins on *nix platforms. But it's not the ideal solution.
-
Re:What about a player?
I hate to say it, but I'm on an amd64 system, and flash works pretty well for me, including youtube. I'm using the 32-bit version of flash player, but I'm using nspluginwrapper with it to allow it to work with a 64 bit version of firefox...
-
Re:What about a player?
I use nspluginwrapper and the 32-bit Flash plugin, it works fairly well, although occasionally Flash "goes away" (blank window with no content) and you need to reload the browser.
That being said, it's certainly better than most of the other alternatives.
-
Re:What about a player?
Use nspluginwrapper. It takes a little effort to set up but runs Flash and a few other proprietary (32-bit-only) plugins with ease.
-
Re:Why do you need it?
That's what nspluginwrapper is for.
-
Re:Why do you need it?
Using nspluginwrapper (link) you can use 32bit Flash (amongst others) with 64bit Firefox.
-
compatible but not miscible
X64 is compatible with x86. Is there some issue I'm not aware of?
Yes, X64 processors (AMD64, Intel EM64T, VIA's newest superscalar low-power) *CAN* run IA32-bits instructions.
*BUT* you can run both inside the same process without using a translation layer.
A 32bits application cannot directly call 64bits functions in a dynamically linked library (for example, it won't be able to understand the returned pointers)
A 64bits application cannot directly call 32bits functions in a dynamically linked library (for example it could request pointers that are outside the library's range.)
That's why on most Linux installation in addition to the basic libraries (all the packages ending in "lib" like SDL-lib) when installing in a mixed environment you also install special compatibility layers (all the package ending in "-32bits") which basically are the necessary bindings and translation layers needed to call the native 64bits libraries from within 32bits applications. On Windows 64 there's a similar thing called WoW64 (Windows on Windows64).
Also the reverse exist too : translation libraries made to run 32bits browser plugins inside a 64bits Firefox - nspluginwrapper.
Anyway most opensource browser plugins use only a thin layer that basically only serves as a launcher which will start an external player in a separate process and redirects the ouput inside the rendered page. You could mix whatever architectures you want (as long as they are supported by the CPU and Linux) they run in separate process each with its own memory model.
Flash works on your 64bits Linux installation because, most probably your distribution automatically downgrade Firefox to 32bits if you select to install Flash, Realplayer, Java, etc. It works flawlessly (I mean on Macromedia Flash's scale of flawlessness, i.e.: has the same frequency of freezes and crashes as a regular 32bits installation), only because the whole firefox stack is running in 32bits (which is possible thanks to the 32bit compatibility layer) and there's no problems with mixed architectures between the browser plugins and the browser itself.
But have a look on you browser about box, I'm pretty sure your browser is running in 32bits mode and not 64bits native.
Unless recent distributions have started shipping nspluginwrapper as a standart (openSUSE 10.3 has not yet).
Or unless, all of sudden, Adobe decided to release a 64bit version of their software - which they didn't a couple of months ago when I last checked and which I seriously doubt they'll ever do.
I personally prefer running Firefox in native 64bits mode. Anyway MPlayer's browser plugins is much better then any proprietary video player. And gnash is sufficient to me for the rare couple of times I need flash (some website use flash instead of <h#> tags to display titles). For video, I prefer using UnPlug and SaveTube and open the video in an external player, rather than using flash video players.
Of course I don't have the typical flash usage that the average user may have and that's why most /.es complain about not enough support for additional architectures. For them it's either stick with 32bits Firefox, or use less stable solutions (nspluginwrapper, gnash, swfdec, etc...) -
Same could be said of Leopard
While I find this story, and the facts therein, amusing, the same could be said of Leopard and its lack of a Mac OS Classic Environment: Linux with SheepShaver has better Classic Mac OS compatibility than Leopard does out of the box.
But I guess this is not a perfect analogy because SheepShaver can be run on Leopard. Maybe someone will port WINE over to Vista.
:-) -
nspluginwrapper
Why not try this?
-
Re:Second Edition
Just to pick a nit. When Mac switched to Intel chips, they killed OS 9 support in OS X.
If you need OS 9 on an Intel Mac, you'll have to run an app like Sheepshaver.
Mac isn't the best example for backwards compatibility. When they decide they're going to change, they're done. And since they do both the hardware AND software, it's dead. -
Re:Still limited AMD64 support
Yea, if you count not having plugins an advantage.
The only 32-bit plugin that doesn't work via nspluginwrapper allowing you to run 32-bit plugins on a 64-bit browser is Java. -
Re:Fine by me
SC2k runs great in dosbox. and I've run the mac classic version under sheepshaver without any major trouble (enabling sound makes it dog slow).
-
VM isn't 32 bit safe, nspluginwrapper
You're right. The Penguin.SWF blog says the flash JIT VM needs to be converted and that's why there's no 64 bit version.
The GP also forgot to mention the 3rd option (for the flash plugin):
3) nspluginwrapper. It's far from easy to get going on Ubuntu Feisty and needs a 32 development environment (in addition to a 64 bit environment) to be compiled but it _can_ be made work. A brief glance suggests it does it stuff by running the plugin in a 32 bit environment and communicating back to the 64 bit browser over sockets. -
Re:If m$ is too pricey
-
Re:"Problem solved by live in geek?" - So that's n
It can - take a look at http://gwenole.beauchesne.info/projects/nspluginw
r apper/ - a wrapper that enables the use of 32-bit plugins on a 64-bit browser.
Works fine with flash on my machine. For gentoo it is just a matter of emerging nspluginwrapper and flash. -
Re:Excuse for Vista
Apple goes out of their way to ensure compatibility my a** look at how then dropped class form lintel systems and they don not want to help Sheep Shaver run os 9.2.2 as it only works up to 9.04 and that is only way to Classic on Intel Macs.
http://gwenole.beauchesne.info/en/projects/sheepsh aver
http://sheepshaver.cebix.net/ -
Flash problem
One of his big problems was getting flash to work with a 64 bit browser. He solved this by going to a 32 bit browser. It is also possible to wrap the 32 bit flash binary using nspluginwrapper http://gwenole.beauchesne.info/projects/nspluginw
r apper/ which works OK most of the time using 64 bit Seamonkey and FC6.
--
Flash on solar power: http://mdsolar.blogspot.com/2007/01/slashdot-users -selling-solar.html -
Re:x86_64 plugin = Heros
There are 2 ways to get a 32-bit Java plugin running under a Linux/AMD64 environment (BTW, AMD64 is the official arch name implemented by AMD and Intel, x86-64 has been officially abandonned):
- Use the Blackdown Java plugin, they provide a 64-bit version (it works ok, but I have come across at least 1 applet able to crash it).
- Use nspluginwrapper that allows you to load 32-bit plugins in 64-bit browsers.
Of course, since Sun has open sourced Java, a 64-bit Java plugin is likely to appear soon.
-
Re:x64_86
You can use nspluginwrapper to use the 32 bit Flash plug-in on AMD64 and compatibles. It works quite well.
-
Use beta 2
The release notes suggest that beta 1 doesn't work but beta 2 does!
-
Re:Too bad Flash 9 isn't released for linux yet
I've been using nspluginwrapper in my 64-bit firefox (compiled, using gentoo) for months now and, the first release notwithstanding, it has been completely stable. I suggest you give it a shot. It even enables your current 32-bit plugins for you on install (at least on gentoo)!
-
Re:Less stuff
You can use sheepshaver to eliminate the PowerPC computer. That's one down, many to go.
-
Re:I switched to a 64 bit
I tried installing Ubuntu 64-bit (amd64) 6.06LTS onto a Dell Precision 690 (dual duo-core processors). Was fine except it couldn't find the drivers for the SAS drives I were using. But Ubuntu 6.10 installed great straight off the disc!
A point to note, 64-bit Macromedia Flash for linux isn't out yet - so one has to do something tricky, like install nspluginwrapper (http://gwenole.beauchesne.info/en/projects/nsplug inwrapper) that allows the use of 32-bit plugins for Firefox.
Apart from that all the standard 64-bit apps for linux work fine!