🚀 go-pugleaf

In article <11781@goofy.megatest.UUCP> djones@megatest.UUCP (Dave Jones) writes:
>Anybody else ever intend to type
>
>   % rm *.o
>
>but failed to release the shift key quite quick enough
>after typing the star?
>
>Result:
>
>  % rm *>o
>
>You've got one new empty file called "o", but plenty of room for it!


Almost...fumbled and got a rm <blah> /* when I meant <blah>.*.  My poor
machine was most unhappy after that.  Seemed to go south at a quick rate;
sort of like pulling the rug out from under its rubber feet.

Recovered it by performing an image backup of a co-worker's 386i and
restoring it onto my system.  Luckily, we have a server from which we 
mount the real important stuff.  I now have great respect of the 'rm'
command.

Dave Regis

In article <11781@goofy.megatest.UUCP> djones@megatest.UUCP (Dave Jones) writes:
>Anybody else ever intend to type
>   % rm *.o
> ...
>Result:
>  % rm *>o
>You've got one new empty file called "o", but plenty of room for it!

Along those lines. I've heard the story of the poor student who
happened to have a file called "-r" in his home directory. As he
wanted to remove all his non directory files (I presume) he typed 
"rm *"... And yes, it does remove *everything* except your beloved
"-r" file... Luckily our back up system was fairly good (hi Dave).

Kees


Kees Goossens                       Keep in Touch with the Dutch:
LFCS, Dept. of Computer Science     JANET: k...@lfcs.ed.ac.uk
University of Edinburgh             UUCP:  ..!mcsun!ukc!lfcs!kgg
Edinburgh EH9 3JZ, UK.              ARPA:  kgg%lfcs...@nsfnet-relay.ac.uk

In article <9...@pldote.intel.com>, dre...@pldote.intel.com (~Dave Regis) writes:
> In article <11781@goofy.megatest.UUCP> djones@megatest.UUCP (Dave Jones) writes:
> >Anybody else ever intend to type
> >   % rm *.o
> >but failed to release the shift key quite quick enough
> >after typing the star?
> >Result:
> >  % rm *>o
> >You've got one new empty file called "o", but plenty of room for it!

> Almost...fumbled and got a rm <blah> /* when I meant <blah>.*.  My poor
> machine was most unhappy after that.  Seemed to go south at a quick rate;
> sort of like pulling the rug out from under its rubber feet.

I too have had a similar disaster using rm.  Once I was removing a file system
from my disk which was something like /usr/foo/bin.  I was in /usr/foo and had
removed several parts of the system by rm ./etc, ./adm, and so on.  But when it
came time to do ./bin, i missed the period.  System didn't like that too much.

Regards,

In article <10880@attcan.UUCP> ram@attcan.UUCP (Richard Meesters) writes:

>I too have had a similar disaster using rm.  Once I was removing a file system
>from my disk which was something like /usr/foo/bin.  I was in /usr/foo and had
>removed several parts of the system by rm ./etc, ./adm, and so on.  But when it
>came time to do ./bin, i missed the period.  System didn't like that too much.


I had a similar experience as well.  Logged in as sysadmin, I was
cleaning up some .login files and some similary named directories and
such in /usr.  I typed 'rm -r .*'.  Well, it seemed like it was taking
an awful long time so I hit control-C to stop it.  It was too late.
It had started deleting all directories and files in '..' which was root.
Had to reload the operating systemafter that.  From then on, I always
alias rm to 'rm -i' so that I can see what it's deleting.

Ray
---


Ray Rankins         |(518) 387-7340 (days)| INTERNET: ran...@zaire.crd.ge.com
2 Moonglow Rd.      |(518) 583-3320 (eves)| COMPUSERVE: 71131,3236
Gansevoort, NY 12831|                     | AmericaOnline: RayRankins
<insert standard disclaimer here>

If you use C-shell it is worth putting the following ALIAS-statement to
.cshrc:

ALIAS rm "rm -i"

It helps a _lot_ .. :-)

--kauto
--
****************** Kauto Huopio (huo...@kannel.lut.fi) **********************
*US Mail: Kauto Huopio, Punkkerikatu 1 A 10, SF-53850 Lappeenranta, Finland * 
*Project: Learn some GNU Emacs first.. :-)                                  *
*****************************************************************************

And then huo...@kannel.lut.fi (Kauto Huopio) babbled...
~If you use C-shell it is worth putting the following ALIAS-statement to
~.cshrc:
~ALIAS rm "rm -i"
~--kauto

	Actually, my .cshrc says:

alias rm '\mv !* ~/.garbage'
alias unrm 'cp ~/.garbage/\!* .'
alias show 'ls -s ~/.garbage'
alias toss '\rm -rf ~/.garbage/* >& /dev/null ; \rm ~/.garbage/.* >& /dev/null'
alias del '\rm'

    Beforehand, just make sure that there is a directory called ".garbage"
    in your home directory.  Or /tmp.  Or wherever you decide to put it.

    aBp.


-- 
Andy Pippin  -*-  api...@polyslo.CalPoly.EDU  -*-  Conserve water, drink beir.

  "Write Only?!?  Must be talking about FORTH.  Nobody can read that."-samlb

In article <25acfa...@polyslo.CalPoly.EDU>, apippin@polyslo (Pinhead@Spikes) writes:
| 
| And then huo...@kannel.lut.fi (Kauto Huopio) babbled...
| ~If you use C-shell it is worth putting the following ALIAS-statement to
| ~.cshrc:
| ~ALIAS rm "rm -i"
| ~--kauto
| 
| 	Actually, my .cshrc says:
| 
| alias rm '\mv !* ~/.garbage'
| alias unrm 'cp ~/.garbage/\!* .'
| alias show 'ls -s ~/.garbage'
| alias toss '\rm -rf ~/.garbage/* >& /dev/null ; \rm ~/.garbage/.* >& /dev/null'
| alias del '\rm'
| 
|     Beforehand, just make sure that there is a directory called ".garbage"
|     in your home directory.  Or /tmp.  Or wherever you decide to put it.
| 
|     aBp.

We interrupt this newsgroup to bring you the following message...

#ifdef SOAPBOX_MODE

Please please please do not encourage people to overload standard
commands with "safe" commands.

(1) people usually put it into their .cshrc in the wrong place, so
that scripts that want to 'rm' a file mysteriously ask for
confirmation, and/or fill up the disk thinking they had *really*
removed the file.

(2) there's no way to protect from all things that can accidentally
remove files, and if you protect one common one, users can *and*
*will* get the assumption that "anything is undoable" (definitely not
true!).

(3) if a user asks a sysadm (my current hat that I'm wearing) to
assist them at their terminal, commands don't operate normally, which
is frustrating as h*ll when you've got this user to help and four
other tasks in your "urgent: needs attention NOW" queue.

If you want an 'rm' that asks you for confirmation, do an

	alias del rm -i

AND DON'T USE RM!  Sheesh.  How tough can that be, people!?!

#endif

We now return you to your regularly scheduled "I've been hacking so
long we had only zeros, not ones and zeros" discussion...

Just another system hacker,
-- 
/== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III  |
| mer...@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn                |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/

api...@polyslo.CalPoly.EDU (Pinhead@Spikes) writes:


>And then huo...@kannel.lut.fi (Kauto Huopio) babbled...
>	Actually, my .cshrc says:

>alias rm '\mv !* ~/.garbage'
>alias unrm 'cp ~/.garbage/\!* .'
>alias show 'ls -s ~/.garbage'
>alias toss '\rm -rf ~/.garbage/* >& /dev/null ; \rm ~/.garbage/.* >& /dev/null'
>alias del '\rm'

Oh how cute! A macintosh trash can for unix (or more appropriately .NeXT/Trash).

I could have used such a scheme the other day. I thought I was
cleaning out tmp after a failed X build when really I had done rm -r *
on /. Luckily the network mounts are first in the directory structure
and it warned me that /Net/sirius was not removed and I was able to
interrupt it before it got to anything it could delete (being on a
heavily laden 3/50 helped too).

Chris

-- 
Chris Whatley
Work: ch...@pelican.ma.utexas.edu (NeXT Mail)		(512/471-7711 ext 123)
Play: ch...@nueces.cactus.org (NeXT Mail)		(512/499-0475)
Also: ch...@emx.utexas.edu

In article <47...@crdgw1.crd.ge.com> ran...@zaire.crd.ge.com (raymond r rankins) writes:
}... I always
}alias rm to 'rm -i' so that I can see what it's deleting.

How tedious.  I aliased rm to invoke a script that creates a directory in
/tmp and moves the "deleted" files to it.  A line in my .logout deletes
the directory and it's contents. (TOPS10/20 users may recognize this
system).  I've also got an "erase" aliased to /bin/rm, but hardly ever use
it.

-- 
The Polymath (aka: Jerry Hollombe, holl...@ttidca.tti.com)  Illegitimis non
Citicorp(+)TTI                                                 Carborundum
3100 Ocean Park Blvd.   (213) 450-9111, x2483
Santa Monica, CA  90405 {csun | philabs | psivax}!ttidca!hollombe

On an old sun workstation (a 100/U which is still running, thank you
very much) I once typed rm -rf / & (God, it hurts just to type that in a
news article!) and realized the error about 10 uSec after hitting the
return key.  Yanking the power plug out of the wall stopped it before it
had a chance to write the updated buffers to disk and it suffered no
loss at all.

I, on the other hand, had a severe laundry problem.
	- Brian

In article <11...@ucsd.Edu> br...@ucsd.edu (Brian Kantor) writes:
}On an old sun workstation (a 100/U which is still running, thank you
}very much) I once typed rm -rf / & (God, it hurts just to type that in a
}news article!) and realized the error about 10 uSec after hitting the
}return key.  Yanking the power plug out of the wall stopped it before it
}had a chance to write the updated buffers to disk and it suffered no
}loss at all.
}
}I, on the other hand, had a severe laundry problem.

I once did the equivalent on a PDP-11/70 (upgraded from 45) running
RSTS/E.  After a particularly long edit session, I slipped and entered a
DEL * (or equivalent -- 'twas long ago).

The only file in my directory was the one and only copy of my (nearly
completed) master's thesis. )-:

After staring at the screen in horror for about 3 seconds I desperately
hit a control-C. (That would stop just about anything under RSTS/E).  To
my amazement, the delete process stopped.  To my relief, I only had to
retype the first 5 pages of my thesis (from hard copy).

Then I went home, lay down and shook for three hours. (-:

-- 
The Polymath (aka: Jerry Hollombe, holl...@ttidca.tti.com)  Illegitimis non
Citicorp(+)TTI                                                 Carborundum
3100 Ocean Park Blvd.   (213) 450-9111, x2483
Santa Monica, CA  90405 {csun | philabs | psivax}!ttidca!hollombe

In article <11...@ucsd.Edu> br...@ucsd.edu (Brian Kantor) writes:
>I once typed rm -rf / & (God, it hurts just to type that in a
>news article!) and realized the error about 10 uSec after hitting the
>return key.  Yanking the power plug out of the wall stopped it before it
>had a chance to write the updated buffers to disk and it suffered no
>loss at all.

I once worked on a bid for a Government contract which involved fault-tolerant
processing.  Everything was handled by redundant hardware (CPUs, memories,
disk controllers and mirrored volumes) and there was, of course, integral
battery backup.  If a board went south, it lit an error LED (Good Scout! :-),
and you simply yanked it out while the system was still running (hey, that's
why there's *two* of everything) and shoved in a new one.  The system said,
"Ooh, a new component.  Better test it ... looks okay, I'll put it online".

It seems that one of our number had been working a few too many hours and
accidentally cleaned out his working directory rather than the old directory.
He immediately told the local system rep (Thanks, Chris!) whose response was:
"Pull *both* CPU cards.  NOW."

Still, I think the thing that saved us was the filesystem organization, which
allowed the "fsdb"-like maintenance program to go in and "undelete" the files.
-- 
cha...@C3.COM	{decuac.dec.com,cucstud}!c3pe!charles	ex::!echo Boo: