Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!decwrl!pyramid!tolerant!waynet
From: waynet@tolerant.UUCP (Wayne Thompson)
Newsgroups: comp.sources.wanted
Subject: Re: rm replacement; keep me from cloberring myself
Message-ID: <510@tolerant.UUCP>
Date: Thu, 20-Aug-87 14:47:25 EDT
Article-I.D.: tolerant.510
Posted: Thu Aug 20 14:47:25 1987
Date-Received: Sat, 22-Aug-87 12:09:17 EDT
Organization: Tolerant Systems Inc., San Jose California
Lines: 25
Keywords: rm unrm rmsecure

I've got couple that I've picked up from the net that I can supply on
request.

rm/unrm - this pair of routines replaces rm so that when you do an rm
          the file(s) is actually mv'ed to /tmp/$user/. The full pathname
          is not remembered, only the tail. As such, if you rm to files
          with the same name the second will overwrite the first. Since
          directories in /tmp are not removed by the os, they will pile
          up until you /bin/rm them, and fill up the /tmp filesystem.
          unrm will mv them into the current directory regardless of their
          directory of origin.

rmsecure - is a script (slow) which will do filename expansion and, if any
           wildcards are used, echo the expanded fileset and ask you if
           your sure. This gives you a chance to preview your rm fileset.

--
Which is worse, ignorance or apathy? Who knows, who cares.

Wayne Thompson
..{bene,mordor,nsc,oliveb,pyramid,ucbvax}!tolerant!waynet

Your mission, should you decide to accept it, is to discern who is
responsible for these opinions, the poster or the company he works for.
Good luck!!