ok, so i was cleaning up my old hd that was mounted
on /opt, and i stupidly typed:
rm -r /usr/share;
when i meant rm -r /opt/usr/share;
well, i stopped it after only a few moments had passed.
my question is about the nature of rm, how does it
do its dirty work? i assume it removes files alphabetically;
so to minimize the damage i would reinstall whatever package
is the highest alphabetically and still there and then try
to determine what else would be before it.
i was fine with this last night, but now i am getting some
emacs errors that its missing some extensions.
i am wondering if the rm started working on all the dirs
at the same time...this would make my situation much worse.
still though, it's just share/ so it's not all that
important, but i'd appreciate anyones' guesses about
rm.
--
tom carlile [EMAIL PROTECTED]
professional systems wrangler
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
