Thread replies: 6
Thread images: 1
Thread images: 1
File: 1441995326040.jpg (171KB, 500x463px) Image search:
[Google]
171KB, 500x463px
HAHAH
Guys I fucked up
I ran "rm /*" on our Debian production server. Now it can't find anything in the usr/bin/ directory.
NOTE that it was not rm -rf /, it was explicitly rm /*. I'm thinking it didn't devastate everything since all the files not in the root directory are there, but for some reason it won't take any of my commands aside from echo and cd. What did it break, exactly? Am I just missing symlinks? If I pop in a Debian CD, can I just reinstall the core files and drive into the sunset?
Halp
>>
>running as root
>running rf command explicitly with root directory
>running as root on production server and this moronic
Yeah not buying it. Nice troll thread though.
>>
As an update, all the files in /usr/bin are still there (I can see them with echo *), so I think it might've nuked a symlink. Any idea what I need to recreate to fix this?
>>
>>55180093
I wish it were a troll. Fat-fingered the ./*. Shit happens. There's nothing super-vital on there anyway, as it's just a failover system and there's backups, but I'd like to un-fuck it without resetting the whole thing.
>>
>>55180035
I bet your rm is aliased for -rf
>>
>>55181098
It's not. Weirdly enough ls is in /bin/, but it won't let me execute it. My $PATH looks fine too.
Thread posts: 6
Thread images: 1
Thread images: 1