Le mercredi 28 mars 2012 à 11:10 +0100, Ruediger Meier a écrit :
On Wednesday 28 March 2012, Frederic Crozat wrote:
Le mercredi 28 mars 2012 à 10:30 +0100, Adam Spiers a écrit :
Cristian Rodríguez (crrodriguez@opensuse.org) wrote:
El 27/03/12 20:54, Carlos E. R. escribió:
On 2012-03-28 01:27, Cristian Rodríguez wrote:
El 27/03/12 20:24, Carlos E. R. escribió: >Oh, how very nice of you, disregarding he fate of your users. > :-(
I am not disregarding it, such programs need to use /var/tmp instead.
Ok, so you go out and reprogram all the Linux list of programs out there. When they fail, you go and mend them. All of them.
That's unreasonable, we can only fix programs included in the opensuse distribution.
So any program outside the openSUSE distribution which puts huge files in /tmp become unusable, and most users of those programs are then forced to use another Linux distro.
Well, Fedora will do a similar switch, so in the future (no idea when, though), programs will be fixed to use /var/tmp when they rely on persistent / huge storage for their own data.
/var/tmp is persistent over reboot which is a different use case. Users or programs writing to /tmp are doing this for a good reason until you proof for any particular case that they are doing wrong.
And as I wrote in my initial mail, this behavior can be disabled.
Why can't it be enabled keeping the current behaviour per default?
Because I wanted feedback, based on facts (and not just reaction to changes, like some people seem to do). So far, we have some feedback, but as Takashi noted, we don't have test results to see if it is really a problem or not.
Currently, we have no data on programs behaviour regarding /tmp, so it is difficult to guess.
Please consider also the user behaviour.
I think it is easier to educate users than patch closed-source programs ;) -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org