mv folder delete-this
rm -rf delete-this
gives you one chance to reconsider what you just did before it is too late. And you never have a risk of a dangerous delete-all lurking in your command history.
mv folder delete-this
rm -rf delete-this
gives you one chance to reconsider what you just did before it is too late. And you never have a risk of a dangerous delete-all lurking in your command history.
Why do you need sudo to run your project? Are you developing kernel drivers?
Even then, nothing in the build directory should have unusual permissions. make && sudo make install or whatever.
Looking at your avatar, do you play Freedoom? Deadflare from version 0.12. This post is just a joke, don't take it too seriously.
I don't play Freedoom regularly, I just like the sprite. I ported it to KaiOS though.
No biggie. At least you preserved /. :)
Me who wants to remove a system-wide script:
rm -rf /usr/bin /local/script.sh
Yes, the space was an accident, and yes, this did happen 😋
Haha, I'm dying laughing...
That's why I always delete in file manager, if I made a mistake I can retrieve it from "waste bin", can you make some kind of recycle bin for rm command? Nvm I found this after 5 second of online searching https://github.com/babarot/gomi
This joke has been out of date for over a decade because the --preserve-root flag is enabled by default in most (all?) distributions.
I did sudo apt purge to remove an extra desktop environment. Then i found out that it also deletes dependencies.
Thankfully i was able to save the output of the command and then used python to parse and construct an apt command to reinstall all the things.
I felt both stupid and smart at the same time
Fun fact, did you know that undefined varuables in Makefiles are substituted for ""? So be careful when copypasting some code from your previous Makfefile and make sure to use guardrails like ./$(VAR)
In the end I ran rm -rf, lost half of my $HOME and did not touch my laptop for a few days. Too bad it ran from inside Neovim. Could have noticed sooner.
One time I ran rm on a directory and it started deleting files on the NAS mount I had in that directory and forgot about. So note to self: do not mount things inside project directories
This is apparently a joke! But I have done this in real life. It's an honest mistake you can make if you're experienced, fast, complacent and careless. Always be prepared for it. Here are some tips:
Don't use sudo for anything other than system operations. Not even for editing configuration files.
Never put any development/sysadmin projects under ownership of root. Always develop the project under your personal unprivileged user account. Use sudo only for the final deployment of project to system directories.
Use sudoedit to edit any system configuration files.
Avoid ./* at all times in favor of just *. While this is counterintuitive, this is actually safer. You will have less habitual urge to type the / alone by accident.
Avoid the -f flag in all instances for any command until some operation fails. That will leave you with enough time to reflect on your mistakes when you make one.
Always keep a data recovery plan. Backups are highly recommended. If you use Btrfs partitions, you can make periodic read-only snapshots of your critical data. You can automate this process with a tool like Snapper.
Btrfs snapshots store de-duplicated data. So each snapshot stores only the changes from the previous one. It doesn't use a lot of space, even when backing up large media files. You'll still get the chance to recover your data at the time of the last snapshot.
Most operating system files aren't critical data and don't need to be backed up. Backup the system configuration files in /etc and the package installation list if your package manager facilitates it.
This is optional, but useful in case your Linux installation gets nuked somehow, including this nonsense.
You can always reinstall the distro and start over again. But often times, you can trivially recover the installation by booting from a live USB/CD and doing some manual repair. Learn to chroot into your nuked root partition and operate from inside it.
Most live disks give you an option to repair an installation, in case you deleted the root partition by accident. You can also repopulate the deleted files using commands like debootstrap and pacstrap.
I restored a system once by kubeexec into a running pod after someone did this on the host. It was ... Strange.
I do not understand?
rm -rf /*
This deletes everything in root; a great way to break your OS and lose all data too.
OP meant to run
rm -rf ./*
Note the period, which represents the current directory. So this deletes everything in the current directory instead of the entire filesystem
This deletes everything in root; a great way to break your OS and lose all data too.
Nowadays rm command will prevent doing this, without option --no-preserve-root .
Yes, thats right...
Why not just:
rm -r *
What is the necessity of that sudo, -f and /?
Disclaimer: I have carelessly committed this nonsense too. Thankfully, the important data was backed up. I used a live USB to access the nuked OS partition and used chroot to repopulate the deleted system files. Didn't even have to reinstall the OS.
Always have a disaster plan. If you have a btrfs partition, even periodic btrfs snapshots are a cheap lifesaver. Everything else can be saved like a breeze with some terminal magic.
all 33 comments