Month: May 2014

/tmp is a system section that is rather active. Temporary downloads get directed there. Package manager (system updater) works through it. Building packages, if not specifically directed elsewhere, also works through the same section.

Why mount /tmp to RAM?

If your hardware uses SSD instead of HDD, you may want to reduce disk activity as SSD is sensitive to it and supposedly gets worn out easily. Reduced number of disk writes can be achieved by mounting /tmp to RAM. There are instructions on the net how to do it.

However, systems built around systemd may already direct /tmp to RAM out of the box. I don’t know if all systemd distros do this, but Manjaro does. More specifically, systemd treats /tmp as tmpfs, which means /tmp is directed both to RAM and swap.

Why not mount /tmp to RAM?

Allowing /tmp to operate in RAM is desirable, if the system disk is an SSD instead of HDD. But when you use HDD, which is more likely, and you compile source into packages every once in a while with relatively limited RAM, then it’s more desirable to have /tmp operate on the disk rather than in RAM. When you compile code into packages and RAM runs out of space, you will get an error.

There are plenty of tutorials on the internet to get Thunderbird mailer to display images in emails, even though this is obvious: Press Show Remote Content. This post is about how to never see the warning again.

Seamonkey is a sane mailer. It displays the same kind of warning, but with two options, either to allow remote content or never warn about it again (and never show the content either). Thunderbird, however, has been sanitised towards insanity, so it only displays Show Remote Content button, but doesn’t seem to offer a way to get rid of the ugly button altogether.

Here’s how: Open Preferences –> Advanced –> General and find about:config. There, find the setting mailnews.message_display.disable_remote_image. Set this to false. Done.