*BANG* OW! MY FOOT! Somebody help me find my foot, and the safety on rm -rf
Does anyone else here know how easy it to say "rm -rf usr" versus "rm -rf /usr"? I sure do!
Curse you transgaming and your silly install mechanism. The *.tgz they distribute is meant to be extracted in the / folder, but I keep forgetting that. So I then go and make a mess out of my /home/common_data/sources/ directory. I go to start removing the pseudo-top level directories. I accidentally add a slash .... *whimper*
So my first question is: does GNU rm come with a safety? Any handy-dandy checks I can have it pull up like "You're trying to delete a top level directory, moron!" or anything of the sort? Anybody have any perl/bash script replacements for rm that do that sort of checking for you? And while we're at it, anybody have any other horror stories to share?
Now, on to the damage portion. It appears that all appropriate top level directories are in /usr:
X11R6, bin, build, doc, etc, include, info, lib, libexec, local, lost+found (cuz /usr is on it's own partition), man, sbin, share, src, ssl, var and windows (where i keep WINE stuff).
As close as I can tell, the only casualty to my Ctrl-C'ed assault on /usr was /usr/local/bin. And it is gone
. Gone gone gone. Gonetyy gonetty gone.
EDIT: I was wrong! I still do have the output I need. Here is what used to live in /usr/local/bin =D( Collapse )
And as I write this, I realize that my one ray of hope just dissapeared. I don't schedule cron to use updatedb, so I'd hoped that my locate command would still have a record of /usr/local/bin. I backed up the full output from locate multiple times. GUESS WHO WAS TOTALLY WRONG? So I have no idea what was in /usr/local/bin. *Groan*
Any advice on how to figure out what of the n-billion utilities that get dumped into /usr/local/bin need to be recompiled would be great. Current Mood: depressed