I have downloaded firefox-xxx.tar.bz2 from the official site and extracted it to separate directories named firefox1, firefox2 etc. I launch Firefox using the script

#!/bin/sh

if [ $(pwd) != "/home/${USER}" ]
then
        HOME=$(pwd)
        echo "Starting firefox from ${HOME}."
	firefox --no-remote
else
        echo "ERROR. Current directory is same as the main Firefox directory."
        exit 1
fi 

exit 0

Been using this way for quite sometimes now for account and cookie separation (yes I know about container extension). Is it safe to do so or should I pass something else as argument for better sandboxing. Also i noticed that, every instances run on the same version as my main properly installed firefox, Does this have something to do with the sandboxing or just a perk of auto-updates?

  • d_k_bo@feddit.de
    8·
    1 year ago

    Since you are running firefox instead of ./firefox, I guess you are using your system-wide firefox anyway. You can just use the built-in profile manager instead.

    • t_uxio@discuss.tchncs.deOP
      2·
      1 year ago

      But when I check the about:profile, it indicates the root directory not as my main one. Like if my main ff is in /home/user/.mozilla then my instance’s root directory is showing /home/user/firefox1/.mozilla.

    • t_uxio@discuss.tchncs.deOP
      2·
      1 year ago

      weirdly enough, when i launch ff by ./firefox --no-remote and check the about:profile, it is showing up as a separate profile in my main ff. \