Difference between revisions of "Talk:Firefox/Profile on RAM"

From ArchWiki
Jump to: navigation, search
 
(23 intermediate revisions by 12 users not shown)
Line 1: Line 1:
Why not just use 'cp', or 'mv' commands in {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}}? [[User:Adamlau|Adamlau]] 18:04, 22 September 2010 (EDT)
+
== Security ==
 +
How about pointing out a few drawbacks like "putting browser profile into {{ic|/tmp}} poses a security risk --- other users can now see it?" [[User:All3fox|All3fox]] ([[User talk:All3fox|talk]]) 07:17, 30 August 2013 (UTC)
  
Isn't 2.1 a bit out of date now that we have the browser.cache.memory.enable setting? [[User:Jamie Kitson|Jamie Kitson]] ([[User talk:Jamie Kitson|talk]]) 19:00, 14 August 2012 (UTC)
+
: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''.--[[User:Kozaki|kozaki]] ([[User talk:Kozaki|talk]]) 17:01, 22 August 2016 (UTC)
 +
 
 +
== $USER ==
 +
I think this line
 +
 
 +
volatile=/dev/shm/firefox-$USER
 +
 
 +
in the script should be changed to
 +
 
 +
volatile=/dev/shm/firefox-${whoami}
 +
 
 +
, 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. [[User:Kovacssanya|Kovacssanya]] ([[User talk: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
 +
 
 +
i.e merging profiles before launching firefox and after closing it.
 +
It has its downsides but it is easier.
 +
[[User:Kisame217|Kisame217]] ([[User talk:Kisame217|talk]]) 12:52, 19 September 2014 (UTC)
 +
 
 +
== .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).
 +
 
 +
{{unsigned|22:25, 20 July 2016‎|Makhlaghi}}
 +
 
 +
== .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[1]?
 +
[1]https://bbs.archlinux.org/viewtopic.php?id=163280
 +
 
 +
--[[User:Nicoadamo|Nicoadamo]] ([[User talk:Nicoadamo|talk]]) 17:11, 10 September 2016 (UTC)
 +
 
 +
== 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.--[[User:Kozaki|kozaki]] ([[User talk:Kozaki|talk]]) 17:07, 22 August 2016 (UTC)

Latest revision as of 09:11, 12 October 2016

Security

How about pointing out a few drawbacks like "putting browser profile into /tmp poses a security risk --- other users can now see it?" All3fox (talk) 07:17, 30 August 2013 (UTC)

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)

$USER

I think this line

volatile=/dev/shm/firefox-$USER

in the script should be changed to

volatile=/dev/shm/firefox-${whoami}

, 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

i.e merging profiles before launching firefox and after closing it. It has its downsides but it is easier. Kisame217 (talk) 12:52, 19 September 2014 (UTC)

.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).

—This unsigned comment is by Makhlaghi (talk) 22:25, 20 July 2016‎. Please sign your posts with ~~~~!

.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[1]? [1]https://bbs.archlinux.org/viewtopic.php?id=163280

--Nicoadamo (talk) 17:11, 10 September 2016 (UTC)

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)