I accidentally untarred archive intended to be extracted in root directory, which among others included some files for /etc directory.
I went on to rm -rv ~/etc, but I quickly typed rm -rv /etc instead, and hit enter, while using a root account.
“Just a little off the top please”
Well at least you got to watch
TIL rm -v is a thing
Your first mistake was attempting to unarchive to / in the first place. Like WTF. Why would this EVER be a sane idea?
that was my reaction when I saw a coworker put random files and directories into / of a server
I feel like some people don’t have a feeling about how a file system works
What’s so bad about that? Except that is trigger me to not have it organized.
hard to properly set permissions and organize
Maybe they do and don’t fear the HFS? I mean do you use the HFS in a docker container?
This is why you should setup daily snapshots of your system volumes.
Btrfs and ZFS exist for a reason.
That or make your system immutable
That’s my current approach. Fedora Atomic, and let someone else break my OS instead of me.
Wish ZFS didn’t constantly cause my proxmox to need to be forcefully restarted after the ZFS pool crashed randomly.
Rest in peace my granny,she got hit by a bazooka
(got no clue why, but really FEELS like an appropirate reaction to have, I salute to you and your pain sir!)
Welcome to the “I have shot myself in the foot with rm” club! Take a seat anywhere!
(Mine was trying to delete the old System 9 “System Folder” by typing rm -rf System\ Folder, but instead hitting the return key when it came time to hit the \, thereby starting a deletion of the running macOS 10 operating system inside the “System” folder. It got through the c’s in the second and a half or so before my frantic control-C attempts halted it. Amazingly, OS X would still boot, but no longer run Carbon apps, necessitating a complete OS reinstall, lol.)
I try to always put the -rf at the end for this reason. Not sure what works on Mac but it does allow it on most Linux shells
You use btrfs, right? Right???
Tried the terminal emulator for the first time today, but I kinda can not get used to the fact, that I cannot move it around :(
Linux will do what you tell it. :)
Reusing names of critical system directories in subdirectories in your home dir.
[OP] accidentally untarred archive intended to be extracted in root directory, which among others included some files for /etc directory.
I agree with this take, don’t wanna blame the victim but there’s a lesson to be learned.
except if you read the accompanying text they already stated the issue by accidentally unpacking an archive to their user directory that was intended for the root directory. that’s how they got an etc dir in their user directory in the first place
I dunno, ~/bin is a fairly common thing in my experience, not that it ends up containing many actual binaries. (The system started it, miss, honest. A quarter of the things in my system’s /bin are text based.)
~/etc is seriously weird though. Never seen that before. On Debians, most of the user copies of things in /etc usually end up under ~/.local/ or at ~/.filenamehere
I use ~/config/* to put directories named the same as system ones. I got used to it in BeOS and brought it to LFS when I finally accepted BeOS wasn’t doing what I needed anymore, kept doing it ever since.
never heard of ~/etc
DId you try CRTL-Z?
HAH rookie, I once forgot the . before the ./
Let he who has not wrongly deleted system critical files in Linux cast the first stone.
I can do one better. A similar ‘rm’ command but while a Windows disk was mounted read/write. So, 2 OSes damaged in one command.
Amateurs. You all did it accidentally. I deleted system critical files intentionally believing it was beneficial.
/dev is just all bloat with stupid recursive directories
Great! Now you can enjoy that freshly assembled directory feeling, knowing that now you only have the configs in there that you need.
