New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use /var/tmp not /tmp #2
Comments
Since /tmp is a general purpose temporary folder, mounting tmpfs over it is a problem of the particular distro. I think the best will be probably to make that target directory configurable in .config, but at the moment I fail to see any reason why I should fix a problem introduced by someone else (systemd), sorry for that. |
BTW the phrase "mail me" at linux-live.org is actually a link to contact form :) |
found the link: http://fedoraproject.org/wiki/Features/tmp-on-tmpfs#Scope you may want to reconsider it based how wide tmpfs on /tmp is going to be considering major distros fedora and unbuntu follow and accept it :( |
I've added a warning to README. Overmounting /tmp by tmpfs is a crazy idea which I am not willing to take into consideration :) |
i looked, my normal operations use only few files there, so i'm taking that risk to save my SSD disk life with tmpfs mount on /tmp :)
|
hi
in case of systems where /tmp is on tmpfs, especially systemd installs (afaik it's systemd default to have /tmp on tmpfs), building slax would take out ram which it would need for xz instead.
you should use /var/tmp for such puporses, i.e /var/tmp is supposed to be temp dir not on ramfs. there was some blog or documentation too about this topic (i don't even know what to search to reach it :)), but it stated that most cd burning tools have already been changed to use /var/tmp for their temporary isos
also, interestingly, www.linux-live.org suggests to mail you, but i can't find mail address anywhere :D
The text was updated successfully, but these errors were encountered: