| 1 |
I vaguely remember a while ago, somebody on this list asked about |
| 2 |
running separate instances of Firefox. I finally figured out how to run |
| 3 |
separate instances of Firefox, as ***COMPLETELY SEPARATE PROCESSES***. |
| 4 |
Namely, that you need ***A SEPARATE PROFILE FOR EACH INSTANCE***. Let's |
| 5 |
start with 2 profiles "trusted" and "default". From the command line, |
| 6 |
execute the following commands... |
| 7 |
|
| 8 |
firefox -new-instance -P trusted & |
| 9 |
firefox -new-instance -P default & |
| 10 |
ps -ef | grep firefox |
| 11 |
|
| 12 |
You won't need the "&" if you launch from a desktop or window-manager |
| 13 |
launcher. In the above example, I launched 2 instances of Firefox, and |
| 14 |
verified their existance by running "ps -ef | grep firefox". |
| 15 |
|
| 16 |
So if you have some sites that you visit regularly, you can have a |
| 17 |
separate profile for each one. This has some advantages... |
| 18 |
|
| 19 |
1) You can have totally different customized setups (including different |
| 20 |
add-ons) for each site. |
| 21 |
|
| 22 |
2) Profiles, including cookies, are stored in separate directories. |
| 23 |
Therefore third-party cookies left by trackers when you're on site A |
| 24 |
using profile A, will not be readable by the same third-party when |
| 25 |
you're on site B, using profile B, making tracking you more difficult |
| 26 |
and less reliable... one... two... three... aaaaawwwwwww. |
| 27 |
|
| 28 |
3) If you have a whole bunch of websites open, and one of them crashes |
| 29 |
Firefox, or hangs it so you need to kill it, you don't end up taking |
| 30 |
down all your browsers. |
| 31 |
|
| 32 |
-- |
| 33 |
Walter Dnes <waltdnes@××××××××.org> |
| 34 |
I don't run "desktop environments"; I run useful applications |
Archives