wtf is this shit

Some exotic programs that insist on writing to /tmp may fail to run and they should be fixed upstream. Writing to /tmp is bad, and you should not use any software that behaves like this.

Some exotic programs that insist on not requiring superuser privileges and system-wide write acces may fail to run and they should be fixed upstream.  Not having superuser and system-wide write access is bad, and you should not use any software that behaves like this.

Please upgrade your legacy Linux systems to Microsoft Windows

Some exotic distrobutions that insist on disallowing writes to /tmp may cause this program to fail to run and they should be fixed upstream. Writing to /tmp is good, and you should not use any distribution that behaves like this.

Other than for scripts shitting up your hard drives, what is /tmp good for exactly?

http://www.youtube.com/watch?v=FEKhgBye5K0

>>5
I use /tmp all the time, it's a ramdisk

Isn't /tmp the swap portion?

    Fluttershy@Equestria$ mount | grep /tmp
    tmpfs on /tmp type tmpfs (rw)

>2013
>Not using /tmp as ramdisk.

>>9
Why can't you use shared memory instead? And why C/C++ doesn't allow treating a range of memory as a file, readable with fread?

>>10
Are you drunk?
I would rather have a file as a range of memory, readable with array indexing!

>>11
I would rather have had your dubs.

>>9
LLLLLLLLLLLLLLLLLLLLLLLLLEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEELLLLLLLLLLLLLLLLLLLLLL
>E/G/IN 2013 /G/RO
XDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
I LOVE YOUR LE MEMES, PLEASE POST THEM ON LE RE/G/G/IT XDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
LLLLLLLLLLLLLEEEEEEEEEEEEEEEEEEEEELLLLLLLLLL
E/G/IN WIN /G/RO! XDDDDDD

check em

>>13
fuck off

>exotic
i set my download dir to /tmp, and i have /tmp as a ramdisk since i've got a few gigs laying around. now i'll never have the problem of having a cancerous download dir taking up precious ssd niggabytes.

WTF is the point of having a directory for temporary files if you can't write to it?

>>11
I would rather have a Lisp closure.

>>1
Use of /tmp may be a security risk, depending on your app, and what you write to /tmp.

That being said, writing to /tmp is not bad. Is like saying goto is bad.

>>19
Writing to /tmp is as much of a security risk as writing anywhere else on the disk.  If you worry that some other user (wtf, you have more than one human user on your computer?) will check your filenames, just make a directory with 0700 in /tmp and put data there.
NOT using /tmp for temporaries is a bug that has to be fixed upstream, because /tmp is and has been for a long time mounted as ramdisk tmpfs in all distros worth their bytes, and writing shit there saves you the SSD/HDD writes.
Of course I am not talking about storing partially downloaded files in /tmp because that would be really stupid.  Which is the whole point of the full text that >>1 quotes only partially:
http://www.sabayon.org/
/tmp is now mounted on a very small tmpfs with nodev,noexec,nosuid options by default for greater security. Some exotic programs that insist on writing to /tmp may fail to run and they should be fixed upstream. Writing to /tmp is bad, and you should not use any software that behaves like this.
So if your piece of shit exotic program first downloads files to /tmp and then moves them all over again to yet another filesystem it should be fixed upstream, or you should kill yourself.  /tmp is for small temp files, sockets and the like, anything that should not survive rebooting.

%░████▀▀▒▒▒▒▒░░░░▄▄▄▄▒▒▒▀▀███████░░
%░░██▒▒▄▄▒░░░░▒▒▀▒▒▒▒▒▒▒▒▒▒▒▒▀▀██▌░
%░░█▌▄▀▀▒▒▒▒▒▒▒▒▒▄▄▄▄▄▒▒▒▒▒▒▒▌▐▒█▐░
%░░▀▌▒▒▒▄▄▄▒▒▒▒▒▀▄▄█▀▒▒░▒▒▒▒▒▐▒▐▒█░
%░░░▐▒▄▀██▄▀▒▒▒▒▒▒▒░░░░▒▒▒▒▒▒▒▌▌▒█░
%░░░▐▒▒▒▒▒▒▐▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▌▄▀█░
%░░░▐▒▒▒▒▒▒▌▒▒▒▒▀▄░░░▒▒▒▒▒▒▒▒▒▌▐██░
%░░░░▌▒▒▒▒▐▒▒▒▒▄▄▀░░░░▒▒▒▒▒▒▒▒▒▌▒█░
%░░░░▐▒▒▒▒▒▀▀▒▀▒▄▄▄▄░▒▒▒▒▒▒▒▒▒░███░
%░░░░░▌▒▒▒▄█▀▀▀▀▀▀▀▀█▒▒▒▒▒▒▒▒░▀▐██░
%░░░░░▐▒▒▒█▒▀████▀▀▒▐▌▒▒▒▒▒░▄▒▒▐░░░
%░░░░░░▐▒▒▀▒▒▒▒▒▒▒▒▒▒▐▒▒▒▒▄▒▒▒▄▐░░░
%░░░░░░▀▌▒▐▌▐▌▀▌▀▌▀▌▀▌▐▀▀▌▒▐▐▌▌▌▌░░
%░░░░░░░█▒▐▒▐▌▒▌▄▌▐▌▄▒▐▌▄▌▒█▌█▒▒▐░░
%░░░░░░░▐▌▌▒▐▌▒▌▒▒▐▌▒▄▐▌▀▄▒▒▒▒▒▒▒▀▄
%░░░░░░░░▀▒▐▀▀▒▀▒▒▀▀▀▀▒▀▒▀▀▒▒▒▒▒▒▒
%YOU'LL COWARDS DON'T EVEN SMOKE CRACK
%POST lN 3 THREADS OR YOU'LL COWARD

>>20
The real problem here is with the phrasing, combined with the arrogant insistence that all problems that occur can and should be fixed by someone else.

The quoted sentence should read, "Some exotic programs that insist on writing large files to /tmp may fail to run."  Some programs do write huge amounts of data to /var or /tmp because they are the most sensible places to put such data. It's not unreasonable to expect users that make extensive use of such applications to just move /tmp instead of changing the way their programs work (assuming that they even can).