per the SDB:SSD Performance Doc, I didn’t have to remove the /tmp directory. The doc says:
It is highly recommended to put the most volatile parts of your data on a TMPFS - this especially includes the /tmp directory. This directory only contains temporary files which are deleted upon reboot. Having this in memory is an excellent way to save your SSD some work. Note that if you keep your system running for a long time, the size of this directory (hence its memory usage) can balloon quite a bit. It is recommended to log out of your DE, remove the content, and log in again if you're experiencing memory pressure.
Mount /tmp in a tmpfs filesystem:
# ln -s /usr/share/systemd/tmp.mount /etc/systemd/system/
This will create the /tmp folder in memory on a fresh boot.
Nothing about having to remove the /tmp directory. (Perhaps the behavior has been changed? I see removing /tmp is mentioned in the bug report. )
What I try to ask is ( and my post is a question ) :
During install , the install process create a folder ‘/tmp’
If the install process create a folder ‘/tmp’ in /If after first reboot you want to create a folder ‘/tmp’ using tmpfs
[INDENT=2]If you succeeded then [/INDENT]
[INDENT=3]you got two ‘/tmp’ folders ( But I guess it is not possible )
[INDENT=3]you first destroy the folder ‘/tmp’ in /
you secondly create ‘/tmp’ using tmpfs
[INDENT=2]If during install , the install process has created silently the folder ‘/tmp’ using something like tmpfs by the mean of systemd
[INDENT=3]it should be appreciated to be informed that there is nothing to do.
[INDENT=3]if the way that systemd use to manage the ‘/tmp’ folder authorize a simple command like [/INDENT]
[INDENT=3]it should be appreciated to be informed that there is nothing more to do.