Indeed, with the tmpfs move (tmp in RAM) however it sounds like they have more Desktops in mind.
You don't want to use RAM for tmp files for which you probably can't do capacity planning, and you don't to enable swap on server either.
Indeed, with the tmpfs move (tmp in RAM) however it sounds like they have more Desktops in mind.
You don't want to use RAM for tmp files for which you probably can't do capacity planning, and you don't to enable swap on server either.
I honestly don't understand that change, as most desktops are RAM limited as well, especially as Debian is regularly used for older machines, which aren't supported by Windows 11 anymore.
Is it common for scripts to download multiple gigabytes to /tmp?
I sometimes manually changed the /tmp to be in memory, or used /dev/shm which by default is in memory. Did not run into any problems just yet, but then again it's just a home server.
Not sure about scripts, but I download and store everything I know I'll only need until the next reboot in /tmp and naturally that tends to be quite a lot from time to time. That worked fine for decades, so I'm not sure what's the benefit if storing the contents of /tmp in memory instead.
Now you can use /var/tmp I think.