lkml.org 
[lkml]   [1996]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Drawbacks of implementing undelete entirely in user space
Date
From
> How about moving the deleted file into a directory .wastebasket/XXXXX,
> where XXXXX is the inode number of the directory the file was in at
> the moment it was deleted. If that directory has the same permissions
> as the original, you do not even need special tools to undelete or
> "empty trash".. a shell script or perl script will do! Also, this works
> recursively and you can restore everything if you undelete in reverse
> order.
>
> Ofcourse the directory structure under .wastbasket stays at max
> 1 level deep. In every directory you can then type "lsrm" and it
> will just do something like

I've not applied this patch (or followed this thread in depth), so
please excuse my ignorance.

How are files kept track of in the '.wastebasket'?
Is there a file the reports the full path name of the file?
Is the removal date/time reported?

These are things that I think would be useful.

--
Andrew E. Mileski
mailto:aem@ott.hookup.net My home page http://www.redhat.com/~aem/
Linux Plug-and-Play Project Leader. See URL http://www.redhat.com/pnp/

Red Hat Software sponsors these pages - I have no other affilitation
with Red Hat Software, and I have never used any of their products.


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.060 / U:3.980 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site