delsafe
delsafe is a set of utilities to hopefully allow you to recover recently deleted files. Basically, when you delete or in certain cases overwrite a file the original file is moved into a trash can. It does this by overriding the original unlink, rename, open, and fopen library calls using the Linux LD_PRELOAD mechanism. Trash cans are placed on top of each mount point and are accessible by each user directly or through links placed in the user's home directory. This makes deletion very fast because, in fact, it is only a renaming. To each filename in the trash can is appended a time/version stamp.
| Operating Systems | POSIX Linux |
|---|---|
| Implementation | Python C |
Recent releases
- 06 May 2009 11:56
Release Notes: pthreads are now used. Some minor bugs were fixed.
- 16 Aug 2008 04:33
Release Notes: This release handles the situation where the trash filename exceeds 255 characters. Some minor bugs have been fixed.
- 20 Apr 2008 00:31
Release Notes: A few major bugs were fixed. Performance was improved.
- 01 Feb 2008 23:30
Release Notes: A small bug that caused "undel foo" to recover "foo-*" files was fixed.
- 03 Jun 2007 18:04
Release Notes: This release is stable, and has minor bugfixes and improvements.
Recent comments
Re: libtrash?
%...
> Both of you have created software with
> similar idea and functionality; his is
> already used with e.g. XFCE. At times,
> doing a better project in a team is way
> better than rolling several
> on-one's-owns.
>
> Of course it's all up to you but in
> science studying what's already done did
> help immensely. :)
Thanks for the suggestion.
I asked because I have been asked for differences between the two applications and to put a comparision table on the homepage.
I don't find very ethical to make such comparisions. People can read the Readme_s or even test and choose what fits better their needs. Here is the brief history of delsafe and why I wrote it.
When I decided to write delsafe, I didn't know of libtrash.
The idea came out to my mind after I lost an important file and not even could remember when. I only knew of libtrash when I discovered a libtrash ebuild in my gentoo tree. I decided to keep on writing because libtrash copies (instead of renaming) when the file is in a different partition of that of the trash can (at least the version I saw then).
This was a great inconvenient for me because I have lots of partitions (currently 9).
I did write it for me. Assuming it could be useful for others, I took some extra time to write a little manual and put it on my site.
That's all.
So, I am not interested in being a member of any team working on this subject and even less in competing with libtrash or any other. Currently delsafe is full working for my purposes. It also does not take me too much time. If I find a better way to prevent my data loss I'll change to it and drop off delsafe. So far delsafe is the best to fit my purposes.
Regards
Re: libtrash?
> I really don't understand why should I
> have any common interest with libtrash's
> author?
Both of you have created software with similar idea and functionality; his is already used with e.g. XFCE. At times, doing a better project in a team is way better than rolling several on-one's-owns.
Of course it's all up to you but in science studying what's already done did help immensely. :)
Re: libtrash?
> -- maybe you'll find some common
> interest with its author
Would you please be more specific on what you mean?
I really don't understand why should I have any common interest with libtrash's author?
libtrash?
pages.stern.nyu.edu/~m... -- maybe you'll find some common interest with its author
psdasilva
26 May 2005 18:18
Heartbeat
- Popularity Score
- 74.83
- Vitality Score
- 6.79
- Subscriptions
- 24
