[lkml]   [1996]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: , Drawbacks of implementing undelete entirely in user space
On Sat, 22 Jun 1996, Rich Tollerton wrote:
> Not even that - a crontab entry containing a shell/perl script that would
> remove files from .wastebasket after a 'days since modified'/number of
> files in .wastebasket/size of .wastebasket would be simple to program and
> very small (I'd think under 5k). Then rename rm to something else that
> script (and people who really really want to delete their files) can
> call, and make a new rm that moves the file to the .wastebasket and
> writes its path in a data file. Total modification size, including both rms
> and man pages would be under 50k.
> Lost anybody there? :)

No, but what happens when the free space on the disk reaches 0 because of
the saved files. If you don't put some of it in the kernel, you can't
use the ext2 u bit to determin which files should be saved on unlinking,
and you can't recycle the space for new files.

PGP key pass phrase forgotten, \ Overload -- core meltdown sequence
again :( | initiated.
/ This space is intentionally left
| blank, apart from this text ;-)

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