Yesterday I covered how I actually runtwo web browsers, one for my real browsing and one for various sortsof testing and isolated browsing. That raises a question: how do youset up something like that?

In theory, you could just use an alternate Firefox profile (with ascript to start your test Firefox with the right magic arguments). Inpractice I have never trusted Firefox's profile system that much, partlybecause in the past I spent some time testing out potentially buggydevelopment builds. So I

Given how Firefox remote control works on Unix , you might wonder how I routinely run twoseparate copies of Firefox and still have my remote control environment work reliablyenough that I haven't pitched one of the copies out the window long ago.

In theory, the answer is Firefox's -no-remote argument. In practicethis doesn't work quite the way you want it to. The problem is that aFirefox instance run with -no-remote will still register itself as avalid target for remote