Le mardi 27 mars 2012 à 23:48 +0200, Jiri Slaby a écrit :
On 03/27/2012 06:08 PM, Frederic Crozat wrote:
- /tmp is mounted as tmpfs, to make the default setups as stateless as possible. As stated on https://fedoraproject.org/wiki/Features/tmp-on-tmpfs , we might need to fix some applications to use /var/tmp instead of /tmp when they need persistent storage. Another big issue is educating users.
This will break a ton of boxes. * People won't be able to hibernate because their memory will be full of temp undroppable bloat.
Let's see how much bloat we can fix, and if eventually, we find too much we can't fix, we can ship with /tmp non-tmpfs.
* The overall system performance will be *hugely* reduced. Again, because the memory will be full of temp bloat, not having memory for gluttonous firefox.
Let's fix firefox so it uses /var/tmp instead of /tmp.
Yes, I still have a notebook with 2G of memory. I still have a 386 box with 512M of memory. And both are currently on the edge. No, thanks, I really don't want any more swapping.
Did they think about this change thoroughly?
I'm not going to do the messenger back and forth with systemd authors. Feel free to raise those topics with them directly.
(And yes, I have /tmp as tmpfs on my 6G-of-RAM machine.)
BTW stateless /tmp can be achieved by rm -rf /tmp/* at each boot.
Except it implies touching the disk..
--
Frederic Crozat