Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!jik
From: jik@athena.mit.edu (Jonathan I. Kamens)
Newsgroups: comp.unix.questions
Subject: Re: files recovery after rm?
Message-ID: <15786@bloom-beacon.MIT.EDU>
Date: 10 Nov 89 02:46:54 GMT
References: <16608@uhnix1.uh.edu> <20530@unix.cis.pitt.edu> <1989Nov9.162314.4713@virtech.uucp> <20551@unix.cis.pitt.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: jik@athena.mit.edu (Jonathan I. Kamens)
Organization: Massachusetts Institute of Technology
Lines: 16

In article <20551@unix.cis.pitt.edu> yahoo@unix.cis.pitt.edu (Kenneth L Moore)
writes:
>Nope. You just aren't allowed to rm. So then you unalias rm and 
>really remove the file. Then source .tshrc and start over. Or use
>"rm" to defeat the aliasing.

  Either "\rm filename" or "/bin/rm filename" will delete a file using
the real rm, even when rm is aliased to something.  Unalias'ing rm,
then removing the file using "rm filename", then sourcing .tshrc (I
thought it was .tcshrc?) all over again is killing a fly with a
sledge-hammer.

Jonathan Kamens			              USnail:
MIT Project Athena				11 Ashford Terrace
jik@Athena.MIT.EDU				Allston, MA  02134
Office: 617-253-8495			      Home: 617-782-0710