Path: utzoo!mnetor!uunet!husc6!m2c!ulowell!eagle!arosen
From: arosen@eagle.ulowell.edu (MFHorn)
Newsgroups: comp.os.vms
Subject: Re: Delete vs. rm
Message-ID: <5683@swan.ulowell.edu>
Date: 24 Mar 88 20:24:13 GMT
References: <36568QAA@PSUVM> <2413@bsu-cs.UUCP> <2903@enea.se>
Sender: news@swan.ulowell.edu
Reply-To: arosen@hawk.ulowell.edu (MFHorn)
Organization: University of Lowell, CS Dept.
Lines: 36

I wrote:
> Which means DCL has to know the syntax of every command on the sytem.

Other people wrote:
about CLD files.

I didn't say you couldn't do it, but it's much easier in unix.  You put
you executable in ~/bin or wherever and say "rehash" and away you go.
As a personal preference, I think CLD files are bogus.

In article <2903@enea.se> sommar@enea.UUCP(Erland Sommarskog) writes:
>  "rm" doesn't know of /LOG, nice to have in command procedures, but also 
>when you are cleaning away lots of blocks, and you want to feel proud 
>on how much you remove. 

I added a -v [verbose] option to rm which does just this.  I can mail
the diffs if anyone likes.  If I happen to get enough requests, I'll
post to a more relevant [unix] newsgroup.

>  "rm" cannot delete files created before a certain date, or that belongs 
>to a certain user. 

It's avoiding the issue, but you can "find . -mtime +3 -exec rm {} \;"
to delete any files in the current directory tree more than three days old.
Flames on the syntax of find to /dev/null [or nla0:]. 

>  "rm" does, as far I know, just unlink the file, there is no /ERASE option 
>with which you can clean the disk space. 

This is a problem, and until someone takes unix security _very_ seriously,
it will probably be ignored.

Andy Rosen           | arosen@hawk.ulowell.edu | "I got this guitar and I
ULowell, Box #3031   | ulowell!arosen          |  learned how to make it
Lowell, Ma 01854     |                         |  talk" -Thunder Road
                   RD in '88 - The way it should be