Making /tmp a ram based tmpfs has been semi-regular behaviour for a long time. Indeed, on Solaris it's always tmpfs.
Note, though "# ln -s /tmp /var/tmp " is BAD; /tmp and /var/tmp should be different. You could make /var/tmp a tmpfs filesystem if you really wanted.
Note: I recommend rebooted after making these types of changes /tmp and /var/tmp to ensure the machine comes up cleanly afterwards. That page tries to work around needing a reboot; I don't recommend that, at all!
The main thing to be careful of, making those directories "noexec" is if you have any procedures that create temporary scripts; they will break.
In summary, I'd never recommend that page to anyone who doesn't know what they're doing, and why. The concepts are good, the implementation is questionable, the consequences may not be as expected.
I have run into problems with /tmp running out of space on desktops even with a 1 GB tmpfs file system.
I know this is an old thread, but as I'm spinning up a new Centos 8 VPS to migrate my stuff to I've had to harden my /tmp the same way I did on my other Centos 7 VPS
This method worked well :
The only charge I made was to make it a 1G file and then the fstab mount needs to include 'loop' like this :
/root/images/tmpfile.bin /tmp ext4 loop,rw,noexec,nosuid,nodev 0 0