Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!navarra
From: navarra@casbah.acns.nwu.edu (John 'tms' Navarra)
Newsgroups: comp.unix.questions
Subject: Re: undelete ?
Message-ID: <1991Apr16.014422.26140@casbah.acns.nwu.edu>
Date: 16 Apr 91 01:44:22 GMT
References: <26542@adm.brl.mil> <1991Apr12.072931.23362@casbah.acns.nwu.edu> <572@racerx.UUCP>
Organization: Northwestern University
Lines: 32

In article <572@racerx.UUCP> ken@racerx.UUCP (Ken Hardy) writes:
>In article <1991Apr12.072931.23362@casbah.acns.nwu.edu>, navarra@casbah.acns.nwu.edu (John 'tms' Navarra) writes:
>> 
>>     NOT TRUE!! There is entomb which I know is available on Purdue computers.
>>       but besides that -- some systems set up a directory which keeps removed
>>  files for a coupla days until they are deleted. Also, if your sysop takes 
>
>
>
>Personally, I use a shell function that moves the files off to a
>temporary directory of my own devising.  Cron cleans it up after me.  If
>my disk gets too full, I browse through it cleaning out things I know I
>don't care for.  I also use that directory for work I know is temporary,
>since it gets cleaned out automatically.  I always have had a problem
>with disks filling up with clutter.  E.g.; interesting sources or notes
>I find on the net go there, since if I don't get around to them within a
>week, I probably won't get to them at all.

     SO DO I!!! This is a good idea for many reasons. All files I remove
 are sent to tmp and are erased by cron sometime in the morning. Similarly,
 I use a program which saves a copy of the file I am currently editing in
 a dir in case I screw up. 

>
>-- 
>Ken Hardy		uunet!racerx!ken		ken@racerx.UUCP


-- 
From the Lab of the MaD ScIenTiST:
      
navarra@casbah.acns.nwu.edu