El 30/03/12 19:34, Brian K. White escribió:
. Even ~/tmp isn't necessarily safe since /tmp has already been well defined for ages as a single shared space.
Being defined since years do not equal it is good or appropiate now. There are
apps that _rely_ on that fact and use /tmp as a form or inter-process communication, and others where it's not exactly required, just stupid and inefficient to have every user have their own redundant identical copy of some large file(s). And as has been mentioned already, most often, if an app is using a file in /tmp, it's for a reason. In case the implication of that blows by you it means if the app developer wanted to use ram, he'd have used ram. If he wanted to use per-user file space he'd have used ~/tmp. Sometimes /tmp is used either unnecessarily or even wrongly, but it's not for YOU to unilaterally accuse ALL software of that, and change the definition of /tmp right out from under 30 years of unix software.
Wow, really ? is that the best you have? a fallacious appeal to tradition ? Unfortunately your opinion does not change the facts that we have to fix tons of bugs, in a weekly manner where software screws up this very fragile misfeature.
Suse isn't a wristwatch or a router or a game console where the totality of the installed software and it's usage and behavior are all finite and addressable. Everything you personally haven't seen isn't "corner cases that don't matter".
It's the other way around. Your singular lack of experiencing a wide variety of situations is the corner case that doesn't matter.
Well, let see who's proposal succeeds and gets implemented. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org