Dev1 Galaxy Forum / the right procedure ?

Re: the right procedure ?

dummy@example.com (Devarch) — Sun, 04 May 2025 20:46:54 +0000

opensnitch https://github.com/evilsocket/opensnitch is must have nowadays.

Re: the right procedure ?

dummy@example.com (GlennW) — Wed, 25 Dec 2024 21:22:25 +0000

Nice tip Ron. ;-)

Re: the right procedure ?

dummy@example.com (Ron) — Wed, 25 Dec 2024 16:52:58 +0000

I'd suggest reading this: https://easylinuxtipsproject.blogspot.c … urity.html
It's just as applicable to Devuan (and any other Linux distro).

Re: the right procedure ?

dummy@example.com (Altoid) — Wed, 25 Dec 2024 14:23:46 +0000

Hello:

Just a (belated) comment / heads-up:

aluma wrote:

... enough RAM (4 GB or more) ...

My Devuan Daedalus system runs on a box with a 120GB SSD and 8GB RAM.
As my conky swap file use always read nought, I decided to reduce it to 2.6GB just in case some application looks for a swap file.
I plan to reduce it further should I need more space in / or /home.

Long after that, I set up a tmpfs like you suggested.
It ran without a hitch till a couple of days ago when I had a system lock-up while streaming a video.
Something I had never encountered before and made me fear for my system's SSD.

After making a full Clonezilla image of my system drive, I had a look (among other things) at df -h and found that it was set up with a capacity of 3.9GB, something I was not aware of:

$ df -h
--- snip ---
tmpfs           3.9G   18M  2.0G   1% /home/groucho/.cache/mozilla/firefox
--- snip ---
$

This is 50% of the available physical system RAM in my box.
And the default value tmpfs claims when it is set up without specifying the desired size.
In this specific case, it was more than the amount assigned* to /dev/shm:

$ df -h | grep tmpfs
tmpfs           788M  800K  787M   1% /run
tmpfs           5.0M  8.0K  5.0M   1% /run/lock
tmpfs           2.1G     0  2.1G   0% /dev/shm
tmpfs           3.9G   20M  2.0G   1% /home/groucho/.cache/mozilla/firefox
tmpfs           788M  8.0K  788M   1% /run/user/1000
$

* apparently limited by the amount of available RAM in a system

Suspecting some sort of conflict (?) somewhere, I did some searching and found this tidbit which may be of use.

I have now set it up with a specified size of 2GB:

$ cat /etc/fstab
--- snip ---
tmpfs     /home/groucho/.cache/mozilla/firefox  tmpfs nosuid,nodev,noatime,user,uid=1000,size=2G  0  0

$ df -h
--- snip ---
tmpfs           2.0G   18M  2.0G   1% /home/groucho/.cache/mozilla/firefox
--- snip ---
$

I really don't really know if the two lockups I had were caused by my system using a 3.9GB tmpfs but I'll report back if I get another lock-up.

Best,

Re: the right procedure ?

dummy@example.com (aluma) — Thu, 13 Jun 2024 05:02:59 +0000

@devur

но архива 'r6a038wc.default-esr/cache2/' больше не существует.

Just look at its contents after launch Firefox.
In RAM, the cache will be created when Firefox is launched in a new session and, naturally, will disappear when the computer is turned off. In addition, it improves browser performanceь and reduces the number of rewrites of SSD drives..

Re: the right procedure ?

dummy@example.com (fanderal) — Wed, 12 Jun 2024 21:28:42 +0000

devur wrote:

unsure whether I want that type of files on my system.

Like all browsers, Firefox is not 100% secure. Vulnerabilities are found and exploited. Clamav is also for Windows so it finds PUAs. PAUs require an NTFS/NTFS+ filesystem as well as the Win OS to run. They cannot run on Linux filesystems or work with a Linux OS. They're useless and take up HD space.

Suggestion: In Firefox > Settings > Privacy and Security > History, is 'Clear history when Firefox closes' checked? In History > Settings, are all of them checked? If the PUAs still get through, find where they're stored and write a script you can click on on the desktop to delete them.

Another way is an icon on the desktop to start Firefox, with a