←back to thread

A deep dive into Debian 13 /tmp: What's new, and what to do if you don't like it

(lowendbox.com)
150 points shaunpud | 1 comments | 29 Aug 25 02:39 UTC | HN request time: 0s | source
Show context
Incipient ◴[29 Aug 25 05:23 UTC] No.45060518[source]▶
Using the example from the article, extracting an archive. Surely that use case is entity not possible using in-memory? What happens if you're dealing with a not-unreasonable 100gb archive?

Who runs around with 100gb+ of swap?!

replies(2): >>45060583 #>>45061038 #
perlgeek ◴[29 Aug 25 05:34 UTC] No.45060583[source]▶
Who runs around with a 100gb+ /tmp partition?

Our default server images come with a 4.4GB /tmp partition...

replies(1): >>45060779 #
wielebny ◴[29 Aug 25 06:14 UTC] No.45060779[source]▶
I run a script that rotates my /tmp/ each day, so I can access yesterday's tmp files at /tmp/20250828/ and so on.

My /tmp is my default folder for downloads and temporary work. It will grow 100GB+ easily.

replies(5): >>45060892 #>>45060901 #>>45061000 #>>45061761 #>>45062109 #
1. bmacho ◴[29 Aug 25 09:50 UTC] No.45062109{3}[source]▶
And even your use case will benefit from any change, since you'll just move to /tmp2 instead of /tmp, which will actually behave you want it to.

So 99.9% of the users + you benefit from the change. I'm sure there are people that really rely on unconventional usages, but they are silent atm.