Re: /tmp as tmpfs and consequence for imaging software
On 11/13/2011 07:31 PM, martin f krafft wrote:
> also sprach Lars Wirzenius <firstname.lastname@example.org> [2011.11.13.1204 +0100]:
>> A fixed policy is going to interact badly with real systems and
>> per-site decisions about, say, disk partitioning and provisioining
>> of RAM for various purposes.
>> The proper policy, IMHO, is that a) all software that uses temporary
>> files should obey TMPDIR if set (and fall back on /tmp if not)
>> and b) all software must deal with out-of-disk-space errors in a
>> sensible way (where the exact details may depend on the software).
> Fully agreed.
> Please do not try to (ab)use policy to tell me how I have to
> administer/manage my systems. Use policy to dictate how programs we
> provide as part of The Debian System must behave.
> I would welcome if TMPDIR-related bugs and bugs related to
> temporary file handling would become release-critical.
That was my though too (maybe badly expressed).
Of course, it's ok to use temporary space, and what
we need to enforce is a way to choose WHERE (even
if it was by other means than the TMPDIR, it would
be ok for me...).