Talk:Firefox/Profile on RAM
- We can have tmpfs with privacy AFAIK. By making use of overlayfs which has acl. Can be enabled in e.g. profile-sync-daemon or anything-sync-daemon.--kozaki (talk) 17:01, 22 August 2016 (UTC)
I think this line
in the script should be changed to
, or the CRON job will fail, because $USER is not set. But as I'm using another distro I don't know wheter it is working in ARCH, so I won't change that line now. Hope I get some feedback here. Kovacssanya (talk) 10:33, 22 November 2013 (UTC)
A more simple way of using firefox-sync is to make a script like this:
#!/bin/bash /bin/firefox-sync firefox /bin/firefox-sync
.profile instead of .bash_profile
This is a comment for the "Sync at login/logout" section. Firefox is loaded by the GUI, which does not necessarily log in through bash (for example GUI users might prefer to login with gdm for GNOME). However .bash_profile is only ran when someone logs in from the command-line.
It would thus be helpful to add that when you have something like gdm installed (or don't log-in with bash when you use Firefox), you have to call firefox-sync from ~/.profile (in the case of GNOME), not in ~/.bash_profile (or ~/.bash_login).
.bash_logout not being called
I see .bash_logout is not called neither when I shutdown nor reboot. My history is not remembered since I tried this article 'Firefox on RAM'. Maybe with KDE/plasma one needs to use systemd? https://bbs.archlinux.org/viewtopic.php?id=163280
Firefox's new Cache relies on browser.dIsk.cache
If setting browser.cache.disk.enable = false, one then loose browser.cache.use_new_backend (FF 32 and above « new cache system ») stability and performance improvements. Since the latter relies on the former being enabled.--kozaki (talk) 17:07, 22 August 2016 (UTC)