| |||||||||||||
Secure deletion and trash bin supportSecure deletion and trash bin supportPosted Dec 7, 2006 21:17 UTC (Thu) by jzbiciak (✭ supporter ✭, #5246)In reply to: Secure deletion and trash bin support by oak Parent article: Secure deletion and trash bin support
I'm saying that I might simply not want a .trash directory in a particular filesystem *ever*. For instance if I have an FS that I use for large temporary files, I don't think it should get a .trash, ever.
(Log in to post comments)
trash bin Posted Dec 8, 2006 19:23 UTC (Fri) by giraffedata (subscriber, #1954) [Link] Presence of a .trash directory (a filesystem option) and a mount option are two different things, both valuable. In reality, I think users wouldn't be satisfied with undeletion without an entire storage management policy capability. The decision whether to delete a file as soon as the last normal reference disappears or keep it around in the trash needs to be based on what directory, filesystem, and mount the file was in as well as its name, and various attributes such as owner, size, and modification time. But to make something mildly useful to some people, just a filesystem option (probably simply the existence of the .trash directory in its root) would be reasonable. I don't even think the per-file attribute would be useful in a system that simple -- I don't know how the designers of the system in question envision that getting set.
|
|||||||||||||