Linux

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:

1. Don't use sudo for anything other than system operations. Not even for editing configuration files.

2. 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.

3. Use sudoedit to edit any system configuration files.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

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

I do not understand?

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 😋

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?

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

No biggie. At least you preserved /. :)

.

I feel like I should try this one day if I reset my distro.