Jim Lesurf writes:
Richard Kettlewell wrote:

These paths don't identify a particular kind of fileystem; they
identify what kind of files should be put there. In particular, /tmp
(or $TMPDIR) is a location for temporary file.

If the operator wants, or does not want, to use a tmpfs for temporary
files, that's up to them. There's no such thing as a path which is
guaranteed to be a tmpfs; what filesystems are used where is down to
local policy.

That sums up why I decided I couldn't use this method for programs I
release for others to use. Its a shame, though, because it potentially
means the programs are slower and may 'wear' the SSD/HD.

I don’t understand your objection. As far as I can see you’re choosing
to avoid even the possibility of a tmpfs, on the grounds that you might
not actually get it. Which seems like cutting off your users’ noses to
spite their faces.

--
http://www.greenend.org.uk/rjk/