Another reason why - really /tmp

[Chris Torek]

> fsck never misses a lost+found directory, and you probably wouldn't
> care to recover any lost files in /tmp anyway.

Not so!  Not, at least, in 4.2BSD.  In particular, if `fsck' wants
to reconnect a file, but there is no lost+found, it will abort a
`preen' style fsck rather than clearing the inode.  And `ex'---and
thus vi---temporary files are stored in /tmp; but they are still
useful, after a crash, for recovering most if not all of your
editing sessions.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris at umcp-cs		ARPA:	chris at mimsy.umd.edu