4 ms·
Flip the question: most storage these days is some kind of solid-state. Why is it better to commit /tmp to a solid-state device (decreasing its operational life
by shadowgovt 2y ago
Flip the question: most storage these days is some kind of solid-state. Why is it better to commit /tmp to a solid-state device (decreasing its operational life) when those files are, by definition, transient and must not be required for future correct program operation?
- pantalaimon 2y agoBecause the alternative is more precious RAM
- MrDrMcCoy 2y agoSo use swap and zswap, then increase the tmpfs size to whatever you want. Systems tend to perform better that way, after all.
- yjftsjthsd-h 2y agoBecause build scripts try to download more files there than fit in RAM.
- shadowgovt 2y agoConfiguring the whole system to account for the needs of software installation is optimizing for the corner case.
- yjftsjthsd-h 2y agoI really don't think installing software is an edge case. On Linux distros, I don't even think compiling software is an edge case.
- shadowgovt 2y agoIt's something the average non-developer does less than once per day, at most. (And the average developer has enough savvy to change settings). ... also, most of the compilation tools I use end up dropping their intermediary files in a peer directory to the source tree or a build directory at the root of the project, not in /tmp. I'm not sure what tools people are using that are leaving compilation intermediates in /tmp.