chroot question

[A J Stiles <deb64@earthshod.co.uk>]

I have observed some odd behaviour since setting up a 32-bit chroot  (in order 
to run some weirdy Java web applet.)  This chroot is totally self-contained, 
even with its own /home directory  (so that my 32-bit application preferences 
don't clobber my 64-bit ones).

If I already have 64-bit Iceweasel running, and try to start 32-bit Iceweasel 
from inside the chroot, I get another instance of the 64-bit browser.  If I 
kill the 64-bit browser, I can start a 32-bit one.  If I then try to start a 
64-bit Iceweasel from the K menu while the 32-bit Iceweasel is running, I get 
another 32-bit Iceweasel.

The upshot seems to be, I can't have both a 32-bit and a 64-bit Iceweasel 
browser open at the same time.

I'm guessing this is due to some kind of namespace conflicts.  Would it work 
if I modify the source package slightly, to change the name of the 
application and call it something like iceweasel32 instead?

-- 
AJS
delta echo bravo six four at earthshod dot co dot uk