You are not logged in.
Pages: 1
I've read in several places that it is recommended to bind-mount /var/tmp to /tmp. I have added this entry on the last line of the /etc/fstab file
<file system> <dir> <type> <options> <dump> <pass>
/tmp /var/tmp /none rw,noexec,nosuid,nodev,bind 0 0I have seperated the /var partition during installation. Is it recommended to bing /var/tmp to /tmp?
Also I have read about mounting /dev/shm with nodev,noexec,nosuid? Why is this needed and how to do it in fstab?
Thank you! ![]()
Last edited by daankata (2017-06-25 19:28:14)
Offline
I've read in several places that it is recommended to bind-mount /var/tmp to /tmp. I have added this entry on the last line of the /etc/fstab file
<file system> <dir> <type> <options> <dump> <pass> /tmp /var/tmp /none rw,noexec,nosuid,nodev,bind 0 0I have seperated the /var partition during installation. Is it recommended to bing /var/tmp to /tmp?
You are asking for responses to information supplied from unspecified sources which gave unspecified reasons.
file-hierarchy covers the expected differences between /tmp and /var/tmp
Also I have read about mounting /dev/shm with nodev,noexec,nosuid? Why is this needed and how to do it in fstab?
Same issue to the why as above. How is covered in fstab. Just to note /dev/shm should be nodev,nosuid by default.
Offline
The only reason you'd want to change /tmp to permanent storage is using an old program that is not aware of the limitations and benefits of tmpfs. Wiping /tmp on every boot is not only a valuable feature, modern software may depend on it.
Offline
He wants to make /var/tmp tmpfs - bad idea.
In addition, wherever one picked up "/none" [sic!] is a terrible source for anything ...
Mounting /dev/shm can remove an attack vector on servers - doing that on a desktop *can* cause you trouble, notably if you lack experience.
It's though not commonly used to store/run executable files.
Online
Pages: 1