However, the main disadvantage of that option That option will mature, but right now it's just not working for me. To it's final destination from a 64-bit shell. Just to make the file accessible, having to manually copy it in Home directory - but not every directory can be shared like that,Īnd all too often I found myself downloading to my home directory Of course you can bind mount several directories like your If you download a file, you can only download it to the 32-bitĬhroot.In your normal 64-bit environment of course (ie xmms, azureus, mplayer). With certain extensions, but in most cases you want to run those applications It is neat that you can assign programs to handle files Every external application started by iceweasel necessarily also runs inside.I used option 1 (the chroot) for a while, but that approach has Use a 32-bit version of the browser without chroot (a bi-arch approach).Use the 64-bit version of the browser and use a wrapper for the 32-bit plugins.

Install everything in a 32-bit chroot and run the browser there.There are three approaches to work around this conspiracy: Their flash plugin- but why Sun is categorically refusing to address our cry forĪ 64-bit java plugin for mozilla based browsers for this many years is beyond me. I could ponder on how much Microsoft is paying Adobe not to release a 64-bit version of The experience of trying to browse the net with an amd64 machine will have won you over If you weren't already convinced that closed source sucked before, then surely

Adobe flash player for firefox dep