←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: 0.207s | source
Show context
gigatexal ◴[29 Aug 25 05:31 UTC] No.45060561[source]▶
Why this change? Writing to it will be faster than disk but idk if am is a precious commodity I’d rather it was just a part of the disk I was writing to.
replies(1): >>45061111 #
rwmj ◴[29 Aug 25 07:09 UTC] No.45061111[source]▶
It's a dumb idea that came from the systemd people. They've never explained properly why it's a good idea, but it's the systemd default and for some reason distros defer to that.
replies(1): >>45062068 #
egorfine ◴[29 Aug 25 09:43 UTC] No.45062068[source]▶
Not at all. tmpfs precedes systemd for like a decade.
replies(1): >>45062111 #
rwmj ◴[29 Aug 25 09:50 UTC] No.45062111[source]▶
It only became the default on Fedora and other Linux distros following systemd because it was the default in systemd.

It was a bad idea on Solaris too, but at least back in those days the trade-off between RAM and disk storage was very different from today now we have NVME drives and such.

replies(1): >>45062225 #
egorfine ◴[29 Aug 25 10:07 UTC] No.45062225[source]▶
Oh no, tmpfs was introduced and used way before systemd.
replies(2): >>45062260 #>>45062794 #
1. blueflow ◴[29 Aug 25 11:46 UTC] No.45062794[source]▶
Which was contested by no-one. He complained about systemd switching /tmp to tmpfs, not systemd people making or causing tmpfs in general.