also sprach Petter Reinholdtsen <[email protected]> [2009.05.26.0737 +0200]: > This is by design. /tmp/ is for temporary data that can and should be > removed every boot, while /var/tmp/ is foor temporary data that should > survive reboots.
Yes, sure, I've read the FHS. But that doesn't help those users of programmes storing files-in-progress in /tmp (mutt, iceweasel to some extent, openoffice, and some others), whose laptop dies or turns itself off when the battery is low. Arguably, those programmes should be fixed, and I am writing a bug report against mutt right now to default to /var/tmp, but is "by design" really enough of an argument to put our users' data at risk until those tools are all fixed? What would be the disadvantages of setting TMPTIME to 1 or 2? -- .''`. martin f. krafft <[email protected]> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems it is better to remain silent and be thought a fool than to open one's mouth and remove all doubt.
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
